What to Do When Mapped Drives Are Missing in Windows 10?

If mapped network drives stopped appearing in File Explorer, the drives are either disconnected or Explorer is hiding them; confirming which it is and then reconnecting the share with the correct UNC path and credentials fixes most cases. Follow the diagnostic steps to determine whether the mapping still exists logically, fix credentials or network issues, and recreate the mapping so it persists across sign‑ins. If the PC is domain‑joined, involve IT before changing Group Policy or domain settings.

Are the mapped drives really missing or just hidden?

What you see: File Explorer shows fewer drives than you expect or mapped letters are gone. This can happen when Windows drops a connection, credentials fail, the server is offline, or Explorer is not displaying the mapping.

Start here so you know what to fix.

1. Open "This PC" in File Explorer and look under "Network locations." If a mapped drive shows a red X, the connection is disconnected.

2. Check for mappings at the system level:

3. In an elevated Command Prompt (search cmd, right‑click, Run as administrator) run:

net use

The command lists mapped drives and their status (OK, Disconnected, or an error). If the drive appears here but not in Explorer, the mapping exists but Explorer’s shell isn’t showing it.

4. In PowerShell as administrator run:

Get-PSDrive -PSProvider FileSystem

If a network drive appears in net use or Get-PSDrive but not in Explorer, the issue is a visibility or timing problem rather than a lost mapping. If neither command lists the drive, treat it as a lost mapping and proceed to reconnect steps.

Before you start (applicability and safe checks)

This article assumes a Windows 10 PC and a user account able to map drives (local admin is helpful for some checks). If the PC is joined to a corporate domain, check with IT before changing Group Policy, SMB settings, or domain policies.

• Preconditions:
• The server or NAS hosting the share is online and reachable on the network.
• You know the share’s UNC path (for example \\fileserver\share) and valid credentials if required.

• Safe checks before changes:

1. Verify you can reach the server by pinging its hostname or IP.
2. Note any stored credentials for the server in Credential Manager; you will remove or update these during troubleshooting.
3. If you will change SMB settings or enable SMB v1, get explicit approval for devices used in a multi‑user or managed environment; enabling SMB v1 increases risk.

• Stopping conditions: stop and contact IT if the mapping was originally created by a central policy (Group Policy Preferences or logon scripts) or if you do not have permission to change network or server settings.

Quick checks to restore simple cases

These low‑risk steps often restore mappings without deeper changes.

1. Re-sign in or reboot after credential or network changes.

2. Verify server reachability:

ping fileserver

If ping by name fails but ping by IP succeeds, DNS or name resolution is the problem; continue to the DNS checks in Advanced diagnostics.

3. Remap using File Explorer:

1. Open File Explorer and click "Map network drive."
2. Choose a drive letter and enter the UNC path (for example \\fileserver\share).
3. If needed, check "Connect using different credentials."

4. Or map with net use (makes mapping persistent):

net use Z: \\fileserver\share /persistent:yes

If the share requires domain credentials, add /user:DOMAIN\username and you will be prompted for the password.

If the mapping succeeds and stays after a restart, stop here. If it disappears after sign‑in, continue to the next sections.

Check common Windows causes and fixes

If quick checks didn’t help, work through these common causes in this order: stored credentials, network profile, SMB settings, Group Policy or logon scripts, and delayed network initialization.

1. Credential Manager (stale or wrong credentials)

1. Open Control Panel > Credential Manager > Windows Credentials.
2. Find entries for the server (hostname or IP) and remove them.
3. Reconnect to the share so Windows prompts you for fresh credentials and save them if appropriate.

If reconnecting still fails with access denied, confirm the username/password and domain are correct.

2. Network profile

1. Open Settings > Network & Internet > Status > Change connection properties and set the connection to Private when you trust the network.

A Public profile can block discovery and mapped shares; changing to Private often restores access on trusted home or small-office networks.

3. SMB client configuration

1. Check client SMB configuration in an elevated PowerShell:

Get-SmbClientConfiguration

2. Inspect active SMB connections:

Get-SmbConnection

If the server requires a specific SMB dialect, consult the server or NAS documentation before changing client settings.

