| Previous | Next |
| ERROR_VID_QUEUE_FULL | ERROR_VID_INVALID_OBJECT_NAME |
ERROR_VID_HANDLER_NOT_PRESENT
ERROR_VID_HANDLER_NOT_PRESENT is HRESULT 0xC0370004 in the VID handler lookup area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: dispatch of a VID message for which no current handler is registered. Record the first returning operation and host-side event before a management layer retries or translates it.
What the code establishes
The queue delivered or attempted to route a message whose message class has no live owner in this partition/worker generation. Investigate initialization ordering, premature unregister, and stale messages.
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 and TOO_MANY_HANDLERS fail during registration. HANDLER_NOT_PRESENT appears at lookup or dispatch after the expected registration is absent.
Evidence that should survive remediation
| Evidence | Why it changes the diagnosis |
|---|---|
| Message class | Record type, version, source, target, and queue sequence. |
| Registration timeline | Keep expected register time, unregister time, and dispatch time. |
| Owner generation | Identify VM worker, partition, or module generation that should own the callback. |
| Stale backlog | Determine whether the message predates a reset, migration, or handler replacement. |
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.
Controlled diagnostic sequence
- Assert handler registration completes before producers can enqueue the message class.
- Drain or version queues across worker/partition replacement.
- Verify rollback does not unregister a handler owned by another successful path.
- Use one deliberately unknown message as a negative dispatch test.
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.
Read the comparison tests
Across these controls for it, preserve dispatch of a VID message for which no current handler is registered as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| Controlled stall or burst — this result | 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. |
| 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. |
Avoid the wrong recovery
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.
Acceptance test
The original class consistently resolves to the intended current-generation handler, while stale or unknown classes are rejected before state mutation. 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.