Windows Update normally works in the background, but occasionally an update appears to take several hours to download, install, or complete after a restart. You may see messages such as:

• “Downloading – 0%”
• “Installing – 25%”
• “Installing – 100%”
• “Pending restart”
• “Working on updates”
• “Updates are underway”
• “Getting Windows ready”
• “Please don't turn off your computer”
• “Configuring Windows updates”
• “Cleaning up”
• “Restarting”
• “Undoing changes made to your computer”

A long update does not automatically mean Windows has frozen. Large cumulative or feature updates, slow storage, limited free disk space, component-store problems, pending servicing operations, third-party security software, driver problems, or corrupted Windows Update files can substantially increase installation time.

However, if the percentage has remained unchanged for several hours and there is little or no disk, CPU, or network activity, troubleshooting may be necessary.

This guide explains how to determine whether Windows Update is genuinely stuck and how to repair Windows Update safely.

Important: Avoid forcibly powering off a computer simply because an update appears slow. Interrupting Windows while it is actively modifying system files can result in an incomplete update, startup problems, or servicing corruption.

1. How Long Should Windows Update Normally Take?

There is no universal installation time.

The duration depends on:

• Type and size of update
• SSD versus mechanical HDD
• CPU performance
• Available RAM
• Internet connection
• Free disk space
• Number of pending updates
• System-file health
• Driver compatibility
• Antivirus/security software
• Whether Windows needs multiple restarts
• Previous failed updates

A normal monthly cumulative update on a modern SSD-based computer might complete relatively quickly, while a major Windows feature upgrade or an update on an older HDD-based system can take much longer.

Therefore, time alone should not determine whether an update has failed.

2. How to Determine Whether Windows Update Is Actually Stuck

Before interrupting anything, check whether the computer is still performing work.

If you are still on the Windows desktop, press:

Ctrl + Shift + Esc

to open Task Manager.

Check:

Processes → CPU / Disk / Network

Processes associated with Windows servicing can include:

• Windows Modules Installer Worker
• TiWorker.exe
• TrustedInstaller.exe
• Service Host processes
• Windows Update
• Delivery Optimization
• DISM
• Windows Installer

Continued CPU or disk activity can indicate that Windows is still processing the update.

If the computer is on the full-screen “Working on updates” stage, Task Manager normally cannot be accessed. In that situation, allowing additional time is generally safer than immediately cutting power.

3. Why Can Windows Update Take Several Hours?

Slow HDD

Mechanical hard drives can dramatically increase Windows servicing time because updates may involve thousands of small file operations.

An older PC with an HDD can therefore spend much longer at stages such as:

Installing 90%

or:

Working on updates 30%

than a similar PC equipped with an SSD.

If Windows itself is consistently slow, replacing an HDD with an SSD can provide a major performance improvement beyond Windows Update alone.

Insufficient Free Disk Space

Windows needs temporary storage while downloading, extracting, staging, installing, and sometimes rolling back updates.

Check:

File Explorer → This PC → Local Disk (C:)

If the system drive is almost full, free some space before retrying the update.

You can also use:

Settings → System → Storage → Temporary files

Remove unnecessary temporary files while avoiding deletion of anything you still require.

Corrupted Windows Update Cache

Windows normally stores downloaded update files under:

C:\Windows\SoftwareDistribution

A damaged or incomplete update download can cause Windows Update to repeatedly process the same files or remain stuck during installation.

Later in this guide, we explain how to rebuild this cache safely.

4. Restart the Computer — But Only When Appropriate

If Windows Update is running inside Settings and the computer remains usable, restarting Windows can clear pending servicing operations.

Use:

Start → Power → Restart

After Windows starts:

Settings → Windows Update → Check for updates

Do not repeatedly force shutdowns during the pre-boot or post-reboot update installation stage.

5. Check Windows Update History

Open:

Settings → Windows Update → Update history

Look for entries showing:

• Successfully installed
• Failed to install
• Installation error

Pay particular attention to the update's KB number, for example:

KBxxxxxxx

If one particular KB repeatedly fails, troubleshooting can be targeted specifically at that update.

6. Run the Windows Update Troubleshooter

On Windows 11, open:

Settings → System → Troubleshoot → Other troubleshooters

Find:

Windows Update

and run the available troubleshooting option.

Restart Windows afterward and check for updates again.

The exact troubleshooting interface can change between Windows releases, so menu wording may differ slightly.

7. Repair the Windows Component Store with DISM

Corruption in the Windows component store can interfere with Windows Update. Microsoft documents DISM as a primary method for repairing Windows servicing corruption.

