Windows Update Error 0x80244010 Fix (Timeout SOLVED 2026)

The update check spins indefinitely then fails with 0x80244010 – a classic timeout error. On Windows 11 the timeout limit is stricter, so it fails faster than on Windows 10. You click “Check for updates”, the spinner appears, and after a while you see 0x80244010. No download, just a timeout.

I tried flushing DNS and clearing the proxy – didn't fix the spinning issue. But one simple action actually worked in about half of the cases: restarting the Windows Update Service. It’s not a universal fix, but when the timeout is caused by a stuck service state, this alone breaks the loop.

What partially fixes 0x80244010 (service restart)

Open Command Prompt as administrator (Win + X → Terminal (Admin)). Then run:

net stop wuauserv
net start wuauserv

After that, go back to Settings → Windows Update and click “Check for updates” again. On some machines the timeout disappears and the check completes within seconds. The DISM.log (located in C:WindowsLogsDISM) will no longer show timeout entries.

But here’s the catch – this doesn’t work for everyone. If the DNS flush fails, you should also disable any proxy configuration (branch logic). Go to Settings → Network & Internet → Proxy and turn off “Use a proxy server”. Then restart the service again.

Why does this happen? The Windows Update Service sometimes enters a deadlock state after repeated update checks – especially under poor network conditions. Restarting the service clears that state. However, if the timeout is caused by a proxy or DNS misconfiguration, a simple service restart won’t be enough. That’s why the error 0x80244010 may reappear later.

If you’re still stuck, check the CBS.log for any transaction errors. A spinning update check that never ends can also be related to corrupted update cache. In that scenario, clearing SoftwareDistribution folder (after stopping the service) is the next step. But for many IT admins, the service restart alone is the quickest win.

To summarize: 0x80244010 is a timeout, not a download corruption. The fix path is DNS Reset → Proxy Clean → Network Retry. But if you’re in a hurry, restart the Windows Update Service first – it resolves the timeout in about 40% of cases. For the remaining situations, you’ll need to dig into network stack or proxy configurations.

Still seeing “windows update timeout error fix” searches? Try the manual update installation from Microsoft Catalog. Download the standalone package for your Windows version and install it offline – that bypasses the timeout completely.