How to Map a Network Drive on Windows 11 (GUI, CMD, GPO)

A new hire needs the finance share on day one, and the ticket says "the S drive is missing again." Mapping it by hand works for one PC, but the second time it breaks you want a method that survives sign-ins, policy refreshes and a Windows 11 upgrade. Here is how to map a network drive on Windows 11 from File Explorer, from the command line, from PowerShell and through Group Policy, plus the four settings in 24H2 that make a working mapping fail.

Map a Network Drive From File Explorer

The manual route is fine for one machine or a one-off share. Microsoft's own steps for Windows 10 and 11 are short.

1. Open File Explorer, select This PC in the left pane, then select More (the three dots) on the toolbar and choose Map network drive. If the toolbar hides it, right-click This PC instead.
2. Pick a letter from the Drive list. Letters near the end of the alphabet avoid clashes with USB sticks and card readers.
3. In Folder, type the UNC path, such as \\fs01\finance, or use Browse to find it.
4. Tick Reconnect at sign-in if the drive should come back after a restart. Tick Connect using different credentials if the share needs an account other than the one signed in.
5. Select Finish.

If Browse shows nothing, network discovery is off. File Explorer's Network view shows a banner for that; select it and choose Turn on network discovery and file sharing. Typing the UNC path works without discovery, so skip the banner when you know the path.

To remove a mapping, right-click the drive under This PC and choose Disconnect.

Map a Drive From the Command Line With net use

net use has mapped drives since Windows NT and still does the job in a Command Prompt or a logon script. The shape is drive letter, UNC path, then options.

cmd
net use S: \\fs01\finance /persistent:yes
net use S: \\fs01\finance /user:CONTOSO\jdoe * /persistent:yes
net use * \\fs01\finance
net use S: /delete
net use * /delete
net use

Line by line: the first maps S: and saves it for the next sign-in. The second maps it with a different account and prompts for the password, because the * after the username asks rather than putting the password in the command history. The third takes the next free letter. The two /delete lines remove one mapping or all of them, and bare net use lists what is mapped right now, including drives that show a red X in File Explorer.

Two options need care. /persistent:yes applies to every mapping you make after it in that session, not just the one on the line, because Windows remembers the last setting used. And /savecred stores the credentials in Windows Credential Manager, which is convenient on a personal PC and a liability on a shared one, since anyone who signs in as that user gets the share without a prompt.

The thread above asks the question users ask technicians: is a mapped letter different from typing the path? Same share, same permissions. The letter is a shortcut stored for that user, plus a flag that says whether to rebuild it at sign-in.

Map a Drive With PowerShell (New-PSDrive and New-SmbMapping)

PowerShell has two cmdlets that look alike and behave differently, and picking the wrong one is the most common reason a scripted mapping never appears in File Explorer.

powershell
# A Windows mapped drive, visible in File Explorer and net use
New-PSDrive -Name "S" -PSProvider FileSystem -Root "\\fs01\finance" -Persist -Scope Global

# The same thing through the SMB module
New-SmbMapping -LocalPath "S:" -RemotePath "\\fs01\finance" -Persistent $true

# Check what is mapped, then remove one
Get-SmbMapping
Remove-SmbMapping -LocalPath "S:" -Force

Without -Persist, New-PSDrive creates a temporary PowerShell drive. It works inside that session and vanishes when the window closes. File Explorer, net use and other apps never see it, because, as Microsoft's cmdlet reference puts it, temporary drives are known only to PowerShell.

-Persist turns it into a Windows mapped drive, with three conditions: the name must be a single letter, the provider must be FileSystem, and the root must be a UNC path. Add -Scope Global when the command runs inside a script, or the drive disappears when the script's scope ends, which looks exactly like a mapping that silently failed.

New-SmbMapping skips those traps. It always creates a real Windows mapping and takes -Persistent $true for sign-in survival. It sits well next to the other useful PowerShell commands a technician keeps to hand, and OpenFrame can run a Get-SmbMapping check as a script across a client's devices and collect the output.

Map Drives for a Whole Office With Group Policy

For domain-joined PCs, Group Policy Preferences Drive Maps is the method that scales: it applies at sign-in, repairs itself at every refresh, and needs no script.

In the Group Policy Management Console, edit a GPO linked to the users' OU and go to User Configuration, Preferences, Windows Settings, Drive Maps. Create a new mapped drive and fill in four things: the Location as a UNC path, the Drive Letter, a Label as name users will see, and Reconnect ticked so the mapping is saved in the user's profile. The Action field decides how the item behaves.

Use Update for almost everything. It creates the mapping if it is missing and otherwise changes only the settings in the item, so a user with a file open does not lose the drive during a refresh. Replace deletes and recreates the drive every time policy applies, which is the cause behind "my S drive disappears for a second every ninety minutes."

Item-level targeting, on the Common tab, scopes one item to a security group, an OU or an IP range. One GPO maps the finance share for the finance group and the projects share for everyone.

