Code 80092004

Code 80092004 DEFAULT
windows update error code 80092004

Here we can see “windows update error code 80092004”

If you get Windows Update error 0x80092004 on Windows 7 or Server 2008, R2, do that. 

Microsoft released updates for all supported versions of Windows — client and server — on the August 2019 Patch Day. You’ll inspect our overview of the updates if you’ve got not done so already.

Reports suggest that some administrators and residential users face issues with the released updates on machines running Windows 7 or Windows Server 2008 R2.

Attempts to put in the updates KB4512506 (monthly rollup update) or KB4512486 (security-only update) fail with the error 0x80092004. The error related to the error code, CRYPT_E_NOT_FOUND, suggests that Windows Update rejects the updates because cryptographic values that the update packages contain aren’t 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 primary time. the corporate signs package only with SHA-2 since August 2019; it signed them with SHA-1 and SHA-2 previously but decided to drop SHA-1 due to known weaknesses.

We published a piece of writing 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 trying to find SHA-1 within the update package and ignore SHA-2. SHA-1 isn’t included anymore, which appears to be the rationale why error 0x80092004 is thrown on those systems.

Microsoft revealed that certain Symantec and Norton software installed on Windows 7 or Windows Server 2008 R2 systems doesn’t play nice with the change. As a result, Microsoft chose dam updates on machines running Symantec and Norton software until the difficulty is resolved. the safety solutions may block or delete Windows Updates.

While the difficulty may be said, e.g., that other antivirus solutions are causing issues with Windows Updates also, it’s more likely that a required update is missing.

Two updates got 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 among these isn’t installed, SHA-2 signed updates won’t be accepted, and therefore the error is thrown instead.

Microsoft confirms that KB4474419 may be a prerequisite on the support website. the corporate lists KB4490628 on the page, also stating that it strongly recommends that it’s updated. SSU updates are installed automatically if Windows Updates are employed but got to be installed manually if updates are installed manually. So it’s unclear why Microsoft doesn’t list the SSU as a prerequisite more clearly.

You can verify that these updates are installed by checking the “Installed Updates” listing within the instrument panel or by running third-party software like Nirsoft’s WinUpdatesList.

If a minimum of one among the updates isn’t installed, install it on the device and run a replacement check for updates after installation; the August 2019 update should install just fine at this point.

User Questions:

  1. Windows Update Error Code 80092004 for the Update KB4340558 (.NET Framework Update)

The Update KB4340558 (.NET Framework Update) was published on July 10, 2018, and I am taking an equivalent 80092004 error for two days; what causes this and how to unravel it?

  1. Error code 80092004 when trying to put in an update on Windows 7

My friend is running Windows 7 Home on his desktop. When running the updates, he gets the error 80092004. The update that fails is KB4519976 (2019-10 Security Monthly Quality Rollup for Windows 7 for x64-based Systems). I even have tried rebooting and running Windows update again and have an equivalent problem. When searching about the matter, I see the error code 80092004, but not specifically for Windows 7 and KB4519976. What do I want to try to to to put in this update? Thanks.

  1. Windows Update Error 80092004 Server 2008R2

We have about 5 windows servers 2008r2 remaining (yes, I do know we’d like to urge prevent them). for a few reasons, once we apply windows security updates were getting the above error. Did anyone saw this?

Peter Johnson

Peter has been an ItechBrand reporter since July 2019. He previously covered tech Brand news in the United States from 2015 to 2017, before moving to San Francisco to write about cybersecurity. as well as over a decade of professional writing experience. He enjoys copious amounts of tea, board games, and football.

Sours: https://itechbrand.com/windows-update-error-code-80092004/

Many users are experiencing issues with this KB4340558.
Try installing it manually if you can.
Go to the link below and type in KB4340558 in the search and then download and install it on your own.
See if you can get it to work that way.

https://www.catalog.update.microsoft.com/home.aspx

