How to Fix Windows Update Stuck on “Checking for Updates”

Windows Update is usually stuck on “Checking for updates” when the scan has stopped making progress, often because of a damaged update cache, blocked service, connectivity problem, or Windows system-file corruption. Restart Windows, check the connection, clock, and free space, then run the troubleshooter; if the scan still hangs, reset the update services and cache from an elevated Command Prompt and run DISM followed by SFC. These repairs do not remove personal files, although you should save open work before restarting or stopping services.

Is Windows Update actually stuck, or should you keep waiting?

A slow scan can look like a hang after a major Windows upgrade, a long period without updates, or a fresh installation. Windows may still be working if the Settings page changes, svchost.exe or Windows Update processes show CPU or disk activity, or network traffic appears periodically.

Checking for updates

The message appears in Windows Update while Windows searches for available updates. A genuine hang is more likely when the same screen remains unchanged for several hours, Task Manager shows little or no activity from Windows Update-related processes, and repeated attempts produce no update history entry or error code. Low free space can also make the scan or download process appear inactive.

Give the scan reasonable time if Windows was recently upgraded or the computer has not checked for updates in months. If there has been no visible progress after several hours under ordinary conditions, stop waiting and begin with the safe checks below. Do not repeatedly click “Check for updates” while the first scan is still running; it rarely helps and makes the state harder to assess.

Before you reset anything, check these Windows Update blockers

These steps apply to supported Windows 10 and Windows 11 systems. You need an Administrator account for service resets and system repairs. Save open work before restarting. The steps do not require a backup, but keeping a current backup is sensible before any major Windows repair.

1. Restart Windows from Start > Power > Restart. Do not use the power button unless Windows is completely unresponsive.
2. Confirm that the date, time, and time zone are correct. An incorrect clock can prevent secure connections to Microsoft update services.

Settings > Time & language > Date & time

3. Open a web page and, if possible, test another network. Disconnect a VPN temporarily. If the current connection is marked as metered, turn that setting off temporarily or connect through an unmetered network.

Settings > Network & internet > Wi-Fi or Ethernet > Metered connection

4. Check the system drive, normally C:, in File Explorer. Windows needs free space to stage downloads, unpack update files, and create temporary rollback data. Remove temporary files or unused applications if the drive is nearly full.
5. Check whether the computer belongs to a company or school. Group Policy, mobile-device management, WSUS, or an administrator-controlled update schedule can intentionally delay or redirect updates. On a managed computer, ask the organization’s administrator before changing update settings.

If the scan still does not move, continue with the built-in repair steps. Do not permanently disable Windows security features. A temporary security-software test belongs later in the process.

Reset Windows Update safely, then repair damaged system files

Use the fixes in this order. The troubleshooter is the least disruptive option. Resetting the cache is more direct and often fixes corrupted or incomplete update data. DISM repairs the Windows component store, and SFC repairs protected system files; run DISM before SFC.

Run the Windows Update troubleshooter

Run the troubleshooter from Settings with an Administrator account. On Windows 11, use the following path:

Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run

On Windows 10, use:

Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter

Apply any recommended repair, restart Windows if asked, and try Windows Update again. If the troubleshooter reports that it could not identify a problem, continue; that result does not rule out a damaged update cache.

Reset the update cache and services

These commands stop Windows update-related services and rename their working folders. They do not delete personal files. Close Settings and save your work before running them.

1. Open Start, type Command Prompt, right-click it, and select Run as administrator. Approve the User Account Control prompt.
2. Stop the services that may have files open.

net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver

These commands stop Windows Update (wuauserv), Background Intelligent Transfer Service (bits), Cryptographic Services (cryptsvc), and Windows Installer (msiserver).

3. Rename the update download and cryptographic catalog folders. Windows will create fresh folders when the services start again.

ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.old

Renaming preserves the old cached data while forcing Windows to create new SoftwareDistribution and catroot2 folders.

4. Start the services again.

net start wuauserv
net start bits
net start cryptsvc
net start msiserver

The expected result is a message that each service was stopped or started successfully. If a service says it was not started, or a folder cannot be renamed because it is in use, restart Windows and repeat the commands before trying more advanced changes. Leave the .old folders in place until updates work; remove them later only if needed.

Repair Windows component files

