Windows 10 tip: Stop regulating a horribly uncertain SMBv1 custom …

The new WannaCry ransomware conflict widespread since of a disadvantage in one of a internet’s many ancient networking protocols, Server Message Block chronicle 1 (aka SMBv1).


If we have an app or hardware device that requires SMBv1, it’s time to embankment it.

Click to enlarge

Your PCs that run Windows 10 were stable from that exploit, though that doesn’t meant you’ll be so propitious a subsequent time.

In a interests of implementing a comprehensive, multi-layer confidence policy, Microsoft recommends that we invalidate a SMBv1 custom completely. The universe has already changed on to SMBv3, and there’s no forgive for stability to let that aged and horribly uncertain custom run on your network.

To henceforth mislay SMBv1 support from Windows 10, use possibly of these dual approaches.

Open Control Panel (just start typing Control in a hunt box to find a by-pass quickly). Click Programs, and afterwards click Turn Windows facilities on or off (under a Programs heading). Clear a check box for SMB 1.0/CIFS File Sharing Support, as shown here. That’s it; you’re protected.

(Note that we can use that same procession in Windows 8.1. For Windows 7, we can’t mislay SMBv1, though we can invalidate it regulating a instructions in this article: How to capacitate and invalidate SMBv1, SMBv2, and SMBv3 in Windows and Windows Server.)

As an choice in Windows 10, open a Windows PowerShell prompt with executive privileges. In a Windows 10 Creators Update, chronicle 1703, right-click a Start symbol and select Windows PowerShell (Admin) from a Quick Link menu.) If you’re using an progressing Windows 10 version, enter Windows PowerShell in a hunt box, afterwards right-click a Windows PowerShell by-pass and click Run as administrator.

From that towering PowerShell prompt, form a following command:

Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol

Press Enter and you’re done.

On a Windows domain, of course, we can use Group Policy. Full instructions (along with links to assistance government know because this is a good idea) are in this Microsoft TechNet article: Disable SMB v1 in Managed Environments with Group Policy.

Disabling SMBv1 shouldn’t have any outcome on modern, entirely updated hardware. Some consumer-grade network trustworthy storage inclination use this custom by default, though a firmware refurbish or a change in settings competence concede we to change it to something some-more secure. Unfortunately, some comparison database programs and even new inclination such as those from Sonos need SMBv1.

If we learn that we have an app or a network device that won’t work but this feature, use Control Panel to spin a underline behind on. Then cruise either that app or device is value a impact on your network confidence and either it’s time to demeanour for a replacement.

Previous tip: Use filters for faster and some-more accurate searches

Next week: Another Windows 10 tip from Ed Bott