How to fix Windows update error 0x80244011?

Error 0x80244011 means that a policy on your PC tells Windows Update to get updates from a company (WSUS) server, but the address of that server is missing. It is a settings problem, not a broken update or a bad connection. Check the update policy first, then clear the leftover setting or ask IT to finish it.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What Windows update error 0x80244011 means

Microsoft's list of Windows Update error codes names 0x80244011 WU_E_PT_SUS_SERVER_NOT_SET and describes it in one line: "WUServer policy value is missing in the registry". SUS stands for Software Update Services, the old name of WSUS, the server that companies and schools use to hand out Windows updates on their own network.

Two policy values work together. UseWUServer in the AU subkey switches Windows Update to an intranet server, and WUServer in the main WindowsUpdate key holds the address of that server. When the switch is on and the address is gone, Windows Update has nowhere to look, so it stops at once with 0x80244011. Nothing is downloaded, and nothing on your PC is damaged.

Why Windows update error 0x80244011 appears

The code has one technical cause, the missing WUServer value, but different stories lead to it. The table puts them in the order we see them on home and small office PCs, each with the fix that matches.

How to fix Windows update error 0x80244011

Fix 1 tells you in two minutes which case you have. Fixes 2 and 3 clear the half finished policy, one through Group Policy and one through the registry, and solve most home cases. Fix 4 stops a tool from putting it back. Fixes 5 and 6 are for the rare case where the policy is clean and updates still fail.

Fix 1. Check whether a WSUS policy without a server address is set

2 minutesNo riskEveryone, first. It takes two minutes and decides which fix you need.

The error name says exactly what Windows misses: the WUServer value. Reading the policy key shows whether UseWUServer is on and whether the address is really gone.

1. Press Win + S, type cmd, right-click Command Prompt and select Run as administrator.
2. Type reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /s and press Enter.
3. Look under the AU subkey for UseWUServer with the value 0x1.
4. Look under the main key for WUServer and WUStatusServer. A working setup has an address such as http://server:8530 there.
5. If UseWUServer is 0x1 and there is no WUServer line, you have found the cause of 0x80244011.
6. If Windows says it was unable to find the key, there is no update policy at all. Go to Fix 5.

reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /s

Fix 2. Set the intranet update service policy to Not Configured in Group Policy

5 minutesLow riskWindows 11 or 10 Pro, Education or Enterprise on a PC you own. Windows Home has no Group Policy Editor.

Microsoft says that with this policy Disabled or Not Configured, the update client connects directly to Windows Update on the internet. Setting it back removes the switch that points Windows at a missing server.

1. Press Win + R, type gpedit.msc and select OK.
2. Go to Computer Configuration > Administrative Templates > Windows Components > Windows Update. On Windows 11 the policy may sit in the subfolder Manage updates offered from Windows Server Update Service.
3. Double-click Specify intranet Microsoft update service location.
4. If it shows Enabled, select Not Configured and then OK.
5. Open Command Prompt as administrator, type gpupdate /force and press Enter.
6. Restart the PC, open Settings > Windows Update and select Check for updates.

More on the editor: Open the Local Group Policy Editor

Fix 3. Delete the leftover UseWUServer value in the registry

10 minutesRead the warningWindows Home, or any edition where Fix 2 did not remove the value. Only on a PC you own.

Without UseWUServer, Windows Update no longer looks for an intranet server, so the missing WUServer address stops mattering and the client goes straight to Microsoft.

1. Open Command Prompt as administrator, as in Fix 1.
2. Type reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v UseWUServer /f and press Enter.
3. Type net stop wuauserv and press Enter, then net start wuauserv and press Enter, to restart the Windows Update service.
4. Run the reg query from Fix 1 again and check that UseWUServer is gone.
5. Open Settings > Windows Update and select Check for updates.

reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v UseWUServer /f
net stop wuauserv
net start wuauserv

Fix 4. Undo the setting in the tool that blocked updates

10 minutesLow riskThe UseWUServer value comes back after Fix 2 or Fix 3, or you once used a tool to stop or delay Windows updates.