30 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks for the answer. Tried that already yesterday, unfortunately, it didn't work.

Kuter Karaoğur, Oğur Khaganate

10 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

i would just hide the update then for now.
Seems like something you are running on that machine is not compatible with the update.

https://support.microsoft.com/en-ca/help/318392...

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I think my problem is about an interception I forcefully made to Windows Update. I had to stop it because at the same time the Recover My Files program was running and I thought that both programs caused 0 Disk to stuck at 100% (but I was wrong, only Recover My Files program triggered system to use 100% of 0 disk), and also Windows Update was installing the updates at the same time (after it downloaded the update) but then it suddenly stucked for 1-2 hours without any advance on the install of the update, so that was when I had to intercept. I stopped the Windows Update then restarted the system, and probably, that caused this error. I also tried other ways like changing the name of C:/Windows/Software Distribution to "Software Distrubiton Old" to trigger the Windows Update to create a new Software Distribution folder and download the updates but that didn't work too, still got the same error, again.

Kuter Karaoğur, Oğur Khaganate

7 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The Update KB4340558 (.NET Framework Update) which is published on 10 July 2018 and I'm taking the same 80092004 error for 2 days, what causes this and how to solve it?

24 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I don't force updates. If they don't run then i hide them to the next cumulative update and 9 times out of 10 the next update will fix it.

10 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes, after 1 week, it seems Microsoft fixed the bug today, I have downloaded and installed it successfully.

Kuter Karaoğur, Oğur Khaganate

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Karaus,

Can you please tell me the exact link & patch you installed to fix it, I have tried everything but no luck. Please, share me the exact link for the download, & the patches to download to fix this buggy update, please send me a soon today.

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Sours: https://answers.microsoft.com/en-us/windows/forum/all/windows-update-error-code-80092004-for-the-update/d4eaca79-5ac3-4ceb-b0ba-79cd18ef2771
  1. Belkin cargador
  2. Lg g6 update android 10
  3. Marriage license pasco wa

If you get Windows Update error 0x80092004 on Windows 7 or Server 2008 R2 do this

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)

If you get Windows Update error 0x80092004 on Windows 7 or Server 2008 R2 do this
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.
Advertisement
Sours: https://www.ghacks.net/2019/08/15/if-you-get-windows-update-error-0x80092004-on-windows-7-or-server-2008-r2-do-this/
FIX Windows Update Error 0x800f0922 on Windows 10 [2021]

Windows Update error code 80092004 on Windows Server 2008

Just when I thought that my Windows Update troubles are behind me another issue with a different code appeared.

This time Windows Update error code 80092004 appeared when I have tried to install 2 patches from August 2019 KB4512506 and KB4512486.

None of the usual tasks for troubleshooting Windows Update issues worked so I had to dig further in order to solve this problem. Upon further investigation, I have discovered that Microsoft changed the signing of update packages for Windows 7 SP1 and Windows Server 2008/R2. Error code 80092004 indicates that Windows Update is checking for the SHA-1 package signature, but can’t find one.

According to this document as of March 12, 2019, 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.

So, in order to fix this issue, I had to manually install both of the following updates in order to be able to continue installing updates from WSUS / Windows Update.

  • Update KB4474419 (This update introduces SHA-2 code sign support for Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2)
  • Update KB4490628  (Addresses an issue in the servicing stack when you install an update that has been signed by using only the SHA-2 hash algorithm)

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.

Once I have installed the above patches, my problem was finally solved!

It’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.

Hopefully, this article will save a lot of headaches for many of our readers.

Sours: https://www.wincert.net/windows-server/windows-update-error-code-80092004-on-windows-server-2008/

80092004 code

Windows Error Code 80092004: What Is It, What Causes It, and How to Fix It?

Last August 2019, Microsoft rolled out security and non-security updates for all supported Windows versions. Unfortunately, as with most Windows updates, many home users and server administrators complained about facing issues. One of them was the notorious update error 80092004.

