Find the attempted filename
| At startup | Configuration, runtime-loaded library, report/template or database file. |
|---|---|
| One workflow only | Export/import file, plug-in, help file or explicit DLL load. |
| Works from one shortcut | Working-directory or relative-path assumption. |
| DLL exists | A transitive dependency or wrong search path may be the missing file. |
Evidence-led diagnosis
- Trace failed file opens and record the full attempted paths.
- Compare working directory, PATH, configuration and application layout.
- Verify deployment release completeness and architecture.
- Correct path construction or installer content rather than copying files globally.
A missing directory produces error 76; native dependency resolution belongs in DLL analysis. Use startup diagnosis for broader failures and the pillar.
Provide error timing, launch method, trace, directory tree and known-good deployment.