Some update blocking and privacy tools stop updates by pointing Windows at an intranet server that does not exist. While the tool runs or its task is scheduled, it can write the value again and bring 0x80244011 back.

1. Think back to any program you used to stop, pause or tweak Windows updates, or to change privacy settings in bulk.
2. Open that program and turn its Windows Update blocking off, or use its option to restore default settings.
3. If you no longer need it, remove it: press Win + I, open Apps > Installed apps, select the three dots next to it and Uninstall.
4. Restart the PC and run the reg query from Fix 1. If UseWUServer is still there, repeat Fix 3 once.
5. Check for updates in Settings > Windows Update.

Fix 5. Reset the Windows Update components

10 minutesLow riskThe policy is gone, but the same update still fails with 0x80244011.

Windows Update may still hold the download it planned from the missing server. Renaming the SoftwareDistribution and catroot2 folders drops that queue, so the next check starts fresh against Microsoft's servers.

1. Open Command Prompt as administrator. Type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Stop the update services. Type the commands below and press Enter after each one. If Windows says that other services depend on Cryptographic Services, it stops them too. A message that a service is not started is fine.

   net stop wuauserv
   net stop bits
   net stop cryptsvc

3. Delete the download queue files. This clears the list of downloads that the Background Intelligent Transfer Service keeps. If Windows says it cannot find the files, continue.

   del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

4. Rename the update cache folders. Renaming keeps a copy in case you need it; Windows creates new, empty folders when the services start again. If you get Access is denied, a service is still running: repeat the previous step.

   ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
   ren %systemroot%\System32\catroot2 catroot2.old

5. Start the services again. Type the commands below and press Enter after each one. The requested service has already been started is fine: Windows started it on its own.

   net start cryptsvc
   net start bits
   net start wuauserv

6. Restart and check for updates. Restart the PC. Then select Start > Settings > Windows Update > Check for updates. The first check can take longer than usual because everything is downloaded again.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Reset Windows Update components

Fix 6. Install the update by hand from the Microsoft Update Catalog

10 minutesLow riskYou need one update now, or the PC is managed and you are waiting for IT.

The catalog file comes through your browser and installs without asking the update server, so the missing WUServer value does not stop it. It does not clear the policy, so the next update fails again until Fix 2 or Fix 3 is done.

1. Check your Windows version. Press Windows key + R, type winver and press Enter. Note the version (for example 25H2) and the OS build.
2. Find the KB number. Open Settings > Windows Update. A failed or pending update is listed with its KB number; earlier ones are under Update history.
3. Check the processor type. Open Settings > System > About and look at System type: an x64-based PC needs the x64 file, an ARM-based PC (for example Snapdragon) needs the arm64 file.
4. Search the catalog. Open the Microsoft Update Catalog at catalog.update.microsoft.com in your browser, type the KB number (for example KB5124010) in the search box and press Enter.
5. Pick the right row. Find the row whose title names your Windows version and your processor type (x64-based or arm64-based) and select Download on that row.
6. Download every file listed. A window lists one or more .msu links. Download all of them into one empty folder, for example C:\packages. On Windows 11 24H2 and later the list can include earlier checkpoint updates that the new one needs.
7. Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.

These steps were written for Windows 11 24H2 and later; Windows 10 22H2. The full page with the other versions and what each result means: Install an update from the Microsoft Update Catalog

If the error 0x80244011 is still there

If the error did not go away, either the policy comes from a source you do not control, or the update client logged a second problem. The update log shows which one.

1. Open PowerShell as administrator, type Get-WindowsUpdateLog and press Enter. It writes WindowsUpdate.log to your desktop.
2. Open the file and search for 0x80244011. Note the time and the lines just before it.
3. If the lines mention a WSUS or intranet server, the policy is still active. Run the reg query from Fix 1 again.
4. If the policy is gone but gpresult /r in Command Prompt lists domain policies, the PC is still managed.

How to keep error 0x80244011 from coming back

