| Previous | Next |
| ERROR_VID_INVALID_NUMA_SETTINGS | ERROR_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED |
ERROR_VID_INVALID_NUMA_NODE_INDEX
ERROR_VID_INVALID_NUMA_NODE_INDEX is HRESULT 0xC0370010 in the Hyper-V NUMA node addressing area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: a NUMA node index supplied to VID that is outside the current host or configured topology. Record the first returning operation and host-side event before a management layer retries or translates it.
State and ownership model
The referenced node does not exist in the topology generation used by the operation. Look for off-by-one errors, stale cached topology, and assumptions carried across hosts.
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: INVALID_NUMA_SETTINGS concerns the full topology; INVALID_NUMA_NODE_INDEX isolates one numeric node reference.
Capture before changing anything
| Evidence | Why it changes the diagnosis |
|---|---|
| Requested index | Record the numeric node index and operation. |
| Enumerated topology | Keep node count and identifiers from the same host and time. |
| Cache generation | Record when topology was queried relative to hardware, firmware, or migration changes. |
| Loop bounds | Capture zero/one-based conversions and selected-node algorithm. |
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.
Reduce the case safely
- Validate index < current node count immediately before use.
- Do not persist host-local NUMA indexes across migration.
- Test single-node and sparse/high-node-count hosts.
- Prefer stable topology data structures over inferred socket numbers.
Evaluate this result with the same workload and VM size while varying only documented NUMA configuration or placement. Record topology on every intended host rather than inferring it from socket labels.
What comparison can tell you
Across these controls for it, preserve a NUMA node index supplied to VID that is outside the current host or configured topology as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Every intended destination host — this result | A it that follows one node indicates a host-local topology or placement constraint. | Use the same VM configuration and record each host NUMA layout in the result test. |
| Local versus cross-node placement — it | Measure workload latency and throughput under both placements. This distinguishes a it correctness failure from a performance advisory. | Hold guest workload and processor affinity stable while comparing it. |
| Automatic versus explicit virtual NUMA — it | If automatic topology removes it, compare each overridden node count, processor limit, and memory limit with host topology. | Keep VM vCPU count, memory, Dynamic Memory mode, and workload fixed for it. |
Do not erase the evidence
A restart can change placement and make it disappear once without proving the topology is valid or performance is stable. Close the result investigation only after repeatable placement and workload comparisons.
Closure criteria
All selections come from current enumeration, boundary tests reject node_count, and migration refreshes host-local indexes. 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: NUMA and Hyper-V virtual machines — used to interpret the boundary.
- Microsoft: configure virtual NUMA — used to interpret the boundary.
- Microsoft: troubleshoot Hyper-V VM performance — used to interpret the boundary.
Looking for a different code? Search another status or error code.