Windows 10: SMBv1 keeps getting disabled no matter what

Hi All,I've just received a new corporate laptop with exact same W10x64 version 10.0.19042.1526 as the old one. Unlike the old one, which doesn't have any problems using SMBv1 client, the new one rejects my attempts to use it with the following text in the pop-up window even though SMB 1.0/CIFS Client remains enabled in Windows features:"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.mic

:)

 

How to Disable SMBv1 and Have SMBv3 Take Over?

My small LAN consists of only 2 PCs, my desktop and my notebook, both running Windows 10 Home. There are also various Apple devices, an Amazon device, some home security devices, and an ASUS RT-N56U
router.

Three days ago, I installed Windows 10 version 1803 on both PCs. Things were fine until yesterday, when my daily backup from my desktop to the notebook hard drive failed. Investigation of my desktop revealed
that none of the three computers (Windows counts the router as a computer) were appearing under Network in File Explorer; in fact, the Computer category was not even displayed there. However, on the notebook, the computer category was displayed in File Explorer,
and all three computers were displayed there. I was able to access folders and files in the desktop from the notebook. I ran my IPScanner (from the desktop), and everything looked OK with all devices responding.

After some browsing on the Internet, I found a suggestion that the problem could be caused because SMBv1 was disabled. Using Windows Features in Control Panel, I found that all three entries under "SMB 1.0/CIFS
File Sharing Support" where indeed disabled (unchecked). I checked the later two boxes ("SMB 1.0/CIFS Client" and "SMB 1.0/CIFS Server"). After rebooting, my LAN worked properly again! I don't know (or much care) how SMBv1 got disabled on my desktop (but not
on my notebook).

Now subsequent browsing has caused me to discover that SMBv1 has long ago been deprecated by Microsoft, and that it has major security issues and indeed should be disabled. My reading indicates that after
disabling SMBv1, SMBv3 (or possibly SMBv2) should have kept my LAN working. That did not happen.

Now I am in a quandary: give up my LAN and my daily backup, or continue using SMBv1. If anyone can tell me how to get SMBv3 to take over after disabling SMBv1, I would be most grateful!

Also, does anyone know if my Norton Security (which informs me it is up to date) is offering any protection from the SMBv1 vulnerability?

 

How to Disable SMBv1 and Have SMBv3 Take Over?

You do not need SMBv1. Go back to where you enabled it and disable it.

*Arrow Enable or Disable SMB1 File Sharing Protocol in Windows | Windows 10 Tutorials

Then you can fix your network showing in 1803 with these steps:

You need to set two services to automatic (delayed start):

Function Discovery Provider Host
Function Discovery Resource Publication

Open a Run box, (win key + R) type services.msc and press enter to open the Services List. Scroll down until you find those two. Set them to automatic (delayed start). Then right click and start them both. That PC will now show up.


These two services should run automatically but for some reason they are not in 1803. This has been checked in 1709 and other versions. For some reason they are not running in 1803 but setting them as above will fix the issue of the network showing for you.

 

Windows update for disabling SMBv1 Vulnerability on Windows 10 1703

Hi All

I would like to know if the SMBV1 vulnerability is applicable for windows 10 1703 edition . I couldnt find this operating system is listed under applicable OS for the MS17-010 advisary. Due to this ambiguity, i dont know which update to be installed on
this edition of windows 10 to fix the SMBv1 flaw.

Please adivise