/
/

How to Enable or Disable SMB1 File Sharing Protocol in Windows

by Lauren Ballejos, IT Editorial Expert
How to Enable or Disable SMB1 File Sharing Protocol blog banner image

Key Points

How to Enable or Disable SMB1 File Sharing Protocol in Windows

  • Why disable SMB1? SMB1 is outdated and prone to vulnerabilities. Microsoft deprecated the protocol in 2022, which also meant security patches would no longer be released in support of it.
  • Check SMB1 status using PowerShell:
    • Get-SmbServerConfiguration | Select EnableSMB1Protocol
    • Get-WindowsOptionalFeature -Online -FeatureName “SMB*”
  • Methods for disabling SMB1:
    • Windows Settings (GUI) – Best for individual users.
    • PowerShell scripts – Best for enterprises and remote management.
    • Group Policy (GPMC) – Best for MSPs or domain administrators.
  • When to enable SMB1: A final option for legacy NAS devices (pre-2016), older printers/scanners (pre-2015), embedded industrial/medical systems, or XP/Server 2003 apps.

The Server Message Block (SMB) protocol is a critical component of Windows networking, allowing secure file and printer sharing between network devices. However, the legacy SMB1 protocol isn’t as stringent as its newer iterations.

This guide will walk you through the process of disabling SMB1 in Windows and how to enable or disable the SMB1 file sharing protocol for legacy devices. These steps should help IT teams or MSPs minimize vulnerabilities within the shared network.

💡 If you’re more of a visual learner, you’ll love our video on How to Enable or Disable SMB1 File Sharing Protocol in Windows.

How to check if SMB1 is enabled in Windows

The quickest way to check if SMB1 is enabled on your system is by using PowerShell.

  1. Use Search 🔎 to open TerminalPowerShellRun as administrator.
  2. To check the SMB1 protocol status:

Get-SmbServerConfiguration | Select EnableSMB1Protocol

  1. To view all SMB versions installed:

Get-WindowsOptionalFeature -Online -FeatureName “SMB*”

💡 Tip: You can also use Control PanelNavigate to ProgramsPrograms and Features. Click “Turn Windows features on or off” and find “SMB 1.0/CIFS File Sharing Support” on the list to see if it’s enabled.

Methods for configuring SMB1 in Windows 10/11

Use the table to choose and quickly navigate to your preferred activation steps.

📌 Prerequisites:

  • Check if SMB1 is enabled.
  • A system restart is required for changes to take effect.
  • Some methods may require system and network access.

📌 Use cases:

  • Disable SMB1 to streamline network protocols.
  • Switch SMB1 to prevent systems from using the legacy protocol.

👉 Reminder: Some steps may vary depending on system defaults or active settings.

Click to Choose a Method

💻

Best for Individual Users 

💻💻💻

Best for Enterprises

Method 1: Windows Settings
Method 2: PowerShell script
Method 3: Group Policy

💡 Tip: Check out the Things to look out for section for tips on managing potential risks.

Method 1: Enable or disable SMB1 via Settings

This GUI-based method is recommended for self-service and remote access activation.

  1. Use Search 🔎 to open Control Panel.
  2. Navigate to ProgramsPrograms and FeaturesToggle Turn Windows features on or off.
  3. Find and manage SMB 1.0/CIFS File Sharing Support according to preferences.
  4. Click OK to apply changes

Method 2: How to enable or disable SMB1 in Windows 10 via PowerShell

Run PowerShell as Administrator and use the following commands:

Disable SMB1 Client: Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Disable SMB1 Server: Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force

Enable SMB1 Client: Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Enable SMB1 Server: Set-SmbServerConfiguration -EnableSMB1Protocol $true -Force

💡 Note: This script may run or fail without displaying any confirmation or prompt. To confirm if changes have been applied successfully, check the corresponding registry keys or system settings.

Method 3: How to disable SMB1 in Windows 10 via Group Policy

Group Policy Management Console (GPMC) is available on Windows Pro, Enterprise, and Education editions, but is not installed by default. This method is for system administrators and MSPs.

  1. Press Win + R, type gpmc.msc, and tap OK to open GPMC.
  2. Create or edit a GPO linked to your target Organizational Unit (OU).
  3. Navigate to Computer ConfigurationAdministrative TemplatesMS Network ClientMicrosoft Network Client.
  4. Manage Configure SMB v1 client driver according to preferences.
  5. Then, go to Computer Configuration Administrative TemplatesMS Network ServerMicrosoft Network Server.
  6. Manage Configure SMB v1 server according to preferences.

You can run the gpupdate /force command to apply the changes immediately. Otherwise, the new settings will be applied on the next update interval.

👉 Watch this GPUpdate video demonstration for a visual reference.

