| Previous | Next |
| NS_E_IMAPI_MEDIUM_INVALIDTYPE | NS_E_PDA_PARTNERSHIPNOTEXIST |
NS_E_PDA_MANUALDEVICE
Practical scope of NS_E_PDA_MANUALDEVICE
This HRESULT is produced at encountering a device configured for manual transfer rather than automatic partnership sync. This result belongs to portable-device discovery, storage and capabilities, not to an undifferentiated “Windows Media problem.”
Pipeline position
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 encountering a device configured for manual transfer rather than automatic partnership sync.
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. In a typical failing run, automation attempts to manage playlists on a device intentionally marked manual.
Reproduction record
| Evidence | Why it matters for manualdevice |
|---|---|
| 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 | device sync mode, partnership state, selected operation and capability flags |
| 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: use manual transfer semantics or establish an automatic-sync partnership if supported. |
Reading the evidence
| Observation | Interpretation |
|---|---|
| The recorded values match the boundary | The result is consistent with encountering a device configured for manual transfer rather than automatic partnership sync; 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 it may be only the Player-level mapping. |
| The same call passes after one isolated change | The comparison supports the manualdevice 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 encountering a device configured for manual transfer rather than automatic partnership sync.
Verification procedure
- Capture
0xC00D1183, it, the exact Player/API operation and the first timestamp at which it appears. - Save device sync mode, partnership state, selected operation and capability flags; 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: use manual transfer semantics or establish an automatic-sync partnership if supported.
- Create a fresh operation generation and verify that the original call advances beyond the manualdevice boundary.
Results that may look similar
| 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_DEVICE_FULL | checking free device storage before adding the requested object |
NS_E_PDA_TOO_MANY_FILE_COLLISIONS | generating destination names that repeatedly collide with existing device objects |
Change the smallest responsible condition
The targeted action is to use manual transfer semantics or establish an automatic-sync partnership if supported. While retesting it, keep unrelated media, device, playlist and network values unchanged.
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.
References
- 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.