| Previous | Next |
| ERROR_VID_INVALID_CHILD_GPA_PAGE_SET | ERROR_VID_RESERVE_PAGE_SET_TOO_SMALL |
ERROR_VID_RESERVE_PAGE_SET_IS_BEING_USED
ERROR_VID_RESERVE_PAGE_SET_IS_BEING_USED is HRESULT 0xC0370023 in the VID reserve page-set lifetime area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: destruction or reuse of a reserve page set that currently backs an active lock or mapping. Record the first returning operation and host-side event before a management layer retries or translates it.
Locate the failing boundary
The reserve set has an outstanding consumer. Find the lock/mapping that borrowed its pages and complete that lifecycle before reclaiming the set.
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: RESERVE_PAGE_SET_TOO_SMALL concerns capacity at acquisition. IS_BEING_USED concerns ownership at destruction or reuse.
Build an incident record
| Evidence | Why it changes the diagnosis |
|---|---|
| Reserve set identity | Record page count, owner partition, and creation generation. |
| Current borrower | Capture memory block, GPA range, lock, and operation using it. |
| Acquire/release timeline | Keep reservation, use, completion, and release events. |
| Teardown caller | Record why reuse or destruction was attempted early. |
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
- Make reserve-set borrowing explicit and reference-counted.
- Release only after the dependent lock/unmap completes.
- Avoid sharing one mutable reserve set across unsynchronized operations.
- Test cancellation and VM stop while the set is borrowed.
Use a controlled partition or disposable VM when a mapping, lock, or teardown test can be destructive. During the result run, keep page units, GPA boundaries, parent object, handle generation, and release order visible.
Interpret three controls
Across these controls for it, preserve destruction or reuse of a reserve page set that currently backs an active lock or mapping as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Smaller exact range — this result | Reduce only page count or mapped extent. If this result moves, range arithmetic, object limits, or reserve capacity is involved. | Keep the same block, GPA base, flags, and partition generation for it. |
| Balanced fresh lifecycle — it | Create, use, release, and destroy one object generation. A different it exposes leaked references, locks, handles, or mappings. | Preserve sizes and operation order while changing only generation. |
| Same request under lower host pressure — it | If it changes after controlled pressure is removed, quantify host/pool capacity; if not, focus on caller bookkeeping. | Do not modify guest disks or unrelated VM devices during the result comparison. |
Keep neighboring states separate
Restarting can release the exact lock, reference, mapping, or opaque handle behind it without fixing the lifecycle defect. Before recovering from it, preserve the object graph and acquire/release counts.
Prove the correction
The reserve set is reclaimed only at zero borrowers and repeated use does not leak or overlap ownership. 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 public Hyper-V architecture surrounding the internal state. They do not create a public user-mode VID API for the named object.
- Microsoft Open Specifications: HRESULT values — used to interpret the boundary.
- Microsoft: WHvMapGpaRange — used to interpret the boundary.
- Microsoft: WHP memory data types — used to interpret the boundary.
- Microsoft: Hyper-V architecture — used to interpret the boundary.
Looking for a different code? Search another status or error code.