To resolve this issue in Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Embedded Standard 7 SP1, install this update from Windows Update. The files are available for download from the Microsoft Update Catalog.

These versions of Windows have reached the end of their support period and no longer get security updates from Microsoft. To keep Windows as secure as possible, we recommend that you move to Windows 10.

When you try to install Windows updates, you get the following error: Failure configuring Windows updates. Reverting changes. Do not turn off your computer. Note If this issue occurs, it may take about 30 minutes to revert the changes, and then the system will show the Windows logon screen.

Fixes an issue in which a computer that is running Windows 7 or Windows Server 2008 R2 stops responding at a black screen. This issue occurs when you try to install Windows 7 SP1 or Windows Server 2008 R2 SP1. Additionally, you receive an "0xC000009A" error message.

RESOLUTION To resolve the issue with Windows update, perform the following: Open C:\WUTEMP folder and delete the contents of the folder (If any files exist). Go to "WindowsUpdate" folder in "Program Files" folder, and delete all the contents except the "V4" folder. NOTE: "WindowsUpdate" is a hidden folder.

This article describes an update that enables urgent updates for the Windows Root Certificate Program in Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 8, Windows RT, Windows Server 2012, Windows 7, and Windows Server 2008 R2.

Learn how to run Windows Update Troubleshooter to resolve errors downloading or installing Windows updates.

This article describes an update that enables you to upgrade your computer from Windows 7 Service Pack 1 (SP1) to a later version of Windows. This update has prerequisites.

Fixes an issue in which update 2853587 cannot be applied to Windows 7 SP1 that has AD LDS OOB installed.

First, you should try checking for updates again. If you need help, see Update Windows 10. If you receive the same message and error on subsequent retries, try this workaround to mitigate the issue: Right click or long press on Command Prompt and select Run as administrator.