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?

 

Question Info


Last updated December 13, 2019 Views 9,500 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hi,

Thank you for writing to Microsoft Community Forums.

The better way to reconnect mapped drives is to turn off fast startup. This will not affect the performance of your device, since PC’s running Windows 10 generally have faster core processors.

Try the below suggested steps.

1. Type Power Options in the Search window.

2. Select Choose what the power buttons do.

3. Click Change settings that are currently unavailable.

4. Uncheck Turn on fast startup.

Hope it helps

Muralidhar

Microsoft Community - Moderator

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi Muralidhar,

We've already checked all the settings, everything is ok.

I'm sure it's related to October update build 1809!!!!!

We never had that issue on the previous version (1803 and 1709).

So, how we can fix that?

Regards,

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello,

This issue is directly related to the 1809 update.  Same issue as the OP.  When I rolled back the 1809 update to 1803, the drives mapped correctly again, no red "X". 

The network drives map to shares on servers running the Server 2012 R2 operating system and those drives do not reconnect, they show disconnected after logon. The user must open file explorer and primary click each disconnected network drive in order to reconnect the drives.

In group policies I have enabled "Always wait for the network at computer startup and logon".  In the properties of the drive mapping GPO I have tried every action: "Create" "Replace" and "Update" with no success. I have turned off the fast startup.

As a temporary work around I have had to setup a bat file to run via GPO after the user logs in to reconnect the drives.

Regards,

Robert

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We are faced with the same issue and the cumulative update on the 9th has not addressed it.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Still, the same issue....cumulative update on the 9th has not fixed that...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

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

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

same problem here.

updated all pc's to 1809, reboot.

all network shares [x] red X, until opened via explorer

(shared from server2012r2)

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I followed your suggestion, but I still have the same issue.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We are having the same problem with Win10 desktops and Server 2016 shares. I'm creating the drive maps using Group Policy on a domain. I can manually click on the drives with the red X and it will force the connection, but unless you do this at every boot, the drives are not online to the system/apps. It was fine before the 1809 update. I have tried many registry hacks, disable fast startup, startup delays, and other suggestions online but nothing fixes it. The only solution I have found is to create a net use script and run it in a scheduled task to re-create the drive maps after a delay once a user logs in. I have seen where some people solved it by disabling the spanning tree protocol on their LAN switches, but I have not tried this yet as I'm not familiar with switch configurations. I don't want to tweak my network gear to fix a problem that MS created in a update. Hopefully MS will address this soon.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You seem to be working with an older version of Windows, because in my 1809 that option is no longer there.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.