| Previous | Next |
| STATUS_PNP_DRIVER_PACKAGE_NOT_FOUND | STATUS_PNP_DRIVER_CONFIGURATION_INCOMPLETE |
STATUS_PNP_DRIVER_CONFIGURATION_NOT_FOUND
STATUS_PNP_DRIVER_CONFIGURATION_NOT_FOUND occurs after Plug and Play has reached a package/configuration stage but cannot locate configuration data required for this device. The status does not by itself prove that the device hardware is absent or that the selected binary is corrupt.
For diagnosis, keep the matching decision and the configuration decision separate. A package may match an ID yet rely on an install section, extension configuration, service entry, or platform-specific model selection that is not applicable to the device instance being configured.
What to preserve in a report
- The device instance ID, reported hardware and compatible IDs, selected INF, and selected model/install section.
- The first configuration-related error in
SetupAPI.dev.log, not only the final status returned to the caller. - The Windows version, architecture, and any extension package that specializes a base driver for this hardware.
References
- Microsoft: INF Models section
- Microsoft: driver-package contents and applicability
- Microsoft: SetupAPI device-installation log
Looking for a different code? Search another status or error code.