| Previous | Next |
| STATUS_DRIVER_ORDINAL_NOT_FOUND | STATUS_RESOURCE_NOT_OWNED |
STATUS_DRIVER_ENTRYPOINT_NOT_FOUND
A required imported driver routine could not be resolved
STATUS_DRIVER_ENTRYPOINT_NOT_FOUND reports that the kernel loader could not locate a named entry point required from a driver. This is an import-resolution problem between binary components; it should not be explained as simply forgetting to set the failing driver's own DriverEntry linker entry point.
What usually makes this actionable
- Preserve the status message fields when available: the requested routine name, the driver that was expected to export it, and the image being loaded.
- Record both driver versions, hashes, signatures, architecture, and the operating-system build.
- Inspect the importing image's import table and the exporting driver's actual symbols/exports. A partial update can leave a consumer expecting an entry point that the installed provider does not expose.
- Check package and servicing history before replacing individual
.sysfiles by hand.
Recovery
Install a mutually compatible driver/package set through its supported deployment path. If the mismatch followed rollback or offline servicing, restore the complete matching component set rather than copying one binary from another machine.
After repair, verify that the same driver load succeeds and that no new dependency-resolution status appears. A later DriverEntry failure is a different stage and must be diagnosed separately.
Official references
Looking for a different code? Search another status or error code.
