- Home users:
Skip the details: Download the updates for your home computer or laptop from the Microsoft Update website now:
- IT professionals:
How to obtain help and support for this security updateHelp installing updates:
Support for Microsoft Update
Security solutions for IT professionals:
TechNet Security Troubleshooting and Support
Help protect your computer that is running Windows from viruses and malware:
Virus Solution and Security Center
Local support according to your country:
Known issues with this security update
- After you install this security update on a computer that is running Windows Server 2003, the Remote Desktop Services service may not start. This issue occurs if the computer has the EnableCertPaddingCheck registry value enabled.
To work around this problem, disable the EnableCertPaddingCheck registry value.
For more information about EnableCertPaddingCheck, see the following Microsoft TechNet topic:
This issue occurs when you install the security update on a system that has partly corrupted data or when the following registry subkey does not exist:
If the HKEY_LOCAL_MACHINE\SCHEMA registry subkey does not exist, you can verify the issue by loading the %SystemRoot%\system32\SMI\Store\Machine\SCHEMA.DAT file.
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. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
To resolve this issue, follow these steps:
- Start the computer in safe mode.
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following subkeys in the registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName
- Change the ActiveComputerName and ComputerName REG_SZ registry entries so that they use the correct computer name.
- Exit Registry Editor, and then restart the computer.
How to determine whether the problem is resolved
If the tool fixed this problem, the following entry is added to the %WinDir%\Logs\CBS\CheckSUR.log file:
Recreated missing key: wcm://Microsoft-Windows-CoreOS?...\metadata\elements\ComputerName
The tool will add the following entries to the CheckSUR.log file whether it actually fixes the problem or not:
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.
Article ID: 2893294 - Last Review: Sep 14, 2017 - Revision: 3