| Previous | Next |
| NS_E_DRM_TRACK_EXCEEDED_PLAYLIST_RESTICTION | NS_E_DRM_UNABLE_TO_GET_DEVICE_CERT |
NS_E_DRM_TRACK_EXCEEDED_TRACKBURN_RESTRICTION
What this HRESULT isolates
When the client returns NS_E_DRM_TRACK_EXCEEDED_TRACKBURN_RESTRICTION (0xC00D2771), the relevant condition is the track has exhausted its overall burn count. 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 selected license and track-burn counter independently of playlist count.
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.
Triage without destroying evidence
- Start from
0xC00D2771and map it to the first WMDRM object that returned it. - Separate content/header evidence, license evidence, machine/device evidence and service/network evidence around “track exceeded trackburn restriction”.
- Before retrying this result, check whether another “track exceeded trackburn restriction” operation was active or whether the previous result may have committed partially.
- Apply the smallest supported fix: obtain a renewed license before another burn; 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 this result is narrow: obtain a renewed license before another burn. After correcting it, reopen or recreate the object that owned “track exceeded trackburn restriction” so the verification does not reuse state from the failed operation.
Representative case: The same track has been burned the maximum number of times across playlists.
Why the symbolic name matters
| Result | Different condition |
|---|---|
NS_E_DRM_TRACK_EXCEEDED_PLAYLIST_RESTICTION | The track has reached its playlist-specific burn limit for this playlist. |
NS_E_DRM_UNABLE_TO_GET_DEVICE_CERT | The client cannot retrieve or validate the target device certificate. |
NS_E_DRM_UNABLE_TO_GET_SECURE_CLOCK | The DRM client cannot read the device or local secure clock. |
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.
Completion criteria
A valid regression has two fixtures: one that deliberately produces “the track has exhausted its overall burn count” and one that applies the targeted correction. Compare callback order, selected license/KID, final rights decision and persistence state; disappearance of the “track exceeded trackburn restriction” dialog alone is not proof.
Code-specific operational note
The user-facing message “The specified track has exceeded it's track burn limit.” describes the visible condition but does not identify the producing API, object instance, or protected identity by itself.
Technical references
Looking for a different code? Search another status or error code.