What Is the Windows Error Code 80092004?

The error code 80092004 is an error that is associated with the August 2019 Windows security update. It comes with the CRYPT_E_NOT_FOUND error message that suggests that the Windows Update utility cannot proceed with the update you are trying to install because the cryptographic values required by the update package are not available or are nowhere to be found.

The Causes of the Windows Error Code 80092004

So, what are the causes of the Windows error code 80092004?

On March 12, 2009, Microsoft released a servicing stack update and SHA-2 code signing support update. This aim of the move was to further improve the components that make up the Windows Update software. Because of these two updates, new Windows updates require digital signatures created with the SHA-2 hashing algorithm.

Though the release was in March, the company did not immediately issue new updates for the devices and apps that rely on it. Perhaps they wanted to give users enough time to download and install the updates. It was only in August 2019 when Microsoft required the use of the infrastructure on Windows-supported devices.

Now, because the more recent Windows updates require the servicing stack infrastructure and the SHA-2 code support, users who haven’t installed the March 2019 Windows update are likely to encounter the 80092004 problem.

Other possible causes of the error are the following:

  • Corrupted or damaged Windows system files
  • System file errors
  • Incomplete Windows update installations
  • Improper deletion of hardware and apps
  • Adware or spyware
  • Not shutting down your PC properly

How to Fix the 80092004 Error Code on Windows

If you are getting the Windows Update error 80092004, fret not. Simply follow the solutions below to resolve the error:

Solution #1: Remove Recent Windows Updates and Packages

To remove the most recent Windows updates and packages, go to Windows Update History and check what KB updates have been installed. After identifying these updates, use the DISM tool to remove them.

To remove Windows updates, follow the steps below:

  1. Open an elevated Command Prompt. To do so, click on the Search bar. Type Command Prompt and hit Enter. Right-click on Command Prompt and select Run as Administrator. If asked for an administrator password, enter your password and hit Allow.
  2. Execute the command below to see a list of recently installed Windows packages:
    DISM /online /Get-Packages
  3. Find the name of the most recent Windows package. It may look like the name below. Remove the package by running the Remove Package program:
    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
  4. Reboot your computer.
  5. Run this command: DISM.exe /Online /Cleanup-Image /StartComponentCleanup

Then let Windows scan for updates and update your system.

Solution #2: Repair Corrupt System Files with SFC and DISM

The System File Checker (SFC) tool usually comes preinstalled on your Windows device. Its primary purpose is to scan your Windows system files for any signs of corruption or damage. If a file has been changed or modified and that has resulted in its corruption, the tool will automatically replace the problematic file with the correct version. To repair corrupt system files with SFC, open an elevated Command Prompt window, input sfc /scannow, and click Enter.

In case the SFC tool does not work, the Deployment Image Servicing and Management (DISM) tool can be run to get replacements for the damaged Windows system files. Enter the DISM.exe /Online /Cleanup-image /Restorehealth command and hit Enter. Take note that this may take a few minutes to complete, so patience is required. Once the process is over, run the sfc /scannow command again. When the scan is over, restart your PC to get your corrupted files replaced with good copies.

Solution #3: Delete Problematic Update Files from the Software Distribution Folder

It is worth noting that in the event of a Windows update failure, your system will just roll back to the previous Windows version and clean up everything behind. If it doesn’t, it is your job to perform a clean-up manually.

When new Windows updates are downloaded, they are automatically saved in the Software Distribution folder. If you suspect that a faulty update is present, you can manually delete it from the said folder. Don’t worry about doing so because Windows is designed to redownload updates automatically.

Solution #4: Run the Windows Update Troubleshooter

Your Windows device has a built-in troubleshooter that may be used to fix any stuck updates or Windows Update-related errors. It’s called the Windows Update Troubleshooter. When this tool is run, it will:

  • end all active Windows Update services,
  • rename the C:\Windows\SoftwareDistribution folder to C:\Windows\SoftwareDistribution.old to clear the Windows Update download cache and force it to start over again, and
  • restart the Windows Update services.

