Home/ Questions/Q 8504725
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T02:06:58+00:00

I am using Dependency Walker to try and resolve a .dll error. I have

  • 0

I am using Dependency Walker to try and resolve a .dll error. I have a main project that includes many libraries. Dependency Walker shows an error on 4 .dlls:

Error opening file. The system cannot find the file specified (2).

Which is funny because the output of Visual Studio’s linker clearly shows that the libraries have been found. Everything in the .exe is linked properly (all symbols are resolved). When I start the application I get a Windows error:

The program has stopped working.

I’m using the same API that was discussed in this question: Win32 DLL importing issues (DllMain). If I build in debug mode I get the error that is quoted about memory initialization.

Are the .dlls being included or is the problem that Dependency Walker can’t see the .dlls? Is this because the relevant libraries are import libraries?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The .dlls were being included. Dependency Walker just didn’t know where to find the files. Adding the library directories to the system PATH variable allowed Dependency Walker to find the libraries.

    • 0