After rebooting the device, validate if SMB1 is disabled using the
Get-SmbServerConfiguration | Select EnableSMB1Protocol command. It should return “False” if SMB1 has been successfully switched off.

When to enable SMB1 file sharing protocol

Enabling SMB1 introduces significant security risks to your network. It’s advisable to only use the sharing protocol as a last resort and with a full understanding of the vulnerabilities. With that said, this action may be necessary to initiate compatibility with other legacy apps or resources in Windows.

If you must still use SMB1, consider the following steps for isolation and remediation.

  • Place legacy systems on isolated network segments
  • Implement strict firewall rules to limit SMB1 traffic
  • Disable SMB1 on all internet-facing systems
  • Use VLANs to separate SMB1 traffic from your main network
  • Consider application-level alternatives or middleware to avoid SMB1 entirely

Apart from exposing the system to known exploits and CVEs, systems running SMB1 may violate compliance requirements (GDPR, HIPAA, PCI) and incur penalties. Keeping it active is also hugely detrimental since security patches are no longer being released for SMB1.

💡 Note: Microsoft has stopped support for SMB1 since 2022.

⚠️ Things to look out for when enabling or disabling SMB1

Below are common risks, their possible consequences, and some practical ways to reverse or prevent issues when changing SMB1 preferences.

RisksPotential ConsequencesReversals
Legacy applications built for Windows XP/Server 2003 environmentsApplication errors, crashes, or inability to access file shares➤ Use containerization or virtualization to isolate SMB1 usage

➤ Develop modernization or replacement plans for long-term migration

Unsegmented networks still using SMB1Malware can spread laterally across the network if one system is compromised➤ Segment networks with VLANs and firewalls

➤ Restrict SMB1 traffic to specific, controlled zones only

Industrial control systems, point-of-sale terminals, and medical equipment running older embedded OSBusiness-critical workflows may fail, leading to downtime or safety risks➤ Where updates aren’t possible, isolate these systems on segmented networks with strict firewall/ACL rules

➤ Consider middleware or virtualization to bridge SMB1 dependencies.

Additionally, consider enforcing the use of SMB2 or SMB3 protocols whenever possible by configuring minimum SMB security settings through Group Policy:

  1. Press Win + R, type gpmc.msc, and tap OK to open GPMC.
  2. Navigate to Computer ConfigurationAdministrative TemplatesNetwork → Lanman Workstation.
  3. Set Enable insecure guest logons to Disabled.

Then, configure the registry to enforce the minimum SMB version:

  1. Press Win + R, type regedit, and tap OK to open the Registry Editor.
  2. Navigate to or copy and paste the following path to the Registry address bar. If the path is incomplete, create the required key.

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

  1. Create or modify the SMB2 DWORD (32-bit) value.
  2. Open it and set the Value data to 1 to require SMB2 or higher across the network.

Conduct regular network-wide audits to identify systems still using the SMB1 protocol. For instance, use tools like Microsoft’s Message Analyzer to capture and analyze network traffic for SMB protocol usage.

Security best practices when managing the SMB1 protocol

Resilient IT security requires a proactive approach to managing legacy protocols like SMB1. While complete removal might pose challenges for organizations with older systems, the ease of use and security benefits far outweigh the compatibility concerns.

By following the steps outlined in this guide, you can swiftly disable SMB1 in Windows and implement proper isolation measures where necessary. Taking action will not only protect your systems from common vulnerabilities and exploits but also improve performance and prepare your infrastructure for future security demands and compliance requirements.

Related topics:

FAQs

No, SMB1 is not safe to use in 2025.

The protocol contains fundamental security vulnerabilities that cannot be patched, and major exploits like EternalBlue remain a threat despite years of awareness. Using SMB1 may violate security compliance requirements in regulated industries.

Legacy NAS devices manufactured before 2016 may become inaccessible, while older multifunction printers and scanners might lose functionality.

Windows XP and Windows Server 2003 machines cannot connect to file shares without SMB1, and some specialized industry applications with hardcoded SMB1 dependencies may fail. Older embedded systems (manufacturing, healthcare, etc.) may lose connectivity.

Yes, SMB1 can be disabled remotely using several methods:

  • PowerShell remoting: Invoke-Command -ComputerName [hostname] -ScriptBlock {Set-SmbServerConfiguration -EnableSMB1Protocol $false -Force}
  • Group Policy deployment to targeted computers/OUs
  • Windows Admin Center for managing multiple servers
  • Configuration Manager (SCCM) using compliance settings

👉 Reminder: Methods may vary depending on licensing or system requirements.

No, disabling SMB1 does not affect modern file-sharing capabilities. Windows automatically uses SMB2 or SMB3 for all file sharing operations between compatible systems.

You might also like

Ready to simplify the hardest parts of IT?