| Previous | Next |
| VDS_E_INVALID_IP_ADDRESS | VDS_E_VOLUME_GUID_PATHNAME_NOT_ALLOWED |
VDS_E_REBOOT_REQUIRED
The VDS catalog is unusually explicit for this HRESULT: a reboot is required before further operations are initiated, and machine behavior and state are undefined for additional VDS work without it. This is not an ordinary transient error with a retry delay. Continuing to mutate storage can make later failures impossible to interpret because the service has already declared the current machine state unsafe for further operations.
Why this state matters
A robust management client should stop its transaction or job at this boundary, persist enough context to resume after startup, and report the reboot requirement as the primary result. Refreshing VDS, reenumerating disks, or recreating the COM object is not equivalent to rebooting the operating system.
Diagnostic focus
- Stop issuing state-changing VDS methods after this HRESULT is observed.
- Persist the operation identity, target disk/volume IDs, and last completed step before requesting a reboot.
- After reboot, reacquire VDS objects and revalidate the entire storage topology before resuming.
- Do not automatically replay the failed call without checking whether the previous operation partially changed disk or volume state.
Technical references
MS-VDS error codes · VDS common return codes · IVdsService::Refresh · IVdsService::Reenumerate · VDS_DISK_PROP
Looking for a different code? Search another status or error code.