| Previous | Next |
| NS_E_DRM_BACKUP_CORRUPT | NS_E_BACKUP_RESTORE_BAD_DATA |
NS_E_DRM_BACKUPRESTORE_BUSY
This status belongs to DRM license-store serialization: a second backup or restore request arrived while an earlier backup/restore operation was still active.
A useful investigation order
- Prove the boundary by ensuring you can identify the active operation ID and its pending completion status.
- After you wait for or cancel the existing operation before starting another, verify both the requested right and the final store/device state.
State to capture before retry
- Protected identity: target machine identity and final license-store commit.
- Operation state: backup or restore operation ID.
- Persistence or transport: backup directory contents and manifest consistency.
- Security context: per-license backup/restore eligibility.
- Correlation point: service response, reset count and daily restore limit.
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
Representative case: Two application commands start restore against the same backup object.
Nearby results with different meanings
| Result | Different condition |
|---|---|
NS_E_BACKUP_RESTORE_BAD_DATA | Backup/restore data fails format or integrity validation. |
NS_E_DRM_BACKUP_CORRUPT | The backup set is incomplete or one of its protected members fails validation. |
NS_E_DRM_BACKUP_EXISTS | The selected backup location already contains a WMDRM backup set. |
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.
Looking for a different code? Search another status or error code.