Open Command Prompt as Administrator or Windows Terminal (Admin).

Run:

DISM /Online /Cleanup-Image /CheckHealth

For a more thorough check:

DISM /Online /Cleanup-Image /ScanHealth

Then repair detected corruption with:

DISM /Online /Cleanup-Image /RestoreHealth

Do not close the window simply because DISM appears to remain on the same percentage for a while. Some stages can take considerable time.

Microsoft notes that DISM can use Windows Update as the source for files needed to repair the Windows image. A separate repair source can also be specified when necessary.

After DISM completes successfully, restart Windows.

8. Run System File Checker

After repairing the component store, run System File Checker.

Open an elevated Command Prompt and execute:

sfc /scannow

SFC verifies protected Windows system files and attempts to replace incorrect or corrupted versions.

Possible results include:

No corruption detected

Windows Resource Protection did not find any integrity violations.

No protected-system-file corruption was detected.

Corruption repaired

Windows may report that corrupt files were found and successfully repaired.

Restart the PC and run Windows Update again.

Files could not be repaired

If SFC reports that some files could not be repaired, investigate the CBS log and component store rather than repeatedly running Windows Update.

9. Reset Windows Update Components

If Windows Update continues taking hours, repeatedly fails, or keeps processing the same update, rebuilding its local cache can help.

Microsoft troubleshooting documentation includes stopping Windows Update-related services and renaming the SoftwareDistribution and catroot2 directories as part of resetting Windows Update components.

Open Command Prompt as Administrator.

Stop the services:

net stop wuauserv
net stop bits
net stop cryptsvc

Rename the update folders:

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

Restart the services:

net start cryptsvc
net start bits
net start wuauserv

Restart the computer.

Then open:

Settings → Windows Update → Check for updates

Windows will recreate the required update-cache directories.

Will this uninstall existing Windows updates?

No. Renaming these cache directories does not normally uninstall updates that have already been installed.

Windows may need to rebuild update metadata and redownload pending update files.

10. Check Whether Windows Update Services Are Running

Press:

Windows + R

Enter:

services.msc

Review these services:

• Windows Update
• Background Intelligent Transfer Service (BITS)
• Cryptographic Services

Do not randomly change service startup types based on generic internet optimization guides. Windows servicing behavior varies by Windows version and configuration.

The goal is to identify services that are disabled by third-party utilities, optimization scripts, Group Policy, or previous troubleshooting.

11. Check Internet Connectivity

The downloading phase depends on internet connectivity.

Test:

ping www.microsoft.com

You can also test DNS:

nslookup www.microsoft.com

A PC can sometimes have general network connectivity while DNS, proxy, firewall, VPN, or filtering issues interfere with Microsoft services.

If Windows Update remains at Downloading 0%, investigate:

• Internet connection
• DNS
• VPN
• Proxy
• Firewall
• Web filtering
• Corporate network policies

If the update has already downloaded and Windows is showing Installing, raw internet speed may no longer be the primary bottleneck.

12. Temporarily Disconnect VPN Software

VPN clients can sometimes interfere with update downloads or Microsoft service connectivity.

Temporarily disconnect the VPN and retry Windows Update.

In business environments, however, verify company policy before disabling security or network software.

13. Check Proxy Configuration

Open an elevated Command Prompt:

netsh winhttp show proxy

If a proxy is configured unexpectedly, investigate it before changing anything.

A direct connection typically reports:

Direct access (no proxy server).

Do not reset a corporate proxy without first confirming that the organization does not require it.

14. Check Date and Time

Incorrect system time can interfere with secure communications.

Open:

Settings → Time & language → Date & time

Enable appropriate automatic time settings and verify:

• Date
• Time
• Time zone

Then retry Windows Update.

15. Check C: Drive Health and Free Space

Open Command Prompt as Administrator:

chkdsk C: /scan

This performs an online scan.

For repairs that require exclusive disk access, Windows may request a reboot.

Storage problems are especially important if the computer exhibits:

• Very high disk usage
• Frequent freezing
• File corruption
• Extremely slow startup
• Repeated update corruption
• Disk-related errors

If a storage device is suspected of failing, prioritize backing up important data.

16. Disconnect Unnecessary USB Devices

During major Windows upgrades, temporarily disconnect nonessential hardware such as:

• USB storage drives
• External hard drives
• Printers
• Scanners
• Card readers
• USB adapters
• Unnecessary docking peripherals

Keep essential input devices connected.

This can reduce the possibility of a problematic peripheral driver interfering with a feature upgrade.

17. Temporarily Investigate Third-Party Antivirus Interference

Security products install low-level services and file-system filters that can sometimes interfere with servicing.

