| Previous | Next |
| SPAPI_E_NO_COMPAT_DRIVERS | SPAPI_E_INVALID_INF_LOGCONFIG |
SPAPI_E_NO_DEVICE_ICON
SPAPI_E_NO_DEVICE_ICON — 0x800F0229
SPAPI_E_NO_DEVICE_ICON means that SetupAPI found the device context but no icon represents that device or device type through the requested property/resource path.
What the status narrows down
For device installation, SetupAPI. Dev. Log is the chronological backbone. Correlate the HRESULT with the device instance ID, selected INF and section, signature or rank decision, file queue, class/co-installer dispatch, and rollback for that exact attempt instead of reading isolated lines from different installations.
Failure to load a registered class icon is different from a device that simply has no device-specific icon.
Evidence worth preserving
- Device instance ID, setup class, device-interface class, and icon-loading API
- Device metadata/icon property and fallback class icon result
- Driver package version, metadata package, and install timestamp
- SetupAPI. Dev. Log and property-query status for the device
A controlled diagnostic sequence
- Request the class icon as a fallback while keeping the device fixed.
- Compare another device using the same driver package and class.
- Reinstall only the metadata/driver package in a disposable test system.
How to read the outcome
Read the comparison results in this order:
Correction and proof
A defensible correction is specific to the evidence: Provide or repair valid device metadata where required, but let administrative tools fall back to the class icon instead of treating appearance as device failure.
Close the incident only when device management remains functional with and without optional metadata, and the UI uses a deterministic fallback.
Technical references
The details above are grounded in the following Microsoft specifications and API documentation:
Looking for a different code? Search another status or error code.