| Previous | Next |
| STATUS_VID_STOP_PENDING | STATUS_VID_EXCEEDED_KM_CONTEXT_COUNT_LIMIT |
STATUS_VID_INVALID_PROCESSOR_STATE
The virtual processor is in the wrong state for the operation
STATUS_VID_INVALID_PROCESSOR_STATE means the VP exists, but the requested operation cannot be applied in its current lifecycle state.
The requested operation is incompatible with the current state of an existing virtual processor in the VID partition. Capture the VP run/stop/reset transition immediately before the failure and compare it with the API or management action being attempted instead of treating the code as a CPU hardware fault.
Examples of relevant transitions include create, setup, run, suspend, stop, reset, and teardown. The exact invalid state depends on the operation that returned the status.
What to inspect
- Record the VP index, partition state, and requested operation.
- Check whether a reset, save, or stop overlapped with a run or register operation.
- Distinguish this from
STATUS_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED, which is about count rather than state.
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.