Windows 11 Stuck on Checking for Updates

Windows 11 Stuck on Checking for Updates

You open Settings > Windows Update, click Check for updates, and the spinner just keeps turning. Not stuck at a percentage, not showing a download in progress — it never even gets that far. The page sits on “Checking for updates…” for minutes, sometimes indefinitely, without ever telling you whether anything is actually available.

This is a different failure than an update that starts downloading and then freezes partway through, and it’s different again from an update that never shows up as available in the first place while the check itself completes normally. This is specifically the check step — the part that’s supposed to just ask Microsoft’s servers what’s new — never resolving one way or the other.

Quick explanation: this guide covers how long is genuinely normal to wait, restarting the Windows Update service itself, a corrupted local update cache blocking the check before it can even start, another program’s background scan competing for the same resources, confirming your internet connection can actually reach Microsoft’s servers, and resetting the network stack as a deeper fallback.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

A spinner stuck on “Checking for updates…” for more than about ten minutes, with no CPU or network activity behind it, means the check itself has hung rather than genuinely still working. Restarting the Windows Update service is the fastest fix and clears the majority of cases on its own. If that doesn’t help, clearing the Windows Update cache resolves most of what’s left, since a corrupted local cache can block the check before it ever reaches Microsoft’s servers. Confirming your internet connection is genuinely working, and resetting the network stack if it isn’t, covers most of the remaining cases.

How Long the Check Should Actually Take

“Checking for updates” is meant to be a quick question-and-answer with Microsoft’s servers — asking what’s new, comparing it against what’s already installed, and reporting back. On a normal connection, that whole exchange usually finishes in well under a minute, occasionally a couple of minutes on a slower or busier network.
A spinner that’s still turning after five or ten minutes, with no other sign anything is happening, has crossed from “a bit slow” into “actually hung.” That’s a meaningfully different situation from a download that’s stuck at a percentage — there’s no percentage here to watch, no file transferring in the background, just a query that never came back with an answer.
Fixyfier’s Fix & Repair section includes a Windows Update Troubleshooter worth running once you’ve concluded the check is genuinely stuck rather than merely taking its time, since it checks for several of the causes covered in this guide automatically.

Restart the Windows Update Service

The check itself is carried out by the Windows Update service running in the background, and that service can get into a stuck or unresponsive state without anything on screen showing why. When that happens, clicking “Check for updates” again doesn’t help, because the same hung service is what handles the new request too.
Restarting the service from scratch — stopping it fully, then starting it again — clears this far more often than simply waiting longer or clicking the button repeatedly, since it gives the check a genuinely fresh process to run in rather than whatever state the old one was stuck in.
Fixyfier’s Windows Tools section includes an Open the Services Console shortcut for finding Windows Update in the services list and restarting it directly, without needing to open Command Prompt to do it.

Another Program Scanning in the Background

Windows Update’s check competes for the same disk and CPU resources as anything else running on the PC, and a heavy background task — a full antivirus scan, a large file sync, an indexing pass after a big folder change — can leave the check waiting behind it long enough that it appears hung even though it’s technically still queued to run.
This is more likely to be the cause on an older or lower-powered PC, or right after a lot of file activity, such as installing a large program or restoring from backup. Opening Task Manager’s Performance tab and checking whether disk or CPU usage is already pinned near 100 percent by something else is a quick way to rule this in or out before assuming the update check itself is broken.
If something else really is monopolizing the system, letting it finish, or pausing it temporarily, often lets the stalled check complete on its own without needing any of the steps further down this guide.

A Corrupted Local Update Cache Blocking the Check

It’s easy to assume a corrupted update cache only causes problems during a download, but damaged files or an inconsistent local database inside the SoftwareDistribution folder can also block the check step itself before it ever reaches out to Microsoft’s servers, since Windows Update reads its own local state as part of that process too.
Before clearing anything, it’s worth confirming the Windows Update service is actually running in the first place, since a service that’s stopped or stuck in a starting-but-never-started state produces the exact same symptom as a corrupted cache. A quick read-only status check from an elevated Command Prompt confirms which one you’re actually dealing with:
sc query wuauserv
Fixyfier’s Fix & Repair section includes a Clear Windows Update Cache tool that clears out exactly this kind of local corruption in one click, giving the check a clean local state to work from on the next attempt.
NordVPN
One Thing Worth Knowing

A VPN Sits Right in the Path This Check Depends On

Since the check itself depends on reaching a specific set of Microsoft servers, a VPN client that's misrouting or filtering traffic can occasionally be why it never resolves — worth briefly disconnecting to test. NordVPN is built to stay out of the way of routine Windows processes like this one, so reconnecting afterward shouldn't reintroduce the same problem.

Learn More About NordVPN

Confirm the Connection Can Actually Reach Microsoft’s Servers

General internet access and a working connection to Windows Update’s specific servers aren’t quite the same thing. It’s entirely possible to browse normally, stream video, and load email while a firewall rule, a DNS problem, or a misconfigured proxy quietly blocks just the connection the update check depends on, leaving the spinner with nothing to come back to.
A stale or broken DNS cache is a particularly easy cause to miss here, since it doesn’t produce an obvious “no internet” symptom anywhere else on the PC — it can single out specifically the addresses Windows Update needs to resolve, while every other site resolves fine.
Fixyfier’s Network & Connectivity section includes Flush DNS and Test Connection tools, useful for clearing a stale resolution issue and confirming the connection is genuinely healthy before assuming the problem is something deeper on the Windows Update side.

Reset the Network Stack as a Deeper Fallback

If the service restart, cache clear, and connectivity checks above all come back clean and the check is still hanging, a deeper misconfiguration in the network stack itself — rather than anything specific to Windows Update — can be the real cause. Windows Update relies on the same underlying network configuration as everything else, so damage there can single out this one connection in ways that are hard to predict.
Resetting the full network configuration rebuilds that stack from a clean, default state, which resolves inconsistencies that are otherwise difficult to track down to one specific setting. It’s a broader fix than anything targeted at Windows Update specifically, which is exactly why it’s worth trying only after the more targeted steps earlier in this guide haven’t helped.
The same Network & Connectivity tools already covered above for flushing DNS and testing the connection also include a full network reset option, worth using here as the broader version of the same fix rather than a separate tool.

Frequently Asked Questions

How is this different from an update that’s stuck downloading?

A stuck download or install has already confirmed an update exists and started working on it — you’ll see a percentage, and it’s that percentage that stops moving. This is a step earlier: Windows hasn’t even determined whether an update exists yet, so there’s no percentage or download to watch, just a spinner that never turns into an answer either way.

Is it safe to just keep waiting instead of restarting the service?

Waiting a bit longer is fine and costs nothing, but past roughly ten minutes with no other sign of activity, it’s very unlikely the check will suddenly complete on its own. Restarting the Windows Update service is a low-risk step that resolves this far more often than simply waiting it out, and it doesn’t touch anything else on the PC.

Could a pending restart from an earlier update be causing this?

It’s possible, if a previous update installed but never got the restart it needed — some leftover pending state can interfere with a fresh check starting cleanly. Restarting the PC fully, not just signing out and back in, settles that possibility and is worth doing early, before working through the service and cache steps in this guide.

Let Fixyfier Get the Check Moving Again

Fixyfier’s Windows Tools section puts Open the Services Console a click away for restarting the Windows Update service directly, its Fix & Repair section’s Clear Windows Update Cache clears out local corruption blocking the check, and its Network & Connectivity tools rule out or fix a connection issue underneath it all — between the three, enough to get a hung “Checking for updates” spinner moving again without guesswork.
Get Fixyfier from the Microsoft Store