| Previous | Next |
| ERROR_VID_CHILD_GPA_PAGE_SET_CORRUPTED | ERROR_VID_INVALID_NUMA_NODE_INDEX |
ERROR_VID_INVALID_NUMA_SETTINGS
ERROR_VID_INVALID_NUMA_SETTINGS is HRESULT 0xC037000F in the Hyper-V virtual NUMA configuration area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: the relationship between configured virtual NUMA nodes and the physical host NUMA topology. Record the first returning operation and host-side event before a management layer retries or translates it.
Locate the failing boundary
The configured node count, processors per node, memory per node, or related limits cannot be represented on this host. This is a configuration validity failure, not merely a performance advisory.
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_NODE_INDEX identifies one bad node reference. REMOTE_NODE_PARENT_GPA_PAGES_USED can describe a running but nonlocal placement. INVALID_NUMA_SETTINGS prevents a valid start/configuration transition.
Build an incident record
| Evidence | Why it changes the diagnosis |
|---|---|
| Host topology | Record physical NUMA nodes, logical processors, and memory per node. |
| VM topology | Keep vCPU count, virtual NUMA nodes, max processors/node, and max memory/node. |
| Dynamic Memory | Record whether enabled and how startup/maximum memory interact with virtual NUMA. |
| Mobility target | Capture source/destination host topology after migration or hardware change. |
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
- Return virtual NUMA settings to automatic defaults as a controlled comparison.
- Ensure no configured node exceeds host-supported processor or memory limits.
- Compare every cluster node if the VM can move.
- Do not treat NUMA spanning as a universal correction for an invalid topology.
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.
Interpret three controls
Across these controls for it, preserve the relationship between configured virtual NUMA nodes and the physical host NUMA topology as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Local versus cross-node placement — this result | 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. |
| Every intended destination host — it | 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. |
Keep neighboring states separate
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.
Prove the correction
The VM starts on every intended host with a topology that matches the workload design and remains valid after restart/migration. 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.