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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-24T13:35:05+00:00

    For those who use GPO in order to map network drives, I use this solution.

    In your GPO when you configure the drive to map, use "Create" and don't check the "Reconnect" option.

    It will simply create the network drive at each boot. It takes sometimes (seconds) for the drive to appear in the explorer but it works well.

    It certainly will works with NAS drive too.

    For those who manually connect network drives.. You have to do it by this method (if you have a DC) or with a startup script as describe above.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-24T13:12:13+00:00

    No support for SMB V2 on Windows 2003 Server unfortunately.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-24T12:31:45+00:00

    believe me friend i can't believe that to date microsoft hasn't solved this big problem yet, made of them. a real shame

    I just tried your script and the same problem still doesn't work for me, and the servers are win2003, server 2008 and NAS DELUXE !!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-24T12:06:42+00:00

    Had the same issue after 2004 update, mapped drive on windows server 2012. Found the fix a moment ago, enable smbv2 protocol with the following powershell command :

    Set-SmbServerConfiguration –EnableSMB2Protocol $true

    • shame on microsoft for having us suffer this long!!

    Was this answer helpful?

    0 comments