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.
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.
Although still a problem for many people, I have found that restarting the service "Workstation" and associated dependencies clears the issue up until the next reboot. Not a permanent fix but it certainly helps with the loss productivity and headaches until Microsoft provides a permanent solution.
This works every time for me.
I'd be curious for a chime in from users how many this quickly serves as a workaround.
If you are experiencing this issue while attaching to a NAS device, I just figured out that settings in the File Services setting on the NAS may have to be adjusted. On my Synology Diskstation DS1513+, that has been installed and running since 2014 with no issues until lately, is by default set to only negotiate SMB protocol by using SMB1.
Please see the settings dialogue box on my NAS. Setting the minimum protocol to SMB1 and the maximum protocol to SMB3 seemed to have completely fixed the issue of connecting to the NAS using URLs.
I hope this helps someone else.
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?
