| Previous | Next |
| SPAPI_E_INF_IN_USE_BY_DEVICES | SPAPI_E_NO_AUTHENTICODE_CATALOG |
SPAPI_E_DI_FUNCTION_OBSOLETE
SPAPI_E_DI_FUNCTION_OBSOLETE identifies this condition: the requested device-installation function is no longer supported as an active operation in the current SetupAPI model.
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.
Obsolete is not transient and should not be handled by retrying the same DIF request.
Evidence worth preserving
- DIF code, caller module, Windows build, and target device class
- Class-installer documentation showing the current supported request
- Whether the caller is an old co-installer or compatibility shim
- SetupAPI. Dev. Log showing dispatch and the component that issued the obsolete request
A controlled diagnostic sequence
- Replace the DIF call with the documented SetupDi/CfgMgr32 operation in a test build.
- Run the legacy caller on the oldest supported and current Windows versions.
- Verify that omitting the obsolete callback does not remove required device state.
Correction and proof
A defensible correction is specific to the evidence: Move the caller to supported device-installation APIs and update the package’s minimum/maximum platform declarations.
Close the incident only when install, update, property change, and removal paths complete without the obsolete request on every supported Windows build.
Technical references
The following documentation is most relevant when checking the code against the actual Windows contract for obsolete DIF request:
Looking for a different code? Search another status or error code.