| Previous | Next |
| VDS_E_REBOOT_REQUIRED | VDS_E_BOOT_PAGEFILE_DRIVE_LETTER |
VDS_E_VOLUME_GUID_PATHNAME_NOT_ALLOWED
Windows volumes have stable volume GUID names, but not every VDS method accepts that syntax as an input access path. This HRESULT is a method contract failure: the caller supplied a volume GUID pathname where the selected operation expects another path form. It should not be translated into “volume GUID is invalid” or “volume does not exist.”
Why this state matters
VDS access-path methods manage drive letters and mounted-folder paths on a volume. Keep the volume identity used to select the VDS object separate from the path string passed to the method. Logging both values usually exposes wrappers that accidentally feed a canonical volume name back into an API that expects a mount path.
Diagnostic focus
- Log the exact path string, including trailing backslash and prefix, passed to the failing VDS method.
- Identify the method contract and use a drive-letter or mounted-folder access path when required.
- Keep the
VDS_VOLUME_PROP2volume GUID as object identity rather than blindly reusing it as every path parameter. - Distinguish this syntax rejection from
VDS_E_PATH_NOT_FOUND, which occurs after a path form has been accepted for lookup.
Technical references
VDS_VOLUME_PROP2 · IVdsVolumeMF::AddAccessPath · IVdsVolumeMF::DeleteAccessPath · MS-VDS error codes · VDS common return codes
Looking for a different code? Search another status or error code.