Symptoms
- Checking for updates spinner runs with no result for 30+ minutes
- No error message appears, it simply never finishes
- Restarting the PC and trying again doesn't help
- May follow a long period without updating or a system issue
Likely causes
- CommonWindows Update service or related services stopped or malfunctioningIf a background service the updater depends on isn't running properly, the check can hang indefinitely.
- CommonCorrupted Windows Update cacheOld, corrupted update data can cause the check process to hang rather than fail with an error.
- PossibleNetwork connectivity issue specific to Microsoft's update serversA DNS or firewall issue can prevent the check from ever completing, without other internet use being affected.
- PossibleThird-party software or group policy blocking the update checkSome system utilities or corporate policies restrict Windows Update in a way that causes it to hang rather than clearly fail.
- Less commonCorrupted system filesDeeper file damage can also present as a check that never finishes.
What to do
- Restart the PC once and try checking for updates again, since a stuck service can sometimes clear on a reboot.
- Run the built-in Windows Update Troubleshooter from Settings > System > Troubleshoot > Other troubleshooters.
- Open Services (search 'services.msc'), find 'Windows Update,' and confirm it's running; if not, right-click and start it.
- Clear the update cache: in an administrator Command Prompt, run 'net stop wuauserv', rename 'C:\Windows\SoftwareDistribution' to 'SoftwareDistribution.old', then run 'net start wuauserv' and try checking again.
- Confirm general internet access works (browse a website) to rule out a broader connectivity problem, separate from an update-server-specific issue.
- Run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' to address possible underlying corruption.
- If on a work or school PC, check whether IT policies restrict update checks, since this may be intentional rather than a fault.
When to call a pro
If clearing the update cache and running DISM don't get the check to complete, a technician can dig into service configuration or group policy settings that might be blocking it.
Safety
Generally low risk
Generally low risk for a careful person. Stop if anything looks different from what this guide describes.