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.
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)
Summary
Article Name
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
Martin Brinkmann
Publisher
Ghacks Technology News
Logo
Advertisement
Applies To.NET Framework 4.7.1 .NET Framework 4.7 .NET Framework 4.6 .NET Framework 4.6.1 .NET Framework 4.6.2
Эта статья также относится к .NET Framework 4.7.2.
Аннотация
В этой статье описывается ошибка «0x80092004», с которой пользователи могут столкнуться при попытке установить обновление безопасности и качества в июле 2018 года KB4340557 или KB4340558 на Windows 8.1, Windows Server 2012 R2 или Windows Server 2012 после того, как они Установить июнь 2018 .NET Рамочный Предварительный просмотр обновления качества Rollup KB4291497 или KB4291495 на системах, которые работают на .NET Framework 4.7.2, 4.7.1, 4.7, 4.6.2, 4.6.1, или 4.6.
Проблемы
Рассмотрим следующий сценарий.
-
Вы используете .NET Framework 4.6 или более позднюю версию на Windows 8.1, Windows Server 2012 или Windows Server 2012 R2.
-
Ранее вы установили июнь 2018 Предварительный обновления качества KB4291497 или KB4291495
-
Вы пытаетесь установить обновления безопасности и качества В июле 2018 года KB4340557 или KB4340558.
В этом случае обновление не устанавливается, и вы получаете сообщение об ошибке установки «0x80092004».
Заметка Чтобы проверить, какие обновления, которые вы установили, выберите кнопку «Пуск», а затем выберите Настройки (gt; Изменение настроек ПК) ( и обновление и восстановление ( иронов;Windows Update
Решение
Корпорация Майкрософт перевыпустила в июле 2018 года обновления системы безопасности и качества .NET Framework Security and quality Rollup, KB 4340558 и KB 4340557 для устранения проблемы с установкой. Вы можете сканировать эти обновления через обновление Windows. Вы также можете скачать и установить эти обновления непосредственно через следующие статьи Базы Знаний:
Обновления безопасности и качества Rollup для .NET Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7 и 4.7.1 для Windows 8.1, RT 8.1 и Server 2012 R2 (KB 4340558)
Обновления безопасности и качества Rollup для .NET Framework 3.5 SP1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7 и 4.7.1 для Windows Server 2012 (KB 4340557)
Статус
Эта проблема решена. Для получения дополнительной информации смотрите раздел «Разрешение».
Нужна дополнительная помощь?
Нужны дополнительные параметры?
Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д.
If you encounter error 0x80092004 while installing updates on Windows 7 or Server 2008 R2, it is most likely due to some cryptography issues (CRYPT_E_NOT_FOUND).
To workaround this problem, you need to manually install the following update(s) :
SHA-2 code signing support update for Windows Server 2008 R2, Windows 7, and Windows Server 2008: September 23, 2019 (KB4474419)
Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: March 12, 2019 (KB4490628)
Once installed, reboot your computer and then perform Windows Updates again. If the issue persist, try to delete Windows Updates Cache using the disk clean up utility.
The reason for Windows Update error 0x80092004 could be many. When Windows Updates do not work out the way they should, then this error code may appear. When Updates are ready for your system, Microsoft offers them to you; but when you click on the Check for Update button and then try to install them, then such updates could result in this issue.
If you receive Windows Update error 0x80092004, follow the solutions below to resolve Windows Update error 0x80092004.
- Remove recent updates and packages
- Delete Files from Software Distribution folder
- Run Windows Update Troubleshooter
- Install the Update manually or wait for it to be offered to your system.
1] Remove recent updates & packages
When an update fails, it usually rolls back and cleans up everything behind it. In case it doesn’t, you can manually clean that package. Go to Update History and figure out what KB updates were installed. Once you figure it out, you can then execute the DISM tool to manually remove it.
Execute this command – it will give you a list of packages installed recently-
Dism /online /Get-Packages
Figure out the name of the package that is most recent. It may look like how it is as below. Run the Remove Package program to remove it.
dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.192.1.9 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 /norestart
Reboot your computer.
Login back, and then run this command again.
Dism.exe /online /Cleanup-Image /StartComponentCleanup
Scan for updates.
NOTE: The remove package command is specifically for AMD 64 Bit machines which were popularly hit by the update. However, you can always try the same steps with any package or update.
2] Delete Files from Software Distribution Folder
When Windows downloads the updates, they are kept in a dedicated folder called as ‘SoftwareDistribution‘ (C:\Windows\SoftwareDistribution). In case of faulty updates, you can delete the files manually from here. This will force the system to re-download the updates again.
3] Run Windows Update Troubleshooter
Run Windows Update Troubleshooter and see if that helps you. There is also an online WU Troubleshooter that may help you.
4] Install the Update manually or wait for the update to be offered
If it is clear which update is causing the problem, you can manually download the KB update from the Microsoft Update Catalog. Just search for the KB and download it. Once its complete, double click to execute the update, and the Windows Update system will pick it up.
If you see an error message CRYPT_E_NOT_FOUND, then it could mean that your system rejected the update because of cryptographic values mismatch. In this case, you need to ensure that the latest Servicing Stack Update is installed on your system.
This is primarily applicable to Windows Server 2008 R2, Windows 7, and Windows Server 2008 systems, and was resolved with the release of KB4474419 which supported SHA-2 Code Signing requirement for Windows and WSUS.
Alternatively, you could wait for the update to be offered to your system and then install it. This is what we would recommend.
Why Windows Update failed to install?
There can be many reasons why Windows Update is failing to install on your system. One possible cause is the less disk space. Your device should have 10 GB or more space on C drive for successful installation of Windows Update. Other causes of the Windows Update failure include corrupted system image files, updates being blocked by antivirus or firewall, etc.
How do I fix Windows Update Service error?
Windows Update Service is responsible for the installation of Windows updates on your system. If this service is missing or not running, you will not be able to install Windows Update. If Windows Update Service is not running and you are unable to start it via Services Manager, clearing the SoftwareDistribution folder can help. If this does not work, troubleshot in a Clean Boot state.
Let us know if any of these solutions helped you to resolve this problem. A. confirmation from your side will only help us improve, and others as well.