Site icon WinCert

Windows Update error code 80092004 on Windows Server 2008

version 1809; KB4482887; startup issues; Windows 10 1903

<p>Just when I thought that my Windows Update troubles are behind me another issue with a different code appeared&period;<&sol;p>&NewLine;<p>This time Windows Update error code <strong>80092004<&sol;strong> appeared when I have tried to install 2 patches from August 2019 <strong>KB4512506<&sol;strong> and <strong>KB4512486<&sol;strong>&period;<&sol;p>&NewLine;<p><img class&equals;"alignnone wp-image-3299 size-full" title&equals;"error code 80092004" src&equals;"https&colon;&sol;&sol;www&period;wincert&period;net&sol;wp-content&sol;uploads&sol;2019&sol;09&sol;windows-upate-error-80092004&lowbar;2&period;jpg" alt&equals;"" width&equals;"575" height&equals;"176" &sol;><&sol;p>&NewLine;<p><img class&equals;"alignnone wp-image-3298 size-full" title&equals;"error code 80092004" src&equals;"https&colon;&sol;&sol;www&period;wincert&period;net&sol;wp-content&sol;uploads&sol;2019&sol;09&sol;windows-upate-error-80092004&period;jpg" alt&equals;"" width&equals;"865" height&equals;"96" &sol;><&sol;p>&NewLine;<p>None of the usual tasks for troubleshooting Windows Update issues worked so I had to dig further in order to solve this problem&period; Upon further investigation&comma; I have discovered that Microsoft changed the signing of update packages for Windows 7 SP1 and Windows Server 2008&sol;R2&period; Error code 80092004 indicates that Windows Update is checking for the SHA-1 package signature&comma; but can&&num;8217&semi;t find one&period;<&sol;p>&NewLine;<p>According to <a href&equals;"https&colon;&sol;&sol;support&period;microsoft&period;com&sol;en-us&sol;help&sol;4472027&sol;2019-sha-2-code-signing-support-requirement-for-windows-and-wsus" target&equals;"&lowbar;blank" rel&equals;"noopener noreferrer">this document<&sol;a> as of March 12&comma; 2019&comma; Microsoft has implemented the requirement for Windows and WSUS to include the SHA-2 updates required for Windows 7 SP1 Windows Server 2008 SP2 and Windows Server R2 SP1&period;<&sol;p>&NewLine;<p>So&comma; in order to fix this issue&comma; I had to manually install both of the following updates in order to be able to continue installing updates from WSUS &sol; Windows Update&period;<&sol;p>&NewLine;<ul>&NewLine;<li>Update <a href&equals;"https&colon;&sol;&sol;support&period;microsoft&period;com&sol;en-us&sol;help&sol;4474419&sol;sha-2-code-signing-support-update" target&equals;"&lowbar;blank" rel&equals;"noopener noreferrer">KB4474419<&sol;a> &lpar;This update introduces SHA-2 code sign support for Windows 7 SP1&comma; Windows Server 2008 R2 SP1&comma; and Windows Server 2008 SP2&rpar;<&sol;li>&NewLine;<li>Update <a href&equals;"https&colon;&sol;&sol;support&period;microsoft&period;com&sol;en-us&sol;help&sol;4490628&sol;servicing-stack-update-for-windows-7-sp1-and-windows-server-2008-r2" target&equals;"&lowbar;blank" rel&equals;"noopener noreferrer">KB4490628 <&sol;a> &lpar;Addresses an issue in the servicing stack when you install an update that has been signed by using only the SHA-2 hash algorithm&rpar;<&sol;li>&NewLine;<&sol;ul>&NewLine;<p>I have also noticed that for some reason on several servers these updates failed to install through WSUS and that was the main culprit of this error code&period;<&sol;p>&NewLine;<p><img class&equals;"alignnone wp-image-3300 size-full" title&equals;"error code 80092004" src&equals;"https&colon;&sol;&sol;www&period;wincert&period;net&sol;wp-content&sol;uploads&sol;2019&sol;09&sol;80092004&lowbar;1&period;jpg" alt&equals;"" width&equals;"772" height&equals;"19" &sol;><&sol;p>&NewLine;<p>Once I have installed the above patches&comma; my problem was finally solved&excl;<&sol;p>&NewLine;<p><img class&equals;"alignnone size-full wp-image-3302" src&equals;"https&colon;&sol;&sol;www&period;wincert&period;net&sol;wp-content&sol;uploads&sol;2019&sol;09&sol;wsus-message&period;jpg" alt&equals;"" width&equals;"570" height&equals;"164" &sol;><&sol;p>&NewLine;<p>It&&num;8217&semi;s also worth saying that some of the users reported that removing Symantec Antivirus from the system fixed the issue after which they were able to install WSUS and Windows Updates&period;<&sol;p>&NewLine;<p>Hopefully&comma; this article will save a lot of headaches for many of our readers&period;<&sol;p>&NewLine;

Exit mobile version