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.
I have the same problem. MS please fix it.
I too had the same issue on one Server 2016 file share. I made an adjustment to our Windows DNS local host which appears to have solved this issue. I noticed, in the DNS, that there was some old computers, long since removed from our network, with the same IP entry as that file host. I nuked the bad DNS entries for the old systems. Waited for DNS propagation. I then, for good measure, added the file server in the local hosts file. I removed the mapped drives from the local workstations, rebooted, and allow the Group Policy to re-add the mapped drives. Worked great after several workstations, several reboots.
Might not work for you, but this has been my troubleshooting experience.
Astarr
Mate,
You're not gonna believe it. I added to the script with FQDN path the parameter " /persistent:no" without "timeout" and it seems to be finally working! Your advice is much more helpful than whole MS team.
Did restart few times and network drive is mapping with no issues. I'll let you know if any problems occurs.
Thanks !
The only solution that works for me with the win 10 - 2004 version is to create a bat file and start it when logging in:
timeout /t 30
net use w: "\network name\folder" /persistent:no
be sure to put /persistent:no
this solution works great with NAS deluxe servers
timeout you can reduce!!!
ps.microsoft did not turn out fair to us who bought their product.
Can’t believe they still haven’t solved this general problem?