Microsoft's troubleshooting guidance specifically includes checking for third-party interference when persistent update problems occur.

If appropriate, temporarily pause third-party antivirus protection and retry the update.

Do not leave the PC unnecessarily unprotected, and re-enable protection afterward.

In managed corporate environments, consult the administrator before changing endpoint-security settings.

18. Try a Clean Boot

If background software is suspected, perform a clean boot.

Press:

Windows + R

Enter:

msconfig

Under Services:

1. Select Hide all Microsoft services.
2. Disable nonessential third-party services.

Then review startup applications in Task Manager and disable unnecessary startup items temporarily.

Restart and retry Windows Update.

Do not disable Microsoft services indiscriminately.

19. Manually Install the Problem Update

If Windows Update repeatedly fails on one specific KB, identify the KB number from:

Settings → Windows Update → Update history

You can then search the official Microsoft Update Catalog for the corresponding package.

Microsoft Update Catalog

Choose the package that matches your:

• Windows version
• Architecture
• Update release

Common architectures include:

• x64
• ARM64

Manual installation can help distinguish a Windows Update download/detection problem from an underlying servicing problem.

Microsoft's troubleshooting guidance also recommends manually downloading an update package when normal Windows Update troubleshooting does not resolve the issue.

20. Do Not Repeatedly Delete Update Files

Deleting Windows Update cache files should be a troubleshooting procedure, not routine maintenance.

Repeatedly clearing the SoftwareDistribution folder can force Windows to redownload data and may actually increase update time.

Use the cache-reset procedure when there is evidence of a corrupted or stuck update.

21. Windows Update Stuck at 0%

If the update remains at Downloading 0%, concentrate on:

• Internet connectivity
• Windows Update service
• BITS
• DNS
• VPN
• Proxy configuration
• Firewall/security filtering
• Corrupted update cache

Try, in order:

1. Restart Windows.
2. Verify internet connectivity.
3. Run Windows Update troubleshooting.
4. Repair Windows with DISM.
5. Run SFC.
6. Reset Windows Update components.
7. Retry Windows Update.

22. Windows Update Stuck at 100%

An update showing 100% does not necessarily mean installation has completely finished.

Windows may still be:

• Verifying packages
• Committing component-store changes
• Cleaning old components
• Updating boot files
• Configuring drivers
• Preparing rollback information

If CPU or disk activity continues, allow additional time.

23. “Working on Updates” Taking Hours

If Windows displays:

Working on updates — Don't turn off your PC

avoid immediately forcing the machine off.

If the device is still showing signs of activity, allow it to continue.

A forced shutdown during servicing should generally be reserved for situations where the computer has remained completely unresponsive for an unusually long period and no safer recovery path is available.

24. What If Windows Is Stuck After Restart?

If Windows repeatedly cannot boot after an update, Windows Recovery Environment may become necessary.

You can access:

Troubleshoot → Advanced options

Depending on the Windows version and failure, recovery options may include:

• Startup Repair
• Uninstall Updates
• System Restore
• Startup Settings
• Command Prompt

Try less destructive recovery methods before considering a reset or clean installation.

25. “Undoing Changes Made to Your Computer”

This message normally means Windows could not successfully complete the update and is attempting to return the system to its previous state.

Do not interrupt the rollback unless absolutely necessary.

After Windows becomes usable again:

1. Check Windows Update history.
2. Identify the failed KB/error.
3. Run DISM.
4. Run SFC.
5. Reset Windows Update components if necessary.
6. Restart.
7. Retry the update.

26. “We Couldn't Complete the Updates”

A common message is:

We couldn't complete the updates. Undoing changes. Don't turn off your computer.

Possible causes include:

• Component-store corruption
• Damaged update files
• Insufficient disk space
• Driver incompatibility
• Security software interference
• Pending servicing operations
• File-system corruption

Microsoft documents component-store corruption as a cause of multiple Windows Update errors and recommends DISM and SFC for several such conditions.

27. Recommended Repair Sequence

For a Windows PC where updates consistently take hours or fail, use this sequence:

Step 1 — Restart Windows

Complete any pending restart.

Step 2 — Check disk space

Ensure the Windows drive has adequate working space.

Step 3 — Check Update History

Identify the failing KB and error code.

Step 4 — Run DISM

DISM /Online /Cleanup-Image /RestoreHealth

Step 5 — Run SFC

sfc /scannow

Step 6 — Restart

Restart Windows after repairs.

Step 7 — Retry Windows Update

Go to:

Settings → Windows Update → Check for updates

Step 8 — Reset Windows Update components if still stuck

