Microsoft Addresses Windows Restart Issues
Reports by Windows users suggest that at least one of the installed security updates of this month's Patch Day have caused restart issues on systems running the Windows operating system.
A recent blog post over at the Microsoft Security Response Center suggests that the problems occurred for the users after installing the patch MS10-015.
The update fixes vulnerabilities in Windows Kernel that may be used by attackers for an elevation of privileges attack.
Jerry Bryant, the Senior Security Communications Manager, states that Microsoft has not yet " confirmed that the issue is specific to MS10-015" as it could also be an "interoperability problem with another component or third-party software".
Microsoft has pulled the security update from Windows Update after being notified about the restart issue. The company has created a workaround fix in form of a Fix It solution that should be applied by users who do have not yet installed the update
Users are encouraged to install the Fix It solution to protect their operating system from the security vulnerability.
As you may recall from previous blog posts, MS10-015 is an Elevation of Privilege that would require the attacker to have valid credentials in order to be able to leverage the vulnerability in an attack. Several other updates in this release were identified as having a high priority for deployment and we continue to encourage customers to thoroughly test the updates and deploy them immediately. At this time, we are not aware of any issues with the other updates that were released this month and we continue to encourage customers to install them as soon as possible in order to help ensure that they protected from the vulnerabilities they address.
It is a small portable tool that users can run to fix the issue with just a couple of clicks regardless of their technical experience.
Users who are experiencing the restart issue are asked to contact Microsoft support either by web or by phone. The contact information are provided on the blog post at the MSRC blog.
Update: The issue has been fixed in the meantime and the update is available again via Windows Update.Advertisement