SMB sharing not working after windows 10 update Build 2004 update

Anonymous
2020-06-20T02:30:38+00:00

Any help is  appreciated

Windows for home | Windows 10 | Internet and connectivity

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.

0 comments
Answer accepted by question author
Monkey57 3,535 Reputation points
2020-11-03T02:21:51+00:00

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.

Was this answer helpful?

20+ people found this answer helpful.
0 comments

246 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-11-04T05:39:00+00:00

    What actually worked for me on a long term basis was a combination of the registry hack:

    HKCU\Network(drive letter), add String Value of "ProviderFlags=1"

    plus updating to Windows 10 Version 20H2.

    Drives that were mapped to NAS devices using SMB1 are now reliably accessible across reboots.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-09-07T15:40:02+00:00

    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

    • to "1".  Set that to 1 and my access started working again - no reboot needed.

    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.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-08-02T07:02:18+00:00

    I upgraded to 2004 on 1 Aug.  After seeing that 2 out of 3 NAS stores were not connecting, went looking for a reason.  Found this page.  After reading 10 pages of workarounds for a basic MS cock-up, decided that my best approach is to just roll back to 1909,

    • I'm past trying to de-bug MS software; it's a tool, and tools need to work.  Try this: did you ever buy a wood chisel and find that replacing the handle also chipped the cutting blade??

    I have rolled-back, and everything works again.

    I also posted to the feedback hub with critique, and pointed whoever reads it to this page.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-06-30T08:21:33+00:00

    This issue has still not been resolved! We recently updated a few computers and this problem started occurring.  We got an obsolete financial software running in our company, which cannot be run/installed on newer server version, therefore we cannot upgrade it and we are currently stuck with windows server 2003.

    Please fix this issue, before it escalates.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments