How to Remove Mapped Drive in Windows 11 (2026 Guide)

Do you see a grayed-out network drive that won’t disappear after a server update? It’s a common source of frustration: that stubborn icon sitting in your File Explorer’s “This PC” folder, labeled “Disconnected,” while you know the underlying share is gone or you simply want to clear the clutter. Many users confuse this stuck visual artifact with an active connection, leading to unnecessary reboots or, worse, registry edits that cause system instability.

Removing a mapped drive is a safe operation that affects only the local shortcut on your machine, not the data on the remote server. Think of it like deleting a bookmark from a web browser—the website itself remains untouched, and your local files are completely safe. In this guide, we will move beyond basic tutorials to address the specific "ghost drive" issues common in Windows 11. We’ll cover three primary methods: the graphical interface for quick fixes, Command Prompt (CMD) for permanent removal, and PowerShell for automated, large-scale management.

Method 1: How to Disconnect a Mapped Drive via File Explorer

The most intuitive way to handle a disconnected or unwanted drive is through the Windows GUI. This method is best when you want a quick disconnect or when you are unfamiliar with command-line tools. However, it’s important to understand the distinction between "Disconnecting" and "Removing" a mapping, especially if the drive is set to reconnect automatically.

Step-by-Step GUI Instructions for Windows 11 & 10

In my experience, Windows 11’s interface is slightly more streamlined than Windows 10, but the core logic remains identical. Here is how to navigate it:

1. Open File Explorer: Press Win + E or click the File Explorer icon on your taskbar.
2. Locate Network Locations: In the left-hand navigation pane, click on This PC. Scroll down to the section labeled Network locations. This is where all your mapped drives reside, separate from your local SSDs and HDDs.
3. Right-Click the Drive: Find the specific drive letter you want to remove (e.g., Z:). Right-click it.
4. Select Disconnect: Choose Disconnect from the context menu. A small prompt may appear confirming the disconnection.

A critical nuance here: if the original mapping was created with the "Reconnect at sign-in" checkbox ticked (the default), simply disconnecting it via the GUI often only severs the current session connection. The mapping remains in your user profile’s registry, and Windows will attempt to re-establish the link on your next boot. To truly remove the mapping using only the GUI, you must navigate to the Network Shortcuts folder and delete the shortcut file itself, a process we will detail in the troubleshooting section below if the icon persists.

Troubleshooting: Why Is the Drive Still Grayed Out?

If you have disconnected the drive but the grayed-out icon remains, you are likely dealing with a UI cache issue rather than an active connection. Windows File Explorer caches the visual state of network resources for performance. If the server goes offline, the icon transitions to a "Disconnected" state but does not automatically vanish until the Explorer process refreshes its view.

Try pressing F5 in File Explorer to force a refresh. If the icon persists, the underlying mapping entry still exists in your user profile. In this scenario, the GUI disconnect was merely a temporary severing of the SMB (Server Message Block) session. To permanently delete the network drive reference, you need to move to the Command Prompt method, which directly instructs the net.exe utility to purge the mapping from the registry key HKCU\Network.

Method 2: Use the Net Use Command to Permanently Delete Network Drives

When I need to ensure a mapping is gone for good—specifically preventing Windows from trying to ping a dead server on every login—I rely on the net use command. This is the definitive way to delete a network drive mapping from the current user profile. Unlike the GUI, which can be ambiguous about whether it’s removing the session or the mapping, CMD gives you precise control.

Removing a Single Drive with net use /delete

To execute this, you need to open Command Prompt. While it works for standard users, opening CMD as an Administrator is often necessary if you encounter permission errors, particularly in corporate environments where drive mappings might be enforced by policy.

Open the Start menu, type cmd, right-click Command Prompt, and select Run as administrator. Then, type the following command:

net use Z: /delete

Replace Z: with your actual drive letter. If successful, you will see the message: Z: was deleted successfully.

This action immediately removes the drive letter from your available drives and purges the mapping from the current user’s registry hive. It’s clean, fast, and doesn’t require a reboot.

Preventing Reconnection: The /persistent:FALSE Flag

Here is where the "Ghost Drive" problem often sneaks in. By default, Windows marks new drive mappings as Persistent. This means that even if you delete the drive today, Windows stores the configuration so it can automatically re-map the drive the next time you log in. If the server is offline during that login sequence, Windows hangs on the connection attempt for 30 seconds or more, creating that frustrating "Disconnected" state.

