Users who just lately upgraded to Windows 10 October 2018 Update (1809) started to complain that mapped community drives usually are not mechanically reconnected at Windows startup. After logging in the person sees a giant crimson cross on the icons of all mapped community drives in File Explorer. If you run the command web use in the command immediate, then in entrance of all of the mapped drives you will notice the standing Unavailable. Neither user-attached community drives, nor GPO-mapped drives mechanically reconnect.
Mapped community drive fail to reconnect after upgrading to Windows 10 1809
In this case, a pop-up window seems in the notification space with the alert:
Click right here to examine the standing of your community drives.
Network drives merely stop to be mounted mechanically after restarting the Windows 10 1809 gadget. Mapped community drives are displayed in File Explorer, however connection to them is unavailable. The downside happens with folders related from NAS gadgets, and with on different Windows / Linux computer systems. This bug in Windows 10 1809 replace is confirmed by Microsoft and is deliberate to be fastened in early 2019. At the second, the Microsoft gives a workaround to the issue of restoring connectivity to the mapped community drives (see KB4471218 — Mapped community drive might fail to reconnect in Windows 10, model 1809). To do that, it’s steered to run a sure script at logщт, or if mapped drives are related utilizing group coverage, change the GPO settings.
Logon script to drive reconnect mapped community drives
Run the notepad (notepad.exe), copy the next PowerShell code into it and save the file to the C:PS listing named MapDrives.ps1:
whereas($True) choose LocalPath,RemotePath
foreach( $MappedDrive in $MappedDrives)
$i = $i - 1
if($error.Count -eq zero -Or $i -eq zero)
Start-Sleep -Seconds 30
This script selects all inaccessible mapped drives and tries to reconnect them in persistent mode.
Create one other MapDrives.cmd script file with the next code:
PowerShell -Command "Set-ExecutionPolicy -Scope PresentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1
PowerShell -File "%SystemDrive%PSMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1
This code permits you to appropriately name the PowerShell script described above. You can place this batch file into the person’s startup by copying the MapDrives.cmd file to the %ProgramInformation%MicrosoftWindowsStart MenuProgramsStartUp listing.
You may create a scheduler job to run the MapDrives.cmd file when a person logs on. You can or from the Task Scheduler GUI console (Taskschd.msc).
- Create a brand new job, specify its identify (reMapNetworkDrives), choose what job must be launched of the BuiltinUsers group;
- On the Triggers tab, choose that the duty ought to run when any person logs on to the system (At go online);
- On the Actions tab, in the Program/script discipline, specify the trail to the MapDrives.cmd file;
- On the Conditions tab you may allow the choices Network -> Start provided that the next community connection is on the market -> Any connection;
- Reboot the pc or logoff/logon underneath your person account. When the person logs in, the script ought to run, which can re-create all mapped drive connections.
Please observe that by default community drives related in the elevated mode usually are not out there in regular mode and vice versa. But you may repair it – see the article .
Reconnecting mapped community drives by way of GPO
If you map community drives to customers utilizing area group insurance policies, you might want to change the coverage settings in order to attach the drives appropriately.
Open the area coverage that connects the drives, and in the part User Settings -> Preferences -> Windows Settings -> Drive maps, discover your community drive project coverage (insurance policies) and alter the Action kind from Update to Replace.
After the coverage is up to date on the purchasers when the person logs in, the mapped community drives can be deleted and reassigned.