CODEWITHSUNDEEP
windowsdllvisual-studio-2013dependenciesdependency-walker
Ben N.
Ben N.

Reputation: 1345

Dependency Walker: missing dlls

I have been trying to resolve .dll dependencies for the executable file with Dependency Walker. Currently, I am getting missing .dlls in the following form:

API-MS-WIN-XXX

EXT-MS-WIN-XXX

For example:

API-MS-WIN-APPMODEL-IDENTITY-L1-2-0.DLL
API-MS-WIN-APPMODEL-RUNTIME-INTERNAL-L1-1-0.DLL
API-MS-WIN-BASE-UTIL-L1-1-0.DLL
API-MS-WIN-CORE-APIQUERY-L1-1-0.DLL
EXT-MS-WIN-RTCORE-NTUSER-SYSCOLORS-L1-1-0.DLL

Does anybody have any ideas on how to resolve these? Any help will be greatly appreciated!

Additional info: I compiled the executable using Visual Studio 2013. The most interesting thing is that I did not receive any errors during compilation. However, I cannot run it due to missing dependencies. I also attached a screenshot of dependency walker:

dependency walker

Update 1: As an attempt to solve the problem I tried to add the path for the libraries that VS used during compilation to the $PATH environment variable without any luck (Dependency Walker still shows unresolved dependencies).

Upvotes: 120

Views: 113909

Answers (5)

Alexis Landin
Alexis Landin

Reputation: 11

Another adition to @Ofek Shilon comment (i cant comment there for lack of reputation).

When using LucasG tool and maybe any other tool, is that dll search is case sensitive. So if you have a "xyz.dll" and the program says you need a "XYZ.dll", you can simply rename it (or better, make a new copy of it and rename).

Upvotes: 0

kuzavas
kuzavas

Reputation: 2216

Dependencies program helped me find a missing DLL in no time. It is open source and available here: https://github.com/lucasg/Dependencies

Upvotes: 10

Ofek Shilon
Ofek Shilon

Reputation: 16147

These are API-sets - essentially, an extra level of call indirection introduced gradually since windows 7. Dependency walker development seemingly halted long before that, and it can't handle API sets properly.

So these are all false alarms and nothing to worry about. You're not missing anything.

Also see On API-MS-WIN-XXXXX.DLL, and Other Dependency Walker Glitches.

Edit: Only in Oct 2017 did someone finally try to fill this gap. Meet Dependencies by lucasg. I've only briefly fiddled with it until now, but it handles API sets well and is at least very worthy of attention.

Upvotes: 143

botheredbybees
botheredbybees

Reputation: 592

I also ignore:

  • EFSCORE.DLL
  • WPAXHOLDER.DLL

Upvotes: 4

Tae-Sung Shin
Tae-Sung Shin

Reputation: 20620

In addition to what @Ofek Shilon said, I usually ignore following dlls that dependency_walker identified as missing when I try to find missing dlls for my program. You will see that your program runs fine when dependency_walker says these dlls are missing.

  • API-MS-WIN-*.dll
  • EXT-MS-WIN-*.dll
  • IESHIMS.dll
  • EMCLIENT.dll
  • DEVICELOCKHELPERS.dll

You can search for dlls other than the ones above to resolve your problem.

Upvotes: 31

Related Questions