| Previous | Next |
| VDS_E_INITIALIZE_NOT_CALLED | VDS_E_ALREADY_REGISTERED |
VSS_E_ASRERROR_DISK_RECREATION_FAILED
Windows cannot recreate a required recovery disk. The recovery workflow has progressed beyond choosing candidate disks, but Windows cannot create the disk structure needed to represent a disk stored in the backup.
The documented condition is: “Windows cannot create a disk on this computer needed to restore from the backup. Make sure the disks are properly connected, or add or change disks, and try the restore again.”
Where VSS_E_ASRERROR_DISK_RECREATION_FAILED appears
This is a disk-recreation failure during Automated System Recovery. It is later than capacity matching: a target may be visible and large enough, yet layout creation, metadata updates or access to the device still fails.
Likely causes
- The selected disk is read-only, offline, write-protected or controlled by a storage policy that prevents layout changes.
- A controller, path or media error interrupts partition-table or volume creation.
- Stale disk metadata conflicts with the layout that ASR is attempting to reconstruct.
- The recovery environment can enumerate the device but lacks a fully functional driver for destructive management operations.
Evidence to capture before changing storage
- Save the selected disk number, bus type, serial number, capacity and current partition style.
- Capture DiskPart detail and System event-log entries generated at the first failed create or metadata operation.
- Record whether the disk is basic, dynamic, virtual, clustered, read-only or presented through multipath storage.
- Preserve the underlying storage HRESULT or Win32 error before the recovery UI maps it to this VSS value.
Diagnostic sequence
- Confirm that the intended target, not an unrelated data disk, received focus.
- Check online and read-only state before considering cleanup of existing metadata.
- Run vendor diagnostics or inspect controller events when the same write fails outside ASR.
- Use a disposable test disk to distinguish backup-layout incompatibility from a device-specific fault.
Recovery and retry
Correct the device state, load the proper driver, or replace a failing target, then restart the restore from a clean recovery session. Disk cleaning is destructive and should be performed only after identity and backup coverage have been verified.
What this HRESULT does not prove
The code does not mean there are too few disks; assignment may already have succeeded. It also does not prove that the backup payload is corrupt, because the failure can occur while writing the target disk rather than reading backup data.
Difference from nearby VSS results
VSS_E_ASRERROR_DISK_ASSIGNMENT_FAILED stops before a target can be chosen. VSS_E_ASRERROR_NO_PHYSICAL_DISK_AVAILABLE means no fixed candidate is visible, whereas this result concerns a chosen disk that cannot be recreated.
Practical example
Windows RE detects a correctly sized disk through a storage controller, but the controller exposes it read-only. ASR assigns the disk and then fails when it attempts to write the partition table, producing this HRESULT.
Guidance for backup software and telemetry
Log both phases separately: candidate selection and disk recreation. The distinction prevents operators from adding capacity when the actual problem is write access or device health.
Official Microsoft references
Looking for a different code? Search another status or error code.