| Previous | Next |
| NS_E_IMAPI_LOSSOFSTREAMING | NS_E_FAIL_LAUNCH_ROXIO_PLUGIN |
NS_E_PDA_DEVICE_FULL
Diagnostic meaning beyond the standard message
The actionable meaning of 0xC00D117F / NS_E_PDA_DEVICE_FULL is checking free device storage before adding the requested object. 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 Device Manager brokers between the Player, a device service provider and MTP, mass-storage or legacy device transports; Enumeration, Plug and Play identity, storage availability, format support and individual file operations are distinct checks. The page-specific boundary is checking free device storage before adding the requested object.
A device shown in Explorer can still disappear from the Player’s WMDM session or reject a media format, filename, directory operation or storage request. One concrete reproduction is: the queued file is larger than the currently reported free space.
Evidence matrix
| Evidence | Why it matters for device full |
|---|---|
| Producing object and operation | PnP instance and interface path, WMDM service-provider CLSID, device/partnership ID, connection generation, storage object and capacity, format-support result, firmware version, operation callback and first device or transport HRESULT |
| Decisive observation | target storage ID, free/total/unusable bytes, item size and reserved overhead |
| 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: free space or select another storage target before restarting the item. |
Decision matrix
| Observation | Interpretation |
|---|---|
| The recorded values match the boundary | The result is consistent with checking free device storage before adding the requested object; 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 device full 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 checking free device storage before adding the requested object.
Minimal experiment
- Capture
0xC00D117F, it, the exact Player/API operation and the first timestamp at which it appears. - Save target storage ID, free/total/unusable bytes, item size and reserved overhead; do this before ejecting media, reconnecting a device, canceling a job or rebuilding the Player object.
- correlate the result with PnP instance and interface path, WMDM service-provider CLSID, device/partnership ID, connection generation, storage object and capacity, format-support result, firmware version, operation callback and first device or transport HRESULT.
- Reproduce once with the original source and destination, then apply only this change: free space or select another storage target before restarting the item.
- Create a fresh operation generation and verify that the original call advances beyond the device full boundary.
Do not collapse it with these results
| Related result | Different diagnostic boundary |
|---|---|
NS_E_PDA_DEVICE_FULL_IN_SESSION | exhausting device capacity after the sync session already transferred earlier items |
NS_E_PDA_FAIL_READ_WAVE_FILE | opening and parsing a WAV source used for device transfer or conversion |
NS_E_PDA_FAIL_SELECT_DEVICE | binding the operation to the user-selected device from the current enumeration |
Recovery and verification
Resolve the responsible precondition by ensuring that you free space or select another storage target before restarting the item. A successful retest must pass the same device full checkpoint, not merely hide the message in a different UI path.
When verifying it, do not assume the old interface pointer remains valid after reconnect; Re-enumerate the device and storage objects and correlate the failure with the same connection generation.
Authoritative documentation
- Windows Media Device Manager SDK.
- Enabling Plug and Play for WMDM devices.
- Portable-device capabilities and shell requirements.
- WMDM connection and storage notifications.
Looking for a different code? Search another status or error code.