net stop wuauserv
net stop bits
net stop cryptsvc

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

net start cryptsvc
net start bits
net start wuauserv

Restart again.

Step 9 — Try manual KB installation

Use Microsoft Update Catalog when one particular update continues failing.

Step 10 — Investigate deeper servicing problems

Review Windows servicing logs if the failure continues.

28. Windows Update Logs for Advanced Troubleshooting

IT administrators should avoid guessing when the same update repeatedly fails.

Important Windows servicing information can be found under:

C:\Windows\Logs\CBS\

A particularly important file is:

CBS.log

Microsoft documents CBS.log as a source for diagnosing servicing and component-store problems.

You can also generate a readable Windows Update log in PowerShell:

Get-WindowsUpdateLog

This can be useful when investigating update detection and installation behavior.

29. Should You Force Shutdown a Windows Update?

Not as the first troubleshooting step.

If Windows is clearly performing update operations, interrupting the process creates unnecessary risk.

A forced shutdown becomes a last-resort recovery action when the system has remained completely unresponsive for an exceptionally long period and normal interaction is impossible.

Even then, be prepared for Windows to:

• Continue updating after reboot
• Roll back the update
• Enter automatic repair
• Require Windows Recovery Environment

30. HDD Versus SSD Can Make a Huge Difference

Windows Update performs extensive disk operations.

A computer with an older mechanical HDD may experience:

• 100% disk utilization
• Slow update extraction
• Long restart times
• Slow cumulative update installation
• Slow component-store operations
• Long DISM/SFC scans

If an otherwise usable PC is still running Windows from an HDD, upgrading to an SSD can significantly improve overall Windows responsiveness and servicing performance.

31. Do Not Assume 100% Disk Usage Means Windows Is Frozen

During servicing, Windows may generate intense storage activity.

Processes such as Windows Modules Installer Worker may legitimately consume substantial CPU or disk resources while updates are being installed.

If resource usage is active and changing, Windows may still be working normally.

32. Feature Updates Can Take Longer Than Monthly Updates

There is an important difference between:

Quality/Cumulative Updates

These typically contain security, reliability, and servicing fixes.

Feature Updates

These can involve substantially more work, including operating-system migration, compatibility checks, driver processing, and post-install configuration.

Therefore, a major feature update can take considerably longer than a normal monthly cumulative update.

33. Avoid “Windows Update Fixer” Utilities from Unknown Websites

Be cautious with third-party programs claiming to:

• Repair Windows Update instantly
• Fix the registry automatically
• Remove Windows errors
• Optimize Windows services
• Install missing DLLs
• Download system files

Such utilities can modify Windows services, registry permissions, security settings, or system files.

Prefer built-in Microsoft tools such as:

• Windows troubleshooting
• DISM
• SFC
• Windows Recovery Environment
• Microsoft Update Catalog

34. Important Note for Windows 10 Users

Microsoft ended standard free support for Windows 10 on October 14, 2025. Microsoft states that Windows 10 PCs continue to work, but standard free Windows Update security fixes are no longer provided after that date.

Therefore, in 2026 and later, troubleshooting a Windows 10 computer should also include checking whether the device is eligible for Windows 11 or covered by an applicable extended-security arrangement.

This is especially important for business computers handling sensitive company or customer information.

35. When Should You Consider an In-Place Repair Installation?

If Windows Update continues failing even after:

• DISM
• SFC
• Update-component reset
• Disk checks
• Driver troubleshooting
• Manual update attempts

then Windows itself may have deeper servicing damage.

An in-place repair installation can reinstall Windows system components while retaining compatible applications, settings, and user data when the appropriate repair-install option is used.

Always maintain a current backup before performing major operating-system repair work.

Frequently Asked Questions

Q1. Is it normal for Windows Update to take several hours?

It can happen, particularly with major updates, older hardware, mechanical HDDs, multiple pending updates, or servicing problems. Several hours does not automatically prove that Windows has frozen.

Q2. Windows Update has been at 100% for an hour. Should I turn the PC off?

Usually not immediately. Windows can continue performing background servicing after the displayed percentage reaches 100%.

Q3. Why is Windows Update stuck at 0%?

Common causes include connectivity problems, BITS or Windows Update service issues, VPN/proxy interference, or damaged update-cache files.

Q4. Why does Windows Update take much longer on an HDD?

Updates involve large numbers of reads, writes, decompression operations, and small-file changes. Mechanical disks have much higher access latency than SSDs.

Q5. Can I safely delete the SoftwareDistribution folder?

For troubleshooting, it is generally preferable to rename it after stopping the appropriate services. Windows then creates a fresh directory. This should not be treated as routine maintenance.

