This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Any help is appreciated
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 51%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Win10 20H2 fixes the issue.
Previously when 2004 broke smb1, I rolled back.
There was no registry change or any other modification made to the system. After Win10 20H2 upgrade was installed via Windows Updates; SMB1 worked as it did before the upgrade.
Thank you Microsoft.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 96%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
I tried that too but it still asks for a password every so often and won't connect while the share is mapped. It's okay during the session but shows a fail after a shutdown and restart.
Like you say all we can do is wait for an update.
FYI, FQDN didn't work with map my drive, but if I replaced it with my local ip address of the network share and tried it under 'add network location' it does. So instead of \nameofserver\drivename i did \192.168.1.xxx\drivename and it was added. I really only use it for file history so in file history i added it in the same way and it seems to be working now. I know this solution won't solve a lot of people's problems depending on the complexity of their needs and network setup, but for anyone with my use case I hope it helps. Hopefully they get this patched soon.
If you've been working with Microsoft systems for a long time, like me too, you shouldn't be surprised at this kind of mess! You could almost imagine that they did this to push the latest Server 2003 to be replaced .... Hold on, but I don't think they're going to fix this.
You are right.. I am angry, they have retired an expensive item, disrupted many businesses in order for their update to go through, millions of dollars in time and equipment wasted because of those knuckleheads! And for what purpose? Years ago they had to comply and be accountable for things being back dateable! When did it change that they no longer have to do so? I have used MS since DOS days... All my systems run pro, not home.. I pay extra money to get my computers to work, but no... They host this page, don't respond, don't respond to their feedback forum and expect you and I to do the jobs of their technicians free of charge. Screw with the registry? Why? It's a laptop! I haven't changed anything. It worked one day, updated Windows then it didn't! You are right! I am so pissed of with their "Well there is only a couple of thousand people that are experiencing this issue!"
