WSUS Windows Error 0x80244010 How to fix it

Server Management Service

In the process of installing a new WSUS server, most Windows users experiences Windows Error 0x80244010.
Here at Ibmi Media, we regularly help our Customers to fix Windows related issues as part of our Server Management Services.
In this context, we shall look into the different ways to solve "Windows Error 0x80244010" and restoring Windows update subsystem functionality.

What triggers Windows Error 0x80244010?

When this error occurs, you will see an error message such as this;

Windows could not search for new updates

An error occurred while checking for new updates for your computer.

Error(s) found;

Code 0x80244010 Windows Update encountered an unknown error.

This error generally happens after installing a new WSUS server.
This error is typical also for the devices that receive updates directly from Windows Update servers.

The Main causes of Windows Error 0x80244010 includes:

1. Generic glitch
Generic glitch is quite common on Windows endpoint machines. Microsoft already has a selection of built-in repair strategies that are ready to deploy.
We can attempt to fix it by running the built-in Windows Update troubleshooter and by applying the fix that it recommends.

2. Corrupt File in the WU temp folders
Similarly, another scenario is a corrupt temp file in the SofwareDistribution or Catroot2folders. This may occur after a botched update or after an AV scan.
In this scenario, we can fix the issue by running a series of commands capable of resetting every WU component including the two temp folders.

3. The machine cannot update conventionally
Under certain circumstances, the WU component might not work automatically.
If the WU function is blocked at a system level, we can most likely fix the issue. Use the System Update Readiness tool to install the updates that are failing to install conventionally.

4. Disabled Detection Frequency policy
When the client exceeds the default number of allowed trips to the WSUS server, it encounters this issue on a Windows Server.
To fix this issue, we have to use the Local Group Policy editor to enable the Automatic Update detection policy and set a global updating interval.

5. System File Corruption
On the other hand, if the Windows Update troubleshooter isn’t able to fix the issue automatically, the affected system may have an underlying corruption issue that cannot resolve conventionally.
In this case, we can fix the issue by refreshing every Windows component with Clean install or Repair install (in-place repair).

First, to diagnose the problem, open the WindowsUpdate.log, which is located in %Windir% folder. Then you will see a report such as this;

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

Make note of the error, "Exceeded max server round trips: 0x80244010". It means that the maximum number of requests to the update server (WSUS) exceeds while 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 exceeds the maximum trip number. The trip limit in the Windows update receiving protocol is set as 200 trips by default.
Similarly, there is a limit on the maximum size of an XML file the client can download from the update server during a trip – 200 KB. The greater number of updates on the server, the larger the size of the downloading XML file.
If a client fails to obtain the necessary data in 200 trips, it disconnects from the server, resulting in error 0x80244010.

Let us now look into system file corruption in detail.

1. System File Corruption

There are dozens of reasons why Windows files or system files might get corrupt, but among the most common are:

i. Unstable network connection:
As a rule, this occurs due to the poor or unstable network connection to the WSUS server or if a client wants to receive too many updates.
The easiest way is to click the "Try Again" button on a client several times in the Windows Update section of the Control Panel or run the command:

wuauclt.exe /detectnow

Once we start the search for updates, wait for 15 minutes for the previous cycle of update search to finish.
In most cases, this can solve the problem, but if there are a lot of clients in the network, this method is not acceptable.

ii. Unsynchronized updates
We can synchronize the updates using the group policy, “Automatic Update detection frequency”. Go to, Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update.
Automatic Update detection frequency specifies the number of hours that Windows will wait before checking for available updates. The exact wait time is found by using the number of hours specified minus a random value between 0 and 20 percent of that number.
For example, if this policy is used to specify a 20-hour detection frequency, then all computers with this policy will check for updates anywhere between 16 and 20 hours.
If the status is set as Enabled, Automatic Updates will check for available updates at specific intervals.
Similarly, If the status is set as Disabled or Not Configured, Automatic Updates will check for available updates at the default interval of 22 hours.
We can also remove the limit on the maximum XML file size that the client can download from the WSUS server.
To do it, run the following command in WSUSDB database:

USE SUSDB GO UPDATE tbConfigurationC SET MaxXMLPerRequest = 0

If we do not want to change our WSUS database settings, clean up the WSUS server using the integrated Cleanup Wizard (Update Service console -> Options -> Server Cleanup Wizard -> all options -> Next). Then, remove old, not in use updates.
As a result, the Windows Update client will get less meta-information from the WSUS server, and the interaction will fit in 200 sessions of 200 KB each.

