| Previous | Next |
| STATUS_VID_QUEUE_FULL | STATUS_VID_INVALID_OBJECT_NAME |
STATUS_VID_HANDLER_NOT_PRESENT
No handler exists for the VID message
STATUS_VID_HANDLER_NOT_PRESENT is the opposite side of the handler registration failures: a message reached VID, but the dispatch target was absent.
A VID message reached a dispatch path for which no handler is currently registered. Correlate handler registration and removal with queue delivery to determine whether initialization never completed or teardown removed the consumer before pending messages were drained.
This commonly points to ordering: a message arrived after teardown, before initialization completed, or after a component failed to register during an earlier setup step.
What to inspect
- Find whether partition teardown, device rescind, queue close, or service restart happened just before the failing message.
- Check whether the message belongs to an optional integration component that was disabled or failed to initialize.
- Do not diagnose this from inside the guest only; the missing object is in the host VID dispatch path.
References
- Microsoft TLFS: inter-partition communication
- Linux kernel documentation: VMBus
- Microsoft: Hyper-V architecture
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.