| Previous | Next |
| STATUS_INVALID_SECURITY_DESCR | STATUS_INVALID_IMAGE_FORMAT |
STATUS_PROCEDURE_NOT_FOUND
The DLL can exist and load successfully while a required export is still missing
STATUS_PROCEDURE_NOT_FOUND points to symbol resolution rather than module search. A DLL may be present at the expected path and map successfully, but the requested exported function name is absent from its export table. GetProcAddress requires name spelling and case to match the exported name exactly.
The most common engineering causes are a version mismatch between caller and DLL, deployment of the wrong architecture or product build, a renamed/removed export, or name decoration and export-definition changes. For implicit imports, inspect the importing image and its import table. For explicit loading, preserve the exact string passed to GetProcAddress.
Do not copy a random same-named DLL from another system or add an unrelated directory to PATH. That can make the loader select a binary with different ABI expectations. Compare the dependency package as a unit, verify the resolved module path and file version, then inspect exports with PE-aware tooling.
What to inspect
- The importing module, resolved dependency path, file version, architecture, and exact requested procedure name.
- The target image export table and whether the symbol is exported under a decorated or different name.
- Deployment or servicing changes that mixed a newer caller with an older dependency, or the reverse.
References
- Microsoft: GetProcAddress
- Microsoft: PE/COFF image format
- Microsoft: Link an executable to a DLL
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.