Chế độ smb windows feateres
Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows
In this article
This article describes how to enable and disable Server Message Block (SMB) version 1 (SMBv1), SMB version 2 (SMBv2), and SMB version 3 (SMBv3) on the SMB client and server components. While disabling or removing SMBv1 might cause some compatibility issues with old computers or software, SMBv1 has significant security vulnerabilities and we strongly encourage you not to use it. Disabling SMBv2 or SMBv3 for troubleshootingWe recommend keeping SMBv2 and SMBv3 enabled, but you might find it useful to disable one temporarily for troubleshooting. For more information, see How to detect status, enable, and disable SMB protocols on the SMB Server. In Windows 10, Windows 8.1, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012, disabling SMBv3 deactivates the following functionality:
In Windows 7 and Windows Server 2008 R2, disabling SMBv2 deactivates the following functionality:
The SMBv2 protocol was introduced in Windows Vista and Windows Server 2008, while the SMBv3 protocol was introduced in Windows 8 and Windows Server 2012. For more information about SMBv2 and SMBv3 capabilities, see the following articles:
How to remove SMBv1Here's how to remove SMBv1 in Windows 10, Windows 8.1, Windows Server 2019, Windows Server 2016, and Windows 2012 R2. PowerShell methodsHere are the steps to detect, disable and enable SMBv1 client and server by using PowerShell commands. Note The computer will restart after you run the PowerShell commands to disable or enable SMBv1.
Windows Server 2012 Windows Server 2012 R2, Windows Server 2016, Windows Server 2019: Server Manager methodTo remove SMBv1 from Windows Server:
Windows 8.1 and Windows 10: Add or Remove Programs methodTo disable SMBv1 on Windows 8.1 and Windows 10:
How to detect status, enable, and disable SMB protocols on the SMB ServerFor Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows 10, and Windows Server 2019Windows 8 and Windows Server 2012 introduced the new Set-SMBServerConfiguration Windows PowerShell cmdlet. The cmdlet enables you to enable or disable the SMBv1, SMBv2, and SMBv3 protocols on the server component. Note When you enable or disable SMBv2 in Windows 8 or Windows Server 2012, SMBv3 is also enabled or disabled. This behavior occurs because these protocols share the same stack. You don't have to restart the computer after you run the Set-SMBServerConfiguration cmdlet. SMBv1 on SMB Server
For more information, see Server storage at Microsoft. SMB v2/v3 on SMB Server
For Windows 7, Windows Server 2008 R2, Windows Vista, and Windows Server 2008To enable or disable SMB protocols on an SMB Server that is running Windows 7, Windows Server 2008 R2, Windows Vista, or Windows Server 2008, use Windows PowerShell or Registry Editor. PowerShell methodsNote This method requires PowerShell 2.0 or later version of PowerShell. SMBv1 on SMB ServerDetect:
Default configuration = Enabled (No registry named value is created), so no SMB1 value will be returned Disable:
Enable:
Note You must restart the computer after you make these changes. For more information, see Server storage at Microsoft. SMBv2/v3 on SMB ServerDetect:
Disable:
Enable:
Note You must restart the computer after you make these changes. Registry EditorImportant Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur. To enable or disable SMBv1 on the SMB server, configure the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
To enable or disable SMBv2 on the SMB server, configure the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Note You must restart the computer after you make these changes. How to detect status, enable, and disable SMB protocols on the SMB ClientHere is how to detect status, enable, and disable SMB protocols on the SMB Client that is running Windows 10, Windows Server 2019, Windows 8.1, Windows Server 2016, Windows Server 2012 R2, and Windows Server 2012. Note When you enable or disable SMBv2 in Windows 8 or in Windows Server 2012, SMBv3 is also enabled or disabled. This behavior occurs because these protocols share the same stack. SMBv1 on SMB Client
For more information, see Server storage at Microsoft SMBv2/v3 on SMB Client
Note
Disable SMBv1 by using Group PolicyThis section introduces how to use Group Policy to disable SMBv1. You can use this method on different versions of Windows. Disable SMBv1 serverThis procedure configures the following new item in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
To use Group Policy to configure this, follow these steps:
In the New Registry Properties dialog box, select the following:
This procedure disables the SMBv1 Server components. This Group Policy must be applied to all necessary workstations, servers, and domain controllers in the domain. Note WMI filters can also be set to exclude unsupported operating systems or selected exclusions, such as Windows XP. Important Be careful when you make these changes on domain controllers on which legacy Windows XP or older Linux and third-party systems (that don't support SMBv2 or SMBv3) require access to SYSVOL or other file shares where SMB v1 is being disabled. Disable SMBv1 clientTo disable the SMBv1 client, the services registry key needs to be updated to disable the start of MRxSMB10 and then the dependency on MRxSMB10 needs to be removed from the entry for LanmanWorkstation so that it can start normally without requiring MRxSMB10 to first start. This guidance updates and replaces the default values in the following two items in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\mrxsmb10 Registry entry: Start REG_DWORD: 4= Disabled HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation Registry entry: DependOnService REG_MULTI_SZ: "Bowser","MRxSmb20″,"NSI" Note The default included MRxSMB10 which is now removed as dependency. To configure this by using Group Policy, follow these steps:
Auditing SMBv1 usageTo determine which clients are attempting to connect to an SMB server with SMBv1, you can enable auditing on Windows Server 2016, Windows 10, and Windows Server 2019. You can also audit on Windows 7 and Windows Server 2008 R2 if the May 2018 monthly update is installed, and on Windows 8.1 and Windows Server 2012 R2 if the July 2017 monthly update is installed.
When SMBv1 auditing is enabled, event 3000 appears in the "Microsoft-Windows-SMBServer\Audit" event log, identifying each client that attempts to connect with SMBv1. SummaryIf all the settings are in the same GPO, Group Policy Management displays the following settings. Testing and validationAfter completing the configuration steps in this article, allow the policy to replicate and update. As necessary for testing, run gpupdate /force at a command prompt, and then review the target computers to make sure that the registry settings are applied correctly. Make sure SMBv2 and SMBv3 are functioning for all other systems in the environment. Note Don't forget to restart the target systems. FeedbackSubmit and view feedback for |