Windows 10: Mapped network drives don't work in Windows 10 version 1809

Compumind · Nov 16, 2018

Symptoms

You experience the following issues in Windows 10, version 1809:

In Windows Explorer, a red X appears on the mapped network drives.

Mapped network drives are displayed as Unavailable when you run the net use command at a command prompt.

In the notification area, a notification displays the following message:Could not reconnect all network drives.

Workaround

You can work around this issue by running scripts to automatically reconnect mapped network drive when you log on the device. To do this, create two script files, and then use one of the workarounds, as appropriate.

Scripts

Create a script file named MapDrives.cmd

The script file includes the following scripts. The file should be run at a regular (non-elevated) command prompt:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%\StartupLog.txt" 2>&1
PowerShell -File "%SystemDrive%\Scripts\MapDrives.ps1" >> "%TEMP%\StartupLog.txt" 2>&1

Create a script file named MapDrives.ps1

The script file includes the following scripts. The file should be run at a regular (non-elevated) command prompt:

$i=3
while($True){
$error.clear()
$MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath
foreach( $MappedDrive in $MappedDrives)
{
try {
New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True
} catch {
Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"
}
}
$i = $i - 1
if($error.Count -eq 0 -Or $i -eq 0) {break}
Start-Sleep -Seconds 30
}

Workarounds

Workaround 1: Create a startup item

Note This workaround works only for the device that has network access at logon. If the device has not established a network connection by the time of logon, the startup script won't automatically reconnect network drives.

Copy the script file (MapDrives.cmd) to the following location:

%ProgramData%\Microsoft\Windows\Start Menu\Programs\StartUp

Copy the script file (MapDrives.ps1) to the following location:

%SystemDrive%\Scripts\

A log file (StartupLog.txt) will be created in the %TEMP%\ folder.

Log off, and then log back on to the device to open the mapped drives.

Workaround 2: Create a scheduled task

Copy the script file MapDrives.ps1 to the following location:

%SystemDrive%\Scripts\

In Task Scheduler, select Action > Create Task.

On the General tab in the Create Task dialog box, type a name (such as Map Network Drives) and description for the task.

Select Change User or Group, select a local user or group (such as LocalComputer\Users), and then select OK.

Select the Run with highest privileges option.

On the Triggers tab, select New, and then select At log on for the Begin the task field.

On the Actions tab, select New, and then select Start a program for the Action field.

Type Powershell.exe for the Program/script field.

In the Add arguments (optional) field, type the following:
-windowsstyle hidden -command .\MapDrives.ps1 >> %TEMP%\StartupLog.txt 2>&1

In the Start in (optional) field, type the location (%SystemDrive%\Scripts\) of the script file.

On the Conditions tab, select the Start only if the following network connection is available option, select Any connection, and then select OK.

Log off, and then log back on to the device to run the scheduled task.

Workaround 3: Group Policy settings

If the mapped drives are defined through the Group Policy settings, update the action of the drive maps to Replace. This will delete the existing mapped drive and create the mapping again on each logon. Any settings on the mapped drive that are changed from the Group Policy settings will be lost on each logon. You may also have to run the gpupdate command (together with the /force parameter) to update the Group Policy settings.
Click to expand...

Source: https://support.microsoft.com/en-us/...0-version-1809

:)

CraigS · Nov 16, 2018

Work Mapped drives not working at home.

Hello All.

I have a user at work that has a laptop as her main work use (docking station at work, then takes it home to work at home).
we have a list of mapped network drives that we use here, including a personal drive.

however when this user gets home or off the network, the personal drive seems to become inactive/go missing.

there are no USB drives that interfere with the network drives, and i am lost looking for solutions.

any suggestions/help would be greatly appreciated.

thanks.

AmirGh1 · Nov 16, 2018

Windows 10 mapped drives not reconnecting after updating to 1809

We have a few mapped network drives. These have worked until the Windows 10 1809 update. Now, none of the drive letters will automatically connect- the folders are all listed with their associated drive
letters and each has a red cross. If I click on the red cross, they all connect OK and stay mapped while the PC is in use. After a restart, it’s the same.

Anyone any idea how to cure this?

CD[#]KM · Nov 16, 2018

Windows 10 mapped drives not reconnecting after updating to 1809

This is definitely an issue with the 1809 update, as here is what we see and have done:

1. First, this is only affecting drives we have mapped to 2012 servers. It is not affecting a couple drives mapped to an old 2003 server (for testing).

2. If I create a new logon/profile, and map a drive, it connects fine. But after logging off and back on, it has the red x and needs to be opened to refresh. This happens if I map from Explorer and using the net use command.

3. Since the mapping to the old 2003 server works (SMB1.0), it is not likely a network or DNS issue. Plus the systems on my network that I have not installed the 1809 update on do not have the issue, just the few I updated.

4. I also tried mapping with the FQDN of the share and it still does the same thing with the red X's

5. Three patches/updates to 1809 update just came out, and I installed them, and they do not resolve the issue.

This issue is not listed as a known issue on the Windows 10 Update History/info page, so I am not confident that Microsoft is aware of this issue and is working on fixing it: https://support.microsoft.com/en-us/help/4464619/windows-10-update-history

Windows 10: Mapped network drives don't work in Windows 10 version 1809

Mapped network drives don't work in Windows 10 version 1809

Mapped network drives don't work in Windows 10 version 1809

Mapped network drives don't work in Windows 10 version 1809

Mapped network drives don't work in Windows 10 version 1809 - Similar Threads - Mapped network drives

Windows 10: Map a network drive.

Windows 10: Map a network drive.

Mapping a network drive windows 10

Map network drive not working in windows 10 solution

Windows 10 map network Drive

Mapped network drives not working in Windows 10

Mapped Network Drives issue in Windows 10 version 1809

Network drive don't work?

Map Network Drive in Windows 10

Users found this page by searching for:

windows 10 1809 ip based drive mapping

windows 1809 network drives ip not working