| Previous | Next |
| ERROR_INVALID_PIXEL_FORMAT | ERROR_INVALID_WINDOW_STYLE |
ERROR_BAD_DRIVER
Windows rejected the specified driver as an invalid driver object or image for this operation
This Win32 status is intentionally broader than a signing failure or DriverEntry failure. It indicates that the driver supplied to the operation could not be accepted as the expected driver. Device installation and driver loading are separate stages, so the surrounding API and log context determine whether the problem is package selection, an invalid image, or a mismatched driver reference.
Preserve the first caller and lower-level error instead of diagnosing from the constant name alone. For device installation, use SetupAPI.dev.log to identify the package and exact failing step. For kernel-driver development, verify that the image was built for the target architecture and uses the required driver entry points and model. Code Integrity events should be consulted only when Windows explicitly reports signature or policy rejection; otherwise this status should not be rewritten as “unsigned driver.”
What to inspect
- Record the API or installer stage that returned the code.
- Identify the exact package, service, and binary involved.
- Separate package/format problems from Code Integrity and DriverEntry failures.
References
- Microsoft: SetupAPI device installation log entries
- Microsoft: driver entry points
- Microsoft: Code Integrity diagnostic events
Looking for a different code? Search another status or error code.