| Previous | Next |
| ERROR_VID_PARTITION_ALREADY_EXISTS | ERROR_VID_PARTITION_NAME_NOT_FOUND |
ERROR_VID_PARTITION_DOES_NOT_EXIST
ERROR_VID_PARTITION_DOES_NOT_EXIST is HRESULT 0xC0370009 in the VID partition handle lifecycle area of the Windows virtualization stack. It applies to an operation referencing a partition object that has already been removed or was never created in this host generation.
What the code establishes
The requested partition identity cannot be resolved to a live VID partition. Common boundaries are stale handles, teardown races, and operations arriving after VM worker replacement.
Neighboring result: PARTITION_NAME_NOT_FOUND emphasizes name lookup; DOES_NOT_EXIST is the broader absence of the partition object expected by the operation.
Evidence that should survive remediation
| Evidence | Why it changes the diagnosis |
|---|---|
| Partition handle and ID | Record numeric/opaque handle, VM ID, name, and generation. |
| Creation success | Keep the result and timestamp of the create/setup path. |
| Removal event | Locate delete, crash cleanup, migration, or service restart that ended the generation. |
| Late caller | Capture the operation that used the stale reference and its synchronization owner. |
Controlled diagnostic sequence
- Invalidate cached handles atomically when partition teardown starts.
- Reject late work at the queue boundary using generation tokens.
- Test concurrent stop with memory, VP, and queue operations.
- Reopen through the supported management path instead of fabricating a handle.
Read the comparison tests
| Control | Interpretation | Hold constant |
|---|---|---|
| Fresh owned object | A clean lifecycle changing this result implicates duplicate initialization, leaked ownership, stale lookup, or incomplete rollback. | Preserve request flags and topology while changing only object instance. |
| Same request on a compatible host | If it follows one host, compare resource limits, topology, build, and inventory before altering VM data. | Use the same request and leave virtual disks unchanged in the result comparison. |
| One operation parameter | Change one count, name, identity, or state transition. If it moves, the selected condition is causal rather than the VM as a whole. | Keep host build, VM ID, and returning operation fixed. |
Avoid the wrong recovery
Acceptance test
No operation crosses the teardown generation, and a new partition receives fresh handles that stale work cannot use.
Technical references
- Microsoft Open Specifications: HRESULT values — used to interpret this result.
- Microsoft: Hyper-V architecture — used to interpret this result.
- Microsoft: Hyper-V TLFS — used to interpret this result.
- Microsoft: Hyper-V operational troubleshooting — used to interpret this result.
Looking for a different code? Search another status or error code.