Missing Dll in dependency walker

c++ dll dependency-walker
user3811406 picture user3811406 · Jul 16, 2014 · Viewed 24.9k times · Source

I am having a dll and which I am opening into the dependency walker with platform visual studio 2003 and OS is 2000. and my that dll find all dependency.

But when I am going to open that dll in to tha another system which is having OS- windows7 and visual studio 2010, I found missing dlls errors.

GDIPLUS.DLL,
GPSVC.DLL,
IESHIMS.DLL.

above listed 3 dll were missing. when I have downloded those dlls and put them into the same location where my dll is residing, I am finding below listed missing dlls list. 

API-MS-WIN-CORE-COM-L1-1-1.DLL,
API-MS-WIN-CORE-DEBUG-L1-1-1.DLL,
API-MS-WIN-CORE-DELAYLOAD-L1-1-1.DLL,
API-MS-WIN-CORE-ERRORHANDLING-L1-1-1.DLL,
API-MS-WIN-CORE-FILE-L1-2-1.DLL,
API-MS-WIN-CORE-FILE-L2-1-1.DLL,
API-MS-WIN-CORE-HEAP-L1-2-0.DLL,
API-MS-WIN-CORE-HEAP-OBSOLETE-L1-1-0.DLL,
API-MS-WIN-CORE-JOB-L2-1-0.DLL,
API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-1.DLL,
API-MS-WIN-CORE-LIBRARYLOADER-L1-2-0.DLL,
API-MS-WIN-CORE-LOCALIZATION-L1-2-1.DLL,
API-MS-WIN-CORE-LOCALIZATION-OBSOLETE-L1-2-0.DLL,
API-MS-WIN-CORE-MEMORY-L1-1-2.DLL,
API-MS-WIN-CORE-PRIVATEPROFILE-L1-1-1.DLL,
API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-2-0.DLL,
API-MS-WIN-CORE-PROCESSTHREADS-L1-1-2.DLL,
API-MS-WIN-CORE-REGISTRY-L1-1-0.DLL,
API-MS-WIN-CORE-REGISTRY-PRIVATE-L1-1-0.DLL,
API-MS-WIN-CORE-STRING-OBSOLETE-L1-1-0.DLL,
API-MS-WIN-CORE-SYNCH-L1-2-0.DLL,
API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL,
API-MS-WIN-CORE-THREADPOOL-L1-2-0.DLL,
API-MS-WIN-CORE-THREADPOOL-LEGACY-L1-1-0.DLL,
API-MS-WIN-CORE-THREADPOOL-PRIVATE-L1-1-0.DLL,
API-MS-WIN-CORE-TIMEZONE-L1-1-0.DLL,
API-MS-WIN-DOWNLEVEL-ADVAPI32-L1-1-0.DLL,
API-MS-WIN-DOWNLEVEL-OLE32-L1-1-0.DLL,
API-MS-WIN-DOWNLEVEL-SHLWAPI-L1-1-0.DLL,
API-MS-WIN-EVENTING-PROVIDER-L1-1-0.DLL,
API-MS-WIN-SECURITY-ACTIVEDIRECTORYCLIENT-L1-1-0.DLL,
API-MS-WIN-SECURITY-BASE-L1-2-0.DLL,
API-MS-WIN-SECURITY-GROUPPOLICY-L1-1-0.DLL,
API-MS-WIN-SECURITY-LSALOOKUP-L1-1-1.DLL,
API-MS-WIN-SECURITY-LSALOOKUP-L2-1-1.DLL,
API-MS-WIN-SECURITY-PROVIDER-L1-1-0.DLL,
API-MS-WIN-SERVICE-CORE-L1-1-1.DLL,
API-MS-WIN-SERVICE-WINSVC-L1-2-0.DLL,
SYSNTFY.DLL.

It is may be because of configuration issue, please help me out to resolve this issue.

Answer

Ofek Shilon picture Ofek Shilon · Apr 5, 2016

All the API-MS-WIN-XXX 'missing' dll's are really API-sets (sometimes referred to as 'virtual DLLs'). Dependency walker just wasn't updated since before their inception. Here are some details.

Related questions

REGSVR32: the module "xxxxx.dll" failed to load ... dependent assembly could not be found

I'm having an issue with regards to registering a *.dll under Windows 7 x64. I've tried placing the *.dll in both, C:/Windows/System32 and C:/Windows/SysWOW64 and attempting to register with "regsvr32 xxxxx.dll" under an elevated command prompt. …

Read More
Reading Dependency walker output

I am having some problems using one of the Dlls in my application and I ran dependency walker on it. i am not sure how to read it but I got following results Does it suggest any x86-x64 incompatibilty? …

Read More
Unable to load DLL (Module could not be found HRESULT: 0x8007007E)

I have dll library with unmanaged C++ API code I need to use in my .NET 4.0 application. But every method i try to load my dll i get an error: Unable to load DLL 'MyOwn.dll': The specified module could …

Read More