SMB sharing not working after windows 10 update Build 2004 update

"still needing to disconnect/remap drives from a ReadyNAS using SMB 1.0 on each reboot. "->

after the first removal and readd- you had to do it again?

Did you remove the check in front of SMB1 Auto Remove in 'Windows Features'?

Hello Monkey57, thanks for the reply.

After removing the SMB1 Client feature, rebooting, enabling the SMB1 client feature and rebooting a second time, volumes mapped to ReadyNAS via CIFS (SMB1) still indicated the network location was not available or the local name was already in use after a reboot, same as before the 20H2 update.  Confirmed I have Windows 10 Version 20H2. 

The Auto Remove SMB1 feature was not and had not been enabled.

Cheers,

TL

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.

This is not the solution. I tried 20H2. Still can't access after reboot

you're right friend .... nothing this with new versions of win10 after 1909 always appears the same problem with smb !! "

is the best solution with reg ProviderFlags

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER \ Network \ K]

"ProviderFlags" = dword: 00000001

for K drive

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.