[German]Again another blog post about the endless topic ‘Network drive mapping doesn’t work in Windows 10’. Microsoft has now admitted in a blog post that mapping network drives is broken under Windows 10 V1809.
A brief history
I had published in October 2018 the German blog post Windows 10: Fehlerhaftes Netzlaufwerk-Mapping ein Feature? on that topic. Users of Windows 10 (and older operating system versions) run into an annoying issue when using mapped network drives. These mapped network drives are not properly mounted at startup or during operation.
The mapped network drives are displayed, but the connection is broken. The above screenshot shows this scenario. The drives with a red X must be clicked to access the contents. Blog reader Karl had already made me aware of this problem in Windows 10 in November 2017. Karl wrote about it:
It’s really annoying, and I wonder if I’m the only user who uses network drives at home. A NAS (target PC running Windows 10) is nothing special anymore.
I’ve made so many attempts to get Microsoft to take up the cause..
I’ve picked up the topic in the German blog post Windows 10: Netzlaufwerke unvollständig verbundenen some time ago.
Network drive mapping in Windows 10 V1809 broken
A few days ago I was informed via Twitter that the mapping of network drives in Windows 10 V1809 is broken. Here is a public tweet (I also got some private tweets).
script to fix that red X on mapped network drives (I don’t think this is an 1809 problem; I’ve had this problem for *years* – you fix it by clicking the drive in Explorer that has the red X and it opens and the X goes away) https://t.co/cxQeZxNxPp
— Scary Mary Branscombe (@marypcbuk) 15. November 2018
Microsoft has published a kb article Mapped network drives don’t work in Windows 10, version 1809 dealing with this issue:
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.
The above description says that mapped network drives are displayed with a red X in Explorer. This is exactly the error description I mentioned above. As a workaround to solve the problem, Microsoft suggests a batch file that executes two PowerShell commands/scripts (the scripts are outlined in the KB article). It also outlines how to work around the problem with group policies. All things that have already been discussed by my blog readers in the blog posts linked above. Susan Bradley also wrote something about this topic.
SMBv1 FAQ and Windows networks
Windows 10 Version 1803: Network environment empty
Windows 7 update KB4103718: Network issues fixed
Windows 7 SP1 network bug (KB4103718/KB4103712)
Network issues with Updates KB4088875 / KB4088878
Windows (Network) error 0x800704B3
Windows 7/8.x/10: Delete Network Profiles