5. In the same elevated Command Prompt, run Deployment Image Servicing and Management (DISM). It can pause at a percentage for a while; let it finish.

DISM.exe /Online /Cleanup-Image /RestoreHealth

A successful run normally ends with a message that the restore operation completed successfully and the operation completed successfully. If DISM reports that source files could not be found, do not guess at registry changes. Use Microsoft’s supported Windows installation media as a repair source or proceed to repair-install support.

6. After DISM finishes successfully, run System File Checker.

sfc /scannow

The useful success messages are:

Windows Resource Protection did not find any integrity violations
Windows Resource Protection found corrupt files and successfully repaired them

Restart Windows after SFC completes, then check for updates again. If SFC says it could not repair some files, repeat it once after DISM and a restart; persistent errors require escalation.

How to confirm Windows Update is working again

After the restart, open Windows Update and select Check for updates. A working repair should produce a completed scan, an available update that begins downloading, or a clear message that the device is up to date. The first scan after a cache reset can take longer because Windows is rebuilding its local update data.

Windows 11: Settings > Windows Update
Windows 10: Settings > Update & Security > Windows Update

Install the offered update and restart when Windows requests it. Then check Update history and confirm that the expected quality update, feature update, or security intelligence update has an Installed status.

Windows 11: Settings > Windows Update > Update history
Windows 10: Settings > Update & Security > Windows Update > View update history

You can also verify the installed Windows version at Settings > System > About by checking Windows specifications, including the version and OS build. The exact build depends on your edition and update channel, so compare it with the update Windows offered rather than relying on a generic build number.

A completed scan, an Update history entry, or a clear up-to-date result confirms that Windows Update is functioning. If the same screen returns after another long period with no activity, record any error code before moving on.

What to do if it still hangs after the reset

Do not force the computer off while Windows is installing an update. A forced shutdown during installation can leave Windows unable to boot or roll back cleanly. If the screen only says that it is checking and the system is responsive, use the normal Restart command instead.

Third-party antivirus, firewall, system-tuning, and network-filtering software can interfere with update services. Temporarily pause or uninstall such software only according to its vendor’s instructions, restart, and test Windows Update. Re-enable protection immediately after the test if it is not the cause. Windows Security can provide protection while compatible third-party software is absent, but do not leave the computer unprotected longer than necessary.

Look for a specific error code in Windows Update history, Settings notifications, or Event Viewer. Open Event Viewer by searching for it, then check Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational. An error code is more useful than repeatedly running the same reset because it can point to a policy, driver, storage, connectivity, or servicing problem.

If DISM cannot repair the component store, SFC repeatedly reports unrepaired files, or updates still hang after the cache reset, use an in-place repair install for the same Windows edition and language. Start Windows installation media from within Windows, choose the option to keep personal files and apps, and follow the installer’s compatibility checks. Read each screen carefully. Do not boot from the media and choose a clean installation unless you intend to erase the system.

Contact Microsoft Support or your organization’s IT administrator when the PC is managed, the repair install is blocked, Windows cannot boot normally, or the update error points to licensing, activation, or hardware failure. Avoid random registry cleaners and scripts that delete protected folders or unregister system components; they can turn a repairable update problem into a broader Windows failure.

Conclusion

Restart first, check the connection, clock, and free space, then run the troubleshooter. If Windows Update still hangs, reset the services and cache from an elevated Command Prompt, run DISM followed by SFC, and verify the result in Update history. Use an in-place repair install or contact Microsoft or organizational support when those repairs fail.

Frequently Asked Questions

Will resetting Windows Update delete my personal files?

No. Renaming `SoftwareDistribution` and `catroot2` resets cached update data and service catalogs, not your documents, photos, applications, or personal settings. Save your work because the commands stop services and you must restart Windows.

How long should Windows Update stay on “Checking for updates”?

There is no single time for every PC. A scan can take longer after a major upgrade or a long period without updates. If several hours pass with no screen change, disk activity, network activity, or Update history entry, treat it as stuck and begin the safe checks.

Should I run SFC before DISM?

No. Run DISM first, then SFC. DISM repairs the Windows component store that SFC uses as a source for replacing damaged protected files.

Can I delete the `.old` update folders immediately?

Leave them until Windows Update works and you have restarted successfully. After that, Windows normally continues using the newly created folders. To reclaim space, stop the related services again before removing the old folders; they are not personal files.