What does HRESULT 0xC00D272B (NS_E_DRM_ACQUIRING_LICENSE) mean?

NS_E_DRM_ACQUIRING_LICENSE

How to classify this result

When the client returns NS_E_DRM_ACQUIRING_LICENSE (0xC00D272B), the relevant condition is another license acquisition is already active for the DRM object. This result belongs to license challenge, acquisition and server response processing, specifically the asynchronous path that builds a license request from the protected content header, sends or exposes the challenge, receives a response and commits accepted licenses to the local store.

Identify the active operation, its completion callback and cancellation cookie.

Minimum incident record

• Protected identity: silent or non-silent acquisition mode and callback/event sequence.
• Operation state: request or challenge identifier and response HTTP status.
• Persistence or transport: server certificate, response signature and returned license count.
• Security context: store commit result after a successful server response.
• Correlation point: content KID and license acquisition URL from the header.

For the “acquiring license” 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.

Why the producing layer matters

Two platform rules frame this result. License acquisition and license storage are separate stages: a valid server response can still fail while being validated or committed locally. Because acquisition is asynchronous, starting a second request before the completion event can produce a state error rather than a network failure.

Triage without destroying evidence

1. Locate the earliest API return, callback or event containing this result and 0xC00D272B.
2. Identify the exact content, license, store, device or migration object instance involved in “acquiring license”.
3. Determine whether “acquiring license” occurred before network exchange, during response validation, while enforcing policy, or while committing protected state.
4. Make one targeted change — wait for or explicitly cancel the existing acquisition before starting another — and repeat the same producing operation.

Why the symbolic name matters

Several values can accompany the “acquiring license” 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 blindly retrying a state-changing license request without correlating the previous challenge and completion event.
• Avoid logging complete license challenges, responses, cookies or credentials in diagnostic output.

Recovery at the right layer

To correct this, wait for or explicitly cancel the existing acquisition before starting another. Preserve the original content/header, store or migration material until the “acquiring license” operation succeeds and survives a fresh application object or required restart.

Representative case: Two UI paths start acquisition for the same content while the first request is pending.

Completion criteria

After the repair, recreate the WMDRM object and run the smallest reproducer. Confirm that 0xC00D272B no longer occurs, that the intended license action completes, and that no store, certificate, clock or migration warning replaces it.

Code-specific operational note

The user-facing message “You cannot begin a new license acquisition process until the current one has been completed.” describes the visible condition but does not identify the producing API, object instance, or protected identity by itself.

Technical references

• Acquiring licenses — API and state rules for the DRM operation described here.
• Handling license acquisition events.
• DRM protection and license distribution.
• DRM client programming guide — API and state rules for the DRM operation described here.