What does HRESULT 0xC00D2783 (NS_E_DRM_DATASTORE_CORRUPT) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The Digital Rights Management data storage is not functioning properly.  Contact Microsoft product support.%0.

Previous	Next
NS_E_DRM_UNABLE_TO_OPEN_DATA_STORE	NS_E_DRM_UNABLE_TO_CREATE_INMEMORYSTORE_OBJECT

NS_E_DRM_DATASTORE_CORRUPT

Where the operation stopped

0xC00D2783 maps to NS_E_DRM_DATASTORE_CORRUPT. Read it as a result from local license store, secure store and machine binding: the DRM data store is readable but fails integrity or structure validation. Keeping the “datastore corrupt” boundary intact prevents a later playback message from hiding the original DRM failure.

State to capture before retry

Protected identity: license identifier and content key identifier (KID).
Operation state: store path, file generation, access result and underlying system error.
Persistence or transport: hardware identity and the last hardware or operating-system change.
Security context: checkpoint, secure-store and registry persistence sequence.
Correlation point: first store API call that failed: open, enumerate, save, close or query.

For the “datastore corrupt” 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.

A useful investigation order

Start from 0xC00D2783 and map it to the first WMDRM object that returned it.
Separate content/header evidence, license evidence, machine/device evidence and service/network evidence around “datastore corrupt”.
Before retrying this result, check whether another “datastore corrupt” operation was active or whether the previous result may have committed partially.
Preserve the file, hash, size and first validation failure.
Apply the smallest supported fix: restore from a supported backup or rebuild/reacquire through supported tooling; avoid resetting unrelated protected state.

Targeted fix

The supported response to this result is narrow: restore from a supported backup or rebuild/reacquire through supported tooling. After correcting it, reopen or recreate the object that owned “datastore corrupt” so the verification does not reuse state from the failed operation.

Representative case: A partial disk restore leaves a truncated DRM store generation.

What not to do first

Avoid deleting or resetting DRM state before recording hashes, timestamps and the first store error.

Nearby results with different meanings

Result	Different condition
`NS_E_DRM_UNABLE_TO_OPEN_DATA_STORE`	The DRM data-store file cannot be opened.
`NS_E_DRM_UNABLE_TO_LOAD_HARDWARE_ID`	The DRM subsystem cannot obtain the machine identity used for protected-state binding.
`NS_E_DRM_CHECKPOINT_FAILED`	The secure-state checkpoint cannot be created or committed.

Verification after correction

A valid regression has two fixtures: one that deliberately produces “the DRM data store is readable but fails integrity or structure validation” and one that applies the targeted correction. Compare callback order, selected license/KID, final rights decision and persistence state; disappearance of the “datastore corrupt” dialog alone is not proof.

Technical references

Licenses and the local license store.
Enumerating licenses in the local store — API and state rules for the DRM operation described here.
DRM client interfaces.
Windows Media DRM error codes.

Looking for a different code? Search another status or error code.