| Previous | Next |
| STATUS_VID_SAVED_STATE_UNRECOGNIZED_ITEM | STATUS_VID_VTL_ACCESS_DENIED |
STATUS_VID_SAVED_STATE_INCOMPATIBLE
The saved state is incompatible with this hypervisor
STATUS_VID_SAVED_STATE_INCOMPATIBLE is a compatibility failure, not merely a read failure. VID recognized that the saved state cannot be resumed on the current hypervisor environment.
VID can identify the saved state but cannot resume it in the current hypervisor environment because the recorded execution context is incompatible. Compare source and target host capabilities, Windows build, processor features, and VM configuration changes; a cold start from the virtual disks is distinct from successfully restoring suspended memory state.
Typical dimensions to compare are host build, processor capabilities, VM configuration version, Hyper-V feature set, and whether the VM moved between hosts with different hardware capabilities.
What to inspect
- Compare the source host and target host: Windows build, CPU generation, virtualization features, and VM configuration version.
- Check whether processor compatibility mode or cluster placement policy is relevant for the VM.
- Plan recovery as a cold boot from disk if saved-state resume is impossible.
References
- Microsoft: Hyper-V live migration troubleshooting
- Microsoft: restored Hyper-V virtual machines will not start
- Microsoft: Windows Hypervisor Platform API definitions
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.