| Previous | Next |
| STATUS_CALLBACK_POP_STACK | STATUS_HIVE_UNLOADED |
STATUS_INCOMPATIBLE_DRIVER_BLOCKED
The driver reached a compatibility block, not a generic file-not-found failure
STATUS_INCOMPATIBLE_DRIVER_BLOCKED is more specific than STATUS_DRIVER_BLOCKED: the published NTSTATUS text identifies incompatibility with the current system. Preserve the driver package and platform identity so the compatibility decision can be understood instead of forcing the same binary to load.
Windows driver policy and Code Integrity diagnostics provide evidence about rejected kernel images. Current Windows versions can also apply vulnerable-driver blocking and application-control policy. The exact event, policy and binary hash should determine the remediation; the symbolic status is not enough to conclude that a signature is missing or that one particular block list was responsible.
What to compare
- Driver version, signer, catalog, package INF and hardware IDs against the current Windows build and device model.
- CodeIntegrity operational events and application-control events recorded at the load attempt.
- Whether an older copy of the driver remains in the Driver Store or service configuration after an upgrade.
- The hardware or software vendor's supported package for the current OS release.
A compatibility block is not repaired by renaming the image or disabling unrelated device settings. Replace the package with a supported build or use the recorded policy evidence to evaluate an intentional policy exception.
References
- Microsoft: Windows driver policy
- Microsoft: Code Integrity diagnostic events
- Microsoft: Recommended driver block rules
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.