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: Oldest
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-12-09T14:29:56+00:00

    Hello there

    SMBV1 seems to be corrupted even in 20h2.

    I just clean install new computer with ISO 20H2 from microsoft and i can get acces to sharing SMBV1 but as soon as i reboot netshare start to crash and unable to browse network anymore explorer keep crashing and freezing.

    Try clean install with 2004 same issue. try clean install 1909 and now smbv1 share work flawlessly

    there are still issue on 2004 and 20h2 with smbv1 share

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-12-10T20:55:14+00:00

    After upgrading to Win10 20H2 it still didn't fix my problem even after turning SMB1 Client off and back on.  My fix ended up being in the registry for the current user. (On an end-user PC)

    HKEY_CURRENT_USER\Network

    Deleted the drive letter giving me the problem, rebooted, allowed the network script to re-run upon login.

    Interestingly enough, my PC that has build 1909 is missing a registry key that 2004 and 20H2 does have called "UseOptions".  Perhaps this may be the culprit and by deleting the entire drive letter from the registry it allowed a clean recreation of the registry entry.

    Unfortunately because the fix appears to be in CURRENT_USER, it may not be a good fix for computers that have multiple users.  The fix may have to be performed on all existing user registries.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-14T20:06:21+00:00

    This suggestion worked but after rebooting the PC the issue reappears.

    Was this answer helpful?

    0 comments