After a brand new WSUS server had been put in in our company community, many Windows purchasers couldn’t obtain new updates from this server with the error 0x80244010. As it turned out, this error is typical not solely to the computer systems which might be up to date from the interior server, but in addition to the gadgets that obtain updates straight from Windows Update servers. Let’s contemplate the way in which to repair the error 0x80244010 and restore Windows replace subsystem performance.
To diagnose the issue, open the WindowsUpdate.log (in Windows 7 and eight.1 it’s situated in %Windir% folder, in Windows 10 you may generate it ). You will see these traces within the replace 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 consumer failed Searching for replace with error 0x80244010
2018-10-04 16:10:29:042 282 2221c AU >>## RESUMED ## AU: Search for updates [CallId = ]2018-10-04 16:10:29:042 282 2221c AU # WARNING: Search callback failed, end result = 0x80244010
2018-10-04 16:10:29:042 282 2221c AU # WARNING: Failed to seek out updates with error code 80244010
The most attention-grabbing line is the error “Exceeded max server round trips: 0x80244010″. It signifies that the utmost variety of requests to the replace server (WSUS) has been exceeded when scanning for updates. This can also be indicated by the Windows Update error code based on the (SUS_E_PT_EXCEEDED_MAX_SERVER_TRIPS). The server disconnects a consumer that has exceeded the utmost trips quantity. The journey restrict within the Windows replace receiving protocol is ready on the replace server and is 200 trips by default. There can also be a restrict on the utmost measurement of an XML file consumer can obtain from the replace server throughout a visit – 200 KB. The larger variety of updates on the server for the consumer to examine, the bigger the dimensions of the XML file being downloaded. If a consumer fails to acquire the mandatory information in 200 trips, it’s short-term disconnected from the server and returns the error 0x80244010.
As a rule, this error happens as a result of poor or unstable community connection to the WSUS server or if a consumer must obtain too many updates (it’s a new WSUS server consumer or a pc, on which the updates haven’t been put in for a very long time).
The easiest method is to click on Try Again button on a consumer a number of instances (Three-7) within the Windows Update part of the Control Panel or run this command:
Important. After you begin the seek for updates, it’s best to look forward to 15 minutes for the earlier cycle of replace search to complete.
In most circumstances it may possibly resolve the issue, but when there are a whole lot of purchasers in your community, this methodology isn’t acceptable.
By default, a consumer checks the server for updates each 22 hours (truly, it’s between 17.5 and 22 hours). Usually a working laptop is turned off for the night time, and its workday is clearly lower than 17 hours. Thus, the updates search is carried out as soon as a day and it fails. And so it goes day after day.
You can synchronize it extra typically utilizing group coverage “Automatic Update detection frequency” (you will discover it within the part Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update), for instance, as much as each Three hours.
You may also take away the restrict on the utmost XML file measurement that the consumer can obtain out of your WSUS server. To do it, run the next command in WSUSDB database.
UPDATE tbConfigurationC SET MaxXMLPerRequest = zero
If you don’t wish to change your WSUS database settings, clear up your WSUS server utilizing the built-in Cleanup Wizard (Update Service console -> Options -> Server Cleanup Wizard -> all choices -> Next) and take away outdated, not used or changed updates (MS Office updates include a whole lot of odd issues). As a end result, a Windows Update consumer will get much less meta-information out of your WSUS server, and the interplay ought to slot in 200 periods of 200 KB every.
Also, if there are a whole lot of WSUS server purchasers, you may enhance the efficiency of WsusPool based on the suggestions within the article .
If neither of the strategies we’ve got thought-about helped to repair the replace error on a consumer, run the on it and clear up your native cache. After that, attempt to seek for updates a number of instances.