4. Group Policy and logon scripts (domain environments)

1. If mappings were deployed by IT, confirm with them first.

2. If you manage the PC and suspect a local policy, run gpedit.msc and check User Configuration > Preferences > Windows Settings > Drive Maps for any configured mappings.

If a central policy is managing mappings, don’t override it without coordinating with IT.

5. Delayed network initialization (race at sign‑in)

Some systems process persistent mappings before the network stack or authentication is ready. Use a short delay and remap after sign‑in.

1. Create a PowerShell script that waits for connectivity then maps drives. Example (adjust UNC and letters):

Start-Sleep -Seconds 10
if (Test-Connection -ComputerName fileserver -Count 2 -Quiet) { New-PSDrive -Name "Z" -PSProvider FileSystem -Root "\\fileserver\share" -Persist }

2. Place a shortcut to the script in the user’s Startup folder or create a Task Scheduler task that runs at logon with a 10–30 second delay.

If these checks don’t restore the mapping, proceed to Advanced diagnostics.

Advanced diagnostics and commands to try

Collect evidence and try targeted fixes if the problem persists.

1. Confirm IP, DNS and adapter configuration:

ipconfig /all

Look for correct IP, DNS servers and adapter status. Name resolution problems break UNC paths.

2. Test name resolution and reachability:

ping fileserver

If name fails but IP works, fix DNS or use the server hostname that resolves.

3. Clear stale mappings before recreating them:

net use * /delete

Use this if you want to remove all mapped drives first. Ensure no critical process depends on those mappings when you run this.

4. Check SMB client connections and mapped drives in PowerShell:

Get-SmbConnection
Get-PSDrive -PSProvider FileSystem

5. Check services that affect network drives

1. Open Services (services.msc) and ensure these services are running: Workstation, TCP/IP NetBIOS Helper. Set them to Automatic or Manual according to your environment.

6. Inspect Event Viewer for errors

1. Open Event Viewer > Windows Logs > System and look for errors from Workstation, Netlogon, or SMBClient around the time of login. The exact messages vary by cause; use the timestamps to correlate with sign‑in attempts.

If diagnostics show DNS or server reachability issues, fix those first (DNS entries, hostnames, server availability). If diagnostics show authentication errors, recheck credentials and domain trust.

Verify results

Confirm the mapping is present and usable.

1. In File Explorer, open This PC and verify the mapped drive appears with the expected letter and accessible folders.

2. Verify at the command line:

net use

Expected output: the mapped drive letter, the remote path and status OK.

3. Verify from PowerShell:

Get-PSDrive -PSProvider FileSystem

Expected output: the mapped drive listed with a valid Root. If the mapping appears in net use or Get-PSDrive but not in Explorer, try signing out and back in or restarting Explorer (Task Manager > Windows Explorer > Restart). If the mapping disappears after a restart, revisit credential storage, delayed mapping script, or Group Policy.

How to make mappings reliable and prevent recurrence

Choose the approach that fits your environment.

• Single PC or small office

1. Create mappings with net use and /persistent:yes so they are stored across logins.

2. Save credentials in Credential Manager and update them when passwords change.

3. If network initialization is slow, use a startup script or Task Scheduler task that runs a short time after logon and remaps drives.

• Domain‑managed environments

1. Use Group Policy Preferences (Drive Maps) to deploy mappings centrally; that is the supported, scalable method for multiple users.

2. Coordinate any SMB protocol changes with IT and check server/NAS vendor guidance before enabling legacy protocols like SMB v1.

Preventive checklist:

• Keep server/NAS firmware and Windows updates current; verify SMB compatibility with the vendor before changing protocols.
• Use stable hostnames that resolve in your network DNS; avoid binding mappings to IPs that can change.
• Avoid mapping to devices that sleep aggressively; configure NAS sleep settings or use scripts tolerant of brief unavailability.

Conclusion

If a simple reconnect restores the drive, you’re done. If not, follow the sequence: confirm whether the mapping exists, check credentials and network reachability, inspect SMB and policy settings, then apply a persistent mapping or a delayed startup script. Contact IT when Group Policy or domain settings may be responsible.