SMB sharing not working after windows 10 update Build 2004 update

Anonymous

Any help is appreciated

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

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.

0 comments

246 additional answers

Anonymous

2020-11-05T11:06:39+00:00

My fix for my Linux server shares was to follow this guide

https://devanswers.co/discover-ubuntu-machines-samba-shares-windows-10-network/

and install windows discovery for my Linux server after my samba shares suddenly become inaccessible 3 days ago for absolutely no F%^&*(*G reason - PC the night before was copying files over to my server just fine, the next afternoon after work I fired up my desktop PC, could ssh into my server just fine, noticed my SMB shares were not working and my server was not even detecable on the network as far was explorer was concerned yet was absolutely online and available via SSH and obviously connected to my router just fine via the router management interface...

Oh and YES I checked all my samba settings on my linux server before I even tried to resolve this issue thinking something might have gone **** there first... but NOOOOO it was as solid as its ever been, even kicked a user off to reboot the server manually in case there was some issue with the services RAM data (ecc ram so I seriously doubt it with no issues noted on the servers hardware diagnostics panel)...

is this a case of MS screwing over people yet again OR WHAT changed in the last 3 days regarding WIN 10 OS?!
Was this answer helpful?

0 comments No comments
Anonymous

2020-11-06T06:40:15+00:00

Hi Guy,

I also find out this issue. But I got temp solution as you must do hardcode in credential manager.

last time at username field, you all put "domain\user"

now you change it to "user @ domain.local"

It will be worked.

hope this can help you all.

Regards

Waichun
Was this answer helpful?

0 comments No comments
Anonymous

2020-11-14T09:25:01+00:00

Thanks, this trick works !

First : add HKCU\Network(drive letter), add String Value of "ProviderFlags=1", reboot Win 1909

Then verify access to SMB 1 device Ok

Next : update to Win 20H2

Shut off computer

Restart

Access to SMB 1 device still Ok.

Work also with network sharing.

11/21 update : unfortunately, after a while, the SMB 1 access is lost again ! Must roll back to 1909...
Was this answer helpful?

0 comments No comments
Anonymous

2020-11-18T22:02:35+00:00
I have new windows 10-PC and virtual with SMB 1.0 that I CANNOT UPDATE in any ways and don't want to, it's for legacy stuff that needs to stay the same. Was working fine with win 7, can connect with ssh and ping and everything else ok.

net use s: \192.168.75.111\www /user:username /persistent:no

System error 384 has occurred.

You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.

Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747

Now I have spent 2 evenings trying to get this to work but it's not
- Most new windows 10 Pro, 20H2
- Tried registry parameter, didn't help
- enabled smb 1.0 from windows features (all sub items checked), it rebooted the machine 2 or 3 times? now it shows enabled, even in powershell, but if I try to take the x off, i get error (attached)
- tried connecting with \name and \192.168.. no work
How Do I get this working ?!?! It's messes up all my work!
Was this answer helpful?

0 comments No comments