| Previous | Next |
| ERROR_HV_NOT_PRESENT | ERROR_VID_TOO_MANY_HANDLERS |
ERROR_VID_DUPLICATE_HANDLER
ERROR_VID_DUPLICATE_HANDLER is HRESULT 0xC0370001 in the VID handler registration area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: registration of a host-side VID message handler that already has an owner. Record the first returning operation and host-side event before a management layer retries or translates it.
State and ownership model
The handler key or message class is already registered in the current virtualization-stack generation. Look for duplicate initialization, module reload, or teardown that failed to unregister.
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: TOO_MANY_HANDLERS is capacity exhaustion; HANDLER_NOT_PRESENT is lookup failure. DUPLICATE_HANDLER instead proves a matching registration already exists.
Capture before changing anything
| Evidence | Why it changes the diagnosis |
|---|---|
| Handler key | Record message class, callback identity, owner module, and target partition. |
| First registration | Keep the successful registration stack and generation. |
| Second registration | Capture the duplicate caller and whether it followed service restart, VM restore, or module reload. |
| Teardown symmetry | Compare unregister calls with successful registrations. |
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
- Make registration idempotent only if the existing owner is exactly the intended one.
- Pair every successful registration with teardown in the same object generation.
- Stress start/stop and failure rollback paths.
- Do not blindly ignore the code; an unexpected existing handler can route messages to stale state.
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.
What comparison can tell you
Across these controls for it, preserve registration of a host-side VID message handler that already has an owner as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Fresh channel generation — this result | 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. |
| Single producer and consumer — it | 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. |
Do not erase the evidence
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.
Closure criteria
The fix yields one active handler per key and repeated create/destroy cycles leave registration counts at baseline. 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.