Mountvol Command: Ultimate Guide to Volume Mount Points

The mountvol command is a crucial Windows command-line utility for managing volume mount points. It allows system administrators to link a physical or logical volume to an empty folder on an NTFS-formatted drive (usually the C: drive) instead of assigning it a traditional drive letter like D: or E:.

Whether you're running out of alphabetic drive letters on a sprawling enterprise file server, attempting to seamlessly expand the storage capacity of a specific application folder (like C:\Database\Logs), or managing hidden EFI system partitions, mastering mountvol provides elegant storage flexibility. IT professionals and storage engineers rely on this command for overcoming legacy Windows structural limitations regarding drive mapping.

This comprehensive guide covers mountvol syntax, all major options (creating, deleting, un-mounting), practical examples for common scenarios, troubleshooting tips, and frequently asked questions. By the end, you'll confidently manage NTFS volume mount points from the command line.

What Is the Mountvol Command?

The mountvol (Volume Mount Manager) command is a built-in utility in Windows Command Prompt and PowerShell. Since the early days of Windows (specifically Windows 2000), NTFS has supported joining an entire storage volume into an empty folder on another volume. This is fundamentally different from a shortcut or a symlink. When you navigate to an active mount point, your operating system treats the folder exactly as if you had jumped to a completely separate physical disk.

This feature is critical because a standard Windows system only supports 26 simultaneous drive letters (A through Z). Enterprise servers often attach far more logical units (LUNs) than 26 via SANs. mountvol bypasses this limitation entirely.

To successfully execute mountvol and manipulate the storage architecture of the operating system, you must run the command prompt with administrative privileges.

Syntax

The basic syntax for the mountvol command involves specifying the path to an empty directory (the future mount point) and the unique Volume Name (the GUID of the volume you want to attach).

mountvol [Drive:]Path VolumeName
mountvol [Drive:]Path /d | /l | /p | /r | /n | /e

Options Table

