What does HRESULT 0xC00D278F (NS_E_DRM_HARDWAREID_MISMATCH) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The requested action cannot be performed because a hardware configuration change has been detected by the Windows Media Digital Rights Management (DRM) components on your computer.%0.

Previous	Next
NS_DRM_E_MIGRATION_IMAGE_ALREADY_EXISTS	NS_E_INVALID_DRMV2CLT_STUBLIB

NS_E_DRM_HARDWAREID_MISMATCH

What this HRESULT isolates

The symbolic result NS_E_DRM_HARDWAREID_MISMATCH narrows 0xC00D278F to local license store, secure store and machine binding. In practical terms, stored DRM state no longer matches the current hardware identity; the producing layer is the protected repositories that hold licenses and DRM state, together with the hardware and checkpoint data used to bind that state to one installation.

Diagnostic inputs that separate the causes

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

For the “hardwareid mismatch” 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.

How to prove the condition

Start from 0xC00D278F 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 “hardwareid mismatch”.
Before retrying this result, check whether another “hardwareid mismatch” operation was active or whether the previous result may have committed partially.
Compare the last known working hardware ID with recent firmware, motherboard or storage changes.
Apply the smallest supported fix: use supported restore, migration or reacquisition for the new identity; avoid resetting unrelated protected state.

What a supported fix should change

Representative case: A motherboard replacement changes the machine binding used by existing licenses.

Common but unsafe responses

Avoid copying a protected license store from another computer as a repair.
Avoid deleting or resetting DRM state before recording hashes, timestamps and the first store error.

Do not merge these HRESULTs

Result	Different condition
`NS_E_DRM_CHECKPOINT_MISMATCH`	The DRM checkpoint does not match the protected data-store generation.
`NS_E_DRM_CHECKPOINT_CORRUPT`	The DRM checkpoint itself fails integrity or structure validation.
`NS_E_REG_FLUSH_FAILURE`	DRM state could not be durably flushed to the registry.

Several values can accompany the “hardwareid mismatch” 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.

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.