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-12-22T20:06:53+00:00

    I think I finally found the fix.  Others online are talking about a registry entry called "ProviderFlags".  Go to HKCU\Network.  Find the drive letter you are having issues mapping.  Add a 32-bit Dword key called "ProviderFlags" and set the value to 1.  Reboot and the issue should go away and start working as normal.

    I have not been able to find an answer as to why this fixes it, but is seems to fix the issue on an individual user account.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-12-22T21:04:58+00:00

    if you had read a few posts before, you would have seen that this tip has been given already. I don't really understand why people still have the problem.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-12-22T22:30:52+00:00

    The internet is littered with proposed solutions to this problem, none of which have been endorsed by Microsoft, and all of which are no more than uninformed amateur workarounds with questionable applicability.

    The community needs to wake-up and accept reality. The overwhelming majority of W10 users are unaffected by, and unaware of, the issue. Microsoft have not acknowledged any workaround and have no incentive to change its' posture - SMB1 NAS will never be accessible under W10.

    Those committed to W10 have no alternative than to either replace their gaged NAS with compliant units or adopt online storage. Given that the internet is a cauldron of criminality, half truths and corporate greed, only a fool would commit their data to corporate online storage irrespective of provider claims of security and integrity.

    So long as LAN and WAN share a common addressing scheme, the only secure way of ex-PC data storage using SMB1 NAS is to configure a LAN controlled by a non-W10 PC divorced from the internet.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-24T14:37:44+00:00

    The community needs to wake-up and accept reality. The overwhelming majority of W10 users are unaffected by, and unaware of, the issue. Microsoft have not acknowledged any workaround and have no incentive to change its' posture - SMB1 NAS will never be accessible under W10.

    Why accept SMB 1 NAS would be out of service because a W10 update ! Security LAN is a personal job, there's many ways to do so, i don't need Microsoft for that.

    But, finally, i think the issue is NOT SMB 1 ! I have  3 computers on my LAN, one is a Microsoft surface recently updated from 1909 to 20H2... My SMB 1  NAS was not connected here before, and i noticed that i still can access the NAS through network sharing after update without problem.

    Then i disconnected the NAS (previously Z:) on my main computer, Win1909. After reboot, i update to Win 20H2 and i notice that registry has changed for network SMB 1. I think the issue is there and the work around is to disconnect the device before updating (to 2004 or 20H2).

    After some stop & start, my SMB 1 NAS can be accessed through network sharing.

    Was this answer helpful?

    0 comments