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 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.

We Run Windows 10 workstations with Linux Samba as a file server.

From time to time, we lose the ability to connect to mapped drives.

We find that the command 'net use x: /delete' will delete the mapped drive x:

We can then re-map the drive using windows 10 mapping and we're good to go until it happens again.

Note that the 'net use' command is reported by MS as deprecated for Windows 10 and there is no mention of a replacement or work-a-round.

Best of luck.

Why wouldn't you just restart the workstation service, instead of remapping? some of my users have 6 mapped drives that would take forever.  Unless you are using a script to remap.