To stop this behavior when you are removing a drive, you should explicitly ensure the mapping is not persistent. While /delete removes the current mapping, you can pair it with the persistence flag to be extra safe, or more commonly, when creating mappings in the future, use:

net use Z: \\server\share /delete /persistent:FALSE

Note: The /persistent:FALSE flag is primarily used when mapping to prevent auto-reconnect, but when deleting, the system essentially removes the persistent flag with the entry. However, understanding this distinction is key to why drives keep coming back.

If you want to verify a drive is not persistent, you can check your current mappings with net use and look at the status column.

Bulk Action: How to Delete All Mapped Drives in CMD

For IT admins or users leaving a company who need to wipe all network access points at once, you can use a wildcard. This is a powerful tool for cleaning up a machine before handing it over.

Run the following command:

net use * /delete

Warning: This will remove all network drive mappings for the current user. It does not affect local physical drives (like C: or D:). It is a safe operation in terms of data loss, but it will disconnect any active network shares you were using. If you have critical data open on these drives, save your work first.

Method 3: Advanced PowerShell Scripts for IT Administrators

For those managing multiple endpoints or running automated scripts, PowerShell offers a more granular approach than CMD. It allows for object-based manipulation of drives, making it easier to filter, sort, and report on network locations.

Using Get-PSDrive and Remove-PSDrive

Open PowerShell as an Administrator. First, let’s identify which drives are actually network drives. We can use Get-PSDrive and filter by the provider and root path.

Get-PSDrive | Where-Object { $_.Provider -eq 'FileSystem' -and $_.Root -like '\\*'}

This command outputs a table of drives where the root path starts with \\ (indicating a UNC path). To remove a specific drive, say Z:

Remove-PSDrive Z

Or, if you want to remove all network drives at once:

Get-PSDrive | Where-Object { $_.Provider -eq 'FileSystem' -and $_.Root -like '\\*'} | Remove-PSDrive

One thing to note from my testing: Remove-PSDrive in standard Windows PowerShell disconnects the drive for the current session. To ensure the mapping is removed from the registry (preventing auto-reconnect), you often still need to verify that the net use mapping is gone or use the CIM/WMI methods below for a more thorough "unmap" operation.

Unmapping via CIM/WMI for Automated Environments

In domain environments, especially when dealing with "cannot delete mapped drive access denied" errors, you may find that standard user privileges are insufficient. Using CIM (Common Information Model) allows for remote management and often bypasses some local session restrictions.

You can use Invoke-CimMethod on the Win32_MappedLogicalDisk class. However, a more practical script for admins involves checking the registry directly or using the Remove-PSDrive cmdlet combined with a net use command under the hood.

A critical factor in corporate settings is Group Policy (GPO). If your organization uses a GPO to automatically map drives at logon, any local deletion you perform will be overridden the next time you log in. The GPO re-applies the mapping, essentially "ghosting" the drive back into existence. In these cases, the only true fix is to modify the GPO on the Domain Controller.

Fixing Ghost Drives: When the Mapped Drive Refuses to Vanish

This is the pain point that drives most users to search for "fix mapped drive not showing in file explorer" or "how to remove a stuck drive." We are talking about the scenario where net use shows no active connections, but the icon remains stubbornly in File Explorer, or the drive letter is in use but disconnected.

Clearing Stuck Disconnected Icons Without Rebooting

You don’t always need to restart your PC to clear a stuck UI element. Here is a safe, step-by-step process I use to refresh the Explorer cache without a full reboot:

1. Close File Explorer: If you have it open, close the window.
2. Restart Windows Explorer:
   • Press Ctrl + Shift + Esc to open Task Manager.
   • Find Windows Explorer in the Processes tab (it might be listed under "Windows processes" or just "Explorer").
   • Right-click it and select Restart.
   • Note: Your desktop icons and taskbar will disappear for a few seconds and then reappear. This forces Windows to reload the navigation pane, often clearing the "ghost" icons.
3. Verify with CMD: Open CMD and run net use. If it says "There are no mapped drives," but you still see the icon in File Explorer after restarting Explorer, you are dealing with a registry-level ghost.

Removing Legacy Registry Entries (Advanced)

If the drive is not listed in net use but still appears in File Explorer, the mapping has been removed from the active network session manager, but the shortcut file or registry key remains in your user profile. This is common after a server migration where the old UNC path is invalid.