To run the Windows Update Troubleshooter, follow these steps:

  1. Go to the Search bar and type troubleshooting.
  2. Click on Windows Update Troubleshooter.
  3. Navigate to the System and Security section and select the Fix problems with Windows Update option.
  4. You will then be taken to the Windows Update troubleshooting window. Here, click Advanced.
  5. In the new window that appears, be sure that the Apply repairs automatically option is enabled.
  6. Click Run as Administrator.
  7. Hit Next.
  8. Wait as the troubleshooter identifies the problem. When problems are detected, it will recommend possible fixes. Most of the time, the tool should be able to successfully fix any Windows Update-related issues. But if it couldn’t, try the next solution.

Solution #5: Install the Required Windows Update Manually

To resolve the 80092004 error, you may manually download the KB update you need from the official Microsoft Update Catalog. Simply search for the update from the Catalog and download it. Once the download is complete, double-click on it to run the update.

Solution #6: Ensure That the Most Recent Servicing Stack Update Is Installed

If the CRYPT_E_NOT_FOUND error keeps on popping up on your screen every time you download a Windows update, it may mean that your system is rejecting the update due to cryptographic value mismatch. In that case, make sure the recent Servicing Stack Update is installed. Search for the latest Servicing Stack Update on the official website of Microsoft Support and install it on your PC.

Wrapping Up

Yes, Microsoft keeps patching and polishing Windows. However, we cannot deny the fact that it is still vulnerable to errors. The Windows Update error 80092004 is a clear example of this.

While Microsoft is continuously working on more fixes for the error, we suggest that you do your homework, too. Scan your Windows computer for malware since it might be the reason for the annoying Windows Update error. To scan your computer, you can utilize the built-in Windows Defender tool. If you are using a Mac, consider using Mac repair app. This reliable tool will get rid of all sorts of malicious entities and ensure your system remains fast and efficient.

Sours: https://softwaretested.com/windows/windows-error-code-80092004/
FIX Windows Update Error 0x800f0922 on Windows 10 [2021]

 locked
Windows Update Failed, error code 80092004

Securityhttps://social.technet.microsoft.com/Forums/windows/en-US/93cc445f-d85d-4b53-b871-49b795be1dcf/windows-update-failed-error-code-80092004?forum=winserversecurityQuestion79/27/2019 3:01:05 AM1/17/2020 2:45:01 PMDiscussion on Windows Server security topics and technologies21

  • Question

  • text/html9/27/2019 3:01:05 AMnauy7770

    Windows info:Windows Server 2008 R2 Enterprise x64

    package info:KB4512486,KB4516033,KB4516065

    If WindowsUpdate.log is required, I can upload.

    Any help would be appreciated, THX!

