SMB sharing not working after windows 10 update Build 2004 update

Well, by default our minimum and maximum were both set for SMB1. I guess it had been set like that since 2014 since the NAS was implemented. I would have thought that maybe Synology would have sent something out or fixed that setting with a DSM update along the way but I guess not. I never even gave that a thought until I was fishing around in the settings and ran across that configuration page. It all kind of makes sense now, looking back. The options for these settings are shown below.

======================

I just changed the maximum to SMB3. I did not test changing both minimum and maximum to SMB2 but I might think that would not be an issue since all our machines are running Windows 10 Pro. Something tells me that taking SMB1 completely out of the picture would be the best thing to do anyway but I was just desperate to get rid of the error we were seeing constantly on the workstations on the LAN. We have a fonts folder with thousands of fonts stored for our graphic design team on a folder on the NAS and I can definitely tell you that changing that maximum setting to SMB3 from SMB1 definitely fixed that teams' access issues to that shared folder on the NAS. It's lightning fast now according to them and there is no lag or issues at all. They were experiencing a lot of weird things like slow file explorer access to those folder and even locking up their machines at times. They say that is all gone now.

I will set the minimum setting on the NAS to SMB2 at close of business today and see if users have any issue with accessing the shares tomorrow.

I'll report back.

We're also using Synology.  Glad that it works for you; however, this is untenable for us as our security policy requires us not to use SMB1.  Likewise, solutions calling for AllowInsecureGuestAuth are also not possible.   Microsoft really needs to fix whatever they did in v2004.

We do use Synology, but we have not seen the issue.  It seems to mainly be on SMB shares for server 2016 that have not moved to Server 2019 yet.  

However, the huge issue we are seeing right now is the VPN not connecting on L2TP.  And there is no Rhyme or reason to it.  We can connect as admins, but not as users.  Change the user to admin - user still cannot connect.  It is really bazaar.  Rolling back to 1909 fixes the problem for those users affected.  If you do a clean install to 2004 you see the problem immediately.  If you upgraded users to 2004 - some users see it - some do not.  Some users have been fine for weeks but this morning it just started to them - nothing changed.  It almost seems like a permission issue in the VPN to a file or something.  Logs show it trying to connect, but the log just says unknown error on both sides.

Has anyone used the always on vpn with 2004 with no errors?

So this has been going on since the release and Microsoft does not have a resolution yet?  This is not limited to SMB 1 - I have seen it in Server 2016 as well not that we are deploying it to customers.  You know - we give them months to fix this before we even deploy - the 2011 update is coming up.  SMB shares being one of the most important aspects of say a Windows File Server and still no resolution?

Also seeing issues with VPN setup on new installs of 2004.