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
    2021-03-03T03:00:08+00:00

    Any help is  appreciated

    SMB1 mapped drive issue solved.

    Adding a summary of all that I tried following a 20H2 upgrade.

    This pertains to Window 10 Pro 20H2 in Domain environment connecting to a Windows 2003 member server shared mapped drive.

    After upgrade to 20H2, the PC was unable to connect to 2003 SMB1 shares and also had high resource usage causing PC to hang and fail when opening File Explorer. The immediate system hang was maybe due to desktop or quick access links pointing to SMB1 Shared locations or files.

    I tried everything I could find to resolve it and here is a summary:

    Some of all of these in order may fix the issues.

    Remove and Re-add SMB1 using Powershell, Run as Admin

    Get-WindowsOptionalFeature -Online -FeatureName smb1protocol

    Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol

    Reboot

    Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol

    Turn on Services:

    Run services.msc

    Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication services and set to Automatic (delayed start)

    Open Explorer Network, enable network discovery if prompted

    Edit local policy:

    gpedit.msc

    computer configuration\Administrative Templates\Network\LanmanWorkstation ENABLE insecure guest logon.

    2 Registry settings:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]

    "EnableLinkedConnections"=dword:00000001

    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\Network\p]

    "ProviderFlags"=dword:00000001

    Note: In the above registry entry "P" is the drive letter I use.

    Thank you to all contributors who helped me solve my problem.

    SMB1 drive access worked and system performance was returned to normal.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  2. Neil D 34,280 Reputation points Volunteer Moderator
    2020-06-23T19:51:16+00:00

    There is something a miss with SMB in 2004. I use File History to my NAS and also have two mapped drives to shares on the NAS. My password would not be accepted

    Over a few days I realised that if I Disconnect the mapped drives in File Explorer and then select File History in Control Panel to input the password the drives can be mapped again without a problem in File Explorer. I currently leave the drives unmapped until I need them and they always work.

    I have ensured SMB 1.0/CIFS File Sharing Support is enabled. (I did disable then re-enable again initially)

    We will have to wait for Microsoft to issue a patch but if you cannot get it to work then use the Feedback Hub to report the problem.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-06-20T02:45:06+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.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-06-26T02:26:54+00:00

    I have the same problem. Waiting for a fix or regedit to resolve.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments