Diagnose the package chain
- Record the exact missing package and application build.
- Inspect executable/package imports and recursively map required BPLs.
- Identify Delphi compiler generation, runtime-package configuration and third-party component version.
- Check application directory and controlled search locations before system directories.
- Compare package hashes/versions with a known deployment.
Failure patterns
| Package absent | Deployment set incomplete. |
|---|---|
| Procedure entry point missing | Package found but built against an incompatible unit/interface. |
| Another BPL/DLL reported | Transitive dependency is missing. |
| Only plug-in/report fails | Package is loaded at runtime rather than startup. |
Copying random BPL files can create a mixed runtime that loads partially and fails later in less obvious ways.
Next path
Normal native libraries belong in DLL diagnosis. Use startup analysis when no package is named and source analysis to recover the runtime-package build configuration. See the Delphi pillar for support choices.
Provide the EXE, complete deployed directory, missing-package error, Delphi version if known and a working installation or installer.