Mapped network drives are convenient when they work — a network location that behaves like a regular drive letter — but they have a reputation for occasionally disconnecting, especially after a restart or period of inactivity. The cause is usually one of a small set of well-understood issues.

Ad placeholder — in-article responsive unit

Fix 1: confirm "Reconnect at sign-in" was actually checked

This is the most common oversight — if this box wasn't checked when the drive was originally mapped, Windows won't automatically reconnect it after a restart:

  1. Right-click the disconnected drive in File Explorer → it may show options to reconnect directly
  2. If you need to remap it: in File Explorer, click This PC, then in the ribbon, Map network drive
  3. Enter the folder path, and make sure "Reconnect at sign-in" is checked this time

Fix 2: a delay between network availability and Windows trying to reconnect

Sometimes Windows attempts to reconnect mapped drives before the network connection is actually fully ready (especially on Wi-Fi, which can take a moment longer than Ethernet to establish after boot), causing the reconnection attempt to fail even though "Reconnect at sign-in" is correctly set. A registry adjustment can help Windows wait appropriately:

  1. Press Windows key + R, type regedit, press Enter
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
  3. Right-click in the right pane → New → DWORD (32-bit) Value, name it RestoreConnection
  4. Set its value to 1
  5. Restart your computer

Fix 3: stored credentials have expired or changed

If the drive requires authentication and your saved password has changed (or expired, common with organizational password policies), the drive will fail to reconnect silently:

  1. Open Credential Manager
  2. Click Windows Credentials
  3. Find the entry related to the network drive/server and remove it
  4. Try accessing the mapped drive again — you should be prompted for fresh credentials, which will then be saved correctly going forward

Fix 4: the host computer or server went to sleep

If the mapped drive points to a shared folder on another regular computer (rather than a dedicated server or NAS), and that computer goes to sleep or hibernates, the share becomes unavailable until it wakes up — this looks identical to a connection problem but is really a power-management issue on the host machine. On the computer hosting the share, check Settings → System → Power & battery and adjust sleep settings if this is happening regularly.

Fix 5: SMB protocol version mismatch

Less common, but worth knowing: if you're connecting to an older NAS device or server that only supports older SMB protocol versions, and a Windows update has tightened default security settings around older SMB versions, connections can become unreliable. This is a deeper issue that may require updating the NAS/server's firmware, or in some cases re-enabling an older SMB version temporarily on the Windows side (via Control Panel → Programs → Turn Windows features on or off → SMB 1.0/CIFS) — though this does reduce security, so it's worth checking whether updating the NAS firmware is possible instead.