0x80244010 windows server 2016

После установки нового сервера WSUS в сети нашей компании многие клиенты не смогли получить новые обновления с сервера с ошибкой 0x80244010. Как оказалось, эта ошибка характерна не только для компьютеров, обновляющихся с внутреннего сервера WSUS, но и для устройств, получающих обновления напрямую с Windows Update. Рассмотрим, основные способы исправления ошибки 0x80244010 и восстановления работоспособности системы обновлений.

Картинка с сайта: winitpro.ru

Если вы увидели ошибку получения или установки обнволения в графической Control Panel или панели Settings, нужно открыть лог агента WindowsUpdate.log. В старых версиях Windows 7 и 8 это файл
%Windir%\WindowsUpdate.log
. В современных Windows 10/11 и Windows Server 2022/2019 вы можете сгенерировать файл WindowsUpdate.log с помощью PowerShell:

Get-WindowsUpdateLog -logpath C:\PS\Logs\WindowsUpdate.log

В моем случае в журнале обновлений обнаружились такие ошибки:

PT WARNING: Exceeded max server round trips: 0x80244010 PT WARNING: Sync of Updates: 0x80244010 PT WARNING: SyncServerUpdatesInternal failed: 0x80244010 Agent * WARNING: Failed to synchronize, error = 0x80244010 Agent * WARNING: Exit code = 0x80244010 Agent ********* Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] Agent ************* Agent WARNING: WU client failed Searching for update with error 0x80244010 AU >>## RESUMED ## AU: Search for updates [CallId = {128CCEAD-F84D-405E-9BC2-607D1694894B}]  

AU # WARNING: Search callback failed, result = 0x80244010 AU # WARNING: Failed to find updates with error code 80244010

Картинка с сайта: winitpro.ru

Обратите внимание на строку Exceeded max server round trips: 0x80244010. Эта ошибка говорит, что при обращении к серверу обновлений (в моем случае это WSUS) было превышено максимальное количество обращений. В результате чего сервер обновлений отключает клиента, который превысил лимит обращений (по умолчанию лимит — 200 обращений).

Также в Windows Update есть ограничение в 200 Кб на максимальный размер XML файла, который клиент получает с сервера в рамках одного обращения. Чем большее количество обновлений на сервере для клиента нужно проверить, тем больший размер XML файла. Если клиент не смог получить необходимые данные с сервера обновлений за 200 сессий, он временно отключается от сервера и возвращает ошибку.

Чаще всего такая ошибка возникает из-за плохого или нестабильного сетевого соединения с сервером обновлений, или когда клиенту нужно получить слишком большое количество обновлений (новый клиент сервера WSUS или компьютер, на котором давно не устанавливались обновлений).

В большинстве случаев пользователю достаточно через несколько минут повторно нажать на кнопку Retry/ Check for Updates в панели управления или выполнить команду:

wuauclt.exe / detectnow

Картинка с сайта: winitpro.ru

В большинстве случаев это решает проблему, но в том случае если клиентов в сети много, такой способ решения проблемы неприемлем.

По умолчанию клиент проверяет обновления на сервере каждые 22 часа. Вы можете изменить этот интервал с помощью параметров групповых политик компьютера. Откройте редактор локальной GPO (
gpedit.msc
) или отредактируйте доменные политику в консоли Group Policy Management Console (
gpmc.msc
). Перейдите в раздел Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update.

Включите параметр Automatic Update detection frequency и увеличьте частоту синхронизаций клиента с сервером обновлений до 3 часов.

Картинка с сайта: winitpro.ru

Также можно на стороне сервера WSUS убрать ограничение на максимальный размер XML файла, который может скачать клиент с сервера. Для этого откройте SQL Server Management Studio и подключитесь к базе данных SUSDB. Выполните выполнить следующую команду T-SQL.

USE SUSDB
GO

Проверьте и запомните текущее значение:

select MaxXMLPerRequest from tbConfigurationC

