What does HRESULT 0xC00D2742 (NS_E_DRM_BACKUP_EXISTS) mean?

NS_E_DRM_BACKUP_EXISTS

The exact DRM condition

0xC00D2742 maps to NS_E_DRM_BACKUP_EXISTS. Read it as a result from license backup, restore and anti-abuse state: the selected backup location already contains a WMDRM backup set. Keeping the “backup exists” boundary intact prevents a later playback message from hiding the original DRM failure.

Record backup-set identity, timestamps and whether it belongs to the same operation/machine.

A useful investigation order

1. Prove the boundary by ensuring you can record backup-set identity, timestamps and whether it belongs to the same operation/machine.
2. After you choose an empty destination or deliberately manage the existing set through the supported workflow, verify both the requested right and the final store/device state.

State to capture before retry

• Protected identity: service response, reset count and daily restore limit.
• Operation state: target machine identity and final license-store commit.
• Persistence or transport: backup or restore operation ID.
• Security context: backup directory contents and manifest consistency.
• Correlation point: per-license backup/restore eligibility.

What not to do first

• Avoid repeatedly resetting or restoring until anti-fraud limits are reached.
• Avoid merging files from different backup sets or inventing request identifiers.

Targeted fix

Resolve the underlying condition directly: choose an empty destination or deliberately manage the existing set through the supported workflow. A player reinstall, reboot or new license request is useful only when it changes the condition “backup exists” and can be verified against the original evidence.

Nearby results with different meanings

Technical references

• Backing up and restoring licenses.
• Backup/restore model and eligibility.
• DRM client interfaces — API and state rules for the DRM operation described here.
• DRM client structures.