Menu
I use Dependency Walker to open wintrust.dll on my Windows 10 and it takes around 40 seconds! When it is opened, I see very strange picture of recurring calls between KERNEL32.DLL and API-MS-WIN-CORE-PROCESSTHREADS-L1-1-1.DLL:
I suppose this is the source of the problem. When I try to open my own dll, that includes wintrust.dll on separate paths, it might take up to 10 minutes (!) to open.
Why is this happening?
407
Dependency Walker (Depends), which can be launched via Process Explorer, no longer works well in Windows 10 as of at least build 10.0. 19043 (21H1 May 2021 update). The UI can hang for several minutes while (e.g.) enumerating Notepad's dependencies. It may be time to have Process Explorer link to an alternative.
Start the program by running the Dependency Walker executable. Navigate to File > Open and select the DLL that is failing to register when using regsvr32. Dependency Walker will show what dependencies are missing and causing the error when registering.
When a program uses a DLL, an issue that is called dependency may cause the program not to run. When a program uses a DLL, a dependency is created. If another program overwrites and breaks this dependency, the original program may not successfully run.
Don't use dependency walker. Here's one good alternative I'm aware of: Dependencies by Lucasg. Unlike dependency walker - it is aware of ApiSets and thus will not recurse indefinitely.
165
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
