| Previous | Next |
| ERROR_VID_SAVED_STATE_CORRUPT | ERROR_VID_SAVED_STATE_INCOMPATIBLE |
ERROR_VID_SAVED_STATE_UNRECOGNIZED_ITEM
ERROR_VID_SAVED_STATE_UNRECOGNIZED_ITEM is HRESULT 0xC0370028 in the Hyper-V saved-state format recognition area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: a record or item in saved runtime state that the current Hyper-V reader does not recognize. Record the first returning operation and host-side event before a management layer retries or translates it.
Locate the failing boundary
The state stream contains a structurally identifiable item whose type/version is unknown to this host. Investigate host build, VM configuration version, device state, and how the files were moved or restored.
Hyper-V architecture documentation identifies VID as the component that provides partition, virtual-processor, and memory-management services., many ERROR_VID_* values describe internal host objects rather than a public API that administrators should call directly. Accordingly, diagnose this result through the named object/state, the VMMS or Worker event chain, and the operation that produced it; do not invent a user-mode VID call from the constant name.
Neighboring result: CORRUPT means the data cannot be trusted/read as intact; INCOMPATIBLE is broader platform incompatibility. UNRECOGNIZED_ITEM points to a specific format element the reader cannot interpret.
Build an incident record
| Evidence | Why it changes the diagnosis |
|---|---|
| Source and target hosts | Record Windows build, Hyper-V updates, architecture, and CPU vendor. |
| VM configuration version | Keep Get-VMHostSupportedVersion/Get-VM data and import history. |
| Saved-state provenance | Record host that created it, checkpoint/backup product, and copy method. |
| Device inventory | Capture virtual devices or features that may contribute versioned saved state. |
Preserve identifiers and counts without dumping guest secrets or unrelated memory. Useful this result timestamps include the last successful operation, first failure, any automatic retry, and the object-generation change that followed.
Run narrow checks
- Try supported import/compatibility checks rather than copying runtime files manually.
- Patch source and target hosts to an intentionally compatible level.
- Use Compare-VM or documented import workflows where applicable.
- If discarding state, preserve a copy and accept loss of volatile execution state.
Work from copies while diagnosing this result. Before changing it state, capture source host, target host, VM version, processor features, storage integrity, and relevant event logs.
Interpret three controls
Across these controls for it, preserve a record or item in saved runtime state that the current Hyper-V reader does not recognize as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Supported compatibility check — this result | Compare-VM, import checks, or configuration-version data can separate it incompatibility from unreadable state. | Preserve source/target host facts before upgrading or discarding state. |
| Boot after explicit state discard — it | Starting from virtual disks can establish that it is confined to volatile runtime state, but it deliberately loses that state. | Copy the affected state first and do not call this a format repair for it. |
| Original host versus destination — it | If it restores only on the source host, compare CPU features, Windows build, configuration version, and virtual devices. | Use an untouched copy of the saved-state and configuration files for it. |
Keep neighboring states separate
Do not delete saved state merely to clear it before making a copy and accepting loss of volatile guest state. In a it recovery, virtual disks remain separate, but guest applications may still require consistency checks after boot.
Prove the correction
The VM restores on a compatible host or starts cleanly after an explicit saved-state discard, and a new save/restore cycle is readable on the intended fleet. Repeat the original operation under the original supported conditions and retain one deliberate negative control. A management command succeeding on a different object is not sufficient to close this incident.
Technical references
These sources define it and the compatibility, processor, and saved-state recovery boundaries used in the diagnosis.
- Microsoft Open Specifications: HRESULT values — used to interpret the boundary.
- Microsoft: Remove-VMSavedState — used to interpret the boundary.
- Microsoft: VM configuration version compatibility — used to interpret the boundary.
- Microsoft: Hyper-V processor compatibility — used to interpret the boundary.
Looking for a different code? Search another status or error code.