Resolve the dependency type
| Type | Evidence |
|---|---|
| Static import | Visible in the PE import table; failure may prevent startup. |
| Delayed/runtime load | Appears only in a workflow, configuration or trace. |
| Vendor wrapper | First DLL exists but depends on another runtime/driver. |
| Architecture mismatch | 32-bit Delphi process cannot load a 64-bit library. |
Evidence-led repair
- Preserve the release and collect module versions.
- Inspect PE imports/exports and architecture.
- Trace actual lookup paths and failed opens.
- Confirm calling convention and expected exported names when source exists.
- Package the verified dependency beside the application or through its vendor-supported installer.
Avoid package confusion
BPL files are Delphi packages and require the BPL-specific workflow. For broad startup symptoms use startup diagnosis; use Windows dependency analysis for side-by-side/runtime/COM evidence and Delphi reverse engineering when source is incomplete.
Provide the exact loader error, EXE/DLL files, architecture, workflow triggering the load and known-good file inventory.