| Previous | Next |
| NS_E_DRM_LICENSE_CONTENT_REVOKED | NS_E_DRM_LICENSE_NOSAP |
NS_E_DRM_DEVICE_NOT_REGISTERED
What this HRESULT isolates
When the client returns NS_E_DRM_DEVICE_NOT_REGISTERED (0xC00D27E2), the relevant condition is license policy requires the target device to be registered to this computer. 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.
Minimum incident record
- 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.
For the “device not registered” investigation, use KIDs, license IDs, hashes, certificate thumbprints, sizes and timestamps where possible. Do not place content keys, complete license blobs, passwords, cookies or decrypted media in ordinary logs.
Triage without destroying evidence
- Start from
0xC00D27E2and map it to the first WMDRM object that returned it. - Separate content/header evidence, license evidence, machine/device evidence and service/network evidence around “device not registered”.
- Before retrying this result, check whether another “device not registered” operation was active or whether the previous result may have committed partially.
- Record device certificate, registration database entry and selected license policy.
- Apply the smallest supported fix: complete supported device registration before retrying the operation; avoid resetting unrelated protected state.
Why the producing layer matters
Two platform rules frame this result. A device can be reachable as storage while still failing WMDRM authentication, secure-clock or policy requirements. Time-bound and subscription licenses may require a trusted device clock; changing the host clock does not repair a device clock that was never obtained or set.
Recovery at the right layer
The supported response to it is narrow: complete supported device registration before retrying the operation. After correcting it, reopen or recreate the object that owned “device not registered” so the verification does not reuse state from the failed operation.
Representative case: A newly connected device is authenticated but has not been registered for this machine.
Why the symbolic name matters
| Result | Different condition |
|---|---|
NS_E_DEVICE_NOT_WMDRM_DEVICE | The attached device does not advertise the WMDRM capability required by this transfer. |
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. |
Several values can accompany the “device not registered” condition in one incident. Order the event chain by timestamp and prefer the first code produced at the lowest specific boundary over a later player-level summary.
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.
Technical references
- IWMDRMDeviceApp interface.
- Device registration — API and state rules for the DRM operation described here.
- Output protection levels.
- Windows Media DRM error codes.
Looking for a different code? Search another status or error code.