Mountvol in Windows: How Volume Mount Points Work, Commands, Benefits, and Safety
QUICK ANSWER mountvol is a built-in Windows command for listing volumes and creating or removing volume mount points. A mount point can be a drive letter suc...
QUICK ANSWER
mountvol is a built-in Windows command for listing volumes and creating or removing volume mount points. A mount point can be a drive letter such as E: or an empty folder such as C:\Mounts\Data. Folder-based mount points let Windows expose another volume through an ordinary directory without assigning it a separate drive letter.
Run mountvol in an elevated Command Prompt to list volume GUID paths and their current mount points. Use /D to remove an access path safely. Treat /P, /N, /R, and especially /S as administrative operations because they can dismount volumes, change automatic mounting behavior, remove persistent associations, or expose the EFI system partition.
What Is Mountvol?
mountvol.exe is a Windows command-line utility that manages volume mount points. It can:
- List local volumes and their current access paths.
- Assign a volume to a drive letter.
- Mount a volume inside a folder.
- Remove a drive letter or folder mount point.
- Dismount and take a basic volume offline.
- Enable or disable automatic mounting of new basic volumes.
- Remove stale mount-point records.
- Temporarily assign a drive letter to the EFI system partition.
Microsoft supports mountvol on Windows 10, Windows 11, Windows Server 2016 and later, and supported Azure Local releases.
This command concerns Windows storage volumes. It is unrelated to mounting network shares, ISO images, Linux filesystems in WSL, or Docker volumes.
How Windows Volume Mount Points Work
Windows identifies each recognized volume by a persistent volume GUID path similar to:
\\?\Volume{2eca078d-5cbc-43d3-aff8-7e8511f60d0e}\
The GUID path identifies the volume independently of a familiar access path. Windows can then associate that volume with one or more mount points, including:
E:\
C:\Mounts\Data\
When a volume is mounted at C:\Mounts\Data, opening that folder redirects access to the root of the mounted volume. The files are physically stored on the mounted volume, not on the volume containing C:\Mounts.
A folder mount point does not merge the capacities of two volumes. The host volume and mounted volume remain separate filesystems with their own:
- Capacity and free space
- File-system metadata
- Permissions and ownership
- Encryption state
- Error conditions
- Backup and recovery requirements
Why Use Mountvol?
Avoid running out of drive letters
Windows offers a limited number of drive letters. Folder mount points allow many local volumes to be organized below paths such as:
C:\Storage\Applications
C:\Storage\Archives
C:\Storage\Logs
Preserve an application path
An additional volume can be mounted at an expected folder without changing the application’s configured path. For example, storage can be presented through C:\AppData\Database.
This does not guarantee application compatibility. Confirm that the application, installer, backup product, and monitoring tools support mounted volumes.
Organize server storage
Administrators can place related volumes under a consistent directory hierarchy instead of managing a long collection of drive letters.
Add storage without replacing the existing volume
A new volume can be made accessible below an existing directory structure. This adds another storage location but does not expand the filesystem or turn the volumes into a single fault-tolerant pool.
Use stable volume identifiers in administrative work
Volume GUID paths help distinguish volumes when drive letters can change, such as with removable media or multi-disk systems.
Requirements and Prerequisites
Before changing mount points:
- Open Command Prompt as an administrator.
- Verify the target volume by label, size, filesystem, existing path, and contents.
- Back up important data or confirm that a current backup exists.
- Stop applications actively using a mount point before removing it.
- Create an empty destination folder when using a folder mount point.
- For
mountvol, place the destination directory on an NTFS volume, as required by the command’s documented syntax. - Ensure that security, backup, monitoring, antivirus, and application software can traverse mounted volumes correctly.
Microsoft’s current Disk Management guidance requires membership in the Administrators or Backup Operators group to mount a drive or remove a mount point. In practice, run the relevant management interface or terminal elevated.
Mountvol Syntax
mountvol [<drive>:]<path> <volumename>
mountvol [<drive>:]<path> /D
mountvol [<drive>:]<path> /L
mountvol [<drive>:]<path> /P
mountvol /R
mountvol /N
mountvol /E
mountvol <drive>: /S
mountvol /?
Commands and switches are case-insensitive.
| Command or switch | Purpose |
|---|---|
mountvol |
Lists volume GUID paths and their current mount points |
<path> <volumename> |
Creates a drive-letter or folder mount point for a volume |
<path> /L |
Displays the volume GUID mounted at the specified path |
<path> /D |
Removes the specified mount point |
<path> /P |
Removes the mount point, dismounts the basic volume, and takes it offline |
/R |
Removes mount-point directories and registry records for volumes no longer present |
/N |
Disables automatic mounting of new basic volumes |
/E |
Re-enables automatic mounting of new basic volumes |
<drive>: /S |
Mounts the EFI system partition on the specified drive letter |
/? |
Displays command help |
How to List Volumes and Mount Points
Open an elevated Command Prompt and run:
mountvol
Typical output resembles:
\\?\Volume{GUID}\
C:\
\\?\Volume{GUID}\
D:\
\\?\Volume{GUID}\
*** NO MOUNT POINTS ***
Each \\?\Volume{GUID}\ entry is a volume name. Indented paths below it are the volume’s current access paths.
*** NO MOUNT POINTS *** means that Windows recognizes the volume, but it does not currently have a listed drive letter or folder mount point. Do not assume that such a volume is unused; it could be a recovery, system, reserved, or otherwise protected volume.
For additional verification, use Disk Management:
- Press
Windows+R. - Enter
diskmgmt.msc. - Review each volume’s size, label, filesystem, status, and current access paths.
How to Mount a Volume in a Folder
The following example mounts an existing volume at C:\Mounts\Data.
Step 1: Create an empty folder
mkdir C:\Mounts\Data
Do not use a folder containing files. After mounting, any existing folder contents would be hidden behind the mounted volume until the mount point is removed.
Step 2: Find the correct volume GUID
mountvol
Identify the target by matching its existing drive letter with the corresponding volume GUID. Cross-check it in Disk Management if there is any uncertainty.
Step 3: Create the mount point
Replace the sample GUID with the exact value reported on your computer:
mountvol C:\Mounts\Data \\?\Volume{2eca078d-5cbc-43d3-aff8-7e8511f60d0e}\
The trailing backslash in the volume GUID path is required.
If the folder path contains spaces, enclose it in quotation marks:
mountvol "C:\Mounted Volumes\Data" \\?\Volume{2eca078d-5cbc-43d3-aff8-7e8511f60d0e}\
Step 4: Verify the result
mountvol C:\Mounts\Data /L
The command should return the mounted volume’s GUID path. You can also open C:\Mounts\Data in File Explorer and confirm the expected contents.
How to Assign a Drive Letter
To make a volume available as X:, first confirm that the letter is unused, then run:
mountvol X: \\?\Volume{2eca078d-5cbc-43d3-aff8-7e8511f60d0e}\
Verify it with:
mountvol X: /L
Windows supports no more than one drive-letter assignment per volume, although a volume can also have folder mount points.
Changing an established drive letter can break shortcuts, services, scheduled tasks, applications, scripts, paging configurations, and backup jobs that reference the old path.
How to Remove a Mount Point Safely
To remove a folder mount point while leaving the volume otherwise mounted and available through any remaining access paths, use:
mountvol C:\Mounts\Data /D
To remove a drive-letter assignment:
mountvol X: /D
/D removes only the specified access path. It does not format the volume or delete its data.
Before removal:
- Stop applications and services using the path.
- Close open files.
- Confirm whether the volume has another valid access path.
- Update dependent scripts, services, shares, and backup jobs.
The destination folder normally remains after its mount point is removed. It can be reused or deleted separately after confirming that it contains nothing required.
Understanding /P: Dismount and Take Offline
The following command performs more than an ordinary mount-point removal:
mountvol C:\Mounts\Data /P
/P:
- Removes the specified mount point.
- Dismounts the basic volume.
- Takes the basic volume offline and makes it unmountable.
- Closes open handles if processes are using the volume.
This can interrupt applications and cause unsaved data, failed transactions, or service outages. Use /D when you only need to remove an access path.
If the volume has multiple mount points, Microsoft instructs administrators to remove the additional mount points with /D before using /P. The volume can be made mountable again by assigning it a new mount point.
Automatic Mounting: /N and /E
Windows normally assigns appropriate access paths to newly detected basic volumes. To disable this behavior:
mountvol /N
To re-enable it:
mountvol /E
These settings apply to automatic mounting of new basic volumes; they do not simply hide one selected disk.
Disabling automount can be useful in controlled deployment, forensic, imaging, or storage-management environments where newly attached volumes must not be automatically exposed. It may also leave newly connected storage without a drive letter, which can confuse users or applications.
Check the current output and test the expected behavior before using this setting in production.
Removing Stale Records with /R
Run the following to remove mount-point directories and registry settings associated with volumes that are no longer in the system:
mountvol /R
This prevents an absent volume from automatically reclaiming its former mount points if it is later reintroduced.
Use /R only when you intend to discard those historical associations. It is not a general disk-repair or free-space command, and it does not remove the data from the absent volume.
Mounting the EFI System Partition with /S
On a UEFI-based Windows installation, the EFI system partition contains boot-related files. To assign it an unused drive letter temporarily:
mountvol S: /S
To remove that assignment afterward:
mountvol S: /D
Warning: Do not modify, delete, encrypt, compress, or replace files on the EFI system partition unless you are following a verified recovery or deployment procedure. Incorrect changes can prevent Windows or other installed operating systems from starting.
Use /S only for legitimate boot repair, deployment, imaging, or diagnostic work. It is not needed for routine storage administration.
Mountvol Compared with Other Windows Tools
| Tool | Best use |
|---|---|
mountvol |
Direct management of volume GUID paths, mount points, automount, and EFI mounting |
| Disk Management | Visual inspection and interactive management of disks, partitions, drive letters, and folder paths |
diskpart |
Scriptable disk, partition, volume, and access-path management |
| PowerShell Storage cmdlets | Automation with structured objects, filtering, validation, and error handling |
| Storage Spaces | Pooling physical disks and creating virtual disks; this is different from folder mount points |
For a beginner, Disk Management is often easier because it displays volume size, status, filesystem, and layout. For repeatable administration, PowerShell provides clearer object-based selection than copying GUIDs manually.
A PowerShell equivalent for adding a folder access path is:
Add-PartitionAccessPath -DiskNumber 2 -PartitionNumber 1 -AccessPath "C:\Mounts\Data"
Remove it with:
Remove-PartitionAccessPath -DiskNumber 2 -PartitionNumber 1 -AccessPath "C:\Mounts\Data"
Always obtain and verify the correct disk and partition numbers with Get-Disk and Get-Partition first.
Security and Operational Considerations
Permissions do not automatically become identical
Accessing a volume through a folder does not make it inherit all security characteristics of the parent volume. Review the permissions and ownership on the mounted volume itself.
A user needs sufficient access to traverse the path leading to the mount point and appropriate permissions on the target volume.
Encryption remains volume-specific
BitLocker and other volume-level protections apply to the volume they protect. Mounting an encrypted volume inside an unencrypted folder does not decrypt it permanently or extend encryption to the host volume.
Backups must include mounted volumes deliberately
Some backup, replication, search, quota, antivirus, and monitoring tools may skip mount points or treat them as separate volumes. Confirm product behavior and recovery procedures rather than assuming a recursive scan includes everything below the folder.
A full mounted volume can look like a folder problem
Free space belongs to the target volume. An application writing to C:\Mounts\Data can fail because the mounted volume is full even when C: has substantial free space.
Removing an access path does not erase data
/D removes the selected route to the volume. Data remains on the volume. However, removing its only access path can make the data appear missing until another path is assigned.
Mount points are not redundancy
A folder mount point provides another namespace path. It does not create mirroring, backups, snapshots, parity, replication, or fault tolerance.
Troubleshooting Mountvol
“Access is denied”
Open Command Prompt by selecting Run as administrator. Also confirm that organizational security policy permits storage-management changes.
“The parameter is incorrect”
Check that:
- The volume GUID was copied exactly.
- The GUID contains braces.
- The volume path begins with
\\?\Volume. - The volume path ends with a backslash.
- Paths containing spaces are enclosed in quotes.
- The selected switch uses the correct syntax.
The destination folder cannot be used
Confirm that the folder:
- Already exists.
- Is empty.
- Resides on a suitable local NTFS volume for the
mountvoloperation. - Is not already a mount point.
- Is not being used in a conflicting way.
The volume is listed with no mount points
Verify that it is a normal data volume before assigning a path. Do not expose EFI, recovery, OEM, reserved, or diagnostic partitions merely because they lack drive letters.
Files disappeared after creating a mount point
Files that previously existed in the destination directory may be hidden while another volume is mounted there. Remove the mount point with /D to reveal the original directory contents.
This is one reason to use only an empty folder.
An application cannot find its data after mount-point removal
Restore the correct mount point or update the application configuration. Also check services, scheduled tasks, shares, scripts, backup definitions, and hard-coded paths.
A newly attached disk receives no drive letter
Automatic mounting may be disabled. An administrator can re-enable it with:
mountvol /E
Then assign an access path through Disk Management if Windows does not assign one automatically.
FAQ
Frequently Asked Questions
Does mountvol format or erase a volume?
Creating a mount point or removing one with /D does not format the volume or erase its files. /P is more disruptive because it dismounts the basic volume, takes it offline, and closes open handles, but it is not a formatting command.
Can a volume have both a drive letter and a folder mount point?
Yes. A local volume can be available through a drive letter and one or more folder mount points. Windows supports only one drive letter per volume.
Can I mount a volume into a non-empty folder?
Use an empty folder. Mounting over a directory containing files hides those files while the mount point exists and creates unnecessary recovery and operational risks.
Does mounting another volume under C: increase the free space of C:?
No. It adds a separate storage location within the C: directory hierarchy. The two volumes retain separate capacities and free-space accounting.
Can mountvol mount a network share?
No. Use a UNC path, net use, PowerShell SMB cmdlets, or File Explorer for network shares. mountvol manages local volume mount points.
Is a volume GUID the same as a disk serial number?
No. A volume GUID path identifies a Windows volume in the mount-manager namespace. It is not the disk’s hardware serial number and should not be treated as one.
Why does a volume GUID end with a backslash?
That is the required Windows volume-name format. Copy the complete value shown by mountvol, including the final backslash.
Should I use /D or /P?
Use /D to remove only the specified mount point. Use /P only when you intentionally need to remove the path, dismount the basic volume, and take it offline.
Can I use mountvol in scripts?
Yes, but validate the volume carefully. Avoid assuming that disk numbers or drive letters always identify the same storage. Log changes, handle errors, and test scripts outside production first.
FINAL RECOMMENDATION / CONCLUSION
Use mountvol when you need precise command-line control over Windows volume GUIDs, drive letters, and folder mount points. Begin with mountvol to inventory the system, verify the intended volume in Disk Management, and prefer /D for routine access-path removal.
Folder mount points are valuable for organizing server storage, reducing dependence on drive letters, and preserving application paths. They do not combine capacity, provide redundancy, or eliminate the need for volume-specific monitoring and backups. Reserve /P, /R, /N, and /S for controlled administrative tasks after understanding their system-wide or disruptive effects.
#mountvol #Windows #Windows11 #WindowsServer #VolumeMountPoint #MountedFolders #VolumeGUID #DiskManagement #StorageManagement #NTFS #DriveLetter #CommandPrompt #PowerShell #Diskpart #EFISystemPartition #SysAdmin #ITSupport #WindowsCommands #DataStorage #Troubleshooting
SOURCES
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.