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-10-07T06:37:50+00:00
    • Found a work around as I have the exact issues with Win10 2004
    • Disable, reboot, enable and reboot
    • Test

    --

    - Control Panel > Program & Features > Turn Windows features on or off > look for SMB 1.0/CIFS Sharing support and DISABLE (un-tick) it.

    • Reboot
    • Control Panel > Program & Features > Turn Windows features on or off > look for SMB 1.0/CIFS Sharing support and ENABLE (tick) it.
    • Reboot
    • It should now work

    This will probably work on reboot, but does it work on a cold start boot.

    I suspect not.

    My problem is that on 2 computers I can access the 2 printers (USB, memorycard, locations), and USB storage, on my Netgear router, if I alter the registry, to include ProviderFlags.

    On the 3rd computer (a laptop ethernet connected to the network), this does not work, even with AuthGuest.... enabled to 1.

    However as a temporary solution I can access these devices as a Network Location, rather than a mapped drive.

    Soon as I try to map them as a mapped drive, file explorer on cold boot slows down and freezes.

    All other mapped drives work fine, and there's around 17 of them.

    Its not ideal, but it sorts the issue for me, until Microsoft can be bothered to fix the issue which was not present, before Windows 10 2004 update.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-01T01:06:31+00:00

    Using the "ProviderFlags" on the mapped drive seems to be a solution for me so far, I only had to do it for the First drive in the list of many.  So far it's held for a week after disconnecting multiple times each day.

    So look in HKEY_CURRENT_USER\Network\  and look at the first drive in list. 

    I had to reboot after, signing out was not enough.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-29T08:12:28+00:00

    Has Microsoft even acknowledged the problem yet?

    I'd like to know this too, has anyone seen anything from them or just the usual ignore the problem and hope it goes away?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-25T12:42:13+00:00

    I found only one solution that works around and helps.

    Restarting the Workstation service

    Unfortunately, network printers shared from old Windows systems sometimes stop working

    Was this answer helpful?

    0 comments