Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 Windows OS Hub / SCCM / Windows Update Error 0x80244022 and WsusPool Memory Limit

December 8, 2017 SCCMWindows 7Windows Server 2008 R2

Windows Update Error 0x80244022 and WsusPool Memory Limit

At one of my customers, I have faced a very interesting problem related to the installation of updates on the clients running Windows 7. The updates are distributed via WSUS server integrated into System Center Configuration Manager (more precisely Software Update Point – SUP). The SCCM server is running Windows Server 2008 R2, the WSUS version is WSUS 3.0 SP2, respectively. Client PCs running Windows 7 SP1 (about 2,000 computers) have to be updated.

Client computers cannot get updates from Software Update Point, the error 0x80244022 appears in the logs.

Client-side WUAhandler.log contains the following errors:

OnSearchComplete - Failed to end search job. Error = 0x80244022.
Scan failed with error = 0x80244022.

WindowsUpdate.log also has a number of errors, like:

2017-11-11 14:25:41:271 612 4858 Setup WARNING: SelfUpdate check failed to download package information, error = 0x80244022
2017-11-11 14:25:41:271 612 4858 Setup WARNING: SelfUpdate check failed to download package information, error = 0x80244022
2017-11-11 14:25:41:271 612 4858 Agent * WARNING: Skipping scan, self-update check returned 0x80244022
2017-11-11 14:25:41:271 612 4858 Agent * WARNING: Exit code = 0x80244022
2017-11-11 14:25:41:271 612 4858 Agent WARNING: WU client failed Searching for update with error 0x80244022
2017-11-11 14:25:41:271 612 4abc AU # WARNING: Search callback failed, result = 0x80244022
2017-11-11 14:25:41:271 612 4abc AU # WARNING: Failed to find updates with error code 80244022

WindowsUpdate.log - : WU client failed Searching for update with error 0x80244022

Server-side WSUSCtrl.log shows this error:

The request failed with HTTP status 503: Service Unavailable
Failures reported during periodic health check by the WSUS Server SCCM-SRV1. Will retry check in 1 minutes

WSUSCtrl.log  The request failed with HTTP status 503: Service Unavailable

I. e., the WSUS site doesn’t respond. Indeed, if you open the URL address of WSUS Administration (http://SCCM-Srv1:8530), this error will appear:

HTTP Error 503. The service is unavailable

HTTP Error 503. The service is unavailable

After opening IIS Manager, I saw that the pool responsible for WSUS (WsusPool) is stopped.

iis WsusPool

After starting it manually, it fall again in 20-30 minutes. In the system log, an interesting entry appeared under Event ID 5117 WAS:

A worker process serving application pool ‘WsusPool’ has requested a recycle because it reached its private bytes memory limit

A worker process serving application pool ‘WsusPool’ has requested a recycle because it reached its private bytes memory limit

By default, the limit of WsusPool memory is 1.8 GB. If it is exceeded (it can happen if there are a lot of WSUS clients, particularly, at the first scan), the pool is reset. To understand, how much memory your pool is using, it’s enough to look at w3wp.exe process. If the limit of 1.8 GB is exceeded, the process is restarted. Thus, to solve this problem, you have to increase the amount of allocated memory.

Note. The issue partially resembles the case we considered earlier with the error 0x8024401C when receiving updates in Windows 10.

You can do it in the IIS Manager, select Application Pools and right-click WsusPool -> Recycling, then enlarge the value in the Private memory usage (in KB) field. WsusPool  increase Private memory usage

It’s up to you to decide how much you increase it, but I recommend to start from 3-4 GB. In my case, 6 GB was enough for 2,000+ WSUS clients.

The size of allocated memory can also be changed in the Advanced Settings of the pool by increasing the value in the Private memory usage (KB) field.

Private memory usage in IIS

Now restart the pool using Start/Stop or Recycle buttons.

iis pool Recycle

After that w3wp.exe stopped consuming over 3 GB of RAM. The next day the computers began to get updates.

Tip. If there are a lot of WSUS clients that get updates from SCCM Software Update Point (especially, those getting the updates for the first time), you can increase the values of the following parameters in the Advanced Settings:

  • Queue Length from 1,000 to 25,000
  • “Service Unavailable” Response Type — from HttpLevel to TcpLevel
  • Failure Interval (minutes) – from 5 to 30
  • Change ‘Maximum Failures’ – from 5 to 60

It is also recommended to install the following updates for WSUS 3.0 SP2 in Windows Server 2008 R2:

  1. KB2720211
  2. KB2734608

And these ones for WSUS 4.0 in Windows Server 2012 R2:

  • KB2919442
  • KB2919355
  • KB3095113
  • KB3159706

2 comments
0
Facebook Twitter Google + Pinterest
previous post
Defending Windows Domain Against Mimikatz Attacks
next post
How to Obtain SeDebugPrivilege when Debug Program Policy is Enabled

Related Reading

How to Enable TLS 1.2 on Windows?

January 18, 2023

How to Restore Deleted EFI System Partition in...

November 30, 2022

Outlook: Your Server Does Not Support the Connection...

October 20, 2022

Adding USB 3.0 and NVMe Drivers to Windows...

September 7, 2022

How to Completely Uninstall Previous Versions of Office...

April 26, 2022

2 comments

Brian February 22, 2019 - 7:06 pm

Awesome info, quickly informed me of my symptoms before I went too far down the path of hours of investigation.

Reply
Brendon Thomas September 29, 2020 - 8:45 pm

THANKS!!!!! This post really helped me to get my WSUS server working as it should. GOOD STUFF!

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • PowerShell
  • VMWare
  • Hyper-V
  • Linux
  • MS Office

Recent Posts

  • Configure User’s Folder Redirection with Group Policy

    February 3, 2023
  • Using Previous Command History in PowerShell Console

    January 31, 2023
  • How to Install the PowerShell Active Directory Module and Manage AD?

    January 31, 2023
  • Finding Duplicate E-mail (SMTP) Addresses in Exchange

    January 27, 2023
  • How to Delete Old User Profiles in Windows?

    January 25, 2023
  • How to Install Free VMware Hypervisor (ESXi)?

    January 24, 2023
  • How to Enable TLS 1.2 on Windows?

    January 18, 2023
  • Allow or Prevent Non-Admin Users from Reboot/Shutdown Windows

    January 17, 2023
  • Fix: Can’t Extend Volume in Windows

    January 12, 2023
  • Wi-Fi (Internet) Disconnects After Sleep or Hibernation on Windows 10/11

    January 11, 2023

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • SCCM and WMI Query to Find All Laptops and Desktops
  • Configuring Remote Control in SCCM 2012
Footer Logo

@2014 - 2023 - Windows OS Hub. All about operating systems for sysadmins


Back To Top