| Previous | Next |
| STATUS_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED | STATUS_VID_INVALID_PROCESSOR_STATE |
STATUS_VID_STOP_PENDING
A virtual processor stop is waiting on an intercept
STATUS_VID_STOP_PENDING is a virtual-processor scheduling and intercept state. Hyper-V may be waiting for an intercepted operation to finish before it can stop the VP cleanly.
VID cannot finish stopping the virtual processor immediately because an intercept is still pending. Identify the pending intercept and the VP that owns it, then correlate completion or cancellation with the stop request; the code describes a temporary run-state dependency rather than a missing processor.
The status is useful because it separates a pending stop from a hard failure to locate the VP or create it. The next evidence to collect is the intercept or run state that prevents immediate stop.
What to inspect
- Check whether the VM is stopping, pausing, saving, or resetting while a device or MMIO intercept is active.
- Capture the VP index and the last exit/intercept reason available from the virtualization layer.
- Look for a blocked emulator or device backend that is preventing completion of the intercepted operation.
References
- Microsoft: WHvCreateVirtualProcessor
- Microsoft: WHvResetPartition
- Microsoft: Windows Hypervisor Platform API definitions
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.