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-09-10T10:35:08+00:00

    I'm having the same problem. I can mount the Samba shared on my another Window10 Build1903. But on Build2004, it keeps saying "Your org security policies block access..."..

    I have tried all the options mentioned here but still no luck..

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-09T20:29:57+00:00

    Temp Fix (encrypted smb) issue.

    Context;

    3 node windows server 2019 failover clustered file share, SMB 3.1.1, you can verfiy SMB version by running “Get-Smbconnection” on client.

    Mapped drives via GPO.

    Problem;

    After Update to windows 10 2004 via endpoint manager, PC showed Mapped drives but when trying to connect we got errors, when trying to browse the unc path ‘access denied’ 

    manually ‘net use /delete drive:’ then run gpdate resolved issue untill reboot, on a few occassion actually had to release and renew IP before the drives would connect.

    Solution;

    i decided to add a mapped drive via GPO to another server to rule out server issue, i mapped a SMB 3.0 share on a windows server 2012 r2, this share worked perfect on every reboot.

    At this point i went back to the file share cluster and disabled file share encryption as this was the only difference apart from the SMB version and finally all my mapped drived work on reboot.

    im unhappy about removing encryption in order for this to work so MS has broken something in SMB during startup of os and mapping drives.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-09T07:33:41+00:00

    The fix from Microsoft (KB...1744) did not solve the problem for us.

    It is some kind of weird: the problem occures in the LAN. If I remove the network cable from my computer and the computer only uses WLAN during boot the problem does not occure.

    Does anybody have any idea?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-04T07:28:21+00:00

    microsoft released a new update KB4571744 this morning that did not resolve this issue. bravo microsoft !!!

    Was this answer helpful?

    0 comments