• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question Drive mappings after update 2004... gone

MtnMan

MtnMan

Diamond Member
Yea, they are gone, explorer sees some of the other devices, but none of the shares... thanks again MS, another FUBAR update.

Reset to 1909 and mappings restored.

From other devices I could still see and access the drive on the build 2004 computer, but nothing from the 2004 machine.
 
Sort by date Sort by votes
I believe I am seeing the same issue. On 2 separate computers, on a brand new fresh install of 2004 build, I was not able to map a network drive on our domain. I tried to enter the domain credentials and it wouldn't take them. Nothing I tried seemed to work. 1909 always worked fine.

The only resolution I had was to add the computer to the domain, and then it would work. Very odd bug!!!
 
Upvote 0 Downvote
I had no issues with the 2004 update on three computers, drive mapping was okay on a NAS server, and four shared disks between the computers.

In fact the only issue I have seen with the 2004 update was with the remote desktop connection. The old RDC would not work and I had to download the newest version from windows store, which works fine.
 
Upvote 0 Downvote
Sounds like the 2004 update is like the coronavirus. It effects everyone differently, with different symptoms. Search on it and there are any number of problems from inability to connect to one drive. mice stop working, Office apps won't open, print spooler crash, thunderbolt ports stop working, issues with some graphics cards,
 
Upvote 0 Downvote
Well tried a bunch of things, and every upgrade to 2004 or 20H2 destroyed all my mappings, and nothing would allow me to see the other computers on my network. Most of those had automatically updated to 2004 or 20H2, without any issues.

What I think was happening is it there were some virtual wireless interfaces that I couldn't get rid of, even after rooting them out of the registery. I think they came from the wireless pcap drivers that I installed as part of Wireshark. This allowed capture of everything on WiFi. I think that is what did me in, as they acquired 169.254.x.x addresses. Didn't matter if I turned WiFi off and used Ethernet, or a old usb wifi adapter.

It was going to come down to crunch time as M$ is making noise about they are going to start forcing updates beyond 1909 early next year.

Final solution, clean install of Windows 10. Probably a couple more days of getting stuff reinstalled and setup the way I want it, but all my drives are mapped.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Back
Top