Parameter	Purpose
`[Drive:]Path`	Specifies the existing empty directory where the mount point will reside.
`VolumeName`	Specifies the volume name (GUID) to associate with the mount point. Format: `\\?\Volume{GUID}\`
`/d`	Removes the volume mount point from the specified folder.
`/l`	Lists the mounted volume name for the specified folder.
`/p`	Removes the mount point from the specified directory and dismounts the volume.
`/r`	Removes all mount point directories that belong to volumes that are no longer in the system.
`/n`	Disables automatic mounting of new volumes.
`/e`	Re-enables automatic mounting of new volumes.
`/?`	Displays the help text.

Parameters and Options Explored

Creating a Mount Point (No flags)

When you supply a path and a Volume GUID, mountvol creates the link. The target path must be a completely empty folder located on an NTFS-formatted volume (like your C: drive).

The /d Option (Delete)

The /d option breaks the link. It removes the capability of the specific folder to act as a portal to the secondary drive. It does not format the volume, lose data, or delete the empty folder itself; it merely severs the connection.

The /r Option (Scrub Offline Volumes)

Over time, if you constantly attach and detach USB drives, LUNs, or virtual disks, the registry becomes clogged with "ghost" volumes. The /r switch forcefully cleans out any volume metadata for disks that are no longer physically attached to the server.

The /n and /e Options (Auto-mount Control)

By default, Windows attempts to automatically mount and assign a letter to any new flash drive or raw logical disk you attach. On secure enterprise servers (like Hyper-V hosts), administrators often use /n to stop this behavior, forcing manual provisioning only, and /e to reverse it back to default.

Examples

In this section, we will look at robust, copy-pasteable examples of using the mountvol command. Note that you must open your Command Prompt or PowerShell as Administrator to successfully execute these mapping operations.

1. View All Volumes and Mount Points

Before making any changes, you must identify the unique GUIDs for every volume currently visible to the operating system.

mountvol

Output:

Creates, deletes, or lists a volume mount point.

Possible values for VolumeName along with current mount points are:

    \\?\Volume{a1b2c3d4-e5f6-7890-a1b2-c3d4e5f67890}\
        C:\

    \\?\Volume{12345678-1234-1234-1234-123456789012}\
        D:\

    \\?\Volume{09876543-abcd-abcd-abcd-098765432100}\
        *** NO MOUNT POINTS ***

Explanation: Running the command with no arguments lists the help text followed by a complete inventory of every partition and volume Windows can see. Volume GUIDs with *** NO MOUNT POINTS *** are attached to the server but have no drive letter and no folder path mapped to them.

2. Mount a Volume to an Empty Folder (Seamless Expansion)

Assume your C:\Database folder is getting dangerously full, but the database expects to write to C:\Database\Logs. You can attach a massive secondary drive directly to that folder to seamlessly offload the space without changing the database software's configuration.

mkdir C:\Database\Logs
mountvol C:\Database\Logs \\?\Volume{09876543-abcd-abcd-abcd-098765432100}\

Output:

The command completed successfully.

Explanation: First, ensure C:\Database\Logs is totally empty (or create it anew using mkdir). Then, call mountvol, target that folder, and paste the specific GUID of your secondary empty volume. Any file written to C:\Database\Logs is now physically written to the secondary drive.

3. Remove a Mount Point

If you need to decommission a secondary drive, you must first break the mount point mapping to ensure the operating system gracefully releases the volume.

mountvol C:\Database\Logs /d

Output:

The command completed successfully.

Explanation: This deletes the mapping. The folder C:\Database\Logs turns back into a regular, empty folder on the C: drive. The secondary volume and all of its data are 100% physically intact and unaffected, just no longer cleanly accessible via that specific path.

4. Dismount and Remove (The /p switch)

If you intend to physically unplug a USB drive or detach an iSCSI LUN immediately after severing the mount point, you should use /p to forcefully dismount the volume from the kernel's perspective.

mountvol C:\Database\Logs /p

Explanation: This combination breaks the folder link (just like /d) AND dismounts the volume from the filesystem hierarchy, ensuring all cache buffers are flushed and the disk is ready for safe physical removal.

5. Find Which Volume Is Attached to a Specific Folder

If you inherit a deeply complex file server, you might see a drive icon on what appears to be a normal folder. You can use /l to list exactly which raw volume GUID is backing that folder.

mountvol C:\Database\Logs /l

Output:

\\?\Volume{09876543-abcd-abcd-abcd-098765432100}\

Explanation: This returns the single raw Volume GUID associated with the target folder. It's a quick verification step for documentation or auditing.

6. Clean Up Ghost Volumes

Over months of attaching and detaching hundreds of virtual disks or USB drives, Windows continues to remember the registry configurations for those offline drives.

mountvol /r

Explanation: This command scrubs the Volume Mount Manager registry. It drops all memory of mount points that belong to volumes which are physically disconnected or offline. This prevents mounting conflicts later.

7. Disable Automatic Drive Letter Assignment

On production servers (like a high-security cluster or a Hyper-V host receiving SAN LUNs), you do not want Windows automatically popping up E:\ every time a new LUN is provisioned to the fiber channel fabric.

mountvol /n

Explanation: This modifies the system so that new volumes must be manually brought online via diskpart or manually mounted via mountvol. They will silently remain offline until deliberately touched by an admin.

8. Access the Hidden EFI System Partition

Modern UEFI computers have a hidden ~100MB FAT32 partition where the Windows bootloader lives. It has no drive letter. You can map it to troubleshoot boot issues.

mountvol Z: /s

Explanation: The undocumented (but widely used in standard repair scenarios) /s flag specifically maps the hidden EFI partition to a drive letter, in this case, Z:. Note: You must kill explorer.exe and re-run it elevated to graphically browse Z:.

Common Use Cases

Here are the most common scenarios where IT professionals leverage the mountvol command.

Bypassing the 26-Letter Limit: When a corporate file server requires 40 different distinct LUNs from a SAN, administrators map them under C:\Mounts\Finance, C:\Mounts\HR, C:\Mounts\IT, bypassing the English alphabet limitation entirely.
Transparent Application Storage Scaling: Expanding Microsoft SQL Server or Microsoft Exchange database directories onto new physical storage without uninstalling or reconfiguring the database paths. The software writes to C:\Exchange\DB1, oblivious that it is actually an independent 2TB SAN LUN.
Hyper-V Cluster Volume Management: Disabling automount (/n) so that newly presented Cluster Shared Volumes (CSVs) don't violently attempt to grab drive letters on the host OS.
Bootloader Repair (EFI): Gaining emergency programmatic access to the \EFI\Microsoft\Boot\BCD file on a corrupted UEFI system to manually rebuild the boot configuration data.
Consolidating User Shares: Providing end-users with a single, massive pseudo-drive letter (e.g., S:\Shares) where every nested sub-folder is actually a different physical disk optimized for specific project workloads.
Cleaning Stale Registry Entries: Running mountvol /r during routine Server maintenance to ensure the VDS (Virtual Disk Service) doesn't hang enumerating hundreds of long-gone USB backup drives.

Tips and Best Practices

To properly orchestrate scalable Windows storage, stick to these proven best practices:

Use Empty Folders Only: The directory you specify for mountvol must be empty. If it contains data, the command will fail or, depending on the toolchain, temporarily hide that data beneath the new volume mapping.
Format is Critical: You can only mount a volume to a folder that resides on an NTFS or ReFS formatted drive. You cannot mount a volume into a folder on an old FAT32 flash drive.
Understand Inheritance: When writing NTFS security permissions (ACLs), mount points can be tricky. A mount point presents the permissions of the root of the target volume, not necessarily the permissions of the parent folder hosting the mount point.
Copy the GUID Correctly: The VolumeName strings (\\?\Volume{...}\) include the trailing backslash. Always copy-paste the exact string generated by typing mountvol with no arguments to prevent syntax errors.
Combine with Diskpart: mountvol only links existing, formatted volumes to folders. You must still use diskpart or Disk Management (diskmgmt.msc) to initially initialize the disk, create the partition, and format it with a filesystem.
Document Everything: While an elegant solution, deeply nested mount points act like invisible storage traps for junior technicians. Explicitly document C:\Mounts\ApplicationData in your internal wiki so no one accidentally formats a 10TB LUN thinking it's a 5MB local folder.

Troubleshooting Common Issues

Working directly with system volume mappings occasionally generates confusing errors.

"The directory is not empty."

Problem: You attempt to map a volume and receive a failure indicating the path has contents. Solution: mountvol requires the target folder (e.g., C:\NewDrive) to contain absolutely zero files, including hidden or system files like desktop.ini. Prevention tip: Always execute mkdir to generate a fresh, definitively empty target directory immediately prior to running mountvol.

"Access is denied"

Problem: The mountvol command output is restricted, or the mapping fails with permission errors. Solution: Creating or stripping volume mount points requires the highest level of administrative security clearance. Your Command Prompt is not elevated. Prevention tip: Right-click CMD or PowerShell and select "Run as Administrator," or ensure your deployment script is running under the highly privileged SYSTEM context.

"The system cannot find the file specified."

Problem: Using /d or attempting to create a mapping results in a "not found" error. Solution: The target directory path is misspelled, the directory doesn't physically exist, or the Volume GUID is incorrect (usually missing the mandatory trailing backslash). Prevention tip: Utilize Tab-completion in the command line for the folder path, and copy-paste the precise Volume GUID string from the blank mountvol output.

Drive Doesn't Auto-Mount Anymore

Problem: When you plug in a USB flash drive, it no longer gets an E: drive or pops up in Windows Explorer. Solution: Someone (or a script) ran mountvol /n on your workstation, disabling Windows automount capabilities. Prevention tip: Run mountvol /e as an administrator, reboot the machine (or restart the Virtual Disk service), and automount capability will be restored.

Related Commands

Here are some commands closely associated with mountvol that every storage administrator needs to understand:

diskpart – Command-line Disk Utility

diskpart is the foundational utility for disk provisioning. Before mountvol can map a drive, diskpart must be used to bring the raw disk online, create a primary partition, format it as NTFS, and assign it a Volume GUID.

mklink – Directory Junctions and Symlinks

While mountvol directly links a raw block-level volume into a folder, mklink /J links an existing folder path to another folder path. mklink operates at the filesystem level, whereas mountvol operates closer to the hardware kernel level.

fsutil – File System Utility

Often used for advanced queries against volumes. For instance, fsutil volume diskfree c: works perfectly on mounted volumes to verify they are allocating the massive storage properly.

vssadmin – Volume Shadow Copy Service

Crucial for backing up these massive LUNs. When backup software strikes a point-in-time snapshot, it leverages vssadmin to pause I/O on the mounted volumes.

Frequently Asked Questions

What does the mountvol command do?

The mountvol command creates, deletes, or lists volume mount points, allowing you to attach an entire hard drive to an empty folder on another drive instead of assigning it an alphabetical drive letter.

Are volume mount points better than drive letters?

For complex architectures, yes. They bypass the 26-letter alphabet limitation, allow applications with hardcoded C: drive paths to seamlessly utilize external storage arrays, and keep the "My Computer" interface uncluttered on enterprise file servers.

Will deleting a mount point with /d delete my data?

Absolutely not. Using mountvol C:\Path /d merely removes the virtual "bridge" connecting the C: drive folder to the secondary volume. The secondary volume and all its files remain perfectly intact and completely unharmed, waiting for a new letter or mount point.

Does Windows Search index mapped volumes?

Yes. If you add C:\MappedDrive to your Windows Indexing options, the crawler will seamlessly move across the volume mount point and index the target disk as if it were a local folder on the C: drive.

Can I mount a network drive with mountvol?

No. mountvol only works with physical local disks (SATA, NVMe, USB) or block-level targets (iSCSI LUNs, Fibre Channel, VHDX files). To map a standard SMB network share to a folder or letter, you must use the net use command or the New-SmbMapping PowerShell cmdlet.

What is the /s parameter for?

mountvol Z: /s is an undocumented but incredibly famous parameter specifically designed to mount the hidden EFI System Partition on UEFI-based Windows installations so that administrators can manually run bcdboot to fix corrupted bootloaders.

Do I need to be an administrator to use it?

Yes. Altering the structural mapping of system volumes requires full administrative privileges. Running it as a standard user will result in "Access is denied."

Does mountvol work in PowerShell?

Yes, the mountvol.exe executable runs perfectly within the PowerShell console. Alternatively, PowerShell Native cmdlets like Add-PartitionAccessPath offer the exact same functionality via object-oriented scripting.

Can I have both a drive letter and a mount point?

Yes. It is entirely possible for a Volume GUID to be mapped to D:\ and simultaneously mapped to C:\SharedData. Both paths will dynamically read and write from the same underlying physical disk.

Quick Reference Card

Here is a quick reference table of vital mountvol commands that busy administrators frequently use.

Command	Purpose	Example
`mountvol`	List all volumes and mappings	Identify the raw GUID of a newly attached SAN LUN
`mountvol C:\Target \\?\Volume{...}\`	Create a mount point	Offload a full database directory to an external disk
`mountvol C:\Target /d`	Remove the mapping	Sever the connection prior to pulling a USB drive
`mountvol /r`	Purge ghost drives	Clean up registry clutter from hundreds of old backups
`mountvol X: /s`	Mount EFI partition	Gain access to corrupted bootloader files

Summary

The mountvol command is a vital piece of the Windows storage architecture puzzle. It grants system administrators elegant control over how physical and logical volumes are presented to the operating system, shattering the rigid constraints of the 26-letter drive alphabet.

We covered the core syntax and the essential options like /d for safe disconnection and the raw creation command for seamless storage expansion. Through practical examples, we looked at how to offload massive application directories like databases or logs onto dedicated storage arrays without breaking hardcoded paths or alerting end users.

Whether you're baselining a multi-terabyte clustered file server, attempting to fix a corrupted UEFI bootloader via the /s flag, or locking down a secure host with the automount /n variable, a strong functional knowledge of mountvol ensures you dictate exactly where and how your data lives.

Ready to test your mountvol skills? Try using the interactive simulator on our platform to build muscle memory without accidentally unmounting your own C: drive. You can also explore our Commands Reference for deeper dives into related administrative utilities, or check out our guide on the diskpart command to solidify your holistic storage expertise.