| Previous | Next |
| STATUS_DLL_INIT_FAILED_LOGOFF | STATUS_DFS_UNAVAILABLE |
STATUS_DRIVER_UNABLE_TO_LOAD
Driver loading failed before the device could start
Loading can fail during image mapping, dependency resolution, code-integrity validation or initialization. The accompanying status and logs distinguish a missing or corrupt binary from a signature policy failure, incompatible architecture, unresolved import or DriverEntry rejection.
Reinstalling repeatedly without reading SetupAPI and Code Integrity logs can overwrite useful context. Verify that the package is staged in the Driver Store and that the service points to the expected image. A successful package installation does not guarantee that the kernel image subsequently loads.
What to inspect
- Capture the nested load status, service ImagePath and exact binary hash and version.
- Review SetupAPI.dev.log, Code Integrity events and System service-control events.
- Verify architecture, dependencies, signature policy and DriverEntry result.
References
- Microsoft: Driver Store
- Microsoft: SetupAPI and Code Integrity diagnostics
- Microsoft: Writing a DriverEntry routine
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: driver loading and I/O manager
Looking for a different code? Search another status or error code.