| Previous | Next |
| VDS_E_REFS_FORMAT_NOT_SUPPORTED | VDS_E_FORMAT_WITH_BOOTBACKING |
VDS_E_DELETE_WITH_BOOTBACKING
This protection is about backing dependency, not merely the volume that directly contains C:\Windows. VDS distinguishes critical storage roles and can reject deletion when the target volume underlies the Windows boot volume. That dependency must be resolved at the storage-topology level; checking the target volume label or drive letter is not enough.
Why this state matters
Before attempting deletion, enumerate the target volume, its pack, plexes, and extents and identify how the boot volume depends on them. In layered or dynamic storage, the visible boot volume can be composed from lower-level disk regions that do not look like the ordinary C: access path. The correct resolution is to change the boot/storage design or migrate the dependency, then re-evaluate the target object.
Diagnostic focus
- Map the boot volume to its VDS plexes and disk extents.
- Identify whether the deletion target contributes backing storage to that topology.
- Use volume GUIDs and extents rather than friendly names or drive letters.
- Do not bypass the protection until the boot dependency has been migrated and verified.
Technical references
MS-VDS error codes · VDS Volume Object · VDS_VOLUME_PLEX_PROP · VDS_VOLUME_PROP · BCDBoot command-line options
Looking for a different code? Search another status or error code.