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-02T19:55:05+00:00

    Yes I can also confirm it worked for my users who are connecting remotely via VPN (we use OpenVPN solution) - only thing I can suggest is have the users wait 20-30 seconds after VPN is connected to make sure the drives get reconnected.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-02T14:46:44+00:00

    Those of you who still have this problem, try the following:

    in the Registration Key [HKEY_CURRENT_USER\Network\*SMBv1 Drive Letter*], create the Value REG_DWORD "ProviderFlags" decimal 1 (0x00000001)

    This should make it possible to communicate properly with the network drive at startup and shutdown. Do the process for all those units you have with smbv1 connection

    Does this fix work for remote users that connect to the network via VPN? I worry that based on your wording "communicate properly with the network drive at startup and shutdown" means that it will only work if they're already on the network at startup, instead of having to connect a vpn after booting up.

    Definitely worked for me.  I'd suggest you test it, may depend on how you have your VPN set up.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-02T14:13:33+00:00

    Those of you who still have this problem, try the following:

    in the Registration Key [HKEY_CURRENT_USER\Network\*SMBv1 Drive Letter*], create the Value REG_DWORD "ProviderFlags" decimal 1 (0x00000001)

    This should make it possible to communicate properly with the network drive at startup and shutdown. Do the process for all those units you have with smbv1 connection

    Does this fix work for remote users that connect to the network via VPN? I worry that based on your wording "communicate properly with the network drive at startup and shutdown" means that it will only work if they're already on the network at startup, instead of having to connect a vpn after booting up.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-01T12:22:22+00:00

    This worked for me!!!

    tnx

    it's bad that it has to be edited for each mapped disk every time a new one is added,

    I hope that the gentlemen from Microsoft will finally solve this problem

    Was this answer helpful?

    0 comments