To clean this up definitively:

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU.
3. Here you will see string values representing the last used drive letters and UNC paths. Delete the entries corresponding to the ghost drive.
4. Also, check HKEY_CURRENT_USER\Network and HKEY_CURRENT_USER\Network\Drives. Delete the sub-keys that match the drive letter you are trying to remove.

Disclaimer: Editing the registry carries a risk. A single error can cause system instability. Always create a system restore point before making changes. This is the definitive fix for "How to remove a mapped drive that no longer exists" when the server IP is gone forever and Windows is just holding onto old data.

Personal vs. Domain Users: Why Your Drive Keeps Coming Back

One of the most confusing aspects of mapped drives is their scope. Many users assume that removing a drive affects the whole computer. It doesn’t. Mapped drives are stored in the HKEY_CURRENT_USER registry hive, which means they are specific to the Windows account that created them.

Understanding User-Context Mapping

If you remove a drive from your personal account, it remains mapped in the Administrator account or any other user profile on that machine. This is a frequent source of confusion for IT admins doing "remote cleanup." If you log in as User A and remove a drive, then log in as User B, the drive will still be there.

To remove a mapped drive from another user's profile, you must either:

1. Log in as that specific user.
2. Use PowerShell scripts that target the specific user's registry key (e.g., HKEY_USERS\[SID]\...), which requires administrative privileges.

This explains why a drive might "come back" when a colleague logs into your shared machine—they are seeing their own user-specific mapping, not yours.

Group Policy (GPO) Overrides

For domain-joined computers, the rules are different. Group Policy can enforce drive mappings that override local user settings. If your IT department has a GPO set up to map a shared file server at logon, your ability to "permanently" delete that drive is limited to the current session.

At the next logon, the GPO engine will re-apply the mapping. To stop this, you must contact your IT administrator to modify the GPO in the Group Policy Management Console (GPMC). Specifically, you need to look at the User Configuration -> Windows Settings -> Mapped Drives section. Until that policy is changed, local deletion is temporary.

FAQ

Why does my mapped network drive disappear after I reboot Windows 11? This usually happens if the drive was mapped with the /persistent:FALSE flag, or if the connection to the server fails during the boot sequence. If the mapping is persistent, Windows attempts to reconnect. If the server is offline or the UNC path is invalid, the drive will show as "Disconnected." If it disappears entirely, the mapping was not set to persist across reboots.

Can I remove a mapped drive if the server is offline? Yes. The mapping is stored locally in your Windows profile. You can disconnect or delete the mapping using File Explorer, CMD (net use), or PowerShell regardless of the server's status. The drive may appear as "Disconnected" in the UI until you refresh or reboot, but the reference can be purged from your system even without a live connection.

What is the difference between unmap and remove mapped drive? In Windows terminology, they are essentially synonymous for the end user. "Unmap" is the technical term often used in PowerShell and scripting contexts, while "Remove" or "Disconnect" is the standard language in the Windows GUI and CMD. Both actions result in the drive letter being no longer available in the local system.

How to keep mapped drive connected when I restart my computer? Ensure the mapping is set to Persistent. When mapping a drive via CMD, use net use X: \\server\share /persistent:TRUE. If it still disconnects, check your network connection. Windows cannot resolve the UNC path if you are on a VPN or Wi-Fi network that isn't connected by the time the boot sequence reaches the drive mapping stage.

Conclusion

Choosing the right method to remove a mapped drive depends on your context. For casual users dealing with a one-off clutter issue, the File Explorer method is sufficient for disconnecting, though deleting the network shortcut file ensures the icon goes away. For a permanent removal that stops Windows from trying to reconnect on every boot, the Command Prompt net use /delete command is the gold standard. IT administrators managing fleet devices should look to PowerShell scripts and Registry cleanup for automated, reliable results, especially when dealing with "ghost" drives that persist after a server decommissioning.

Remember, "ghost drives" are rarely active connections; they are usually UI cache artifacts or stale registry entries. And if you are on a domain, check your Group Policy settings before blaming the operating system—GPOs are the ultimate authority that can override your local changes.

If you are an IT Admin managing multiple endpoints, consider automating this process with RMM tools to ensure consistency across your fleet. For personal use, keep this guide bookmarked for the next time a network drive acts up.

[Read more: How to Map a Network Drive in Windows 11]