| Previous | Next |
| NS_E_LICENSE_HEADER_MISSING_URL | NS_E_DRM_INVALID_APPCERT |
NS_E_DEVICE_NOT_WMDRM_DEVICE
How to classify this result
When the client returns NS_E_DEVICE_NOT_WMDRM_DEVICE (0xC00D277B), the relevant condition is the attached device does not advertise the WMDRM capability required by this transfer. This result belongs to portable-device certificate, secure clock and transfer policy, specifically the device-facing path that authenticates a WMDRM-capable device, obtains its certificate and secure clock, evaluates transfer policy, and records metering or registration state.
Record device protocol capabilities and the operation requested.
Minimum incident record
The smallest useful record contains:
- Code-specific proof: record device protocol capabilities and the operation requested.
- Protected identity: device certificate chain and serial identity.
- Operation state: secure clock value, source and last successful update.
- Persistence or transport: requested transfer/burn action and license restriction.
- Security context: device activation, registration and metering result.
- Correlation point: device model, firmware and WMDRM capability.
Triage without destroying evidence
- Locate the earliest API return, callback or event containing this result and
0xC00D277B. - Identify the exact content, license, store, device or migration object instance involved in “device not wmdrm device”.
- Determine whether “device not wmdrm device” occurred before network exchange, during response validation, while enforcing policy, or while committing protected state.
- Perform the code-specific check: record device protocol capabilities and the operation requested.
- Make one targeted change — use unprotected/compatible content or a device supporting the required WMDRM profile — and repeat the same producing operation.
Why the symbolic name matters
| Result | Different condition |
|---|---|
NS_E_DRM_LIC_NEEDS_DEVICE_CLOCK_SET | The selected license requires a secure device clock that has not been set. |
NS_E_DRM_TRANSFER_CHAINED_LICENSES_UNSUPPORTED | The requested device transfer does not support the selected chained-license relationship. |
NS_E_DRM_POLICY_METERING_DISABLED | The content requires metering but metering is disabled for the client or device path. |
Shortcuts that make diagnosis worse
- Avoid formatting the device before preserving its certificate, clock and firmware evidence.
- Avoid treating an unsupported-device result as a generic USB or file-copy failure.
Recovery at the right layer
To correct this, use unprotected/compatible content or a device supporting the required WMDRM profile.
Representative case: A mass-storage player accepts files but does not implement subscription-license transfer.
Code-specific operational note
The user-facing message “The current attached device does not support WMDRM.” describes the visible condition but does not identify the producing API, object instance, or protected identity by itself.
Technical references
- IWMDRMDeviceApp interface — API and state rules relevant to this result.
- Device registration — platform documentation used to distinguish it from adjacent results.
- Output protection levels — official Windows Media DRM context.
- Windows Media DRM error codes
Looking for a different code? Search another status or error code.