For consumer or highly isolated, managed computers that do not require SMB at all, you can disable the Server or Workstation services. You can do this manually by using the “Services” snap-in (Services.msc) and the PowerShell Set-Service cmdlet, or by using Group Policy Preferences.

Customers must either configure SMB Server to require SMB Server signing or enable SMB Server EPA to harden their systems against this class of attack.

Fixes an issue that occurs when you access shared folders in Windows 2012 R2, Windows 8.1, or Windows RT 8.1 by using SMB version 1 protocol from Windows Server 2003 R2 or Windows XP.

To reduce the risk of this issue, we recommend that you configure environments that run Windows NT 4, Windows 2000, Windows XP, and Windows Server 2003 to allow the use of NTLMv2 only. To do this, manually set the LAN Manager Authentication Level to 3 or higher as described here.

There are two methods to work around this issue. Use one of the following methods, as appropriate for your situation. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly.

To view the complete security bulletin, visit one of the following Microsoft Web sites: To fix this problem automatically, click the Fix this problem link that is related to disabling or enabling the bulletin. Then, click Run in the File Download dialog box and follow the steps in this wizard. Note This wizard may be in English only.

Fixes a problem in which the error message "Cannot access a remote file share" is logged when you try to access a remote share in Windows 8 or Windows Server 2012.

Resolves a vulnerability in Windows that could allow remote code execution if an attacker sends specially crafted messages to a Microsoft Server Message Block 1.0 (SMBv1) server.

Explains how to turn off the Distributed Component Object Model (DCOM) protocol in Windows XP.

To resolve this error, follow these steps: Make sure that you are trying to install the correct update. To do this, check the KB number in Table 1 in Method 1. Compare it to your system version, system service pack level, and system bit level (x64, IA64, or x86).