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.
Those of you who still have this problem, try the following:
in the Registration Key [HKEY_CURRENT_USER\Network\*SMBv1 Drive Letter*], create the Value REG_DWORD "ProviderFlags" decimal 1 (0x00000001)
This should make it possible to communicate properly with the network drive at startup and shutdown. Do the process for all those units you have with smbv1 connection
Does this fix work for remote users that connect to the network via VPN? I worry that based on your wording "communicate properly with the network drive at startup and shutdown" means that it will only work if they're already on the network at startup, instead of having to connect a vpn after booting up.
Definitely worked for me. I'd suggest you test it, may depend on how you have your VPN set up.
Yes I can also confirm it worked for my users who are connecting remotely via VPN (we use OpenVPN solution) - only thing I can suggest is have the users wait 20-30 seconds after VPN is connected to make sure the drives get reconnected.
microsoft released a new update KB4571744 this morning that did not resolve this issue. bravo microsoft !!!
After updating to 2004 (knowing about the potential problem after previous experience), I put the ProviderFlags w/value 1, rebooted, and still no access.
Ran all MS updates post-2004, including a driver update for WD NAS, rebooted and still no access. Looked at my Programs and Features and somehow the box for SMBv1... was unchecked - re-checked upper level option and rebooted, still no access. The 2nd SMB option in P&F for SMB Direct was already checked. Looked in the Group Policy editor to verify setting for the Allow Guest Authentications, and it was still set to Enabled. After rebooting one more time, still no access.
Turned out, that policy enabling didn't actually set the value in my registry for it - HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth
Not sure how some of those options got turned off, could have been from my first attempt to load 2004 & get SMB to work again, but they had been turned on prior to this 2004 re-install.
So, if I had left my original SMB manipulations in place, using that ProviderFlags tip might have worked from the get go. Still ended up working, so thanks for the tip.
