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-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
  2. Anonymous
    2020-08-21T08:28:53+00:00

    Those of you who still have this problem, try the following:

    in the Registration Key [HKEY_CURRENT_USER\Network\*SMBv1 Drive Letter*], create the Value REG_DWORD "ProviderFlags" decimal 1 (0x00000001)

    This should make it possible to communicate properly with the network drive at startup and shutdown. Do the process for all those units you have with smbv1 connection

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2020-07-07T10:49:52+00:00

    If you are using Guest account on your NAS, I think you need to change the following key and restart your PC/laptop to get it fixed.

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

    "AllowInsecureGuestAuth"=dword:1

    https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows-10-and-windows-ser

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-06-23T19:31:56+00:00

    Hello, Yuri. Go to the Control Panel > Program & Features > Turn Windows features on or off > look for SMB 1.0/CIFS Sharing support and enable it.

     Unfortunately this feature seems to be broken in build 2004.  Had it enabled in build 1909 without issue.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments