| Previous | Next |
| NS_E_WMP_WMDM_NORIGHTS | NS_E_WMP_IMAPI_GENERIC |
NS_E_WMP_WMDM_INCORRECT_RIGHTS
The exact DRM boundary
This HRESULT is specific: NS_E_WMP_WMDM_INCORRECT_RIGHTS appears because rights are present but their conditions do not match this device-transfer request. Within protected-content transfer to portable devices, this result is raised while processing Windows Media Player and Windows Media Device Manager coordination between the application, secure content provider and device service provider during protected-file synchronization.
To prove this boundary rather than infer it from a dialog, compare device count, expiration, security level and transfer-count conditions.
Fields for a reproducible report
| Field | Value |
|---|---|
| Direct check | compare device count, expiration, security level and transfer-count conditions |
| Policy input | requested action plus the exact license, certificate, profile, output or registration property evaluated by this result |
| Temporal state | trusted/system time, validity interval, request sequence and retry number when they influence this result |
| Lower result | the earliest store, network, cryptographic, driver or provider status preceding the final it wrapper |
| Owner | operation, API/callback, object or session identifier, and component/device version associated with it |
What to log
Do not separate it from its owning state: portable-device identity, WMDM secure channel, transfer certificate, device DRM capability flags, secure clock, content license and transfer transaction. The diagnostic record for this HRESULT is device firmware and provider identity, WMDM capability/status flags, secure-channel authentication result, license rights for sync and the transfer-completion status.
This evidence matters because the rejected condition is specifically that rights are present but their conditions do not match this device-transfer request.
Expected state change
When documenting it, state the rejected input and the expected successor state. The rejected input is demonstrated when you compare device count, expiration, security level and transfer-count conditions; the successor becomes reachable after you use a qualifying device or obtain a license with matching sync conditions. The result comparison should preserve content and device identity so success cannot be attributed to testing a different asset.
Scope and consequences
The established fact is that rights are present but their conditions do not match this device-transfer request. That fact does not independently establish damaged media bytes, a missing decoder, a generally broken network, or invalid rights for every other action.
If the Player, encoder, setup program or device layer later emits a broader error, retain it as the first specific result. The object and operation attached to it are usually more diagnostic than a later cleanup or user-interface summary.
Troubleshooting order
- Preserve it and
0xC00D11AAbefore cleanup, fallback or another media item changes the context. - Run the direct check for this HRESULT: compare device count, expiration, security level and transfer-count conditions.
- Compare the failure with a known-good case that changes only the property named by this condition: rights are present but their conditions do not match this device-transfer request.
- Apply the narrow correction for this HRESULT: use a qualifying device or obtain a license with matching sync conditions.
- Associate it with its current protected-content transfer to portable devices object and the requested action.
- Repeat the same action with the same content/device identity and verify that it is not replaced by another policy or trust failure.
Related codes, different contracts
| Result | Why it points elsewhere |
|---|---|
NS_E_WMP_WMDM_BUSY | another client or operation currently owns the portable-device transfer path |
NS_E_WMP_WMDM_NORIGHTS | the protected item exposes no right that permits synchronization to the selected device |
NS_E_PDA_CEWMDM_DRM_ERROR | a Windows CE/WMDM device failed during the protected-content exchange or firmware-mediated DRM step |
Change the rejected precondition
Repair the owner of the check: use a qualifying device or obtain a license with matching sync conditions. Success means that the same requested action is accepted after that precise state change, not merely that another file or device happens to work.
- While investigating it, keep this restriction: Do not convert or copy the protected file outside the secure transfer path as a diagnostic shortcut; that tests a different rights model and may consume or invalidate evidence.
- Do not alter trusted time, revocation enforcement, certificate validation or output policy merely to suppress it; that bypasses the decision instead of correcting its input.
- Retain one failing artifact and one corrected artifact so the resolution of it can be regression-tested.
Closure criterion
For the final it test, keep the content KID or file hash, requested action, user/account, device identity and output route unchanged wherever they apply.
Technical references
- Handling protected content — lists the security and state transitions used to interpret it.
- Handling protected content in an application — defines the platform objects used when diagnosing it.
- Windows Media Device Manager architecture — documents the protocol or API boundary behind it.
- Windows Media Device Manager error codes — provides the normative workflow relevant to it.
Looking for a different code? Search another status or error code.