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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-08-31T21:01:55+00:00

    This worked for me, and I'm quite the newbie to network admin.  For other newbies, to add this key, go to start, type in regedit, open the app, navigate to the key HKEY_CURRENT_USER\Network\

    then look for the letter of the mapped drive (I only had the one anyway)

    then click on edit, new, DWORD Value, change the name of the new value to ProviderFlags, set the value as decimal 1.  Then close and re-boot.

    I'd probably set a restore point before you do this, or export a backup of the registry, in case you mess it up.  Unlikely though.

    My problem had been that I have an old scanner still running on an XP machine, that cannot be upgraded, and the rest of my network is Windows 10.  After the update the W10 machines could no longer access the mapped drive on the XP machine, even with SMB1 options still set as they were before the upgrade.  I rolled back to keep the business running until I could figure this out. 

    It's getting harder to keep that old scanner going but a new one is very expensive (medical x-rays from phosphor plates) and I'm retiring in the next 5 years.  Of course the manufacturer long ago abandoned the scanner, and all updates.  The new ones do the exact same as the old ones, it's a grayscale image after all, nothing high tech there.  I just wanted to explain why so many businesses still need things like a working XP 32bit machine, SMB1 access and so on. 

    Thanks for forums like this, since I can't call tech support and am on my own.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-08-28T18:09:42+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

    This worked for me too.  Thanks Serafin

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-08-27T12:31:41+00:00

    This actually fixed my very similar problem.

    I couldn't access any SMB shares after update 2004, even having enabled every version of the SMB client. 

    I set that particular dword to 1 and then restarted the Workstation service (it also restarts the Computer Browser service) and I'm able to now access every share in our very motley network environment (there's even an ancient WinXP machine kept around running somewhere, controlling some hardware, that I hadn't been able to access for a while).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-25T09:45:35+00:00

    Please explain GPO...

    I have tried this, then after a reboot, I lose conection again...

    But truthfully, there shouldnt have to be a registry hack... Please Note: I have a few Windows 10 machines that I map their drives, they dont lose connection! Why is that?

    Was this answer helpful?

    0 comments