| Previous | Next |
| ERROR_SYSTEM_HIVE_TOO_LARGE | ERROR_VOLSNAP_PREPARE_HIBERNATE |
ERROR_DRIVER_FAILED_PRIOR_UNLOAD
Windows could not load the driver because an earlier version is still resident
PnP drivers are unloaded only after their devices and device objects have been removed and the I/O manager reaches a safe unload point. A new image cannot simply replace code that is still active in a device stack. This error therefore describes driver lifetime state, not a file-copy problem.
Identify which device instances still use the earlier driver and whether open handles or incomplete removal keep the old stack alive. Surprise removal and UMDF restart scenarios can also leave teardown waiting for clients to close handles. For kernel drivers, review whether every FDO/filter DO is detached and deleted on remove and whether the driver has released global references. Rebooting replaces the resident image, but a repeatable development-time failure usually means the unload or device-removal path should be traced.
What to inspect
- Enumerate device instances and stacks still bound to the old driver.
- Check open handles and pending remove processing before replacing the binary.
- For driver code, audit device deletion, detach, and global reference cleanup.
References
- Microsoft: removing a device in a function driver
- Microsoft: PnP device state transitions
- Microsoft: when PnP remove IRPs are issued
Looking for a different code? Search another status or error code.