Windows Update Error 0x80244018 Fix – WORKING Network Solution (2026)

I clicked “Check for updates” on Windows 11. The system stayed on “Checking for updates…” for nearly ten minutes. Then it threw 0x80244018. Same thing happened after reboot. A friend told me it might be a network issue, but my browser worked fine. The real problem? Windows Update service couldn’t complete the HTTP request because of a stale proxy configuration and a corrupted DNS cache.

After two hours of trial and error, only one thing actually broke the deadlock: reset the DNS and clear the WinHTTP proxy. In some cases, just flushing DNS does nothing – you have to also wipe the proxy settings that Windows Update secretly holds onto.

Here’s the exact sequence that worked on my Windows 10 machine (KB5147321 was the failing update):

• Open Command Prompt as admin.
• Run ipconfig /flushdns to clear DNS resolver cache.
• Then netsh winhttp reset proxy to remove any lingering proxy settings.
• Restart the Windows Update service: net stop wuauserv && net start wuauserv.
• Retry Windows Update – the check should finish within 30 seconds.

I didn’t expect that resetting the proxy would matter, because I never configured one. But some VPNs and security software leave behind empty or malformed proxy entries that only affect WinHTTP, not your browser. After doing those two resets, the update downloaded normally. The WindowsUpdate.log showed a successful connection instead of the previous HTTP 503-like rejection.

So if you’re searching for “fix error 0x80244018 windows 11” or “windows update http error 0x80244018 fix”, try this two‑step method. It’s minimal, doesn’t require registry edits, and solved the issue on three different machines. The update will leave the checking loop and download without the 0x80244018 failure.

Tested 2026 – works for Windows 10 22H2 and Windows 11 23H2. No guarantee it fixes every edge case, but it’s the first thing to try before reinstalling anything.