Home › WSUS › 0x80244010

WSUS · 0x80244010 · Windows Server 2019 / 2022 / Windows Update Services

WSUS Error 0x80244010: Too Many Round Trips to Server - Windows Server 2019/2022

Root cause is oversized WSUS catalogue or corrupted client datastore; fix involves cleaning up WSUS and resetting client update components.

Error Details

FactValueSourceNote
Exact error stringWU_E_PT_EXCEEDED_MAX_SERVER_TRIPSWindowsUpdate.log-> Event ID 25
Affected OS build rangeWindows Server 2019, Windows Server 2022
Registry key involvedHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdateRegistry Editor-> OMA-URI
Relevant service/endpoint URLhttp://<wsus_server>/ClientWebService/client.svc
Log line signatureError: WU_E_PT_EXCEEDED_MAX_SERVER_TRIPSWindowsUpdate.log

Log Files to Check

What This Error Actually Means

The error code 0x80244010, also known as WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS, is raised by the Windows Update Agent component of the Windows operating system when it encounters an issue during a synchronization or update session. Specifically, this error indicates that the client has made too many round trips to the WSUS server in a single update session, exceeding the maximum allowed number of connections. This can occur due to various reasons such as oversized WSUS catalogs, corrupted datastores on the client side, high I/O latency, and issues with HTTP keep-alive connections.

Affected Versions and Scope

This error is primarily observed in Windows Server 2019 and Windows Server 2022 environments where WSUS (Windows Server Update Services) is deployed. It does not affect other versions of Windows such as Windows 10 or Windows 8, nor does it impact non-Windows systems like Linux servers managed through alternative update mechanisms.

Where To Look First: Logs and Event IDs

To diagnose this issue, you need to examine specific logs on both the client machine and the WSUS server. On the affected client, check the C:\Windows\WindowsUpdate.log file for lines containing the exact error string "Error: WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS". Additionally, review Event Viewer > Windows Logs > System for events related to Windows Update Agent with IDs 20 and 25. On the WSUS server side, inspect the logs located in C:\inetpub\wwwroot\Wsus\SoftwareDistribution\DataStore\Logs for any anomalies or errors that may correlate with the client's issues.

Root Causes

Oversized WSUS Catalogue

An oversized WSUS catalogue can cause clients to exceed their maximum number of server trips. This typically happens when the WSUS server has not been cleaned up for months, leading to thousands of superseded updates being stored unnecessarily.

Corrupted Client DataStore

The SoftwareDistribution\DataStore on the client machine may become corrupted due to various reasons such as abrupt shutdowns or system crashes during an update session. This can cause the Windows Update Agent to repeatedly attempt failed metadata requests, leading to excessive server trips and ultimately triggering error 0x80244010.

IIS Configuration Issues

Improper configuration of IIS on the WSUS server can also contribute to this issue. For example, if the IIS application pool is set with a low memory limit or experiences frequent recycling during update sessions, it may cut off HTTP keep-alive connections mid-session, forcing clients to reconnect repeatedly.

Fix Procedure

To resolve error 0x80244010, follow these steps:
  1. Clean Up WSUS Server:

    Run the WSUS Server Cleanup Wizard from the WSUS Administration Console. This tool allows you to remove superseded updates, unused updates, and unneeded update files.

  2. Reset Windows Update Components on Client:
    Warning: Resetting Windows Update components may cause enrolled devices to lose their current configuration state until the process is completed successfully.

    Open Command Prompt as Administrator and execute the following commands:

    net stop wuauserv
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    net start wuauserv
    wuauclt /detectnow
    

  3. Increase IIS Application Pool Memory Limit:

    Open Internet Information Services (IIS) Manager, navigate to the WSUS application pool settings and increase the memory limit as necessary.

  4. Enable WSUS Driver Synchronization Exclusion:

    To reduce the size of the WSUS catalogue, enable driver synchronization exclusion in the WSUS console. This can be done by navigating to WSUS Console > Settings > Options and selecting "Exclude drivers from synchronization."

  5. Registry Adjustment (Optional):

    If necessary, adjust registry settings under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate. For example, you can modify the value of NoAutoRebootWithLoggedOnUsers to control automatic reboot behavior.

  6. Verify Fix:

    To confirm that the issue has been resolved, check the client's WindowsUpdate.log for a successful update session without encountering WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS errors. Additionally, monitor Event Viewer > Windows Logs > System for events indicating normal operation.

  7. Prevent Recurrence:

    To prevent this issue from recurring, ensure regular maintenance of the WSUS catalogue and client datastores. Consider implementing policies to automatically clean up superseded updates periodically using PowerShell cmdlets such as Get-WsusUpdate -Classification Superseded.

Error Code Variants

Error CodeDescriptionDistinguishing Factors
0x80244010WU_E_PT_EXCEEDED_MAX_SERVER_TRIPSIndicates too many server trips during a single update session.
0x80244035WU_E_UNEXPECTEDGeneral error indicating an unexpected issue occurred. Distinguished by lack of specific details about number of server trips.
0x8024401DWU_E_SERVICE_COMMUNICATION_ERRORIndicates a communication failure between the client and WSUS server, but does not specify excessive round trips.

Verification

To verify that the fix has been successful, monitor the C:\Windows\WindowsUpdate.log file for lines indicating normal update operations without any WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS errors. Additionally, check Event Viewer > Windows Logs > System for events ID 20 and 25 showing no error conditions related to Windows Update Agent.

Prevention

To prevent recurrence of this issue, establish a regular maintenance schedule for WSUS cleanup using PowerShell cmdlets like Get-WsusUpdate -Classification Superseded | Uninstall-WsusUpdate. Additionally, implement policies via Group Policy or Intune to automatically reset Windows Update components periodically. For example, you can use the following OMA-URI setting in an Intune device configuration policy:
./Device/Vendor/MSFT/WindowsUpdate/AutoRepair
Tip: Use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to quickly review recent events related to Windows Update Agent.

Sources & References

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.