[Ibmi Media Support Experts rely on a systematic troubleshooting approach as much as we focus on the right tools for the job.]

Methods to troubleshoot Windows Error 0x80244010?

Windows Error 0x80244010 and its solution involves various steps. Now, let us have a detailed look into it:
1. Run the Windows Update troubleshooter
To launch the Windows Update troubleshooter on Windows 7 in order to fix the 80244010 error, follow the below steps:
i. Press Windows key + R to open up a Run dialog box
ii. Type ‘control’ and press Enter to open up the classic Control Panel interface
iii. Once inside, use the search function in the top-right corner to search for ‘troubleshoot’
iv. Then, from the list of results, click on Troubleshooting to expand on the list of integrated troubleshooters
v. In Troubleshoot computer problem screen, click on System and Security from the list of available options
vi. Click on ‘Windows Update’ under the ‘Windows category’
vii. After we successfully manage to open the troubleshooter, start by clicking on the Advanced button and checking the box along with Apply repairs automatically
viii. Once its done, click on Next to advance to the next menu.
ix. Wait for the initial scan to complete, then click on Apply this fix if the repair strategy is not done automatically.
x. When prompted to restart, do so and see if the issue is resolved at the next system startup by attempting to use the Windows Update feature again.

2. Reset WU components
i. Press Windows key + R to open up a Run dialog box
ii. Type ‘cmd‘ inside the text box and press ‘Ctrl + Shift + Enter’ to open up an elevated Command Prompt.
iii. In case you find the UAC (User Account Control), click Yes to grant admin access.
iv. Once inside, type the following commands and press ‘Enter’ after each one:

net stop wuauserv net stop cryptSvc net stop bits net stop msiserver

v. These successive commands will stop the Windows Update service, the MSI Installer, the Cryptographic service, and the BITS service.
vi. Run the following commands in the same elevated CMD window and press Enter after each one to rename the two folders responsible for storing temporary WU files (SoftwareDistribution and Catroot2):

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 Catroot2.old

vii. Renaming these two folders will force the Windows Update component to create new folders and prevent any corrupt files from affecting the updating operations
viii. After the two folders rename, run these final commands in quick succession (press Enter after each one) to start the same services that we disabled at step 2:

net start wuauserv net start cryptSvc net start bits net start msiserver

ix. Once the service restarts, repeat the action that was previously causing the Windows Update 80244010 error and see if the resolve it done.

3. Run the System Update Readiness Tool
i. Visit the URL https://www.microsoft.com/en-us/download/details.aspx?id=20858 and download the latest version of the System Update Readiness Tool. Once it’s done, select the language and click the Download button for the latest version.
ii. Keep in mind that the download is quite large, so wait patiently.
iii. Once the download is complete, open the System Update Readiness Tool executable and wait for the initial scan to complete.
iv. We can see the utility downloading and installing the updates that were previously failing with the 80244010 error.
v. After the operation is complete, restart your computer and see if the fix is done.

4. Enable the Detection Frequency policy
To set Automatic Update detection frequency, follow the steps given below:
i. In the Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand Windows Components
ii. Then click ‘Windows Update’
iii. In the details pane, click Automatic Update detection frequency, click Enabled, and type the number of hours for the detection interval
iv. Click OK
v. Refresh OS components

5. Clean install:
On one hand, this procedure is the easiest, but the disadvantage is that unless you back up your data, you will lose personal files. As opposed to a clean install, this procedure does not require compatible installation media.

6. Repair install (in-place upgrade):
Likewise, this procedure will require to use a compatible installation media. We will have to be technical, but the advantage is that the operation will only touch the Windows files. This means, all your personal files & settings will remain untouched.
If neither of the methods helps fix the update error, clear Windows Update temporary cache and try to search for updates several times.

7. Stop Windows Update service
i. Click ‘Start’ and type for “services.msc”,
ii. In search results “services.msc” should show up. Open it,
iii. A new window will open containing all Windows services,
iv. Search for ‘Windows Update’
v. Right-click on ‘Windows Update’ and click ‘Stop’.

8. Clear the Windows Update temporary cache folder
i. Hold windows-key pressed and hit “R” key simultaneous,
ii. A small new window will appear,
iii. Type %windir%\SoftwareDistribution\DataStore in this new window and click OK,
iv. This will open Windows Explorer in the correct location,
v. Delete all contents of this folder.

9. Start the Windows Update Service again
i. Switch back to the windows Services,
ii. Locate Windows Update,
iii. Right-click on it and choose Start.