How to Delete Mapped Network Drive in Windows 11/10: 5 Methods

You try to right-click your M: drive, but the option is grayed out, or the drive simply refuses to disappear. If you are here, you likely know that specific frustration. A disconnected network drive sitting in "This PC" isn't just a visual annoyance; it blocks that drive letter from being used for other purposes and can cause errors when mapping new shares.

To clear the clutter, you need to know how to delete mapped network drive entries safely. A crucial distinction to make upfront: removing the mapping does not delete the files on the server. It merely severs the local link. Think of it like removing a bookmark from a browser—the webpage (the data) still exists on the internet (the server), but you no longer have the shortcut on your browser bar.

Whether you prefer the visual simplicity of Windows File Explorer or the precision of the command line, this guide covers five distinct methods. We will start with the standard GUI approach for most users, move through Command Prompt solutions for power users, and finally tackle the stubborn "ghost" drives that refuse to disconnect. By the end, you’ll have a toolkit to handle everything from a simple cleanup to a registry-level purge.

The Quick Fix: Unmap a Drive via Windows File Explorer

For the vast majority of users, the most intuitive way to remove a mapped drive is through the graphical interface. This is the remove mapped drive windows method that most tech support lines will suggest first because it requires no typing and minimal risk of accidental data loss.

Step-by-Step Guide to Disconnecting a Single Drive

Open Windows File Explorer by pressing Win + E or clicking the folder icon on your taskbar. Navigate to This PC in the left-hand navigation pane. Here, you will see your local C: drive, D: drive, and any mapped network drives listed under the "Network locations" section.

Locate the specific drive letter you wish to eliminate. For instance, if you have a drive mapped to Z:, find that entry. Right-click the drive icon. In Windows 11, you may need to click "Show more options" to reveal the classic context menu. Select Disconnect.

A confirmation dialog will appear, asking if you want to disconnect the network drive. Click Yes. The drive icon should immediately vanish from the list. The drive letter is now available for reuse. If you attempt this and receive a "Network path not found" error, the mapping is already broken on the backend, but the record persists locally. In that case, you will need to move to the Command Prompt methods below.

Advanced Method: Use 'net use' in Command Prompt

When the GUI is unresponsive or you need to script the removal process, the Command Prompt becomes your best friend. This section focuses on the net use syntax, which is the backbone of network drive management in Windows.

Deleting a Specific Drive Letter

To manually remove a specific mapping, you need to open Command Prompt with administrative privileges. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).

Type the following command to see your current mappings:

net use

This command lists all active connections. Look for the line corresponding to the drive you want to delete, such as \\server\share mapped to Z:. To delete it, use the syntax:

net use Z: /delete /y

The /y flag is crucial here. It tells Windows to assume "yes" to any confirmation prompts and forces the deletion without waiting for user input. This is essential for scripting or when the UI is frozen. Note that you are referring to the drive letter (Z:), not the UNC path, in this command structure. If you have Administrator rights, this should execute cleanly. If you encounter an "Access denied" error, ensure you ran the prompt as Admin.

Bulk Removing All Mapped Drives

Sometimes, especially in IT administration or when resetting a profile, you want to wipe the slate clean. You don't want to delete Z:, then Y:, then X:. You want them all gone.

You can achieve this with a single wildcard command:

net use * /delete /y

This command targets all network connections and forces their deletion. It is highly effective for temporary connections or when a user profile becomes cluttered with stale mappings.

However, a word of caution: this is a blunt instrument. It will remove all mapped drives, including temporary ones created by applications like Microsoft Office or OneDrive. For an IT admin resetting a user machine, this is fine. For a home user who wants to keep their work drive but delete their old gaming server mapping, this is too aggressive. Use it only when you intend to clear everything for that user session.

If you prefer a scriptable approach for batch processing, you can wrap this in a simple .bat file:

@echo off
net use * /delete /y
echo All network drives disconnected.

Run this script with administrative privileges to ensure it has the necessary rights to override persistent connections.

Troubleshooting: When a Mapped Drive Won't Disconnect

You’ve typed the command, clicked disconnect, and the drive is still there. Or, it’s gone from the command list but the icon lingers in File Explorer. This is the mapped drive not responding scenario that drives many users to distraction.

Fixing the 'Drive In Use' Error

The most common reason a drive refuses to disconnect is that a process is actively holding onto it. Windows will not kill an active SMB connection if a file handle is open.

Check the obvious suspects first. Do you have a text file from that drive open in Notepad? Is Excel trying to auto-save a workbook on that path? Or is the File Explorer window itself displaying a preview pane for files on that drive? Close all applications that might be referencing the UNC path.

If closing apps doesn’t work, try a nuclear option within the standard tools: restart Windows Explorer.

1. Open Task Manager (Ctrl + Shift + Esc).
2. Find Windows Explorer (explorer.exe) in the Processes tab.
3. Right-click it and select Restart.

This refreshes the UI. If the drive disappears from the interface after this, the issue was likely a cached UI element. If it persists, a background process is still locking the connection.

Forcing Deletion with Third-Party Tools (pskill)

When standard tools fail due to "ghost" processes—background services that have locked a file but are no longer visible in Task Manager’s standard view—you need to get down to the PID (Process ID) level. This is where Sysinternals tools, specifically handle.exe or pskill, come into play.

First, download the Sysinternals suite from the Microsoft Learn website. You are looking for handle.exe to identify the lock, and pskill to forcefully terminate the process if necessary.

