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 No 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 No comments

246 additional answers

Sort by: Oldest
  1. Anonymous
    2021-03-16T17:22:51+00:00

    BIG, FINALLY WORKED OUT

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-03-27T22:18:39+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.

    I am not sure it is a solution:

    I preserve my primary PC from 2004 upgrade and 2 weeks ago system force the upgrade to  20H2. After that problems with SMBv1 appears - sometimes all mapings works well, but some hours after system start File Explorer opening cause endless ''This Computer' refresh with unfinished progress bar. In this case command 'net use' hangs. The only solution is system reboot, but this is unacceptable.

    kB

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-04-06T15:49:03+00:00

    Thanks so much!  After a recent update to Windows 10, the supposed last version and best OS ever (actually a steaming pile of ****, reminds me of windows 98), my trusty WD TV Live Hub mapped drive would no longer connect.  I could remap it and it would work until I restarted, then it was gone again.  I would get the message "the local device name is already in use. This connection has not been restored".

    Adding that registry key to the drive name fixed it.  I am forever grateful.

    As for MS, I am betting at some point in the not-too-distant future they will realize they cannot continue down this path and start over, again - at least I hope they will.  Otherwise I will be forced to move to another OS, or build my own.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-04-07T15:36:13+00:00

    Got all of the settings you suggest and still no joy.

    Was this answer helpful?

    0 comments No comments