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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-16T21:51:22+00:00

    Hello, Yuri, SMB 1.0/CIFS Sharing won't show up where it was shown before.

    Instead, you will see SMB direct which won't work at all.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-18T10:52:31+00:00

    man same here I use freenas and can't even connect to it I tried everything nothing i get tit to connect and i restart computer and i can't connect to it anymore

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-20T03:50:33+00:00

    Although still a problem for many people, I have found that restarting the service "Workstation" and associated dependencies clears the issue up until the next reboot. Not a permanent fix but it certainly helps with the loss productivity and headaches until Microsoft provides a permanent solution.

    This works every time for me.

    I'd be curious for a chime in from users how many this quickly serves as a workaround.

    Thanks, Steve!  This worked for me.  A few months back, my NAS stopped appearing under my network locations.  I was able to add it as a pinned location, but that stopped working today.  None of the usual fixes worked, but starting/restarting the "Workstation" service did.

    Hope the problem gets resolved soon, but thanks for the workaround!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-10-22T13:41:27+00:00

    Restarting 'Workstation' service is fixing this for those on the fly fixes where rebooting doesn't.. Great.

    This sucks though.

    On one PC the "ProviderFlags" worked great but I only set that on one of the drives, maybe I need to set that for all the network drives for this other PC that is doing this...

    Was this answer helpful?

    0 comments