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-07-17T14:50:12+00:00

    Although that is a viable option for those of you who are running windows file servers. 

    This still does not help for 3rd party storage appliances such as netapp.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-17T12:06:33+00:00

    Hello , 

    I had multiple black screen issue after login on PCs and Laptop since the windows 10 update Version 2004.

    When window session finally starts, Windows explorer was not able to display Local and network drive. It was just spinning, and spinning with no results.  Even Microsoft Office application was not able to start.

    I finally got the solution today.  

    We enabled the SMB1 Windows feature for compatibility with our old file server.  If i remove the SMB1 everything goes back to normal. 

    So we simply start the process to migrate the old file server to server 2019.

    This took a week to troubleshoot and if I can help other people with the same issue ,  that will be great!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-17T08:13:41+00:00

    Same issue here, we've got old 2003 server (I know ....). A real mess with mapped drive, the explorer freeze, need to reboot and disconnect it with net use command, then reboot. The only workaround I use is to create shortcuts but if you have some apps that use drive letter, it's over ....

    Edit 07/17/07

    Latest win10 tuesday patch (19041.388) doesn't seems to resolve the problem ...

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-16T21:59:41+00:00

    Definitely an issue with 2004. BTW 1909 and 1903 work fine with my SMB1 mapped drives.

    If a drive is mapped and the computer restarts, the drive will not connect. If I remove the mapped drive and a restart or just do an IPconfig /release and then in IPconfig/renew I can connect and remap. Works until I restart again. Curious thing is that if I just have a desktop shortcut for the share, it will connect fine.... Even after a restart. If the drive is mapped it fails to connect upon restart. The scripting method WORKAROUND seems to work sometimes, but not always.

    Hoping that Microsoft resolves this soon with a patch for 2004. It has become a real issue in my environment.

    Was this answer helpful?

    0 comments