Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, June 17, 2020 9:17 AM
I am running Windows 10 Professional version 20H2 on a Dell laptop and generally have had no problems. On the computer, I map to 6 networked drives on my home LAN, and have successfully done so since purchasing and setting up this laptop a year ago. I connect via wifi, and haven't had any problems with mapping; reading from or writing to these drives until the recent upgrade of Win10 to version 2020.
Before this upgrade, if I disconnected my computer from my LAN, when I reconnected to my network, my mapped drives would all show a red X on them in Explorer - as I'd expect. If I then selected a specific drive, I would be asked for my credentials (user name and password), which I'd supply, and the drive would be instantly available. This was the case for all six drives, regardless of the remote server system. This is EXACTLY as I would expect and was never considered a problem.
However, after the 2020 upgrade, if I disconnect / reconnect as before, the mapped network drives still show a red X. Now, though, if I select a drive, I will - eventually - get a dialog that tells me that 'The specified network name is no longer available' and I cannot reconnect to the drive. I have to disconnect the mapped drive and re-map it, when it will instantly connect and it can be used exactly as before. This process is not difficult - but it is extremely tedious every time I disconnect from my LAN. I see from my research that similar problems have been ongoing for many years, although as I described above, I never saw the problem before the upgrade. I have tried some of the so-called 'fixes', although none have been at all successful, and I have removed them all. So - is this a known issue with Win10 version 2020 (and 20H2) - and if so, what steps is Microsoft taking to solve it? Indeed, IS there a workable solution? Many thanks for any assistance - Mike
All replies (14)
Thursday, June 18, 2020 5:02 AM
Hi,
Sorry for the inconvenience has caused.
Based on my further research, I found a video which introduced a workaround of this issue, and the video provided a script that can help to this situation.
Here's the link:
https://www.youtube.com/watch?v=q8KVJdgewNk
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
If it works please tell us and this may help other people who has the same problem with you.
Thanks!
Best regards,
Cherry
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, June 19, 2020 7:18 AM
Thank you for your advice, but this website offers nothing in the way of a solution to my problem. This might have been obvious had you looked at the date of the solution - 2018. I thought that I had made it very clear that the problem I have has ONLY occurred since the latest upgrade to Windows 10, and this makes it extremely unlikely that a 'solution' from 2018 would solve a problem first seen in May 2020. Indeed, the so-called solution on this website actually "solves" what I have clearly identified in my second paragraph was the 'state of play' before the upgrade, and as I said then, and will say again now 'This is EXACTLY as I would expect and was never considered a problem.'
Running the associated batch file merely leaves me with a series of dialogs on the screen, each of which says: 'An error occurred while reconnecting X: to \SERVER\share Microsoft Windows Network: The local device name is already in use, The connection has not been restored' Of course, the value X: and the name \SERVER\share changes for each according to its mapping.
So, sorry, but this is about as useful as a chocolate teapot........
Regards
Mike
Friday, June 19, 2020 9:37 AM
Hi，
Please try this way：
Open regedit，run as administrator，go to
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Policies\System
Click on Edit\New\Dword (32bit) Value
Value name: EnableLinkedConnections
Value data: 1
base: Hexadecimal
Restart your computer to apply the changes.
Note: Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Or backup regedit before you change it.
BR
Cherry
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Sunday, June 21, 2020 3:03 AM
Thank you again, Cherry, but I'm afraid this hasn't made an iota of difference. In fact, when I checked, there wasn't a (sub)key \Policies\System under the \CurrentVersion key in my registry The only key under \CurrentVersion was \Internet Settings. I created the new keys and then, as suggested added the new DWord and set it to 1 (0x00000001)
Here's my selected key pasted directly from RegEdit:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Policies\System
so that you can see it is indeed correct.
I think I will have to live with this inconsistency until a correct fix is made available. As a technically competent person, it is not a problem - more of a 'ho-hum' chore as I only reboot my system a couple of times a week after using it elsewhere. However, I do have concern that a less technically able user would have great difficulties with this!
Monday, June 22, 2020 3:02 AM
Hi，
I'm so sorry for the inconvenience, however, I have seen someone occurred the same situation for you, he resolved it by reinstalling the system. So, if it's not too trouble for you, would you please reinstall the operation system?
Sorry again for the trouble caused.
Best regards,
Cherry
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, June 24, 2020 4:55 AM
Hi,
Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Cherry
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, June 26, 2020 6:54 AM | 1 vote
Thank you for your reply, Cherry. However, I will NOT reinstall my OS. The trouble and effort to do this hugely outweighs any possible benefit - and as I have said before, although a pain, the chore of remapping my network drives is just that. A chore that I can live with. It's obvious that the problem has been caused by a recent upgrade, as for the year or so since I bought this current laptop, networked drives were always available after a restart. It is only since the major upgrade earlier this month (June) that the problem has occurred, so there must be a problem with the upgrade. Find the problem; advise me of the fix and I may be inclined to do something about it. Thanks again.
Mike
Monday, June 29, 2020 2:26 AM
Hi ,
As far as I know , this is a known early issue with v1809. Since your OS version is 1903, please check whether the following workarounds help you:
https://www.kapilarya.com/fix-mapped-drives-not-working-in-windows-10-v1809
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best Regards,
Cherry
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, July 1, 2020 1:45 AM
Hi,
Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Cherry
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, July 1, 2020 5:40 AM
Hello
I have exactly the same problem.
The problem appeared after upgrading windows 10 to version 2004
For now, a temporary solution is to disconnect all drives
net.exe use * /d /y
and then remap, but the solution works only until you restart your computer.
After restarting, the problem returns.
Best Regards,
Arek
Thursday, July 2, 2020 9:38 PM
We are getting more and more reports like this one after upgrading Windows 10 new version 2004. If you did the update in 15 days, you may have an option to restore to the previous version. Please refer to this post:
Don’t install Windows 10 version 2004 until major problems are fixed
Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com
Friday, July 3, 2020 1:33 AM
Hi,
Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
Best Regards,
Cherry
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, July 6, 2020 2:41 AM
Hi，
As this thread has been quiet for a while, we will mark it as ‘Answered’ as the information provided should be helpful. If you need further help, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.
Best regards
Cherry
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Sunday, July 26, 2020 2:49 AM | 1 vote
Cherry, you clearly havn't understood the problem that thousands of us are having after this most recent "update". Both my desktop and laptop are experiencingi this. My mapped drives are to a 24 drive Synology NAS and they disapear after a restart every time. Further, the windows explorer has been so messed up that finding stuff on my own system (including the mapped drives after i reconnect them) requires a rediculous amount of probing thru file trees as there is no longer a "My Computer" and other common shortcuts that have exhisted in windows since probably before you were born. This "update" did no good, but broke many things.
Also, I cannot use my own display name because microsoft forums only allows 1 person with the same name in the entire world to use a name. Cant wait to see how silly looking 7.5 billion unique user IDs look.