| Previous | Next |
| ERROR_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED | ERROR_VID_INVALID_PROCESSOR_STATE |
ERROR_VID_STOP_PENDING
ERROR_VID_STOP_PENDING is HRESULT 0xC037001C in the VID virtual-processor stop transition area of the Windows virtualization stack. The built-in message names the immediate result; the useful custom context is the exact boundary: a request to stop a virtual processor while an intercept or exit transition is still pending. Record the first returning operation and host-side event before a management layer retries or translates it.
Object lifecycle behind the result
The VP cannot reach the requested stopped state immediately because the virtualization stack must finish handling a pending intercept. Preserve the exit reason and cancellation sequence rather than issuing repeated stops.
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: INVALID_PROCESSOR_STATE means the requested operation does not fit the VP state generally. STOP_PENDING identifies a transitional condition with outstanding intercept work.
Diagnostic evidence matrix
| Evidence | Why it changes the diagnosis |
|---|---|
| VP identity | Record partition, VP index, thread, and generation. |
| Pending intercept | Capture exit reason, message, or emulation work not yet completed. |
| Stop request | Keep initiator, timestamp, and desired VM transition. |
| Cancellation path | Record whether run cancellation, device completion, or acknowledgement was issued. |
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.
Test one variable at a time
- Request cancellation/exit through the supported VP run path.
- Complete or abort intercept handling before final teardown.
- Serialize stop with device-emulation callbacks.
- Test stop during each major exit reason under instrumentation.
Reduce this result to one partition and as few VPs as possible. In the result trace, instrument each run, exit, cancel, stop, reset, and delete transition so an asynchronous completion is not mistaken for an immediate state change.
How to read the controls
Across these controls for it, preserve a request to stop a virtual processor while an intercept or exit transition is still pending as the boundary under test.
| Control | Interpretation | Hold constant |
|---|---|---|
| One VP versus target count — this result | If it appears only as processors are added, record the first failing index and capability/configuration limit. | Keep partition properties and host topology fixed. |
| Clean partition generation — it | A fresh partition changing it points to stale VP state, pending exits, or incomplete deletion rather than guest code. | Use identical VP indexes, registers, and run sequence in the result comparison. |
| Instrumented run/stop race — it | Control run, cancel, intercept completion, stop, reset, and delete order. The first illegal transition explains it. | Keep one VP and one deterministic exit reason until ordering is proven. |
Boundaries of this status
Repeated start/stop commands can obscure the first illegal VP transition behind it. Preserve run-thread, exit reason, pending intercept, cancellation, and state-completion order.
Regression proof
The VP reaches stopped state after pending work drains, without repeated stop storms or lost intercept completion. 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: WHvCreateVirtualProcessor — used to interpret the boundary.
- Microsoft: WHvRunVirtualProcessor — used to interpret the boundary.
- Microsoft: WHvCancelRunVirtualProcessor — used to interpret the boundary.
Looking for a different code? Search another status or error code.