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.
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.
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.
- Found a work around as I have the exact issues with Win10 2004
- Disable, reboot, enable and reboot
- Test
--
- Control Panel > Program & Features > Turn Windows features on or off > look for SMB 1.0/CIFS Sharing support and DISABLE (un-tick) it.
- Reboot
- Control Panel > Program & Features > Turn Windows features on or off > look for SMB 1.0/CIFS Sharing support and ENABLE (tick) it.
- Reboot
- It should now work
This will probably work on reboot, but does it work on a cold start boot.
I suspect not.
My problem is that on 2 computers I can access the 2 printers (USB, memorycard, locations), and USB storage, on my Netgear router, if I alter the registry, to include ProviderFlags.
On the 3rd computer (a laptop ethernet connected to the network), this does not work, even with AuthGuest.... enabled to 1.
However as a temporary solution I can access these devices as a Network Location, rather than a mapped drive.
Soon as I try to map them as a mapped drive, file explorer on cold boot slows down and freezes.
All other mapped drives work fine, and there's around 17 of them.
Its not ideal, but it sorts the issue for me, until Microsoft can be bothered to fix the issue which was not present, before Windows 10 2004 update.
- Found a work around as I have the exact issues with Win10 2004
- Disable, reboot, enable and reboot
- Test
--
- Control Panel > Program & Features > Turn Windows features on or off > look for SMB 1.0/CIFS Sharing support and DISABLE (un-tick) it.
- Reboot
- Control Panel > Program & Features > Turn Windows features on or off > look for SMB 1.0/CIFS Sharing support and ENABLE (tick) it.
- Reboot
- It should now work
Just togging and rebooting isn't enough you have to see if it holds over time.... Let me know if it stays active for over a week.. Otherwise try the "ProviderFlags"
