Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows 7 / WSUS Windows Update Error 0x80244010: Exceeded max server round trips

January 31, 2019 Windows 10Windows 7Windows Server 2008 R2Windows Server 2012 R2

WSUS Windows Update Error 0x80244010: Exceeded max server round trips

After a new WSUS server had been installed in our corporate network, many Windows clients could not receive new updates from this server with the error 0x80244010. As it turned out, this error is typical not only to the computers that are updated from the internal WSUS server, but also to the devices that receive updates directly from Windows Update servers. Let’s consider the way to fix the error 0x80244010 and restore Windows update subsystem functionality.

windows could not searc for new updates code 80244010

To diagnose the problem, open the WindowsUpdate.log (in Windows 7 and 8.1 it is located in %Windir% folder, in Windows 10 you can generate it as follows). You will see these lines in the update log:

2018-10-04 16:10:28:661 121 2a2b2 PT WARNING: Exceeded max server round trips: 0x80244010
2018-10-04 16:10:28:661 121 2a2b2 PT WARNING: Sync of Updates: 0x80244010
2018-10-04 16:10:28:661 121 2a2b2 PT WARNING: SyncServerUpdatesInternal failed: 0x80244010
2018-10-04 16:10:28:661 121 2a2b2 Agent * WARNING: Failed to synchronize, error = 0x80244010
2018-10-04 16:10:29:042 282 2a2b2 Agent * WARNING: Exit code = 0x80244010
2018-10-04 16:10:29:042 282 2a2b2 Agent *********
2018-10-04 16:10:29:042 282 2a2b2 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2018-10-04 16:10:29:042 282 2a2b2 Agent *************
2018-10-04 16:10:29:042 282 2a2b2 Agent WARNING: WU client failed Searching for update with error 0x80244010
2018-10-04 16:10:29:042 282 2221c AU >>## RESUMED ## AU: Search for updates [CallId = {128CCEAD-F84D-405E-9BC2-607D1694894B}]
2018-10-04 16:10:29:042 282 2221c AU # WARNING: Search callback failed, result = 0x80244010
2018-10-04 16:10:29:042 282 2221c AU # WARNING: Failed to find updates with error code 80244010

windows update error : Exceeded max server round trips: 0x80244010

The most interesting line is the error “Exceeded max server round trips: 0x80244010″. It means that the maximum number of requests to the update server (WSUS) has been exceeded when scanning for updates. This is also indicated by the Windows Update error code according to the table (SUS_E_PT_EXCEEDED_MAX_SERVER_TRIPS). The server disconnects a client that has exceeded the maximum trips number. The trip limit in the Windows update receiving protocol is set on the update server and is 200 trips by default. There is also a limit on the maximum size of an XML file that a client can download from the update server during a trip – 200 KB. The greater number of updates on the server for the client to check, the larger the size of the XML file being downloaded. If a client fails to obtain the necessary data in 200 trips, it is temporary disconnected from the server and returns the error 0x80244010.

As a rule, this error occurs due to the poor or unstable network connection to the WSUS server or if a client needs to receive too many updates (it is a new WSUS server client or a computer, on which the updates haven’t been installed for a long time).

The easiest way is to click Try Again button on a client several times (3-7) in the Windows Update section of the Control Panel or run this command:

wuauclt.exe /detectnow

Important. After you start the search for updates, you should wait for 15 minutes for the previous cycle of update search to finish.

In most cases it can solve the problem, but if there are a lot of clients in your network, this method is not acceptable.

By default, a client checks the server for updates every 22 hours (actually, it is between 17.5 and 22 hours). Usually a working computer is turned off for the night, and its workday is obviously less than 17 hours. Thus, the updates search is performed once a day and it fails. And so it goes day after day.

You can synchronize it more often using group policy “Automatic Update detection frequency” (you can find it in the section Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update), for example, up to every 3 hours.

Set the group policy Automatic Update detection frequency to 3 or 4 hours

You can also remove the limit on the maximum XML file size that the client can download from your WSUS server. To do it, run the following command in WSUSDB database.

USE SUSDB
GO
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0

If you don’t want to change your WSUS database settings, clean up your WSUS server using the integrated Cleanup Wizard (Update Service console -> Options -> Server Cleanup Wizard -> all options -> Next) and remove old, not used or replaced updates (MS Office updates contain a lot of odd things). As a result, a Windows Update client will get less meta-information from your WSUS server, and the interaction should fit in 200 sessions of 200 KB each.

wsus server cleanup wizard

Also, if there are a lot of WSUS server clients, you can increase the performance of WsusPool according to the recommendations in the article Fixing Windows Update error 0x80244022.

If neither of the methods we have considered helped to fix the update error on a client, run the script to reset Windows Update Agent settings on it and clean up your local cache. After that, try to search for updates several times.

6 comments
2
Facebook Twitter Google + Pinterest
previous post
Configuring SSO (Single Sign-On) Authentication on Windows Server RDS
next post
How to Disable Automatic Driver Updates in Windows 10?

Related Reading

How to Sign a PowerShell Script (PS1) with...

February 25, 2021

How to Shadow (Remote Control) a User’s RDP...

February 22, 2021

Configuring PowerShell Script Execution Policy

February 18, 2021

Configuring Proxy Settings on Windows Using Group Policy...

February 17, 2021

Updating Group Policy Settings on Windows Domain Computers

February 16, 2021

6 comments

Matthew Karwoski May 16, 2019 - 2:01 pm

Great article, thank you.

Reply
John McCormack July 5, 2019 - 5:16 am

Much appreciated, this has been bothering me for some weeks.

Reply
Nayan August 16, 2019 - 10:48 am

excellent, problem is resolved now.

Reply
Darius May 6, 2020 - 8:07 am

Thank you very much!

Reply
Christian Casutt June 8, 2020 - 7:58 pm

hero-style, awesome, thanks soooooooooooooooooo much!

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

Thanks for your post! this helped me greatly along with some changes to IIS after I upgraded from 2012 to 2012 R2 and had nightmares with my WSUS Server. Keep up the good work!

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • Accessing USB Flash Drive from VMWare ESXi

    February 26, 2021
  • How to Sign a PowerShell Script (PS1) with a Code Signing Certificate?

    February 25, 2021
  • Change the Default Port Number (TCP/1433) for a MS SQL Server Instance

    February 24, 2021
  • How to Shadow (Remote Control) a User’s RDP session on RDS Windows Server 2016/2019?

    February 22, 2021
  • Configuring PowerShell Script Execution Policy

    February 18, 2021
  • Configuring Proxy Settings on Windows Using Group Policy Preferences

    February 17, 2021
  • Updating Group Policy Settings on Windows Domain Computers

    February 16, 2021
  • Managing Administrative Shares (Admin$, IPC$, C$, D$) in Windows 10

    February 11, 2021
  • Packet Monitor (PktMon) – Built-in Packet Sniffer in Windows 10

    February 10, 2021
  • Fixing “Winload.efi is Missing or Contains Errors” in Windows 10

    February 5, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • How to Allow Multiple RDP Sessions in Windows 10?
  • How to Repair EFI/GPT Bootloader on Windows 10?
  • How to Restore Deleted EFI System Partition in Windows 10?
  • Network Computers are not Showing Up in Windows 10
  • Booting Windows 7 / 10 from GPT Disk on BIOS (non-UEFI) systems
  • How to Run Program without Admin Privileges and to Bypass UAC Prompt?
  • Removable USB Flash Drive as Local HDD in Windows 10 / 7
Footer Logo

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


Back To Top