DepCheck shows why a Windows module (exe, dll, ocx) will not load. Drop a file on it and it resolves the imports the way the loader does.

Example result after DepCheck scanning itself.

What it resolves

The real search order, not a directory scan:

• KnownDLLs, from the system directory first.
• apiset contracts (api-ms-*, ext-ms-*), through the apiset map.
• SxS / manifest redirection: a Common-Controls 6.0 manifest gives the WinSxS comctl32.dll, not 5.82 from System32.
• The search path of the analyzed binary's architecture: a 64-bit build reports SysWOW64 dependencies for a 32-bit target, and the other way around.
• Dependencies of the wrong bitness, reported instead of passed.
• Per file: SHA-256, and whether it carries a Zone.Identifier.

Download v0.4.0

One executable, nothing to install, Windows XP and later. Either build analyzes 32-bit and 64-bit binaries; pick the one matching your Windows.
Authenticode signed – check the signature before running.
SHA256SUMS.txt · All releases and release notes

Usage

Drop a file on the window or on the icon. From a console it writes the tree to stdout:

DepCheck.exe some.dll
DepCheck.exe /depth:2 some.dll

/depth:N limits the walk depth (0, the default, is unlimited). Exit code:

Free to use. Bugs and requests: open an issue on GitHub, or mail mark[NO SPAM].[NO SPAM]jansen[NO SPAM]@[NO SPAM]reactos.org