{"id":3890,"date":"2018-11-27T20:17:04","date_gmt":"2018-11-27T20:17:04","guid":{"rendered":"https:\/\/www.fileinspect.com\/blog\/?p=3890"},"modified":"2020-03-04T09:11:14","modified_gmt":"2020-03-04T09:11:14","slug":"fix-mapped-network-drives-problem","status":"publish","type":"post","link":"https:\/\/www.fileinspect.com\/blog\/fix-mapped-network-drives-problem\/","title":{"rendered":"How to fix mapped network drives problem on Windows 10?"},"content":{"rendered":"

After fixing the data deletion issue earlier this month, Microsoft rereleased the Windows 10 October Update, saying the rollout would be slower and targeted to devices that were ready.<\/p>\n

But, within the same week, IT professionals discovered another bug. While this is not new while upgrading Windows 10, this time the mapped network drives fail to reconnect after restarting a PC.<\/p>\n

So, what are the causes of network drive problems in Windows 10 October 2018 update? You\u2019ll also notice a red \u201cX\u201d on the mapped network drives in File Explorer which makes the drives appear as if they are disconnected. Users reported that trying to open a file on one drive might take you to a completely different file.<\/p>\n

Running the net use command displays the mapped network drives as unavailable and there\u2019s a notification displaying the \u201cCould not reconnect all network drives\u201d message.<\/p>\n

Acknowledging the problem, Microsoft warned that a permanent fix was not coming soon, at least not until 2019. Well, that is an awfully long time to wait and the company provided a resolution to solve the issue.<\/p>\n

Here is a step by step guide on how to resolve mapped network drives problem in Windows 10 October Update.<\/p>\n

How to resolve Mapped Network Drives Problem on Windows 10?<\/h2>\n

The mapped network drives are mainly used by network administrators and if you’re an average home user, you’re not likely to notice the bug.<\/p>\n

To fix the issue, you can run scripts to automatically reconnect the mapped network drives when you restart and log on to your computer. You need to create two scripts, – namely the Command Prompt script and the PowerShell script.<\/p>\n

Additionally, reconfiguring the Group Policy settings could solve the problem, especially for those in an Active Directory domain. If you find these solutions to be too complicated, you can pause automatic updates until a stable feature update is released.<\/p>\n

How to create scripts?<\/h2>\n

Follow these instructions to create the scripts to use with the appropriate workaround.<\/p>\n

Creating a Command Prompt script<\/h3>\n
    \n
  1. Launch Notepad.<\/li>\n
  2. Copy and paste the script below on a blank page.<\/li>\n<\/ol>\n

    PowerShell -Command “Set-ExecutionPolicy -Scope CurrentUser Unrestricted” >> “%TEMP%\\StartupLog.txt” 2>&1<\/p>\n

    PowerShell -File “%SystemDrive%\\Scripts\\MapDrives.ps1” >> “%TEMP%\\StartupLog.txt” 2>&1<\/p>\n

      \n
    1. Click the \u201cFile\u201d menu, and select Save As.<\/li>\n
    2. Use MapDrives.cmd as the file name and extension.<\/li>\n<\/ol>\n

      Creating the PowerShell script<\/h3>\n
        \n
      1. Launch Notepad.<\/li>\n
      2. Copy and paste the script below on a blank page.<\/li>\n<\/ol>\n

        $i=3<\/p>\n

        while($True){<\/p>\n

        $error.clear()<\/p>\n

        $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath<\/p>\n

        foreach( $MappedDrive in $MappedDrives)<\/p>\n

        {<\/p>\n

        try {<\/p>\n

        New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True<\/p>\n

        } catch {<\/p>\n

        Write-Host “There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath”<\/p>\n

        }<\/p>\n

        }<\/p>\n

        $i = $i – 1<\/p>\n

        if($error.Count -eq 0 -Or $i -eq 0) {break}<\/p>\n

        Start-Sleep -Seconds 30<\/p>\n

        }<\/p>\n

          \n
        1. Click the \u201cFile\u201d menu, and select Save As.<\/li>\n
        2. Use MapDrives.ps1 as the file name and extension.<\/li>\n<\/ol>\n

          Solution 1: Run scripts at startup<\/h2>\n

          Use the Command Prompt and PowerShell scripts you created above to reconnect the mapped network drives.<\/p>\n

          Note: This fix only works if the device has an established network connection at login.<\/p>\n

            \n
          1. Launch File Explorer.<\/li>\n
          2. Navigate to the following location:<\/li>\n<\/ol>\n

            %ProgramData%\\Microsoft\\Windows\\Start Menu\\Programs\\StartUp<\/p>\n

              \n
            1. Copy the MapDrives.cmd script file into the Startup folder.<\/li>\n
            2. Navigate to the following location:<\/li>\n<\/ol>\n

              %SystemDrive%\\Scripts<\/p>\n

                \n
              1. Copy the MapDrives.ps1 script file into the Scripts folder.<\/li>\n<\/ol>\n

                Important tip: If you don\u2019t see the Scripts folder, you can quickly create one. Open the C drive in File Explorer, and click on New Folder (or use Ctrl + Shift + N). Name the folder \u201cScripts\u201d<\/p>\n

                  \n
                1. This creates a log file (StartupLog.txt) in the %TEMP% folder showing the log information.<\/li>\n
                2. Sign out of your system, and then sign back in. The mapped drives should work normally.<\/li>\n<\/ol>\n

                  Solution 2: Run the scripts using Task Scheduler<\/h2>\n

                  Using the Task Scheduler, create a task to reconnect the mapped network drives while logging into your device.<\/p>\n

                    \n
                  1. Launch File Explorer.<\/li>\n
                  2. Follow this path to open the Scripts folder:<\/li>\n<\/ol>\n

                    %SystemDrive%\\Scripts<\/p>\n

                    Important tip: If you don\u2019t see the Scripts folder, you can quickly create one. Open the C drive in File Explorer, and click on New Folder (or use Ctrl + Shift + N). Name the folder \u201cScripts\u201d<\/p>\n

                      \n
                    1. Copy the MapDrives.ps1 script file into the Scripts folder.<\/li>\n
                    2. Click Start or press the Windows Key.<\/li>\n
                    3. Type the words \u2018Task Scheduler\u2019 and hit Enter.<\/li>\n
                    4. In Task Scheduler, go to Action > Create Task.<\/li>\n
                    5. Make sure you’re on the General tab.<\/li>\n
                    6. In the Name dialog box, assign a relevant name to the task, for instance, Map Network Drives, and add a description.<\/li>\n
                    7. Select the “Change User or Group” button, and select a local user or group, for example, Users or Guests.<\/li>\n
                    8. Click OK.<\/li>\n
                    9. Check the box next to \u201cRun with highest privileges.\u201d<\/li>\n
                    10. Under the \u201cTriggers\u201d tab, select New.<\/li>\n
                    11. Click Begin the task > At log on.<\/li>\n
                    12. Click OK.<\/li>\n
                    13. Open the \u201cActions\u201d tab, and click \u201cNew.\u201d<\/li>\n
                    14. Using the \u201cAction\u201d drop-down list, select \u201cStart a program.\u201d<\/li>\n
                    15. Type Powershell.exe in the \u201cProgram\/script box.\u201d<\/li>\n
                    16. In the \u201cAdd arguments (optional)\u201d field, type:<\/li>\n<\/ol>\n

                      -windowsstyle hidden -command .\\MapDrives.ps1 >> %TEMP%\\StartupLog.txt 2>&1<\/p>\n

                        \n
                      1. In the \u201cStart in (optional)” field, type the location of the script file as follows:<\/li>\n<\/ol>\n

                        %SystemDrive%\\Scripts\\<\/p>\n

                          \n
                        1. Click OK.<\/li>\n
                        2. Next, go to the \u201cConditions\u201d tab.<\/li>\n
                        3. Check the box next to \u201cStart only if the network connection is available.\u201d<\/li>\n
                        4. Select \u201cAny connection,\u201d and click OK.<\/li>\n<\/ol>\n

                          Sign out and then sign back into your account to run the mapped drives without issues.<\/p>\n

                          Solution 3: Modify the Group Policy Settings<\/h2>\n

                          As a network administrator, you can edit the Group Policy Object (GPO) by choosing \u201cReplace\u201d in the \u201cAction\u201d drop-down list. Use the following steps:<\/p>\n

                            \n
                          1. Right-click your policy object and select \u201cEdit\u201d<\/li>\n
                          2. Open User Configuration > Preferences > Windows Settings > Drive Maps.<\/li>\n
                          3. Right-click \u201cDrive Maps.\u201d<\/li>\n
                          4. Select New > Mapped Drive.<\/li>\n
                          5. Select the \u201cGeneral\u201d tab, and then click Action > Replace<\/li>\n
                          6. This deletes the specified mapped drive, if it exists, and then recreates a new one. If the mapped drive doesn\u2019t exist, this action creates a new mapped drive when the user logs back into the account.<\/li>\n
                          7. Restart the machine and you should see the mapped drives in File Explorer.<\/li>\n<\/ol>\n

                            Solution 4: Delay Windows 10 October Update<\/h2>\n

                            If you\u2019ve not yet upgraded to Windows 10 October Update, you can defer new feature updates for several months.<\/p>\n

                            Follow these steps:<\/p>\n

                              \n
                            1. From the Start Menu, go to Settings.<\/li>\n
                            2. Scroll down to Update & Security.<\/li>\n
                            3. In \u201cWindows Update,\u201d click \u201cAdvanced options\u201d<\/li>\n
                            4. Navigate to \u201cChoose when updates are installed\u201d<\/li>\n
                            5. Select either:<\/li>\n<\/ol>\n