| Previous | Next |
| ERROR_VID_DUPLICATE_HANDLER | ERROR_VID_QUEUE_FULL |
ERROR_VID_TOO_MANY_HANDLERS
ERROR_VID_TOO_MANY_HANDLERS is HRESULT 0xC0370002 in the VID handler capacity area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: the maximum number of host-side message handlers accepted by VID. Record the first returning operation and host-side event before a management layer retries or translates it.
Why this HRESULT is specific
Registration reached the handler limit. Determine whether the workload legitimately exceeds a platform bound or whether handlers leak across VM, partition, or service lifecycles.
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: DUPLICATE_HANDLER indicates one colliding key; TOO_MANY_HANDLERS can occur with distinct registrations that cumulatively exhaust capacity.
Records worth collecting
| Evidence | Why it changes the diagnosis |
|---|---|
| Handler inventory | Count active handlers by partition, message type, and owner generation. |
| Lifecycle balance | Record successful register/unregister totals and failures during rollback. |
| Scale trigger | Keep VM count, devices, queues, and the exact registration number that fails. |
| Host history | Note repeated migrations, restores, worker crashes, or service restarts. |
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.
A reproducible test plan
- Run a create/destroy loop and verify the active count returns to baseline.
- Stop one controlled VM and see whether capacity is released.
- Reduce optional handler registrations without changing the failing core path.
- Collect traces before restarting VMMS or the host.
Exercise this result with bounded producers and a fully instrumented consumer. Preserve message ordering, queue generation, handler ownership, target VP, and acknowledgement timestamps while changing only one concurrency condition.
Comparison matrix
Across these controls for it, preserve the maximum number of host-side message handlers accepted by VID as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Single producer and consumer — this result | If it disappears with serialized ownership, the queue, handler, acknowledgement, or delivery race is implicated. | Preserve message type, partition, target VP, and queue capacity for it. |
| Fresh channel generation — it | A new queue or handler generation changing it points to stale registration, backlog, or incomplete teardown. | Keep payload, producer order, and host build unchanged in the result test. |
| Controlled stall or burst — it | Deliberately slow the consumer or bound the producer rate. The threshold at which it appears identifies backpressure versus lifecycle failure. | Record queue depth, oldest-item age, and acknowledgement timing. |
Misleading shortcuts
A VM or service restart can empty queues and replace handler generations, temporarily hiding it. Before clearing the result channel, capture depth, oldest item, owner, delivery sequence, and acknowledgement state.
A handle observed is generation-bound. Keep its parent partition and object type beside the token; never serialize it, copy it to another partition, or reuse it after the terminal transition.
Verification after repair
Resolution requires stable handler counts over lifecycle stress and successful registration at the intended maximum supported scale. 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 TLFS: inter-partition communication — used to interpret the boundary.
- Microsoft TLFS: HV_MESSAGE — 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.