| Previous | Next |
| ERROR_SYNC_FOREGROUND_REFRESH_REQUIRED | ERROR_INVALID_IMPORT_OF_NON_DLL |
ERROR_DRIVER_BLOCKED
The driver was rejected by a load policy before it could manage the device
A blocked driver is different from DriverEntry failure: the image does not become an active driver merely because a service or device references it. Modern Windows enforces kernel-mode signing and Code Integrity policy, and other compatibility or platform policies can also prevent a driver from loading.
Start with the Code Integrity and System event logs and the device installation log. Determine the exact driver image, signer, and policy reason rather than replacing random device drivers. Signature verification can fail because an image is unsigned, altered after signing, or otherwise unacceptable to current policy. During driver development, use the documented signing and test-signing workflow; disabling protection ad hoc can hide the deployment defect and change system security state.
What to inspect
- Identify the exact .sys image and package selected for the device.
- Read Code Integrity events for the specific verification or policy failure.
- Check signing and package installation logs before replacing or bypassing the driver.
References
- Microsoft: kernel-mode driver signing policy
- Microsoft: Code Integrity diagnostic events
- Microsoft: SetupAPI device installation log entries
Looking for a different code? Search another status or error code.