You can configure the App Volumes agent to interact with mapped volumes by using a system path to the volume, instead of mapping it to a drive letter.
Most modern applications are compatible with this behavior, but some applications might require a drive letter to access program or application files. To support such situations while maintaining the familiar user interface, App Volumes can hide the drive from Windows Explorer after it is mapped.
Configure this behaviour with the DriveLetterSettings registry value. The value for DriveLetterSettings is in a hexadecimal format, and any number of flags might be combined to implement multiple parameters. For example, if you want to use the 0x00000001 and 0x00000008 flags, the result is 0x00000009. Enter this as 9 because you only work with the significant digits.
|0x0000001||DRIVELETTER_REMOVE_WRITABLE. Do not assign drive letter for writable volumes.|
|0x0000002||DRIVELETTER_REMOVE_READONLY. Do not assign drive letter for AppStack volumes.|
|0x0000004||DRIVELETTER_HIDE_WRITABLE. Hide drive letter for writable volumes.|
|0x0000008||DRIVELETTER_HIDE_READONLY. Hide drive letter for AppStack volumes.|
The default registry value is 3. This means that for writable volumes, the drive letter is hidden, and for AppStackvolumes, the drive letter is not assigned.