| Previous | Next |
| VDS_E_INCORRECT_SYSTEM_VOLUME_EXTENT_INFO | VDS_E_VOLUME_SHRINK_FVE_LOCKED |
VDS_E_SYSTEM_DISK
This HRESULT is another critical-role protection, but its message is broader than VDS_E_BOOT_DISK: it covers the current system disk or BIOS disk 0. VDS publishes distinct flags for system disk, boot disk, boot-from-disk, and firmware visibility. A management program should therefore avoid collapsing all of these conditions into the single label “OS disk.”
Why this state matters
The rejected operation is a disk-attribute change. The right diagnostic is to capture the current VDS flags and firmware/boot role before deciding whether maintenance must occur from another boot environment. Disk numbering shown by management tools is not a sufficient substitute for VDS role detection, particularly after cloning or changes to BIOS/EFI boot order.
Diagnostic focus
- Record the complete
VDS_DISK_FLAGmask for the target disk. - Distinguish SYSTEM_DISK from BOOT_DISK and BOOT_FROM_DISK in logs and user-facing diagnostics.
- Identify which disk attribute change was attempted and whether it can safely be performed from offline maintenance.
- Do not try to bypass the rejection by changing SAN policy or clearing read-only flags on a critical system disk.
Technical references
VDS_DISK_FLAG · VDS_DISK_PROP · VDS common return codes · MS-VDS error codes · IVdsDisk::GetProperties
Looking for a different code? Search another status or error code.