Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

WSUS Windows Error 0x80244010 – Causes and fix

by | Nov 23, 2020

Windows Error 0x80244010 generally triggers while installing a new WSUS server for many of the Windows clients.

Our Server Administration Techs handles different issues that cause this error on a daily basis.

Today, let us discuss various methods to fix ‘Windows Error 0x80244010’ and restore Windows update subsystem functionality.


Windows Error 0x80244010 – Causes

Windows Error 0x80244010

After installing a new WSUS server, many Windows clients could not receive new updates, resulting in the error 0x80244010. This error is typical also for the devices that receive updates directly from Windows Update servers.

Major causes of Windows Error 0x80244010 includes:

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

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.

System File Corruption

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

  • 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.

  • 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.

[Bobcares support techs 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 involve various steps. Let’s have a detailed look into it:

  • 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:

  1. Press Windows key + R to open up a Run dialog box
  2. Type ‘control’ and press Enter to open up the classic Control Panel interface
  3. Once inside, use the search function in the top-right corner to search for ‘troubleshoot’
  4. Then, from the list of results, click on Troubleshooting to expand on the list of integrated troubleshooters
  5. In Troubleshoot computer problem screen, click on System and Security from the list of available options
  6. Click on ‘Windows Update’ under the ‘Windows category’
  7. After we successfully manage to open the troubleshooter, start by clicking on the Advanced button and checking the box along with Apply repairs automatically
  8. Once its done, click on Next to advance to the next menu.
  9. Wait for the initial scan to complete, then click on Apply this fix if the repair strategy is not done automatically.
  10. 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.
  • Reset WU components

  1. Press Windows key + R to open up a Run dialog box
  2. Type ‘cmd‘ inside the text box and press ‘Ctrl + Shift + Enter’ to open up a Command Prompt
  3. In case you find the UAC (User Account Control), click Yes to grant admin access.
  4. Once inside, type the following commands and press ‘Enter’ after each one:
    net stop wuauserv net stop cryptSvc net stop bits net stop msiserver
  5. These successive commands will stop the Windows Update service, the MSI Installer, the Cryptographic service, and the BITS service.
  6. Run the following commands in the same 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
  7. Renaming these two folders will force the Windows Update component to create new folders and prevent any corrupt files from affecting the updating operations
  8. 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
  9. Once the service restarts, repeat the action that was previously causing the Windows Update 80244010 error and see if the resolve it done.
  • Run the System Update Readiness Tool

  1. Visit the URL 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.
  2. Keep in mind that the download is quite large, so wait patiently.
  3. Once the download is complete, open the System Update Readiness Tool executable and wait for the initial scan to complete.
  4. We can see the utility downloading and installing the updates that were previously failing with the 80244010 error.
  5. After the operation is complete, restart your computer and see if the fix is done.
  • Enable the Detection Frequency policy

To set Automatic Update detection frequency, follow the steps given below:

  1. In the Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand Windows Components
  2. Then click ‘Windows Update’
  3. In the details pane, click Automatic Update detection frequency, click Enabled, and type the number of hours for the detection interval
  4. Click OK
  5. Refresh OS components
  • 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.

  • 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.

  • Stop Windows Update service

  1. Click ‘Start’ and type for “services.msc”,
  2. In search results “services.msc” should show up. Open it,
  3. A new window will open containing all Windows services,
  4. Search for ‘Windows Update’
  5. Right-click on ‘Windows Update’ and click ‘Stop’.
  • Clear the Windows Update temporary cache folder

  1. Hold windows-key pressed and hit “R” key simultaneous,
  2. A small new window will appear,
  3. Type %windir%\SoftwareDistribution\DataStore in this new window and click OK,
  4. This will open Windows Explorer in the correct location,
  5. Delete all contents of this folder.
  • Start the Windows Update Service again

  1. Switch back to the windows Services,
  2. Locate Windows Update,
  3. Right-click on it and choose Start.

[Looking for assistance to fix windows errors? We are here for you!]


To conclude, WSUS Windows Error 0x80244010 can occurs due to several reasons including, generic glitch, corrupt file in the WU temp folders, system file corruption and so on. Today, we saw how our Support Engineers systematically troubleshoot the WSUS Windows Error 0x80244010.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.