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-12-22T18:29:16+00:00

    20H2 is cosmetic and does not fix the NAS access issues.

    The only solution to enable affected NAS is to bin W10 and go back to W7.

    My exchanges with Netgear convince me that they regard the gaging of older NAS as a wonderful marketing opportunity to force NAS users to junk perfectly useable equipment and replace with new items. No doubt in time such replacements will be afflicted with similar gaging restrictions.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-12-17T09:58:35+00:00

    Hi,

    try to restart service WorkStation, and everything will run like a charm till the next reboot

    please Microsoft fix that !!!

    it's been a long time now that problem have been escalated.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-12-14T20:19:35+00:00

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

    After rebooting did you login as the same windows user?  Are you doing drive mappings with a logon script? (Batch file)

    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