Do not type credentials into the Connect as fields. Since the MS14-025 update in May 2014, the Group Policy editor no longer lets you save a password in a Drive Map item, because the stored value could be decrypted by any domain user. If a share needs a different account, fix the permissions on the share instead.

Why the Drive Does Not Show Up

The mapping "worked" but the letter is missing from File Explorer. Four causes cover nearly every ticket.

You mapped it as an administrator. With User Account Control on, an admin account gets two sign-in sessions, a standard one and an elevated one, and a drive mapping belongs to the session that created it. Map a drive from an elevated PowerShell and the standard File Explorer session never sees it; the reverse is why a mapped drive vanishes inside an app you ran as administrator. Microsoft documents the EnableLinkedConnections registry value as a workaround, but the cleaner fix is to test mappings as the user who will use them.

The poster above tried a GPO Drive Map, a scheduled task and a logon script, and the drive never appeared. The resolution was the first cause on this list: they were testing as a domain admin, and on a standard user account every method worked. The replies also caught the second cause, New-PSDrive where New-SmbMapping was wanted.

The script used a temporary PowerShell drive. Covered above: no -Persist, no -Scope Global, no drive after the script exits.

The policy item uses Replace. The drive exists, then disappears during the refresh, then returns. Switch the action to Update.

The drive reconnects before the network is ready. Laptops on Wi-Fi sign in before the adapter has an address, so the saved mapping fails with "Could not reconnect all network drives" and opens the moment the user clicks it. On a domain the policy Always wait for the network at computer startup and logon makes sign-in wait; on a workgroup PC a scheduled task that runs net use at logon with a short delay does the same job.

Four Settings That Break Mappings on Windows 11 24H2

Windows 11 tightened SMB in ways that turn an old NAS or a router share into an error. The mapping command is right; the connection is refused. These are the four to check, with the error each produces.

SMB1 is gone. Windows 11 ships without the SMB1 client or server. A device that only speaks SMB1 produces "You can't connect to the file share because it's not secure" or "The specified network name is no longer available." Microsoft's advice is to update or replace the device rather than reinstall SMB1; Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol shows whether it is present.

Signing is required. Windows 11 24H2 Pro, Enterprise and Education require SMB signing in both directions by default. A third-party server that cannot sign fails with 0xc000a000, "The cryptographic signature is invalid." Microsoft says to enable signing on the server, not to turn the requirement off on the client. Get-SmbClientConfiguration | FL RequireSecuritySignature shows the client's state.

Guest access is blocked. Shares that allow anyone in without a password fail with "You can't access this shared folder because your organization's security policies block unauthenticated guest access." Guest logons do not support signing, so on 24H2 the two settings compound. Give the share a real account instead.

Name resolution or the firewall. Error 0x80070035, "The network path was not found," means the client could not reach port 445 on the server by that name. Check the name first with nslookup fs01, because a stale record or a DNS server not responding produces the same message. Then check the server's firewall for the File and Printer Sharing (SMB-In) rule.

A red X on a working drive is a different thing: the server drops idle SMB sessions after 15 minutes by default, and the drive reconnects the moment it is clicked.

Which Method to Use

One PC, one share: File Explorer with Reconnect at sign-in ticked. A workgroup or a handful of PCs: a logon script with net use or New-SmbMapping. A domain: a Group Policy Drive Map with the Update action and item-level targeting by group. A share that needs a different account than the user's own: fix the share permissions, because every method that stores a password for you is the one you will regret.

Short Version

Map it in File Explorer for one PC, with net use or New-SmbMapping for a script, and with a Group Policy Drive Map set to Update for a domain. When the letter is missing, check whether you mapped it from an elevated session. When the connection is refused on Windows 11 24H2, check SMB1, signing and guest access on the server before touching the client. If the path itself will not resolve, start with the ipconfig commands that show which DNS server the PC is asking.

FAQ

Why does my mapped drive show a red X in Windows 11?

The server dropped the idle session, which happens after 15 minutes of inactivity by default. The drive reconnects when you open it. If an application needs the session to stay open, run net config server /autodisconnect:-1 on the server.

Does net use work on Windows 11?

Yes. net use S: \\server\share /persistent:yes maps a drive that survives sign-in, net use S: /delete removes it, and net use on its own lists every mapping, including disconnected ones.

Why does New-PSDrive not show the drive in File Explorer?

Without -Persist, New-PSDrive makes a temporary drive that exists only inside PowerShell. Add -Persist and -Scope Global with a single-letter name and a UNC root, or use New-SmbMapping, which always creates a Windows mapping.

Can I map a network drive over the internet without a VPN?

Not over plain SMB on port 445. Windows 11 with a Windows Server 2025 file server supports SMB over QUIC, which tunnels SMB inside TLS 1.3 on UDP 443; the server administrator has to enable it and issue a certificate first.