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 behavior with the DriveLetterSettings, an svdriver parameter.
By default, a drive letter is not assigned to either application packages or Writable Volumes.
A Writable Volume can be assigned a drive letter.
App Volumes agent assigns any available drive letter, starting from
Administrators can assign a specific drive letter to a Writable Volume using the svservice parameter, DriveLetter. For more information about this parameter, see Parameters for Configuring svservice.
Hide drive letter for Writable Volumes.
Hide drive letter for AppStack volumes.
For more information about DriveLetterSettings, see Parameters for Configuring svdriver.