Blog

SMBv1 Vulnerability: What It Is and How to Disable It

Configuration Drift
Endpoint Hardening
Vulnerabilities
A weathered padlock on a cracked server enclosure representing SMBv1 vulnerability risk.

SMBv1 (Server Message Block version 1) is a 1980s Windows file-sharing protocol with no encryption, no mutual authentication and no integrity checks. Its flaws, patched by Microsoft in MS17-010, were exploited by WannaCry and NotPetya in 2017. To fix it, check where SMBv1 is enabled, map what depends on it, disable it, and monitor so it stays off.

What is SMBv1? 

SMBv1 (Server Message Block version 1) is a network file sharing protocol that was developed in the 1980s and later extended by Microsoft. It enables systems on the same network to share files, printers, and other resources.

While it was widely used in early versions of Windows, SMBv1 is now considered obsolete and dangerous. It lacks modern security features such as encryption, mutual authentication, integrity checks, and protection against man-in-the-middle attacks. These weaknesses have made it a prime target for attackers, most infamously during the 2017 WannaCry and NotPetya ransomware outbreaks, which caused billions in global damage.

Why is SMBv1 a security risk?

Although SMBv1 is not itself a vulnerability, it plays host to many vulnerabilities and unequivocally renders the organization vulnerable. For this reason, and for its tendency to pop back up after removal, many consider SMBv1 a critical misconfiguration.

A single exposed endpoint, if not properly isolated and monitored, can lead to operational disruptions, costly recovery efforts, and compliance failures. If exploited, SMBv1 enables attackers to remotely execute code and move laterally. That gives them the keys to kingdom and the speed to go anywhere they want within it.

Because of these risks, leading security frameworks - including Microsoft, NIST, CIS, and CISA - all agree: SMBv1 must go. They recommend fully disabling it, upgrading to newer versions like SMBv2 or SMBv3, and routinely scanning for remnants that may linger in shadow IT or misconfigured systems.

The best-known SMBv1 flaws are the six vulnerabilities fixed in Microsoft security bulletin MS17-010 (CVE-2017-0143 to CVE-2017-0148). The EternalBlue exploit used them to achieve remote code execution over TCP port 445, which is how WannaCry and NotPetya spread from machine to machine without any user interaction. Any unpatched host with SMBv1 enabled and port 445 reachable is still exposed to the same technique today.

How to check if SMBv1 is enabled

On Windows 10, Windows 11 and Windows Server, run PowerShell as an administrator.

To check the SMB server setting:

Get-SmbServerConfiguration | Select EnableSMB1Protocol

To check whether the SMBv1 feature is installed:

Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Before you disable anything, find out who is still using SMBv1. Turn on access auditing with Set-SmbServerConfiguration -AuditSmb1Access $true, then watch Event Viewer under Applications and Services Logs, Microsoft, Windows, SMBServer, Audit for event ID 3000. Each event names a client that connected over SMBv1. That list is your dependency map.

How to disable SMBv1

SMBv1 is not installed by default on Windows 10 and Windows Server version 1709 and later, but upgrades, legacy images and older builds often still carry it.

To disable the SMBv1 server:

Set-SmbServerConfiguration -EnableSMB1Protocol $false

To remove the feature entirely on Windows 10 and 11:

Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

On Windows Server:

Uninstall-WindowsFeature -Name FS-SMB1

A restart is required. At scale, push the same setting through Group Policy or your endpoint management tool, starting with a pilot group taken from the audit log in the previous step. Keep a rollback plan for any device that fails, because the most common result of a rushed removal is a printer, NAS or legacy application that stops working.

Why SMBv1 Remediation Projects Stall

Legacy dependencies, poor visibility, and configuration drift make SMBv1 a stubborn threat. But letting it remain is no longer an option: the costs - operational, financial, and reputational - are growing fast. It requires careful coordination across Security, Infrastructure, and IT Operations teams.
SMBv1 remediation projects can run anywhere from 5 to 12 months and cost between $475,417 and $663,750, on average. Those costs are tied to skilled labor requirements, thorough environment mapping (with shadow IT presenting a serious challenge), detailed planning, exception and workaround design and development, specialized test environments, and phased rollouts.