Q6. Does resetting Windows Update remove installed updates?

Resetting the local Windows Update cache does not normally uninstall updates that are already installed.

Q7. What does DISM /RestoreHealth do?

DISM checks and repairs the Windows component store used for servicing. Microsoft recommends it for Windows Update corruption and installation problems.

Q8. What does SFC /scannow do?

SFC scans protected Windows system files and replaces incorrect or corrupted versions when repair files are available.

Q9. Should I run DISM or SFC first?

For suspected servicing/component-store corruption, a practical sequence is:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

This allows DISM to repair the component store that Windows servicing and SFC may depend upon.

Q10. Why does DISM itself appear stuck?

DISM can remain at a particular percentage for a considerable time while processing the component store. Do not terminate it merely because the displayed percentage temporarily stops changing.

Q11. Can antivirus software make Windows Update slow?

Third-party security software can occasionally interfere with servicing operations. Microsoft includes third-party interference among the areas to investigate when update problems persist.

Q12. Will faster internet make the installation phase faster?

It mainly helps with downloading. Once packages are downloaded, CPU performance, storage speed, component-store health, drivers, and the complexity of the update become more important.

Q13. Why does Windows say “Undoing changes”?

Windows detected that the update could not be completed and is attempting to restore the previous working configuration.

Q14. Can I manually download a Windows Update?

Yes. Individual updates can often be downloaded from the official Microsoft Update Catalog:

Microsoft Update Catalog

Make sure you select the correct update and architecture.

Q15. Can low disk space cause extremely slow Windows Updates?

Yes. Windows needs temporary working space for downloads, extraction, installation, component servicing, and rollback data.

Q16. Should I disable the Windows Update service permanently?

No. Permanently disabling Windows Update is generally not recommended because updates provide important security and reliability fixes for supported Windows versions.

Q17. Can a damaged SSD or HDD cause Windows Update problems?

Yes. Storage errors can lead to corrupted files, failed installations, freezes, and unusually long servicing operations.

Q18. Why does the PC restart several times during an update?

Some updates require different installation stages to occur before Windows starts, during boot, and after Windows loads. Multiple automatic restarts can therefore be normal.

Q19. What should I do if the same KB keeps failing?

Record the KB number and error code, run DISM and SFC, reset Windows Update components if necessary, restart, and then try the package manually from Microsoft Update Catalog.

Q20. What if none of these solutions fixes Windows Update?

Back up important data and investigate the Windows servicing logs. If the component store or operating system remains damaged, consider an in-place repair installation before resorting to a clean Windows installation.

Final Technical Checklist

When Windows Update is taking hours, do not immediately assume the PC has frozen.

First determine whether Windows is still processing data. Then work through the problem systematically:

Check activity → Restart safely → Check free space → Review Update History → Run DISM → Run SFC → Reset Windows Update components → Check disk/network/security software → Manually install the KB → Investigate logs → Consider repair installation.

Microsoft's current Windows troubleshooting guidance likewise emphasizes restarting pending operations, repairing the Windows image/component store, checking system-file corruption, and attempting manual update installation when required.

The most important rule is to avoid repeatedly forcing the computer off during active servicing. A Windows Update that is genuinely slow is usually easier to troubleshoot than a Windows installation damaged by an interrupted update.

 

#WindowsUpdate #Windows11 #Windows10 #WindowsUpdateStuck #WindowsUpdateFix #WindowsTroubleshooting #WindowsUpdateSlow #WindowsUpdateError #WindowsUpdateRepair #WindowsUpdateTakingHours #WindowsUpdateTakingForever #WindowsUpdateTroubleshooting #WindowsUpdate100Percent #WindowsUpdate0Percent #WindowsUpdateFailed #WindowsUpdateCache #SoftwareDistribution #Catroot2 #DISM #DISMRestoreHealth #SFC #SFCScannow #WindowsRepair #WindowsSystemFiles #WindowsComponentStore #WindowsUpdateComponents #WindowsUpdateService #BITS #MicrosoftUpdate #MicrosoftUpdateCatalog #WindowsUpdateKB #WindowsUpdateDownload #WindowsUpdateInstallation #WindowsUpdateRestart #WorkingOnUpdates #GettingWindowsReady #WindowsUpdateFrozen #WindowsUpdatePending #WindowsUpdateHistory #WindowsUpdateLogs #CBSLog #WindowsRecovery #WindowsRepairGuide #Windows11Troubleshooting #PCRepair #ComputerRepair #ITSupport #WindowsSupport #TechnicalSupport #BisonInfosolutions