To identify who is locking the drive, open Command Prompt as Admin and run:

handle -a -n 0

Note: The handle command syntax can be tricky. A more targeted approach for SMB locks often involves checking for open handles to the UNC path string.

Alternatively, if you suspect a specific service is the culprit, you can use pskill to terminate a suspicious process. However, blindly killing processes is risky. Instead, I recommend using handle.exe to list processes holding open files on the specific UNC path (e.g., \\server\share).

handle -a C:\Users\YourName\AppData\Local\Microsoft\Windows\...

Correction: Identifying SMB locks is complex because the "file" is the network share itself. A practical workaround I’ve found effective is using Procmon (Process Monitor). Run Procmon, filter for the UNC path string, and it will show you exactly which Process ID has an open handle. Once you have the PID, you can use taskkill /F /PID <number> to end that specific process, then run your net use /delete command again.

Persistent Issues: Drive Reappears After Reboot or Login

You’ve disconnected the drive, it’s gone. You restart your computer for an unrelated update. You log in, and there it is. The drive is back. This is the most common complaint I receive: delete mapped drive permanently windows seems impossible because the system keeps auto-reconnecting.

Why Mapped Drives Come Back Automatically

When you map a drive, there is usually a checkbox in the mapping dialog labeled "Reconnect at sign-in." If you checked this, Windows stores the instruction to automatically re-establish the connection every time you log in.

Under the hood, this behavior is managed by two components:

1. Windows Credential Manager: Stores your username and password (or domain credentials) so the re-connection can happen seamlessly without prompting you.
2. Registry Entries: Specifically under HKEY_CURRENT_USER\Network, Windows stores the mapping details. Each drive letter is a subkey here (e.g., HKCU\Network\Z:).

If you simply disconnect the drive, you break the active connection. But the persistent configuration remains in the registry and credential store. So, on the next login, Windows sees the entry, grabs the credentials, and re-maps the drive. To delete it permanently, you must remove these persistent records.

Clearing Stale Mappings in Registry & Credential Manager

Warning: Editing the registry is risky. A single misplaced character can destabilize Windows. Always create a backup before proceeding.

1. Back Up the Registry: Press Win + R, type regedit, and when the prompt appears, click Yes. Before changing anything, go to File > Export. Save this file to your desktop just in case.

2. Navigate to the Network Key: In the left pane, expand HKEY_CURRENT_USER. Click on the Network folder. You will see subfolders named after drive letters (e.g., M, Z).

3. Delete the Specific Entry: Right-click the folder corresponding to the drive you want to remove (e.g., M) and select Delete. This removes the instruction to reconnect that specific drive.

4. Clear Saved Credentials: Sometimes, the registry entry is gone, but the Credential Manager still holds the password, allowing a re-connection if the drive is mapped again. Go to Control Panel > Credential Manager > Windows Credentials. Look for the network path (e.g., \\server\share) and delete the entry.

By removing both the registry auto-reconnect flag and the stored credentials, you ensure that the drive will not silently reappear. If you then need to use that server, you will have to manually map it again and enter your credentials, effectively "resetting" the trust.

FAQ

Does deleting a mapped network drive delete the files on the server? No. Deleting or "unmapping" a drive only removes the local shortcut on your computer. The actual data resides on the server or NAS device. Think of it like deleting a folder from your desktop shortcuts; the files themselves remain safe on the original storage device. Only an administrator with write permissions on the server share can delete the actual files.

Why can't I delete my mapped network drive? There are three primary reasons. First, the drive is currently "in use" by a background process (like a file preview). Second, you lack Administrator privileges, which are required to force-delete persistent mappings via Command Prompt. Third, stale registry entries are causing a "ghost" connection that standard UI methods cannot break. If you are stuck, refer to the Troubleshooting section above, specifically the part about restarting Explorer or using Process Monitor.

What is the difference between 'Disconnect' and 'Delete' in Windows? In the context of mapped drives, these terms are often used interchangeably by users, but they have technical nuances. "Disconnect" breaks the active session link; if you were mapped with "Reconnect at sign-in" checked, the link will return after a reboot. "Delete" (via net use /delete) removes the mapping configuration for the current session. To permanently remove it, you must also clear the registry entries as detailed in the "Persistent Issues" section. Both result in the drive icon disappearing from "This PC" immediately.

How do I delete all mapped drives in Net Use? You can clear all current mappings for your user session by opening Command Prompt as Administrator and running: net use * /delete /y. The asterisk (*) is a wildcard that targets all network connections. This is useful for IT admins resetting a user profile, but be aware it will also remove temporary connections made by other applications.

Conclusion

Getting rid of a stubborn mapped network drive rarely requires a single, magic command. It usually involves a layered approach. For most users, Windows File Explorer is sufficient to disconnect a healthy drive. For those dealing with stuck connections, the net use command in Command Prompt provides the force needed to break active locks.

However, if the drive keeps coming back after a reboot, the solution lies deeper in the system's architecture. Clearing the registry keys under HKEY_CURRENT_USER\Network and removing stored credentials is the definitive way to delete mapped network drive entries permanently.

Remember, you are not deleting data—you are just clearing the local link. If the drive still acts up after you’ve cleared the registry and credentials, a simple system restart is often the ultimate fix for stale SMB connections. The kernel cache will flush, and the ghost connection will finally vanish.

Struggling with persistent "In Use" errors or want a deeper dive into managing SMB connections? Download our free checklist on "Managing SMB Connections in Windows" to audit your entire network drive setup.