What does HRESULT 0xC00D11C9 (NS_E_WMP_IMAPI_DEVICE_INVALIDTYPE) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Windows Media Player cannot burn the files. If the burner is busy, wait for the current task to finish. If necessary, verify that the burner is connected properly and that you have installed the latest device driver.%0

Previous	Next
NS_E_WMP_VIDEO_CODEC_NOT_INSTALLED	NS_E_WMP_DRM_DRIVER_AUTH_FAILURE

NS_E_WMP_IMAPI_DEVICE_INVALIDTYPE

Failure boundary and ownership

NS_E_WMP_IMAPI_DEVICE_INVALIDTYPE with value 0xC00D11C9 records binding a recording operation to a device that does not support the required recorder profile. The producing call and its state are more diagnostic than a later aggregate Player failure.

Underlying mechanism

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 binding a recording operation to a device that does not support the required recorder profile.

A recorder that enumerates can still be busy, incompatible with the inserted medium or unable to sustain the selected write operation. The condition can be reproduced when a virtual or read-only drive is selected for a physical write command.

Trace fields worth keeping

Evidence	Why it matters for imapi device invalidtype
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	device class, supported profiles, inserted media and chosen burn interface
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: select a recorder/profile combination that supports the intended audio, data or erase operation.

What the comparison proves

Observation	Interpretation
The recorded values match the boundary	The result is consistent with binding a recording operation to a device that does not support the required recorder profile; 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 invalidtype 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 binding a recording operation to a device that does not support the required recorder profile.

Decision path

Capture 0xC00D11C9, it, the exact Player/API operation and the first timestamp at which it appears.
Save device class, supported profiles, inserted media and chosen burn interface; 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: select a recorder/profile combination that supports the intended audio, data or erase operation.
Create a fresh operation generation and verify that the original call advances beyond the imapi device invalidtype boundary.

Close alternatives

Related result	Different diagnostic boundary
`NS_E_WMP_CD_ANOTHER_USER`	acquiring the optical drive while another user session owns the CD operation
`NS_E_WMP_CD_STASH_NO_SPACE`	allocating local staging space for files and converted audio before burning
`NS_E_WMP_IMAPI_LOSS_OF_STREAMING`	feeding the recorder slowly enough that its write buffer underruns

Safe correction

Correct this boundary by making sure you select a recorder/profile combination that supports the intended audio, data or erase operation. Then reacquire the interface or media state that produced it and repeat that call.

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.

Source material

Looking for a different code? Search another status or error code.