If you try to access an SMB 1 share from Windows 10 you may receive the following error message:
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.
Enable SMB1 on Windows 10
- Press Windows Key + R to bring up the run dialog and type:
optionalfeatures
- Expand “SMB 1.0/CIFS File Sharing Support” and then check the box next to “SMB 1.0/CIFS Client“
- Click OK
- The installation will now proceed and you should be able to access shares using the SMB 1 Protocol again.
Enable SMB1 on Windows 10 with PowerShell
If you would prefer to do a command line installation, use the following command from an elevated PowerShell Prompt:
Enable-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol-Client" -AllFor more information see:
https://support.microsoft.com/en-gb/help/4034314/smbv1-is-not-installed-by-default-in-windows
Manfred Kipp says
Thank you for this tip, that made it possible for me to find all the “old” (known in win7) intranet server-candidates also on my new win10 PC.
I really appreciate!
Anish says
Thank you soo much… its really worked…..
Ole says
Thanks for info. Didn’t really have time to move multiple shared folders from one server to a newer one just because of one user.
rm says
Thank you for this info – helps a great deal!
Christopher Pereira says
CP This has made my day.. I have been struggling for many hours to get my win 10 pc to recognise my WDMyCloud device attached to the home network, without any luck. This has been a real miracle. Many thanks
J. Jurado says
Thanks
You need to be clone!
We need more helpful humans been’s
Thank You.
Priyal Doshi says
It works
Lorenzo Cordini says
Thanks, but what if the SMB 1.0 isn’t included in the Optional Features window popping up?
David Q Romney says
Many thanks; it works. I had to reinstall Win 10, and forgot about the SMB 1.0 issue with my Drobo FS. I works now.
AA says
Thanks for you help. It really worked. The other sites used the C:\prompt command and that did not work.
Dolche Guevara says
Shame that there is no SMB v1 in Turn Windows features on or off, in Windows 7 now (like it was before).
Graeme says
Got Windows couldn’t complete the requested changes, The referenced assembly is not installed on your system
Graeme says
OK I allowed an update (with reboot) to go ahead, this resulted in:
version 20H2 OS build 19042.985
Retried the above “fix” and this time it worked. So could have been lucky (2nd time) or it may have needed the update.
FYI: every time I turn this laptop on it says it needs to reboot to install something . I I allowed it BEFORE I did what I came to do , then usually the need has passed. I suspect 90%+ of activity on this lap top is installing updates (it’s not my daily machine)
Following the update+fix “net view” shows my NAS (Qnap so SMB1) but oddly a couple of SMB3 boxes, which didn’t show before (i.e. the laptop didn’t even show itself before!)
mark says
life saver – thought I was never going to find the solution
Luke says
Man, I have struggled with this probably for as long as Windows 10 has been released. Thanks to your tip, even my old Windows NT 4.0 machine is able to access Windows 10 and Windows 11 machines, and vice versa (when you also enable the SMB1 “server” box). It also worked flawlessly for Win2k and WinXP (all running in VMware of course). Many thanks.
Marek Salaquarda says
I didn’t find SMB1.0/CIFS client item after running optionalfeatures