| Previous | Next |
| NS_E_WMP_IMAPI_GENERIC | NS_E_WMP_IMAPI_DEVICE_BUSY |
NS_E_WMP_IMAPI_DEVICE_NOTPRESENT
Diagnostic meaning beyond the standard message
The actionable meaning of 0xC00D11AD / NS_E_WMP_IMAPI_DEVICE_NOTPRESENT is opening the recorder after it was removed or its device path changed. Keep the object generation and lower-level result attached to the result event.
Why the operation can reach this point
At the checkpoint, windows Media Player builds a burn playlist, refreshes its calculated status and delegates physical recording or erase work to the optical-disc stack; The recorder, inserted medium, burn format, staging files and write engine each have a separate lifecycle. The page-specific boundary is opening the recorder after it was removed or its device path changed.
A recorder that enumerates can still be busy, incompatible with the inserted medium or unable to sustain the selected write operation. One concrete reproduction is: a USB burner is unplugged after the burn list was prepared.
Evidence matrix
| Evidence | Why it matters for imapi device notpresent |
|---|---|
| Producing object and operation | recorder unique ID and exclusive-access owner, inserted media profile/state, burn format, playlist item, source locality, duration/byte estimate, staging directory free space, write speed, current IMAPI action and underlying HRESULT |
| Decisive observation | recorder unique ID, PnP presence, interface path and media-change/device-removal event |
| Generation identity | Record the same disc, device, job or Player operation generation that returned this result; a reconnect or media change creates a different test. |
| Underlying result | Keep the first device, filesystem, COM, codec, DirectShow, IMAPI or BITS result seen before the Player mapped it to this result. |
| Controlled comparison | Repeat the producing call after changing only this condition: re-enumerate recorders after reconnect and select the new device object. |
Decision matrix
| Observation | Interpretation |
|---|---|
| The recorded values match the boundary | The result is consistent with opening the recorder after it was removed or its device path changed; correct that state before changing unrelated codecs, drivers or playlists. |
| A lower layer failed before this result | Preserve that earlier HRESULT or device result because this result may be only the Player-level mapping. |
| The same call passes after one isolated change | The comparison supports the imapi device notpresent diagnosis rather than a broad installation failure. |
| The code changes after retesting it | The boundary was passed; diagnose the new HRESULT as the next independent stage. |
It scopes the failure to opening the recorder after it was removed or its device path changed.
Minimal experiment
- Capture
0xC00D11AD, it, the exact Player/API operation and the first timestamp at which it appears. - Save recorder unique ID, PnP presence, interface path and media-change/device-removal event; do this before ejecting media, reconnecting a device, canceling a job or rebuilding the Player object.
- correlate the result with recorder unique ID and exclusive-access owner, inserted media profile/state, burn format, playlist item, source locality, duration/byte estimate, staging directory free space, write speed, current IMAPI action and underlying HRESULT.
- Reproduce once with the original source and destination, then apply only this change: re-enumerate recorders after reconnect and select the new device object.
- Create a fresh operation generation and verify that the original call advances beyond the imapi device notpresent boundary.
Do not collapse it with these results
| Related result | Different diagnostic boundary |
|---|---|
NS_E_WMP_IMAPI_DEVICE_BUSY | acquiring the recorder while another operation or process owns it |
NS_E_WMP_IMAPI_GENERIC | mapping an IMAPI result that the Player did not classify more specifically |
NS_E_WMP_IMAPI_FAILURE | receiving a generic failure from the Image Mastering API during recording |
Recovery and verification
Resolve the responsible precondition by ensuring that you re-enumerate recorders after reconnect and select the new device object. A successful retest must pass the same imapi device notpresent checkpoint, not merely hide the message in a different UI path.
When verifying it, do not repeatedly start a new burn against a drive that still owns or finalizes the previous session; Capture the media state and recorder owner before ejecting or replacing the disc.
Authoritative documentation
- About CD Burning.
- IWMPCdromBurn interface.
- Image Mastering API interfaces and media states.
- Checking recorder and media support.
- IDiscRecorder2::AcquireExclusiveAccess.
Looking for a different code? Search another status or error code.