Identify the loader failure
| Evidence | Interpretation |
|---|---|
| Module not found before UI | Static import or dependency of an imported DLL. |
| Entry point not found | File exists, but required export/version differs. |
| Bad image or architecture error | 32/64-bit or damaged binary mismatch. |
| Failure only in one workflow | Delayed loading, plug-in, database client or vendor SDK. |
Diagnostic sequence
- Preserve the known release and record hashes/versions.
- Inspect PE imports and architecture of the executable and candidate DLLs.
- Capture failed module searches and the actual file loaded.
- Check application directory, system paths, working directory and vendor configuration.
- Trace each dependency recursively; do not stop at the first filename.
Copying a DLL into a system directory can mask the search-path problem and affect unrelated applications.
Keep the boundary clear
COM identity problems belong in COM troubleshooting; registration command failures belong in registration diagnosis. Use the broader Windows dependency workflow for native/runtime loading, and startup diagnosis when no DLL is identified.
Provide the exact error, complete application directory, installer, working-machine file inventory and Windows architecture.