Mapped Drive Shows Empty in Windows 10/11 After Login

EP
Erropedia Team
📅 June 27, 2026 📅 Updated Aug 2, 2026 👁 16 views Network & Connectivity Intermediate
You map a network drive, it shows up in File Explorer, but the folder is empty. Happens often after Windows updates or sleep/wake cycles.

When This Happens

You map a network drive — say Z: pointing to \\server\share. It shows up in File Explorer with the correct label and icon. But when you click on it, the folder pane is empty. No files, no folders. You can still access the share directly via the UNC path (\\server\share) and see everything fine.

This bug is common on Windows 10 and Windows 11 after the 22H2 update. Also happens when you put the PC to sleep and wake it up. Or when you connect via VPN — the drive gets mapped before the network is fully ready.

Root Cause

What's actually happening here is that Windows mounts the drive letter before it establishes a proper authenticated session with the remote server. The drive mapping exists at the kernel level — it's a symlink in the object manager namespace — but the actual SMB session isn't alive. So Explorer sees the drive letter, tries to list it, gets nothing back because the session is dead.

The reason this happens specifically after updates or sleep is that Windows changes the way it handles network drive persistence. In older versions, mapped drives kept their connection alive. In newer versions, Windows might drop the session to save power or because of a security policy change. The drive letter stays, the connection doesn't.

The Fix — Step by Step

  1. Check if the drive is actually connected.
    Open Command Prompt as admin. Type net use Z: and hit Enter. If it says "The connection is no longer available" or "Disconnected", you've confirmed the issue.
  2. Disconnect and remap the drive.
    Run net use Z: /delete. Then remap: net use Z: \\server\share /persistent:yes. This often fixes it temporarily.
  3. Apply the Group Policy fix (permanent).
    The real fix is to tell Windows to wait for the network before mounting drives. Press Win + R, type gpedit.msc (Pro/Enterprise only — see step 4 for Home users).
    Go to: Computer Configuration > Administrative Templates > System > Logon.
    Find "Always wait for the network at computer startup and logon". Set it to Enabled.
    Then find "Specify startup policy processing wait time". Set it to a value like 30 seconds.
  4. For Windows 10/11 Home users — use a script.
    Home edition doesn't have gpedit. Create a scheduled task instead:
    Open Task Scheduler. Create a task that runs at logon. Trigger: "At log on of any user". Action: start a program C:\Windows\System32\cmd.exe with arguments /c net use Z: /delete & net use Z: \\server\share /persistent:yes.
    Check the box "Run with highest privileges". This remaps the drive on every login, after the network is ready.
  5. Set the drive to reconnect on idle.
    Open Registry Editor (regedit). Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Restore. Create a DWORD called RestoreTimeout and set it to decimal 60. This gives Windows 60 seconds to restore the connection before showing it as disconnected.

Why Step 3 Works

The Group Policy setting forces Windows to wait until the network stack is fully initialized before processing logon scripts and drive mappings. Without it, Windows maps the drive during boot when the network adapter might not have an IP yet — or the SMB session hasn't authenticated. The 30-second wait means the network driver, DHCP, DNS, and the SMB redirector all get time to come up. It's a brute-force delay, but it works because it addresses the timing mismatch.

Still Empty? Check These

  • Permissions. Open the share directly via \\server\share. If you get an access denied, the problem is on the server side — your user account doesn't have read rights. Mapped drive can't show files it can't see.
  • Hidden files. The folder might contain only hidden or system files. In File Explorer, enable "Show hidden files" and uncheck "Hide protected operating system files".
  • Antivirus or firewall. Some security software blocks SMB traffic after resume. Temporarily disable the firewall to test. If it works, add an exception for svchost.exe on port 445.
  • VPN or network profile. If you use a VPN, make sure the VPN connection is established before you check the drive. Some VPNs change the network profile to "Public" — Windows blocks drive access on public networks by default. Set the network to "Private" in Windows Settings.

If nothing works, don't waste time. Use the UNC path directly (\\server\share) and pin it to Quick Access. The mapped drive is a convenience, not a necessity. If your IT department pushes mapped drives via Group Policy, talk to them — they might have a policy that conflicts with local settings.

Related Errors in Network & Connectivity
WiFi Keeps Dropping on Windows 10/11 – A Real Fix That Works 0XC01E0580 I2C not supported error 0XC01E0580 on monitor 0XC00D158B Fix NS_E_PORT_IN_USE_HTTP (0XC00D158B) in 3 steps 0X80130004 Fix 0x80130004: Cluster Network Already Offline Error
mapped drive empty network drive shows empty Windows mapped drive not showing files mapped drive empty after sleep network drive empty fix Windows 11 mapped drive empty mapped drive permissions empty group policy mapped drive empty mapped drive not refreshing network location empty

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.