Diagnosing Application Load Failures with Dependency Walker

Step-by-step Dependency Walker tutorial for developers

Overview

Dependency Walker (depends.exe) inspects a Windows executable or DLL to list dependent modules and exported/imported functions. Use it to find missing DLLs, circular dependencies, and load-time problems.

Prerequisites

• Windows PC.
• Download Dependency Walker (legacy tool) or use it from an existing install.
• The target EXE/DLL you want to analyze.

1. Open the target file

1. Launch Dependency Walker.
2. File → Open and select the EXE or DLL.
3. Wait while it builds the dependency tree and resolves modules.

2. Read the main panes

• Module Tree (left): hierarchical list of modules the target depends on.
• Module List (top-right): flat list with full paths, file versions, and timestamps.
• Function List (bottom-right): imported and exported functions (names and ordinals).
• CPU/time/message bar: shows profiling and error messages.

3. Identify missing or failed modules

• Look for modules marked with a red icon or “Error opening file” messages.
• Check the full path in the Module List to see which file was loaded (or attempted).
• If a system DLL is missing, verify Windows version/architecture (x86 vs x64).

4. Check architecture mismatches

• Confirm the target and listed modules’ architectures (x86 vs x64) in the Module List.
• Common problem: 32-bit process attempting to load 64-bit DLL or vice versa.

5. Inspect imported/exported functions

• Select a module to view its imported functions (shows which DLLs provide which symbols).
• Missing imports are indicated and can cause load failures—note the function name and ordinal.

6. Resolve dependency issues

• For missing DLLs: obtain the correct binary (matching architecture and OS), install runtimes (VC++ redistributable), or adjust PATH.
• For unresolved imports: rebuild the module with correct exports, or use alternative libraries that provide needed symbols.
• For delay-load or runtime-loading issues: consider using Process Monitor or enabling loader logging to see runtime behavior.

7. Use profiling/run-time tracing (if available)

• Dependency Walker can perform a profile run to simulate program load and record module loads and errors; run profiling on the target executable to capture runtime load sequence.
• For modern apps using side-by-side assemblies or API sets, Dependency Walker may show misleading errors—combine with Process Monitor or the Application Event Log.

8. Verify fixes

• Re-run Dependency Walker after applying fixes to confirm missing modules/imports are resolved and no new errors appear.
• Optionally run the actual application and monitor with Process Monitor or Procmon to confirm runtime behavior.

Tips & limitations

• Dependency Walker is legacy and may produce false positives for modern Windows features (API sets, side-by-side assemblies, Windows Store apps).
• For contemporary diagnostics consider modern tools (Process Explorer, Procmon, dumpbin, Visual Studio’s Module window, or pefile scripts) alongside Dependency Walker.

Quick checklist

• Confirm file architecture matches dependencies.
• Locate any red/errored modules and note their paths.
• Check for missing imports/ordinals.
• Install required redistributables or correct binaries.
• Re-run and validate with runtime monitoring.

If you want, I can: provide a short command-line alternative using dumpbin, or generate a step-by-step checklist tailored to a 32-bit vs 64-bit troubleshooting scenario.