Fixing Windows Updates Failed with Error 0x80244022

If you have a workstation that failed to Windows Update with the error 0x80244022 from a WSUS, the fix is pretty simple and straightforward.

The reason why the error occurs is that the Application Pool that runs the WSUS service stopped.

Go to the WSUS server and open IIS Manager. Click Application Pools, select WsusPool, and click Start to restart the Application Pool.

Now, let’s try again on the workstation and see if the updates can go through.

The consequence of having this WsusPool application pool stopped is that you can’t access the WSUS dashboard on the WSUS server either, a Connection Error awaits you there instead.

If this happens often, it will delay your workstation/server update process. Better to address it now rather than later. As this post points out, to prevent WsusPool from being stopped, you will need to disable the Rapid-Fail Protection and increase the Private Memory Limit.

Where do I find these two settings?

Highlight the WsusPool in the IIS Application Pools window, and click the Advanced Settings… on the right side Actions pane.

Scroll down a bit towards the bottom of the list, change the Enabled setting for the Rapid-Fail Protection to False, and increase the Private Memory Limit to 3GB under the Recycling section.

Click OK to save the settings and restart the WsusPool.

21 thoughts on “Fixing Windows Updates Failed with Error 0x80244022

  1. This is partially wrong, its not the reason, its a symptom.

    The actual reason is the low memory limit it has, you can change it by selecting the pool, get into the recycling option, and remove or change the memory limit.

  2. Some Insiders have reported seeing this error “Some updates were cancelled. We’ll keep trying in case new updates become available” in Windows Update. If you encounter it, try deleting the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\8b24b027-XXXXX-XXXXXXX
    Check the Error is fixed if it’s not then going the next method.
    Solution 1. Reset the Windows update components manually

  3. Worked here as well, thanks!

    Looked through countless guides to try to solve this but didn’t think it had anything to do with the wsus server on the network.

  4. Unfortunately this was not a solution for the issue I am seeing. The issue I have is in FCM when I try to run Cluster-Aware Updating.

  5. In my case, the WSUS App Pool was stopped. I started this, then logged onto the WSUS console and clicked “Reset Server Node”, which seemed to fix / abate the problem.

  6. It worked, but after downloading/ installing the update, i received this message when i tried to actvate windows : 0x8007232B, meanin “the DNS name does not exist.”
    But i don’t know how to fix this.

  7. these actions made no change for me. Error continues to appear when trying to update a server using SCCM (remediate). I have no clue what is the issue, I run the windows update troubleshooter, deleted software distribution folder and many different other suggestions and server does not update.

Leave a Reply

Your email address will not be published. Required fields are marked *