All replies

  • text/html9/27/2019 8:06:52 AMKiki Shi2

    Hi,

    Instead of signing the packages with both SHA-1 and SHA-2, only a SHA-2 hash value is stored in the package. The error code: 80092004 indicates that Windows Update is looking for the SHA-1 signature in the package and does not find it.

    I suggest you refer to the following links for more assistance:

    Windows Updates KB4512506/KB4512486 drops error 0x80092004

    If you get Windows Update error 0x80092004 on Windows 7 or Server 2008 R2 do this

    Note: This is a third-party link and we do not have any guarantees on this website. This is just for your convenience. And Microsoft does not make any guarantees about the content.

    Hope can help you.

    Best regards,

    Kiki Shi


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact [email protected]

  • text/html9/30/2019 1:32:17 AMKiki Shi0

    Hi,

    I am very happy to help you. Would you mind letting me know the update of the problem?  If you think the answer is helpful, please mark it as a reply, which will help more users get valid information.

    Have a nice day=.=

    Best regards,

    Kiki Shi


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact [email protected]

  • text/html10/10/2019 6:40:16 AMnauy7770

    Hi Kiki. Fristly THANK YOU for your supports! Sorry for replying so late.

    I saw the article, it says that due to SHA-2 code problem, Update KB4474419 and Update KB4490628 need to be installed.

    I'd like to ask one more question, do I need to install KB4474419 or KB4490628, or both of them?

  • text/html10/10/2019 7:18:08 AMKiki Shi0

    Hi,

    You are welcome^_^

    You need to install both of them due to the problem.

    Hope can help you.

    Please let us know if you would like further help.

    Best regards,

    Kiki Shi


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact [email protected]

  • text/html12/4/2019 9:37:52 AMnauy7770

    It worked, the update succeeded.problem finally solved....

    I download these two packages and found one of them was already installed. After I finished the install and reboot my cp, it shows 5 new update packages, includes KB4512486 and KB4516033. And they are all successfully installed at last.

    I really appreciate your help, here is my sincerely Thanks to you, Kiki. And, Please forgive my bother(it's really being a long time since your last reply QAQ

  • text/html12/4/2019 10:05:26 AMKiki Shi0

    Hi,

    You are welcome~

    I am very glad to hear that this problem has been solved. Thank you for sharing. We are very grateful for your time and effort.

    Please mark a helpful reply as answer, this behavior can let other forum users get useful information.

    Have a nice day*_*~

    Best Regards,

    Kiki


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact [email protected]

Sours: https://social.technet.microsoft.com/Forums/windows/en-US/93cc445f-d85d-4b53-b871-49b795be1dcf/windows-update-failed-error-code-80092004?forum=winserversecurity

You will also like:

FIX: Windows Update Error 0x80092004 on Windows 7, Server 2008 (Solved)

The Windows Update Error 0x80092004 on Windows 7 & Server 2008 OS, may appear if the KB4474419 and KB4490628 are not installed on the computer. In fact, the error Error Code 80092004 in Windows Update, appears in systems where the SHA-2 code signing support is missing. Thankfully, the SHA-2 code signing can  be activated after installing the KB4474419 and KB4490628 updates, by following the instructions below.

FIX Windows Update Error Code 0x80092004

* More info: To help protect the security of the Windows operating system, updates were previously signed (using both the SHA-1 and SHA-2 hash algorithms). The signatures are used to authenticate that the updates come directly from Microsoft and were not tampered with during delivery. Because of weaknesses in the SHA-1 algorithm and to align to industry standards, Microsoft have changed the signing of Windows updates to use the more secure SHA-2 algorithm exclusively. Stronger alternatives such as the Secure Hash Algorithm 2 (SHA-2) are now strongly preferred as they do not experience the same issues.
Source: https://support.microsoft.com/en-us/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus

This tutorial contains instructions to fix the Windows Update Error 0x80092004 (CRYPT_E_NOT_FOUND) in Windows 7 & Window Server 2008 OS.

 

How to Resolve the Error Code 80092004 in Windows 7 & Server 2008 Update.

Windows 7 SP1 & Windows Server 2008 R2 SP1

To solve the Windows Update Error 0x80092004 on Windows 7 SP1 & Server 2008R2 SP1:

1. Download and install the following Updates from the Microsoft Update Catalog:

  • Servicing stack update (SSU) (KB4490628).
  • SHA-2 update (KB4474419) released September 10, 2019.

2. When the installation is completed. restart your computer.

 

Windows Server 2008 SP2

To resolve the Windows Update Error Code 80092004 on Windows Server 2008:

1. Download and install the following Updates from the Microsoft Update Catalog:

2. When the installation is completed. restart your computer.

That's all folks! Which method worked for you? Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.

If this article was useful for you, please consider supporting us by making a donation. Even $1can a make a huge difference for us.
Sours: https://www.repairwin.com/fix-windows-update-error-0x80092004-on-windows-7-server-2008/


390 391 392 393 394