0x80244010
Microsoft Windows Update
Severity: ModerateWhat Does This Error Mean?
Windows Update error 0x80244010 means Windows Update was redirected too many times while trying to connect to Microsoft's servers and gave up. This is similar to a website sending you in circles — each page redirect takes you to another redirect and you never reach the actual content. This almost always points to a proxy server, network appliance, or misconfigured network settings that are intercepting and rerouting Windows Update traffic.
Affected Models
- Windows 10
- Windows 11
- Windows 8.1
Common Causes
- A proxy server is configured in Windows or on the network that is causing redirect loops
- Corporate or school network security software is intercepting and redirecting Windows Update connections
- Incorrect Windows proxy settings left over from a VPN or network tool installation
- A malware infection has modified proxy settings to redirect Windows Update traffic
- A DNS hijack or network appliance is intercepting Microsoft update server requests
How to Fix It
-
Remove proxy settings from Windows. Open Command Prompt as Administrator and type: netsh winhttp reset proxy — restart your PC and retry Windows Update.
This removes any proxy configuration from the Windows HTTP stack that Windows Update uses. This is the most common fix for this specific error.
-
Check Internet Options for proxy settings. Open the Start menu, search for 'Internet Options,' go to the Connections tab, click LAN Settings, and uncheck 'Use a proxy server for your LAN' if it is checked.
Some applications set proxy settings here that persist even after the app is uninstalled. Clearing this fixes redirect loops.
-
Check for malware that modifies proxy settings. Open Command Prompt as Administrator and type: netsh winhttp show proxy — if it shows a proxy server you did not set up, malware may have modified it. Run Malwarebytes to scan and clean.
Browser hijacking malware often sets proxy servers to intercept and redirect traffic, which interferes with Windows Update.
-
Reset the Windows network stack. In Administrator Command Prompt: netsh winsock reset — netsh int ip reset — restart the PC.
A complete reset of the network stack clears misconfigured settings that cause redirect problems.
-
Run the Windows Update Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters and click Run next to Windows Update.
The troubleshooter checks proxy and network settings that affect Windows Update and can reset them automatically.
When to Call a Professional
In business or school environments, this error is often caused by the network security configuration. Contact your IT department — they may need to whitelist Windows Update URLs in the proxy or content filter.
Frequently Asked Questions
What is an HTTP redirect loop?
When you visit a website, the server sometimes sends a 'redirect' response, pointing your browser to a different address. A redirect loop happens when Server A redirects you to Server B, and Server B redirects you back to Server A — over and over. Browsers and applications have a built-in limit on how many redirects they will follow before giving up. Windows Update hits that limit and reports this error when a proxy or network device creates such a loop.
I am on a home network with no proxy. Why am I getting this?
Some applications — especially VPN clients, parental control software, and internet security suites — set a proxy in Windows when they install. If you recently installed or uninstalled such software, it may have left proxy settings behind. Run: netsh winhttp show proxy in Command Prompt to see if a proxy is configured. If it shows a proxy address you do not recognize, removing it with netsh winhttp reset proxy should fix the error.
Could this be caused by my antivirus scanning HTTPS traffic?
Yes. Some antivirus products perform HTTPS inspection, which acts as a proxy for all secure web traffic including Windows Update. If the HTTPS inspection feature is malfunctioning, it can cause redirect errors. Check your antivirus settings for 'HTTPS scanning,' 'SSL inspection,' or 'web shield' features and try disabling them temporarily to test.