Отключите ограничение:
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0

Чтобы не менять настройки в базе WSUS, можно выполнить очистку WSUS сервера с помощью встроенного мастера очистки (Консоль Update Service -> Options -> Server Cleanup Wizard -> все опции -> Next). Это удалит старые, неиспользуемые, и замененные обновления (особенно много мусора от обновлений MS Office), из-за которых может долго выполняться сканирование.

В результате такой операции, клиент Windows Update будет получать намного меньше мета-информации с WSUS сервера, и его взаимодействие должно уместиться в 200 сессий по 200кб.

Картинка с сайта: winitpro.ru

Также попробуйте увеличить производительность пула WsusPool в IIS на сервере WSUS по рекомендация из стати Ошибка обновления Windows 80244022

WsusPool (Application Pools -> WsusPool -> Advanced settings):

• Private Memory Limit (KB) – 0 (убрать лимит 1.2 на использование RAM рабочим процессов WSUS)
• Queue Length — 25000 (увеличить длину очереди к пулу приложения с 10000)
• Limit Interval (minutes) — 15 (увеличить минут время для сброса счетчиков и выполнения CPU Throttling с 5 минут до 15)
• Service Unavailable Response — TcpLevel (при старом значение HttpLevel клиенту возвращается ошибка HTTP 503)

Отредактируйте файл config ( C:\Program Files\Update Services\WebServices\ClientWebService\web.config), заменив строку
httpRuntime maxRequestLength="4096"
на
httpRuntime maxRequestLength="204800" executionTimeout="7200"

Если все рассмотренные способы не помогли исправить ошибку обновления на клиенте, попробуйте полностью сбросить на нем настройки Windows Update и восстановить настройки по-умолчанию. После чего выполните несколько циклов поиска обновлений.

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

Картинка с сайта: bobcares.com

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.

 Causes of Windows Error 0x80244010

Major causes of Windows Error 0x80244010 include:

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

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.

Reasons Behind 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:

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:

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:WindowsSoftwareDistribution SoftwareDistribution.old ren C:WindowsSystem32catroot2 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 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.
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%SoftwareDistributionDataStore 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!]

Conclusion

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.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

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.

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.

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

1. System File Corruption

wuauclt.exe /detectnow

USE SUSDB GO UPDATE tbConfigurationC SET MaxXMLPerRequest = 0

Methods to troubleshoot Windows Error 0x80244010?

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

[Looking for assistance to fix windows errors? We are available to help you today!]

After deploying a new WSUS server on our corporate network, many Windows clients were unable to receive updates from the server with the error 0x80244010. It turns out that this error occurs not only on computers that download updates from the internal WSUS server. It also occurs on devices that receive updates directly from Windows Update. Let’s take a look at how to fix the 0x80244010 error and restore the functionality of the Windows Update.

Картинка с сайта: woshub.com

If you see an error in the graphical Control Panel or Settings Panel when you try to download or install an update, you need to open the Windows Update agent log. This is %Windir%\WindowsUpdate.log in older versions of Windows 7 and 8. On the latest versions of Windows 10/11 and Windows Server 2022/2019, you should use PowerShell to generate a WindowsUpdate.log file:

I found the following errors in the update log:

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

Картинка с сайта: woshub.com

The most interesting line is the error “Exceeded max server round trips: 0x80244010″. This error message says that when trying to check for updates on the update server (in my case, the WSUS), it has exceeded the maximum number of requests. The update server disconnects a client that has exceeded the maximum number of trips (the default limit is 200 trips).

Windows Update also has a 200KB limit on the maximum size of the XML file that the client can download from the server in a single trip. The greater the number of updates on the server for the client to check, the larger the size of the XML file to download. If the client has not retrieved the required data from the update server in 200 trips, it will temporarily disconnect from the server and return the error 0x80244010.

The most common cause of this error is a poor or unstable network connection to the update server, or if the client is trying to receive too many updates (a new WSUS server client, or a computer that hasn’t been updated in a long time).

