| Previous | Next |
| STATUS_VID_MBP_COUNT_EXCEEDED_LIMIT | STATUS_VID_SAVED_STATE_UNRECOGNIZED_ITEM |
STATUS_VID_SAVED_STATE_CORRUPT
The Hyper-V saved state cannot be read reliably
STATUS_VID_SAVED_STATE_CORRUPT identifies the saved-state data, not the guest virtual hard disk, as the object that cannot be read reliably.
VID cannot reliably read the saved runtime state needed to resume the virtual machine, while the VM's virtual disks are a separate resource. Preserve evidence about the saved-state files and storage errors before removing that state; Microsoft documents that deleting saved state loses memory contents but leaves virtual hard disks unaffected.
Microsoft troubleshooting guidance for this class of failure explicitly treats deleting saved state as a recovery step when a VM cannot be restored from that state.
What to inspect
- Preserve the VM configuration, checkpoint tree, and saved-state files before making destructive changes.
- Check storage, antivirus, backup, and checkpoint events around the time the saved state was written.
- After recovery, verify whether the VM boots cleanly from disk rather than assuming disk corruption from this status alone.
References
- Microsoft: Hyper-V live migration troubleshooting
- Microsoft: restored Hyper-V virtual machines will not start
- Microsoft: Hyper-V architecture
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.