Microsoft released updates for all supported versions of Windows - client and server - on the August 2019 Patch Day. You can check out our overview of the updates if you have not done so already. Reports suggest that some administrators and home users face issues with the released updates on machines running Windows 7 or Windows Server 2008 R2. Installing the most recent update means that you also get all the previous updates, including important security fixes. Current status of Windows 7 SP1 and Windows Server 2008 R2 SP1 For the most up-to-date information about Known Issues for Windows and Windows Server, please go to the Windows release health dashboard. Microsoft changed the signing of update packages for Windows 7 and Windows Server 2008 R2 devices on the August 2019 Patch Day for the first time. The company signs packages only with SHA-2 since August 2019; it signed them with SHA-1 and SHA-2 previously but decided to drop SHA-1 because of known weaknesses.
- Windows Server 2008 R2 Updates Windows 10
- Windows Server 2008 R2 Update 80072ee2
- Windows Server 2008 R2 Update Reset
- Windows Server 2008 R2 Update Agent
by Martin Brinkmann on August 15, 2019 in Windows - 36 comments
Mar 23, 2019 Hey All, I came across an issue the other day when trying to install windows updates on Server 2008R2 (yes I know it's old will be decomm'd) There were about 5 updates to install so I assumed it wouldn't take too long. Extended support for Windows Server 2008 and Windows Server 2008 R2 is ending on January 14, 2020. There are two modernization paths available: On-premises upgrade, or migration by rehosting in Azure. If you rehost in Azure, you can migrate your existing Server images free of charge. Oct 12, 2009 Windows Server 2008 R2. To start the download, click the Download button and then do one of the following, or select another language from Change Language and then click Change. Click Run to start the installation immediately. Click Save to copy the download to your computer for installation at a.
Microsoft released updates for all supported versions of Windows -- client and server -- on the August 2019 Patch Day. You can check out our overview of the updates if you have not done so already.
Reports suggest that some administrators and home users face issues with the released updates on machines running Windows 7 or Windows Server 2008 R2.
Attempts to install the updates KB4512506 (monthly rollup update) or KB4512486 (security-only update) fail with the error 0x80092004. The error associated with the error code, CRYPT_E_NOT_FOUND, suggests that Windows Update rejects the updates because cryptographic values that the update packages contain are not found.
Microsoft changed the signing of update packages for Windows 7 and Windows Server 2008 R2 devices on the August 2019 Patch Day for the first time. The company signs packages only with SHA-2 since August 2019; it signed them with SHA-1 and SHA-2 previously but decided to drop SHA-1 because of known weaknesses.
Windows Server 2008 R2 Updates Windows 10
We published an article in 2018 about the change stating that Windows 7 and Server 2008 R2 systems needed certain patches to continue receiving updates.
It appears that affected Windows systems are looking for SHA-1 in the update package and ignore SHA-2. SHA-1 is not included anymore and that appears to be the reason why error 0x80092004 is thrown on those systems.
Tip: it is always good to research Windows updates before installing updates.
Microsoft revealed that certain Symantec and Norton software installed on Windows 7 or Windows Server 2008 R2 systems does not play nice with the change and Microsoft made the decision to block updates on machines running Symantec and Norton software until the issue is resolved. The security solutions may block or delete Windows Updates.
While it is possible that the issue is related, e.g. that other antivirus solutions are causing issues with Windows Updates as well, it is more likely that a required update is missing.
Two updates need to be installed on Windows 7 and Windows Server 2008 R2 systems so that SHA-2 signed updates are installed correctly:
- KB4474419 -- SHA-2 code signing support update for Windows Server 2008 R2, Windows 7, and Windows Server 2008: August 13, 2019
- KB4490628 -- Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: March 12, 2019
If one of these is not installed, SHA-2 signed updates won't be accepted and the error is thrown instead.
Microsoft confirms that KB4474419 is a prerequisite on the support website. The company lists KB4490628 on the page as well stating that it strongly recommends that it is updated. SSU updates are installed automatically if Windows Updates is used but need to be installed manually if updates are installed manually. It is unclear why Microsoft does not list the SSU as a prerequisite more clearly.
You can verify that these updates are installed by checking the 'Installed Updates' listing in the Control Panel or by running third-party software such as Nirsoft's WinUpdatesList.
If at least one of the updates is not installed, install it on the device and run a new check for updates after installation; the August 2019 update should install just fine this time.
Now You: Did you run into any issues installing the August 2019 updates? (via Born)
If you get Windows Update error 0x80092004 on Windows 7 or Server 2008 R2 do this
Description
if you are getting error 0x80092004 during installation of the latest updates for Windows 7 SP1 or Windows Server 2008 R2, you are missing a critical update.
Author
Ghacks Technology News
Windows Server 2008 R2 Update 80072ee2
Logo
AdvertisementViewed 421 times
i have a 2008 R2 Standard server (on VMware) that is stuck without being able to update.
Behavior:
Windows update fails on check for new updates error code 8000FFFF.
Windows Server 2008 R2 Update Reset
When rebooting, server attempts to configure updates. Reboots to login screen, then reboots a second time. At that point it attempts to configure updates (stops at 35%) and then displays the error 'Error installing updates. Reverting changes.' then we get to the login screen.
Windows Server 2008 R2 Update Agent
I Cannot run 'sfc /scannow' i get the error:
I have run the System Update Readiness Tool from this webpage:https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readinessCheckSUR.log:
I have tried deleting files from the %windir/SoftwareDistribution/Download & DataStore.I have tried stopping & starting (confirmed automatic delayed start) BITS, Windows Installer & Windows Update service. Windows 10 license key.
I tried removing registry keys:HKLM/Software/Microsoft/Windows/CurrentVersion/WindowsUpdateHKCU/Software/Microsoft/Windows/CurrentVersion/WindowsUpdate
Nothing appears to work. I still get the 8000FFFF error and the constant attempt to install some phantom update that doesn't exist and reboots twice then reverts.
Any help would be greatly appreciated! Thanks in advance.
UPDATE
Contents of most recent cbs log:
airyt
airytairyt