SMB sharing not working after windows 10 update Build 2004 update

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.

OK, is the fix remains after reboot ? ... (after 2004 upgrade, SMB1 access was ok but lost after reboot, so i rolled back to 1909 too)

I just wanted to report back that we no longer have to restart the "workstation" service in order for workstations to connect to the NAS any longer. It was a great workaround and may prove to have underlying benefits until MSFT patches the issue permanently but I am convinced that changing the minimum and maximum SMB protocol values on the NAS settings was the culprit for us.

Noting that users are likely using various OS and versions, this may or may not fix everything for them.

Thanks for all the kudos for the workaround. I hope everyone can assume maximum productivity until the fix arises.

I just wasted 4 hours thinking I screwed up my smb.conf on the Ubuntu box's samba share somehow. Until I changed up my search query to "Samba stopped working on Windows 10" and this page was the first hit.  I usually am quicker to check Microsoft forums, but swore it was something I did in the linux cli. Anyway, this worked for me instantly, as I stood mouth agape at how quickly it was "fixed" (albeit temporarily). Microsoft, please fix permanently. 

Thanks, Steve!

please fix this issue.  no matter what, smbv1 and mapped network drives are still needed and will be for quite a long time more.