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. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2020-11-23T15:02:03+00:00

    I upgraded to 20H2 and toggled off and on SMB1 and it worked once until rebooting. Basically the same thing it did on version 2004. I dont think 20H2 fixed the issue

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-18T22:02:35+00:00

    I have new windows 10-PC and virtual with SMB 1.0 that I CANNOT UPDATE in any ways and don't want to, it's for legacy stuff that needs to stay the same. Was working fine with win 7, can connect with ssh and ping and everything else ok.

    net use s: \192.168.75.111\www /user:username /persistent:no

    System error 384 has occurred.

    You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.

    Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747

    Now I have spent 2 evenings trying to get this to work but it's not

    • Most new windows 10 Pro, 20H2
    • Tried registry parameter, didn't help
    • enabled smb 1.0 from windows features (all sub items checked), it rebooted the machine 2 or 3 times? now it shows enabled, even in powershell, but if I try to take the x off, i get error (attached)
    • tried connecting with \name and \192.168.. no work

    How Do I get this working ?!?! It's messes up all my work!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-14T09:25:01+00:00

    Thanks, this trick works !

    First  : add HKCU\Network(drive letter), add String Value of "ProviderFlags=1", reboot Win 1909

    Then verify access to SMB 1 device Ok

    Next : update to Win 20H2

    Shut off computer

    Restart

    Access to SMB 1 device still Ok.

    Work also with network sharing.

    11/21 update : unfortunately, after a while, the SMB 1 access is lost again ! Must roll back to 1909...

    Was this answer helpful?

    0 comments