Windows 10 left support on 14 October 2025, and only PCs in Extended Security Updates still get its security patches. Clearing the policy matters even more there, because a PC stuck on 0x80244011 receives none of them.

Frequently asked questions

What does error code 0x80244011 mean?

It means the WUServer policy value is missing in the registry. Microsoft names the code WU_E_PT_SUS_SERVER_NOT_SET. The PC has the UseWUServer policy turned on, which tells Windows Update to use a company WSUS server, but the address of that server is not written. Windows Update has no server to ask and stops. The update itself and your system files are fine. Clear the leftover policy with Fix 2 or Fix 3, or ask IT to add the address on a managed PC.

What does "Download error - 0x80244011" in Windows 11 mean?

It is how Windows 11 shows the code next to an update in Settings > Windows Update. The update appears in the list, but the download cannot start because Windows Update is set to fetch it from an intranet server whose address is missing. Selecting Retry gives the same result until the policy is cleared. Run the reg query from Fix 1 to confirm, then set the policy to Not Configured or delete the UseWUServer value.

What is 0x80244011(-2145107951)?

It is the same error written twice: once in hexadecimal and once as a signed decimal number. Some scripts, PowerShell modules and management tools print error codes this way. The decimal form -2145107951 and 0x80244011 are the same value, WU_E_PT_SUS_SERVER_NOT_SET. The fixes do not change: check the Windows Update policy key with reg query and clear the UseWUServer value on a PC you own.

Is 0x80244011 a network or internet problem?

No. Your internet connection can be perfect and the error still appears, because Windows Update never gets as far as connecting. It reads the policy, sees that it should use an intranet server, finds no address and stops. That is why resetting the router, changing DNS or turning off a VPN does not help with this code. Related codes such as 0x80244017 and 0x80244018 are connection answers from a server; 0x80244011 is a local setting.

I did not set any WSUS server. Why is my PC set to use one?

The most common reasons are a laptop that once belonged to a company or school and kept part of its policy, or a tool that blocked Windows updates by pointing them at an intranet server. Both write the policy into the registry without showing it in Settings. Run the reg query from Fix 1 to see the values. If nothing you know could have set them and they keep coming back, run a full scan with Microsoft Defender as well.

Can I just set UseWUServer to 0 instead of deleting it?

Microsoft documents only the value 1, which turns the intranet server on. Deleting the value is the cleaner choice, because Windows then behaves as if the policy was never set and connects to Windows Update directly. Setting it to 0 is used by some administrators, but we could not confirm it in Microsoft's documentation. Whichever you do, back up the key first with the registry backup procedure.

Does 0x80244011 belong to one update, such as KB5043145?

No. The code does not depend on the update. Any update that Windows Update tries to download fails with it, from a monthly cumulative update or a preview such as KB5043145 for Windows 11 22H2 to a driver or a Defender update. Clearing the policy fixes all of them at once. If you need one update right away, download it from the Microsoft Update Catalog as in Fix 6.

The error did not go away after the fixes. What now?

Run the reg query from Fix 1 once more. If UseWUServer is back, something writes it again: a blocking tool, a scheduled task of such a tool, or a domain or MDM policy. Fix 4 and the still broken section show how to tell them apart. If the policy is gone and you now see another code, it is a different problem with its own fix. If you see the same code on a managed PC, only IT can change the policy.

Will the Media Creation Tool or a reinstall fix 0x80244011?

An in place reinstall that keeps your files can bring Windows up to date, because it installs from its own media. It does not always remove the policy key, so the next update can fail with the same code. Clearing UseWUServer takes a few minutes and keeps everything else as it is. Keep the reinstall for the case where the policy is clean and Windows Update still fails with other errors.

What does "ошибка не исчезла" or "me da este error" mean for this code?

This page is in English, but the steps work on Windows in any language, because the commands and registry names stay the same. If the error did not go away ("ошибка не исчезла"), check whether the UseWUServer value came back, as in Fix 4. If you just got the error ("me da este error", "que significa esto"), it means the update policy points to a company server whose address is missing. Start with Fix 1.