This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Recently added Arc-Enabled servers to the Update Management Center (Preview) and were working fine until a couple days ago. Suddenly, most of them could not get update data and returned error 0x80244022:
Now, the machines cannot even locally get update data. The machines are connected to the internet and otherwise functioning properly. The troubleshooter reports no issues and restarting the machine did not help.
Is it possible that adding these servers to Update Management Center broke them? Any ideas would be greatly appreciated.
The issue is persistent both in the update management center and locally on the machines. I have tried all of the automated solutions proposed by Microsoft.
Could this be an issue with how I configured the Update management system or a larger issue with the preview?
WSUS was continuously crashing due to the volume of requests. We removed the IIS limit so WSUS wouldn't crash which resolved the problem.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 41%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
@Anonymous , thank you for sharing this resolution with the community.
@Anonymous , based on the question, the error code 0x80244022 is similar to error 503 which means temporary overload (as also seen from PowerShell window output).
This seems to be a transient error caused by temporary overload of the api endpoint and not something on the local machine level. Can you please check if you are still facing this issue? I assume that it would have been resolved by now.
If you are still facing this issue, I would suggest opening a support ticket to investigate this issue further.