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. Anonymous
    2020-09-19T00:01:28+00:00

    My issues is a complete failure of all SMB shares and mapped drives, complete.

    I can't access legacy SMB 1.0 shares, I can't access Windows 10 shares, I can't access them by IP, name or fully qualified domain name.

    Network is just gone.

    I've got 4 computers that work just fine with 2004 update.

    I've got two that will not work under any circumstances.

    Both of them worked perfectly until 2004. One of them basically exists as a file server and remote workhorse for long jobs, 99% file server.

    Has Microsoft even acknowledged the problem yet?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-23T12:45:43+00:00

    HI,

    by adding persitent: no that's good for me.

    thank you

    Christophe

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-25T12:42:13+00:00

    I found only one solution that works around and helps.

    Restarting the Workstation service

    Unfortunately, network printers shared from old Windows systems sometimes stop working

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-29T08:12:28+00:00

    Has Microsoft even acknowledged the problem yet?

    I'd like to know this too, has anyone seen anything from them or just the usual ignore the problem and hope it goes away?

    Was this answer helpful?

    0 comments