drive letter for the existing mount points and place it in the user accounts startup folder. This is not preferred, as the mapping only appears at the end of user logon. Here is an example: @ECHO off SUBST f: d:\mount\db SUBST g: d:\mount\log The user must log off and back on or the service must be restarted for the changes to take effect. Run on boot (registry) Edit the registry to run the built-in subst command during computer startup or user logon by leveraging the appropriate Run registry key. The easiest way to do this is to create a registry file (.reg), and double click the file to import the settings into the registry. This is not preferred, as the mapping only appears at the end of bootup. Example to run during computer boot REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "F Drive"="SUBST f: d:\\mount\\db" "G Drive"="SUBST g: d:\\mount\\log" The computer must be rebooted for the changes to take effect. Example of user logon REGEDIT4 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "F Drive"="SUBST f: d:\\mount\\db" "G Drive"="SUBST g: d:\\mount\\log" The user must log off and back on for the changes to take effect. Limitations Windows actions which act on disks at the physical layer are not possible. Since (at least) Microsoft Windows XP SP2 autorun.inf files present in the new drive letter are ignored; thus, AutoRun/AutoPlay does not work on drive letters created in this way. In addition, assigning a custom icon or label to the drive letter created this way via autorun.inf does not work. A custom label assigned to the drive letter created with subst only appears if the source drive/volume does not have a volume label set (check and set with the label command). Starting with Windows Vista, deleted files are immediately deleted permanently, and are not moved to the Recycle Bin. Prior to Windows Vista (in Windows XP, for example) files from substituted "disks" were moved to the Recycle Bin when deleted. A registry entry could be added to re-enable the Recycle Bin. Files or folders on drives created this way may have different access rights. Software installations may not work correctly, because the Config.msi directory created by the windows installer can not be accessed properly. Log files can not be written although the executing user has administrative rights. See also Drive letter assignment Floating drive Load drive NTFS symbolic link References Further reading External links subst | Microsoft Docs SS64.com about "subst" psubst tool for