network drive fails to connect when starting up

The correct fix depends on whether the NAS mapping is managed by Group Policy or is an ordinary File Explorer mapping: wait for the network in the first case, or run a network-dependent reconnect task in the second.

If the drive is mapped by Group Policy

Windows clients normally do not wait for the network to initialize before logon; Group Policy is processed later after connectivity becomes available. Enable the policy that makes startup and logon processing synchronous instead.^1^

This policy applies to supported Pro, Enterprise, Education, and IoT Enterprise editions—not Windows Home.

1. Press Windows+R, enter gpedit.msc, and select OK.
2. Go to Computer Configuration → Administrative Templates → System → Logon.
3. Open Always wait for the network at computer startup and logon.
4. Select Enabled, then Apply → OK.
5. Restart and verify that the mapped drive is available without restarting Explorer.

For an Intune-managed device, the corresponding device policy is:

./Device/Vendor/MSFT/Policy/Config/ADMX_Logon/SyncForegroundPolicy

This is particularly relevant when the mapping uses the Group Policy Drive Maps extension; asynchronous processing can prevent that extension from applying when a slow connection is detected.^2^

If it is a normal File Explorer mapping

Since restarting Explorer restores access, configure a standard-user scheduled task to reconnect unavailable mappings after a network becomes available. Microsoft documents this workaround specifically for Windows 10 version 1809, so first run winver; use the documented script directly only if that is your version.^3^

1. Create C:\Scripts\MapDrives.ps1:

$i = 3
while ($true) {
    $Error.Clear()
    Get-SmbMapping |
        Where-Object Status -eq 'Unavailable' |
        ForEach-Object {
            New-SmbMapping -LocalPath $_.LocalPath `
                -RemotePath $_.RemotePath -Persistent $true
        }
    if ($Error.Count -eq 0 -or --$i -eq 0) { break }
    Start-Sleep -Seconds 30
}

2. Open Task Scheduler → Action → Create Task.
3. On General, name it Reconnect NAS drives and run it as your normal user. Do not select “Run with highest privileges”; an elevated mapping may not appear in the standard Explorer session.
4. On Triggers, add At log on.
5. On Actions, select Start a program:
   • Program: Powershell.exe
   • Arguments: -WindowStyle Hidden -File "C:\Scripts\MapDrives.ps1"
6. On Conditions, enable Start only if the following network connection is available and choose Any connection. Task Scheduler supports restricting execution until networking is available.^4^
7. Sign out and back in, then check the task’s Last Run Result and the drive status.

If the computer is not running Windows 10 version 1809, the documentation does not establish that its specific reconnect defect applies. In that case, prefer the Group Policy remedy when the drive is centrally mapped; otherwise, use Task Scheduler only as an operational workaround and investigate the Wi-Fi startup delay separately.

Do not enable SMBv1, insecure guest access, or disable SMB signing for this symptom alone. Those changes address NAS protocol or authentication compatibility, while the fact that access works after restarting Explorer points instead to connection timing.

References

1. Policy CSP - ADMX_Logon
2. Policy CSP - ADMX_GroupPolicy
3. Mapped network drive may fail to reconnect in Windows 10, version 1809
4. RunOnlyIfNetworkAvailable (settingsType) Element