The extended timeline and complexity make it easy for things to fall through the cracks. And the longer the project drags on, the more consequential your interim exposure becomes. Of course, it also pulls time and focus away from other project and strategic initiatives.

In short, remediating SMBv1 is a headache, and one that’s often repeated if configuration drift brings SMBv1 back after the fact.

How to Keep SMBv1 From Coming Back

Remediating SMBv1 is a complex, multi-faceted effort, requiring coordination across teams, testing, rollouts, and constant vigilance. It's easy to miss specific endpoints, overlook dependencies, and fail to account for the implications of user changes or third-party updates.

Remedio's SMBv1 remediation checklist helps your team stay organized throughout the process and avoid mistakes. It breaks down each critical step, so tasks are coordinated, risks are managed, and nothing is forgotten or left incomplete. An unstructured hardening project can feel like the Wild West, and a step-by-step checklist brings order to it, helping your team to:

  • Keep all tasks visible, owned, and prioritized
  • Map dependencies with full operational awareness 
  • Strategically, identify, justify, and contain edge cases
  • Thoroughly test and validate changes before pushing them to production 
  • Establish a framework for continuous monitoring to catch any re-emergence
  • Plan confidently for long-term resilience

SMBv1 is best treated as a configuration problem rather than a one-off vulnerability fix: disabling it once does not keep it off, because rebuilds, legacy images and software installs can quietly bring it back. Remedio Baseline detects SMBv1 wherever it reappears and restores the approved configuration automatically.

Download the Checklist and take the first step toward a safer, streamlined future »

FAQ

Why is SMBv1 still found in enterprise environments?
Like NTLM, SMBv1 usually survives because something still depends on it, not because teams are unaware of the risk. Legacy applications, medical devices, manufacturing equipment, embedded Windows systems, NAS appliances, and unsupported vendor software may all still require it, and in many organizations nobody knows which ones until disabling SMBv1 causes an outage. Operational technology is the hardest case, because those devices have long lifecycles and limited vendor support. Where a device cannot be upgraded yet, isolate it, apply compensating controls, and give it a retirement date.
Is SMBv1 enabled by default in Windows 10 and Windows 11?
No. Microsoft stopped installing SMBv1 by default starting with Windows 10 version 1709 (the Fall Creators Update) and Windows Server version 1709, and Windows 11 does not include it out of the box. It can still be present on devices upgraded from older versions, built from legacy images, or where an application reinstalled it.
What port does SMBv1 use?
SMBv1 runs over TCP port 445, the same port as SMBv2 and SMBv3, and older configurations may also use NetBIOS on port 139. Blocking 445 at the network edge limits external exposure, but it does not remove SMBv1 from internal hosts, which is where lateral movement happens.
Is disabling SMBv1 enough to eliminate the risk?
Disabling SMBv1 is essential, but it only works if it stays disabled. Configuration drift, software installs, legacy images, and system rebuilds can all quietly bring it back. Treat a disabled SMBv1 as a state you verify continuously across the environment, not a project you close once.
What breaks when SMBv1 is removed?
It depends on the environment, but common impacts include file sharing failures, printer connectivity issues, application errors, failed backups, authentication problems, and lost communication with legacy devices. Most modern Windows systems negotiate SMBv2 or SMBv3 automatically, so the risk sits with older operating systems and specialized equipment, which may need upgrades, replacement, or compensating controls before SMBv1 can go.

About Author

Bar Bikovsky

Bar Bikovsky

Global cybersecurity sales leader

With a strong background in technology and sales, Bar helps businesses identify and prioritize key challenges — translating technical complexity into clear, actionable solutions. By combining big-picture thinking with hands-on engagement, he plays a pivotal role in expanding Remedio reach & impact.

Fix Misconfigurations Without Fear

Automate configuration security while keeping full control.

Book a Demo