SMB sharing not working after windows 10 update Build 2004 update

I use a Drobo5n NAS and prior to this update, had no issues with connecting mapped drives.

Once I did this update however, I found that it no longer accepted the mapped drives on many computers - some immediately - and a few several days later (after working initially). 

I have had to turn on SMB1 Client for other software/hardware connections so I first verified that it was indeed set up but that alone was not the answer.

For some computers it was just a matter of running command prompt as Administrator and using the following for each drive I needed to map:  

@echo create new drive mapping for P:

@net use P: \Drobo5n\Public /persistent:yes

This did work on 1 PC.

But on another, I had to add the following: 

from regedit:

HKLM>SOFTWARE>Microsoft>Windows>CurrentVersion>Policies>System 

add Dword(32Bit):  EnableLinkedConnections 

change Value Data to 1 (Hexadecimal)

Save

For another PC, after doing the above steps I had luck after doing an additional command:

Shut down all computer and network gear and restart pc

Press Windows Key + R

Type: services.msc, hit enter

• Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication services and set to Automatic (delayed start)

-Open Explorer Network, enable network discovery if prompted

and....

run gpedit.msc

computer configuration\Administrative Templates\Network\LanmanWorkstation   

ENABLE insecure guest logon.

I had 1 computer that I used every fix found and the above mentioned as well as all the "fixes" located at TheGeekPage.com/Fix-windows-10-error-code-0x80070035-the-network-path-was-not-found and still no connecting.   

I was able to reconnect to the one PC that had a mapped drive that no longer worked by adding "  .\  " in front of the username (I had to use the user name of the PC) and their password.  I had previously been able to access it with the username (of that pc) alone, but no longer.

The Drobo5n Dashboard won't mount the shares either... (I can ping and get replies back from the device)

I now get an error about the server cannot perform the action requested.  I tried to find articles about that message but most were written in 2012 or 2015 - not current.  I tried a couple without success.

I finally took the PC back to the previous version and like a charm, everything works great.  I turned off the automatic updates so it won't install this update without my knowledge/permission and have turned it off on the other pc's i manage.

There is no server at this office; we use rdp to access a cloud server for our EMR.  I have spent approximately 10 hours on 3 pc's alone just to get them up and running.

My Window 10 pc's sharing option was working fine.

I share my pc's vpn to my console.

But after windows update, when i try to share it says unexpected condition occured. not all of your request in the settings could be made. So I installed thirdparty app and it doesn't work until we purchase pro membership.

I found a solution on this forum:

https://community.spiceworks.com/topic/2277832-windows-10-2004-can-t-access-network-shares-and-old-2003-server?page=1#entry-8914007 

bbaker.westakAug 4, 2020 at 11:50 PM

Just in case anyone is still dealing with this there does appear to be a functioning work around.  It'll at least get us by until we can finally and fully deprecate our SMB1 shares.

The trick is to add the registry key "ProviderFlags" as a REG_DWORD with a value of 1 (0x00000001) to HKEY_CURRENT_USER\Network\*SMBv1 Drive Letter*

Then reboot or log on/off.  It fixes the perpetual "reconnecting" status of the SMBv1 drive at logon and everything has been functioning normally and quickly for users we've added that registry key.  Only needs to be added to the drive letters under Network that correspond to SMBv1 shares.

Seeing as though the new word in computers is sandboxing.. shouldn't MS work on a sandbox solution rather than just cutting the service? Just how much money has MS cost small business to get rid of Linux based NAS systems to force them onto an MS based server... it is a **** joke, no person from MS has responded to either feedback or this thread, yet they are soon to enforce this update whilst this problem exists?