How to Fix ‘Could Not Reconnect All Network Drives’ in Windows 11

When logging into Windows 11, seeing a taskbar notification banner stating “Could not reconnect all network drives” accompanied by red “X” icons across mapped network shares in File Explorer indicates that the Windows Shell attempted to mount Server Message Block (SMB) network shares before the physical network adapter completed IP configuration. Because modern computers boot rapidly with solid-state drives (SSDs) and Windows Fast Startup, user login completes seconds before Wi-Fi or Ethernet adapters establish DHCP leases. Although clicking on the disconnected drive icon typically opens the share without issue, the notification disrupts automated backup tasks and creates false alarms. Resolving this issue involves configuring group policies to wait for network connectivity or automating deferred drive mapping.

Why Windows Reports Disconnected Network Drives at Startup

During the Windows 11 logon sequence, the Multiple Provider Router (MPR) queries mapped network drive configurations stored under HKEY_CURRENT_USER\Network and initiates connection handshakes with remote file servers or NAS appliances. If the network adapter driver is still initialising or waiting for an IP address lease from the local DHCP server, the SMB connection attempt fails immediately. While Windows retains the mapped drive letter, it marks the drive with a disconnected status and displays the notification banner.

Common causes of network drive reconnection failures include:

• Asynchronous Network Initialization: Windows 11 loading the desktop shell before local network hardware acquires a default gateway. For file execution stalls, see our guide on fixing Windows Cannot Access Specified Device, Path, or File.
• Fast Startup State Hibernation: Windows Fast Startup restoring a hybrid kernel state that skips standard network protocol stack initialization. For account lockouts, see our guide on fixing Referenced Account Is Currently Locked Out in Windows 11.
• Stale Credentials in Windows Vault: Saved credentials in Credential Manager lacking permission to authenticate with the remote SMB share. For update faults, see our guide on fixing Windows Update Error 0x80070003 in Windows 11.
• ProviderFlags Registry Configuration: Missing registry flags that instruct Windows to suppress reconnection warnings.

System Component	Default Windows Behaviour	Failure Trigger	Recommended Policy Adjustment
Windows Logon Engine	Asynchronous (Fast Logon)	Desktop loads before DHCP lease	“Always wait for the network at computer startup”
Multiple Provider Router	Immediate SMB ping on boot	Network adapter offline during ping	Set ProviderFlags to 1 (Suppress notification)
Fast Startup	Resumes from hiberfil.sys	Network driver state desynchronised	Disable Fast Startup in Power Options

Method 1: Enable “Always Wait for the Network at Computer Startup”

For Windows 11 Pro, Enterprise, and Education editions, configuring this Group Policy forces Windows to wait until network adapters are fully initialised before displaying the desktop.

1. Press Win + R, type gpedit.msc, and press Enter.
2. In the Local Group Policy Editor, navigate to:
   Computer Configuration > Administrative Templates > System > Logon
3. In the right pane, locate and double-click the policy named Always wait for the network at computer startup and logon.
4. Select Enabled at the top-left of the policy window.
5. Click Apply, then click OK.
6. Close the Group Policy Editor and restart your computer. Windows will now ensure your network adapter is connected before mapping network drives.

Method 2: Suppress Warnings via ProviderFlags Registry Value

Modifying the network drive configuration in the Windows Registry instructs the operating system to maintain active drive mappings without raising taskbar warnings.

1. Press Win + R, type regedit, and press Enter.
2. Navigate to:
   HKEY_CURRENT_USER\Network
3. Under the Network key, you will see subkeys corresponding to your mapped drive letters (e.g., Z, Y, X).
4. Click into the letter subkey. In the right pane, check for a DWORD value named ProviderFlags.
5. If it does not exist, right-click an empty area in the right pane, select New > DWORD (32-bit) Value, and name it ProviderFlags.
6. Double-click ProviderFlags and set its Value data to 1 (Hexadecimal).
7. Repeat this process for each mapped drive letter under the Network key.
8. Restart your computer. Windows will cleanly handle the network drive connections silently.

Method 3: Create a Delayed Network Drive Mapping Script

Deploying a lightweight PowerShell script via Task Scheduler ensures network drives are mapped only after Windows establishes an active network connection.

1. Press Win + S, type notepad, and open Notepad.
2. Paste the following script lines to wait for network availability before mapping:
   Start-Sleep -Seconds 10
net use Z: "\\Server\ShareName" /persistent:yes
   (Replace Z: and the UNC share path with your actual network drive details).
3. Click File > Save As, name the file MapDrives.ps1, change the file type to All Files (*.*), and save it in C:\Scripts\.
4. Press Win + R, type taskschd.msc, and press Enter.
5. Click Create Basic Task, name it “Delayed Drive Mapping”, set the trigger to When I log on, and set the action to Start a program.
6. In the Program/script field, type powershell.exe, and in Add arguments, type -WindowStyle Hidden -ExecutionPolicy Bypass -File "C:\Scripts\MapDrives.ps1".
7. Save the task. Network drives will now map smoothly without triggering reconnection warnings.

Method 4: Disable Windows Fast Startup

Fast Startup bypasses cold network card driver re-initialisation, frequently leaving SMB network stacks in a dormant state.

1. Open the classic Control Panel, select Hardware and Sound, and click Power Options.
2. Click Choose what the power buttons do in the left pane.
3. Click Change settings that are currently unavailable.
4. Untick the checkbox labelled Turn on fast startup (recommended).
5. Click Save changes, shut down your computer completely, and boot back into Windows.

Method 5: Update Stored Network Credentials in Credential Manager

Ensuring your network share authentication credentials are permanently stored in the Windows Vault prevents authentication re-prompts.

1. Press Win + S, type Credential Manager, and open the utility.
2. Click Windows Credentials.
3. Click Add a Windows credential.
4. Enter the exact hostname or IP address of your NAS or server (e.g. 192.168.1.100 or FILESERVER).
5. Enter the corresponding username and password, then click OK. Windows will now automatically authenticate mapped drives upon boot.