In most cases, all the user needs to do is click the Retry/Check for Updates button in Control Panel again after a few minutes, or run the command:

wuauclt.exe /detectnow

In most cases, this solves the problem. However, if there are many clients on the network, this method of solving the problem is unacceptable.

By default, the client checks the server for updates every 22 hours (actually, it is between 17.5 and 22 hours).  Usually, an office computer is switched off at night and its working day is obviously less than 17 hours. So the update check is run once a day and fails. And so on, day after day.

You can change this interval using the computer’s Group Policy settings. Open the local Group Policy editor (gpedit.msc) or create a domain GPO with the Group Policy Management Console (gpmc.msc). Navigate to Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update.

Enable the Automatic Update detection frequency option and reduce the frequency of client synchronization with the update server to 3 hours.

Картинка с сайта: woshub.com

You can also remove the limit on the maximum XML file size that the client can download from your WSUS server. To do this, open SQL Server Management Studio and connect to the SUSDB database. Execute the following T-SQL command:

USE SUSDB
GO

Check and remember the current value:

select MaxXMLPerRequest from tbConfigurationC

Disable the XML file size restriction:
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0

If you do not want to change the settings in the WSUS database, you can clean up the WSUS server by using the built-in Cleanup Wizard (Update Service console -> Options -> Server Cleanup Wizard -> all options -> Next) and remove old, unused, or replaced updates (especially a lot of junk from MS Office updates).

As a result, the Windows Update client will receive much less meta-information from the WSUS server, and its interaction should fit into 200 sessions of 200 KB each.

Картинка с сайта: woshub.com

Also, if there are a lot of WSUS clients in your company, you need to increase the performance of the WsusPool pool in IIS on the WSUS server (can cause the Windows Update error 0x80244022):

WsusPool (Application Pools -> WsusPool -> Advanced settings):

• Private Memory Limit (KB) – 0 (remove the 1.2 GB limit on RAM usage by WSUS working processes)
• Queue Length — 25000 (increase the application pool queue length from 10000)
• Limit Interval (minutes) — 15 (increase the counter reset and CPU throttle time from 5 to 15 minutes)
• Service Unavailable Response — TcpLevel (with the old HttpLevel value, an HTTP 503 error is returned to the client.)

Edit the configuration file ( C:\Program Files\Update Services\WebServices\ClientWebService\web.config) by replacing the httpRuntime maxRequestLength="4096" with  httpRuntime maxRequestLength="204800" executionTimeout="7200"

If all of the above methods have failed to resolve the update error on the client, try completely resetting the Windows Update Agent settings on the client’s computer and restoring the default settings. After that, do a few cycles of the update check.

I have recently stumbled upon another Windows Update error on Windows Server 2016. This time the system was unable to check for updates with Windows Update error code 80244010.

Картинка с сайта: www.wincert.net

Windows could not search for new updates. There was a problem checking for updates. Error found: Code 80244010. Windows Update ran into a problem. I had no luck with deleting the contents of the Software Distribution folder. Even re-registering and re-reporting to WSUS didn’t help.

After this, I have checked the WindowsUpdate.log located in C:\Windows\ folder where I have noticed the following error message:

852 1150 PT WARNING: Exceeded max server round trips: 0x80244010
852 1150 PT WARNING: Sync of Updates: 0x80244010
852 1150 PT WARNING: SyncServerUpdatesInternal failed: 0x80244010
852 1150 Agent * WARNING: Failed to synchronize, error = 0x80244010
852 1150 Agent * WARNING: Exit code = 0x80244010

Because of this error, there was no way to get updates from the server without waiting for a couple of days.

After a couple of days without any additional intervention from my side, I have logged on to the server and have noticed that updates are available for installation.

Картинка с сайта: www.wincert.net

Hopefully, this article will save some time for admins with the same Windows Update error code 80244010.