| Previous | Next |
| STATUS_PNP_NO_COMPAT_DRIVERS | STATUS_PNP_DRIVER_CONFIGURATION_NOT_FOUND |
STATUS_PNP_DRIVER_PACKAGE_NOT_FOUND
STATUS_PNP_DRIVER_PACKAGE_NOT_FOUND indicates that a driver package referenced by the installation workflow cannot be located on this Windows installation. It is not the same as STATUS_PNP_NO_COMPAT_DRIVERS: here the workflow has a package identity or reference, but the package is unavailable.
Diagnose package presence before changing device resources. A driver package consists of an INF, catalog, binaries, and device-specific applicability information; a copied driver binary without the corresponding staged package does not recreate that package.
Useful checks
- Identify the published INF and package version mentioned near the failure in
SetupAPI.dev.log. - Verify that the package was staged for the current Windows image and has not been removed, superseded, or partially deployed.
- Separate package discovery from later failures such as an unmatched ID, a missing configuration, or a failed device start.
References
- Microsoft: components of a driver package
- Microsoft: SetupAPI device-installation log
- MS-ERREF: NTSTATUS values
Looking for a different code? Search another status or error code.