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: Newest
  1. Anonymous
    2020-08-05T13:08:03+00:00

    Has anyone seen what Windows 10X is? Apparently we lose control of everything but our files... No registry access etc... so we as a community work out how to fix things at our/companies expense, alter the registry and then the next update changes it back... I have to save text files as a fix to everything they do. I shouldn't have to do that! They don't pay me nor do they reimburse me for retiring perfectly good items that now have NO resale value!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-08-05T12:50:47+00:00

    I will try that this weekend. Thank you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-08-05T06:37:31+00:00

    Seeing as though the new word in computers is sandboxing.. shouldn't MS work on a sandbox solution rather than just cutting the service? Just how much money has MS cost small business to get rid of Linux based NAS systems to force them onto an MS based server... it is a **** joke, no person from MS has responded to either feedback or this thread, yet they are soon to enforce this update whilst this problem exists?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-08-05T06:22:27+00:00

    I found a solution on this forum:

    https://community.spiceworks.com/topic/2277832-windows-10-2004-can-t-access-network-shares-and-old-2003-server?page=1#entry-8914007 

    bbaker.westakAug 4, 2020 at 11:50 PM

    Just in case anyone is still dealing with this there does appear to be a functioning work around.  It'll at least get us by until we can finally and fully deprecate our SMB1 shares.

    The trick is to add the registry key "ProviderFlags" as a REG_DWORD with a value of 1 (0x00000001) to HKEY_CURRENT_USER\Network\*SMBv1 Drive Letter*

    Then reboot or log on/off.  It fixes the perpetual "reconnecting" status of the SMBv1 drive at logon and everything has been functioning normally and quickly for users we've added that registry key.  Only needs to be added to the drive letters under Network that correspond to SMBv1 shares.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments