Error 0x80244022 is one of those Windows Update errors that looks alarming but is usually not a sign that Windows is broken. In most cases, it means something is temporarily blocking your PC from talking to Microsoft’s update servers — and the fix is simpler than the error code suggests.
This guide explains exactly what 0x80244022 means, every possible cause, and every proven fix — for home users, Microsoft Store errors, and IT administrators dealing with WSUS environments.
What Does 0x80244022 Mean?
Error 0x80244022 is Windows Update’s internal code for WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL — which maps directly to an HTTP 503 Service Unavailable response.
In plain language: your PC successfully reached Microsoft’s update servers — or your organization’s WSUS update server — but the server sent back a 503 response, meaning it was temporarily unable to handle the request.
The key point here is that your PC’s internet connection is working. The problem is on the server side — either the server is temporarily overloaded, undergoing maintenance, or something between your PC and the server is blocking or interfering with the connection.
This error is logged internally as WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL, the same code Windows Update uses for an HTTP 503 Service Unavailable response. Fdaytalk
You will typically see this error in:
Settings, Windows Update — when checking for or downloading updates. The Windows Update Troubleshooter — when it fails to connect. Microsoft Store — when downloading or updating apps. WSUS or Microsoft Intune logs — in enterprise environments.
Where Is It Appearing — Home PC or Enterprise?
Before picking a fix, identify where 0x80244022 is showing up. The cause and fix differ significantly between home PCs and managed enterprise environments.
Home PC — Windows Update or Microsoft Store
On a home or standard office PC, 0x80244022 most commonly means either Microsoft’s servers are temporarily unavailable, your proxy or firewall is blocking the connection, or your Windows Update cache has become corrupted.
Enterprise — WSUS or Intune
In an enterprise environment where Windows Update is managed through WSUS (Windows Server Update Services), Software Update Point (SUP), or Microsoft Intune, 0x80244022 almost always means the WSUS or SUP server is under heavy load, has a stopped app pool, is misconfigured, or has been decommissioned while clients still point to it.
0x80244022 is very common in WSUS/SUP environments and can also occur when Microsoft Update is temporarily busy or your client cannot reach it properly. WSUS/SUP under load or misconfigured — app pool recycling, low queue length, low private memory limit, app pool stopped — clients then see 503 and show 0x80244022.
Identify which scenario applies and start with the relevant section below.
Fix 1 — Check If Microsoft’s Servers Are Down
This fix rules out a server-side issue before any local troubleshooting, since 0x80244022 often appears in waves when Microsoft’s update or Store infrastructure has a regional outage. Check the Microsoft 365 Status page or search for recent reports of Windows Update or Microsoft Store outages. If an outage is confirmed, wait and retry later instead of changing any local settings.
Go to status.cloud.microsoft and look for any active incidents affecting Windows Update or Microsoft Store. You can also search “Windows Update down” or “Microsoft Store outage” to check community reports.
If an outage is confirmed, do not change any settings. Wait 30 to 60 minutes and retry. 0x80244022 during a server outage resolves itself once Microsoft restores service.
This step saves significant troubleshooting time — if the problem is on Microsoft’s end, no local fix will work until the server issue is resolved.
Fix 2 — Reset Microsoft Store Cache (Store Errors Only)
This fix applies when 0x80244022 shows up while installing or updating apps from the Microsoft Store, since it clears the Store’s cached license and connection data without touching installed apps.
Press Win + R, type wsreset.exe, and press Enter.
A blank Command Prompt window opens, runs for one to two minutes, closes on its own, and the Microsoft Store relaunches automatically. Try updating or installing the app again.
If wsreset does not fix it, go to Settings, Apps, Installed apps, find Microsoft Store in the list, click the three dots, select Advanced options, and click Repair. If repair does not work, click Reset.
Fix 3 — Run Windows Update Troubleshooter
Windows has a built-in tool that identifies and fixes the most common update connection problems automatically.
Windows 11:
Go to Settings, System, Troubleshoot, Other troubleshooters. Find Windows Update and click Run.
Windows 10:
Go to Settings, Update and Security, Troubleshoot, Additional troubleshooters. Select Windows Update and click Run the troubleshooter.
The troubleshooter checks for stopped services, incorrect registry settings, corrupted update cache, and firewall interference. Apply any recommended fixes and restart your PC before trying Windows Update again.
Fix 4 — Restart Windows Update Services
If the Windows Update service itself is stopped or in a stuck state, it will fail to connect to Microsoft’s servers regardless of network conditions.
Open Command Prompt as administrator and run these commands one by one:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
net start msiserver
net start bits
net start cryptSvc
net start wuauservAfter all services restart, go to Settings, Windows Update and click Check for updates.
Fix 5 — Clear the Windows Update Cache
A corrupted Software Distribution folder — where Windows stores downloaded update files — can cause 0x80244022 by feeding corrupted data into the connection process.
Open Command Prompt as administrator and run:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start msiserver
net start bits
net start cryptSvc
net start wuauservThis renames the corrupted folders — Windows creates fresh empty replacements and re-downloads whatever it needs. Go to Settings, Windows Update and click Check for updates.
Fix 6 — Check Your System Clock
This is one of the most frequently overlooked causes of 0x80244022.
System clock drift breaks the TLS handshake with the update server, which gets returned as a 503.
Windows Update communicates with Microsoft’s servers over HTTPS, which requires a valid TLS certificate handshake. If your PC’s clock is more than five minutes off from the actual current time, the TLS handshake fails — and Microsoft’s server returns this as a 503 Service Unavailable response.
Right-click the clock in the system tray and click Adjust date and time. Make sure Set time automatically is enabled and your time zone is correct. Click Sync now to force an immediate time sync.
After syncing, try Windows Update again.
Fix 7 — Check Proxy and VPN Settings
If you are connecting through a corporate proxy or VPN, the proxy configuration may be blocking requests to Windows Update servers.
Check proxy settings:
Go to Settings, Network and Internet, Proxy. If a manual proxy is configured, verify the address and port are correct. If you are on a home network and see a proxy configured that you did not set up, disable it.
Check VPN:
If you are connected to a VPN, try disconnecting temporarily and retrying Windows Update. Some VPN configurations route update traffic through corporate infrastructure where Windows Update is blocked or throttled.
Reset proxy settings via Command Prompt:
Open Command Prompt as administrator and run:
netsh winhttp reset proxyRestart and try Windows Update again.
Fix 8 — Temporarily Disable Firewall or Antivirus
Disable any third-party antivirus or firewall temporarily and retry the update. If it succeeds, add an exception for Windows Update and Microsoft Store traffic in the security software instead of leaving protection off.
Third-party security software — particularly those with aggressive network inspection features — can intercept and block Windows Update traffic in ways that produce 0x80244022. Right-click your antivirus icon in the system tray and temporarily disable real-time protection or network filtering. Try Windows Update immediately. If it succeeds, re-enable protection and add an exception for Windows Update rather than leaving protection disabled.
The Windows Update domains to whitelist if you need to add exceptions are: windowsupdate.microsoft.com, update.microsoft.com, download.windowsupdate.com, and dl.delivery.mp.microsoft.com.
Fix 9 — Reset Network Components
If other fixes have not worked, corrupted network stack settings may be preventing Windows from reaching the update servers.
Open Command Prompt as administrator and run:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renewRestart your computer after these commands complete. Do not run them over a remote desktop session — the network reset will disconnect you. Run them directly on the machine.
Fix 10 — Run DISM and SFC
Corrupted Windows system files can prevent the Windows Update client from functioning correctly, producing connection errors including 0x80244022.
Open Command Prompt as administrator and run:
DISM /Online /Cleanup-Image /RestoreHealthWait for this to complete — it can take 15 to 30 minutes. Then run:
sfc /scannowRestart after both complete and try Windows Update again.
If DISM returns a “source files not found” error, you can mount a Windows installation ISO and point DISM to it:
DISM /Online /Cleanup-Image /RestoreHealth /Source:X:\Sources\install.wim /LimitAccessReplace X: with the drive letter of your mounted ISO.
Fix 11 — Reset Windows Update Components via PowerShell
If none of the above fixes have resolved the error, a comprehensive Windows Update component reset addresses more deeply entrenched configuration issues.
Open PowerShell as administrator and run each of these commands in sequence:
powershell
Stop-Service -Name wuauserv, cryptSvc, bits, msiserver -Force
Remove-Item "C:\Windows\SoftwareDistribution" -Recurse -Force
Remove-Item "C:\Windows\System32\catroot2" -Recurse -Force
Start-Service -Name msiserver, bits, cryptSvc, wuauservAfter the reset completes, go to Settings, Windows Update and click Check for updates.
Enterprise Fix — WSUS and SUP Environments
If you are an IT administrator managing Windows updates through WSUS or Configuration Manager Software Update Point, 0x80244022 on client devices almost always means the WSUS server itself is the problem rather than the clients.
Check the WSUS App Pool in IIS
Open IIS Manager on the WSUS server. Go to Application Pools and look for WsusPool. If it shows Stopped, right-click and click Start. A stopped app pool causes all client connections to return 503.
Increase App Pool Private Memory Limit
A common WSUS issue is the WsusPool app pool hitting its private memory limit and restarting repeatedly under load. Right-click WsusPool, click Advanced Settings, and find Private Memory Limit (KB). Set it to 0 (unlimited) or increase it significantly — 4GB (4194304 KB) is a common recommendation.
Also increase the Queue Length from the default 1000 to 2000 under the same Advanced Settings. Click OK and restart the app pool.
Run WSUS Server Cleanup
A WSUS database that has not been cleaned in a long time accumulates declined updates, superseded updates, and orphaned content that slows the server significantly. In the WSUS console, go to Options, Server Cleanup Wizard and run a full cleanup. This can take hours on a neglected server but significantly improves performance and connection reliability afterward.
Verify Client WSUS Configuration
Run gpresult /h gpresult.html on an affected client to verify which WSUS server the client is pointed to. If the WSUS server address has changed — due to migration, decommissioning, or configuration change — clients still pointing to the old address will fail with 0x80244022.
Check SUP Connectivity from the Client
On an affected client, open a browser and navigate to http://[WSUS-Server-Name]:8530/simpleauthwebservice/simpleauth.asmx. A successful connection returns a valid XML response. An error or timeout confirms the WSUS server is not responding to client connections.
Quick Diagnostic — Which Fix to Try First
| Your Situation | Start With |
|---|---|
| Error just started today, multiple users affected | Fix 1 — Check Microsoft server status |
| Error in Microsoft Store only | Fix 2 — wsreset.exe |
| Home PC, error appeared after recent changes | Fix 3 — Windows Update Troubleshooter |
| Corporate PC, many users affected | Enterprise Fix — WSUS App Pool |
| PC clock shows wrong time | Fix 6 — Sync system clock |
| Recently installed third-party antivirus | Fix 8 — Temporarily disable |
| Error persists after all basic fixes | Fix 10 — DISM and SFC |
How 0x80244022 Connects to Recent Windows Updates
If you encountered 0x80244022 while trying to install recent Windows updates, understanding which updates were involved helps identify whether the issue is local or broader.
The July 2026 Patch Tuesday update KB5101650 saw higher than normal update server load on release day — July 14, 2026 — as millions of devices simultaneously attempted to download the 570-vulnerability fix package. Some users encountered 0x80244022 during the initial hours of the release simply due to Microsoft’s servers being under heavy load. Waiting and retrying resolved the issue.
The emergency KB5121767 released July 18 for affected Dell PCs similarly saw connection errors on initial release due to sudden demand from devices that had been blocked from the July update.
For KB5043080 — the checkpoint prerequisite update that all Windows 11 24H2 and 25H2 updates require — 0x80244022 errors during manual installation from the catalog are typically resolved by Fix 7 (proxy check) or Fix 9 (network reset) rather than indicating a missing prerequisite.
KB2267602 — Microsoft Defender’s daily security intelligence update — regularly produces 0x80244022 on networks with aggressive security monitoring. The daily frequency of Defender updates means any network-level interference that causes 0x80244022 will appear every day. Fix 7 and Fix 8 are the first stops for KB2267602 specifically.
Frequently Asked Questions
What does Windows Update error 0x80244022 mean?
Error 0x80244022 means WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL — an HTTP 503 Service Unavailable response from the update server. It means your PC reached the update server but the server returned a 503 response, indicating it was temporarily unable to handle the request. It is usually caused by a server outage, WSUS configuration issue, proxy interference, or corrupted Windows Update cache.
Is 0x80244022 a serious error?
In most cases, no. It is a connection error rather than a Windows corruption error. It does not indicate your Windows installation is damaged. The fixes range from waiting out a server outage to resetting the Windows Update cache, and most cases resolve without significant troubleshooting.
Why does 0x80244022 appear in waves with multiple users affected simultaneously?
When multiple users see 0x80244022 at the same time, it usually indicates a Microsoft server outage or a WSUS server issue affecting all clients at once. Check Microsoft’s service status page before troubleshooting individual devices — if the problem is server-side, local fixes will not work until the server issue is resolved.
How do I fix 0x80244022 on a PC managed by WSUS?
Check the WsusPool application pool in IIS Manager on the WSUS server — if it is stopped, start it. Increase the private memory limit for the app pool to prevent it from stopping under load. Run the WSUS Server Cleanup Wizard if the server has not been cleaned recently. Verify that client group policy points to the correct, active WSUS server address.
Can 0x80244022 appear in Microsoft Store?
Yes. Microsoft Store uses the same Windows Update infrastructure and can return 0x80244022 when the Store’s servers return a 503 response. For Store-specific errors, run wsreset.exe first — it clears the Store cache without affecting installed apps and resolves most Store 0x80244022 occurrences.
Does a wrong system clock cause 0x80244022?
Yes. If your PC’s clock is more than five minutes off from the actual current time, the TLS handshake with Microsoft’s update servers fails and the server returns a 503 response — logged as 0x80244022. Enabling automatic time synchronization in Settings resolves this specific cause.
Why does 0x80244022 appear every day with KB2267602?
KB2267602 is Microsoft Defender’s daily security intelligence update. If your network has a proxy, VPN, or firewall that interferes with Windows Update traffic, you will see 0x80244022 every day when Defender tries to update. Fix 7 (proxy check) and Fix 8 (antivirus exception) are the most relevant solutions for this pattern.
How long should I wait before troubleshooting if Microsoft’s servers are down?
Check the Microsoft service status page to confirm an outage. If confirmed, wait at least 30 to 60 minutes and retry. Server-side 503 responses typically resolve within an hour for planned maintenance and within a few hours for unplanned outages. Do not change local settings while a confirmed server outage is active.
