| Previous | Next |
| NS_E_DRM_LICENSE_SERVER_INFO_MISSING | NS_E_DRM_PD_TOO_MANY_DEVICES |
NS_E_DRM_BUSY
Failure scope
For NS_E_DRM_BUSY, the failed contract is that another process or operation holds the DRM subsystem lock. This result comes from Windows Media DRM client internals, whose state machine implements the client DRM engine that initializes security components, validates content and license identifiers, performs individualization, manages license chains and coordinates protected playback capabilities.
To prove this boundary rather than infer it from a dialog, identify active DRM clients and the operation that owns the serialization point.
Data worth retaining
The object graph behind this result includes DRM component version, KID, content header signature, license chain, uplink license, individualization state, portable-device registrations and local configuration. A trace should retain the KID and header hash, DRM component version, individualization status, license-chain identifiers, registry/configuration lookup and the first client callback reporting failure.
A later generic error must not replace this evidence: the original condition remains that another process or operation holds the DRM subsystem lock.
The transition to retest
A useful failure model links cause and recovery: another process or operation holds the DRM subsystem lock. Verify that model when you identify active DRM clients and the operation that owns the serialization point, then make the smallest change needed to wait for completion or terminate the stuck owner cleanly before retrying. Record the first lower-layer status beside this result because wrapper HRESULTs can otherwise conceal the producing component.
Verification inputs
| Field | Value |
|---|---|
| Direct check | identify active DRM clients and the operation that owns the serialization point |
Different owners, similar dialog
| Result | Why it points elsewhere |
|---|---|
NS_E_DRM_SIGNATURE_FAILURE | creation or verification of a protected content header signature failed |
NS_E_DRM_LICENSE_SERVER_INFO_MISSING | the client cannot read configuration that identifies or describes the license service |
NS_E_DRM_PD_TOO_MANY_DEVICES | portable-media registration data already contains the maximum supported target-device set |
Separate cause from wrapper
Another process or operation holds the DRM subsystem lock.
Test without erasing evidence
- Preserve it and
0xC00D2841before cleanup, fallback or another media item changes the context. - Apply the targeted fix: wait for completion or terminate the stuck owner cleanly before retrying.
- Associate it with its current Windows Media DRM client internals object and the requested action.
- Run the direct check: identify active DRM clients and the operation that owns the serialization point.
- Compare the failure with a known-good case that changes only the property named by this condition: another process or operation holds the DRM subsystem lock.
When a retry is valid
A matching correction is to wait for completion or terminate the stuck owner cleanly before retrying.
- Preserve the evidence before making changes.
Technical references
Looking for a different code? Search another status or error code.