Windows Update is responsible for downloading and installing security patches, cumulative updates, servicing updates, drivers, Microsoft Defender updates, and feature improvements. Sometimes Windows Update starts normally but remains at:

Downloading – 0%

even though the computer has a working internet connection.

The problem may disappear after several minutes, but if the percentage remains at 0% for an unusually long period, Windows Update may be unable to download, verify, stage, or process the update.

Microsoft identifies restart requirements, internet connectivity, insufficient disk space, Windows Update service problems, incomplete updates, and corruption in Windows Update files among the possible causes of update problems.

This guide explains how to troubleshoot Windows Update stuck at 0% on Windows 11 and Windows 10, starting with safe basic checks and progressing to advanced Windows Update component repairs.

What Does "Windows Update Stuck at 0%" Mean?

Normally, Windows Update follows several stages:

Check for updates → Download → Verify → Install → Restart → Complete

If the system displays:

Downloading – 0%

it does not necessarily mean that absolutely nothing is happening.

Windows may initially be:

• Checking update metadata
• Preparing the download
• Checking prerequisites
• Verifying existing packages
• Evaluating dependencies
• Checking available storage
• Preparing the component store
• Contacting Microsoft Update servers
• Waiting for another servicing operation

Therefore, a temporary 0% reading is not automatically a fault.

However, if Windows remains at 0% for a long period and there is no meaningful network or update activity, troubleshooting is appropriate.

Common Symptoms

Users experiencing this problem may notice:

• Windows Update remains at "Downloading 0%."
• Multiple updates remain at 0%.
• "Checking for updates" takes indefinitely.
• Updates show "Pending download."
• Updates repeatedly retry.
• The download starts after reboot but becomes stuck again.
• Windows Update displays "Something went wrong."
• A cumulative update refuses to download.
• Windows Update downloads but installation does not begin.
• Microsoft Defender updates also fail.
• Windows Update displays an error code.
• The computer repeatedly asks to retry the update.

Common Causes of Windows Update Stuck at 0%

1. Temporary Windows Update Problem

Windows Update or one of its supporting services may temporarily stop responding.

A simple restart can clear pending operations and restart the servicing environment.

2. Internet Connectivity Problem

Windows Update requires reliable access to Microsoft's update infrastructure.

A connection can appear "Connected" while still having problems involving:

• DNS resolution
• Packet loss
• Proxy configuration
• VPN connectivity
• Firewall filtering
• Gateway problems
• ISP connectivity
• Restricted corporate networks

Test normal internet connectivity before performing advanced Windows repairs.

3. Windows Update Service Problem

The Windows Update service (wuauserv) is a core part of the update process.

If the service is disabled, incorrectly configured, or malfunctioning, updates may not download normally.

4. BITS Service Problem

The Background Intelligent Transfer Service (BITS) is used by Windows components to transfer data in the background.

Problems with BITS can interfere with update downloads.

5. Corrupted SoftwareDistribution Folder

Windows stores temporary Windows Update information under:

C:\Windows\SoftwareDistribution

Corruption or incomplete downloads in this location can prevent subsequent updates from downloading correctly.

Resetting this update cache is one of the most useful troubleshooting procedures for persistent Windows Update problems.

6. Corrupted Catroot2 Data

Windows also uses:

C:\Windows\System32\catroot2

during update processing and cryptographic verification.

Problems in the update component data can contribute to Windows Update failures.

7. Insufficient Disk Space

Windows needs free disk space not only for the downloaded update but also for temporary files, extraction, servicing operations, rollback data, and installation.

Microsoft specifically recommends checking available disk space when Windows Update becomes stuck.

Check:

Settings → System → Storage

Pay particular attention to free space on the Windows system drive, normally C:.

8. System File or Component Store Corruption

Windows Update depends on the Windows servicing/component store.

If these files become corrupted, updates may fail during downloading, staging, or installation.

Microsoft documents DISM and System File Checker as tools for repairing Windows servicing corruption.

9. VPN or Proxy Configuration

VPNs and proxy servers can sometimes interfere with communication between Windows and Microsoft's update servers.

This is particularly relevant on:

• Corporate networks
• Managed PCs
• RDP environments
• Proxy-based networks
• Firewall-controlled offices

10. Third-Party Security Software

Some endpoint security, firewall, web-filtering, or antivirus products may interfere with Windows Update traffic or servicing operations.

Do not permanently disable security software as a troubleshooting method.

If testing requires temporarily disabling a third-party security product, restore protection immediately afterward.

How to Fix Windows Update Stuck at 0%

Follow these methods approximately in order.

Method 1: Wait Before Assuming Windows Update Is Frozen

If Windows Update has only recently reached 0%, allow some time.

Large cumulative or feature updates can spend considerable time preparing before the displayed download percentage changes.

This is particularly common on:

• Older computers
• PCs using HDDs instead of SSDs
• Systems with low RAM
• Slow internet connections
• Machines that have missed many previous updates
• Systems undergoing servicing operations

If the percentage eventually increases, no repair may be necessary.

Method 2: Restart Windows

Restart the computer rather than simply shutting it down and switching it back on.

Go to:

Start → Power → Restart

After Windows loads:

Settings → Windows Update → Check for updates

Microsoft lists restarting the device among the standard troubleshooting steps for stuck updates.

Method 3: Check Internet Connectivity

Open several websites and verify that internet connectivity is stable.

You can also open Command Prompt and test connectivity:

ping 8.8.8.8

Then test DNS resolution:

ping www.microsoft.com

If the IP address responds but domain names do not, investigate DNS configuration.

Also try restarting:

• Router
• Firewall
• Modem
• Wi-Fi access point

where appropriate.

Method 4: Disconnect VPN Temporarily

If you are connected through a VPN, disconnect it temporarily and check Windows Update again.

Some VPN configurations can alter DNS, routing, filtering, or proxy behavior and prevent normal communication with update infrastructure.

Reconnect the VPN after testing.

Method 5: Check Date and Time

Incorrect system time can cause secure communication and certificate-related problems.

Open:

Settings → Time & language → Date & time

Enable, where appropriate:

Set time automatically

and confirm the correct time zone.

Method 6: Check Available Disk Space

Open:

File Explorer → This PC

Check free space on the C: drive.

Microsoft's Windows Update guidance specifically recommends ensuring adequate disk space for updates.

You can remove unnecessary temporary files from:

Settings → System → Storage → Temporary files

Be careful when selecting categories containing personal or required files.

Method 7: Run the Windows Update Troubleshooter

On current Windows 11 systems, Microsoft recommends starting with the automated Windows Update troubleshooter available through Get Help. Windows also exposes troubleshooting options through Settings.

Try:

Settings → System → Troubleshoot → Other troubleshooters

Find:

Windows Update

and run the troubleshooter where available.

Restart Windows afterward and check for updates again.

Method 8: Check Windows Update Services

Press:

Windows + R

Type:

services.msc

Press Enter.

Look for relevant services, particularly:

• Windows Update
• Background Intelligent Transfer Service
• Cryptographic Services

If a required service has been deliberately disabled, Windows Update may fail.

Do not randomly change service startup types on managed corporate systems because Group Policy or endpoint-management software may control them.

Method 9: Clear the Windows Update Download Cache

A damaged Windows Update cache is a common cause of stuck downloads.

Microsoft's troubleshooting guidance includes stopping Windows Update, clearing the contents of SoftwareDistribution, and starting Windows Update again for certain update problems.

A safer advanced approach is to rename the cache rather than permanently deleting it.

Open Command Prompt as Administrator.

Run:

net stop wuauserv

net stop bits

Then rename the folder:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

Restart the services:

net start bits

net start wuauserv

Restart Windows.

Then open:

Settings → Windows Update → Check for updates

Windows can recreate the required update cache.

Method 10: Completely Reset Windows Update Components

If clearing SoftwareDistribution alone does not solve the problem, reset the main update cache and cryptographic catalog cache.

Open Command Prompt as Administrator and run:

net stop wuauserv

net stop bits

net stop cryptSvc

Then:

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.

Microsoft documents this Windows Update component reset sequence as a troubleshooting method for persistent update errors.

Important

Do not delete or modify unrelated folders inside C:\Windows.

The folders above are specifically associated with Windows servicing/update operations.

Method 11: Repair Windows with DISM

If Windows Update components repeatedly become corrupted or updates continue failing, check the Windows component store.

Open Command Prompt as Administrator.

Run:

DISM /Online /Cleanup-Image /ScanHealth

You can also check whether corruption has already been flagged:

DISM /Online /Cleanup-Image /CheckHealth

To perform a repair, run:

DISM /Online /Cleanup-Image /RestoreHealth

Microsoft documents /RestoreHealth as the repair operation for an online Windows image. By default, the repair process can use Windows Update as a source for required repair files.

Allow DISM to finish.

Do not close Command Prompt merely because the percentage appears to remain unchanged for some time.

Method 12: Run System File Checker

After DISM completes successfully, run:

sfc /scannow

System File Checker scans protected Windows system files and attempts to repair corrupted versions.

Microsoft's Windows Update corruption guidance recommends running SFC after DISM and then attempting Windows Update again.

When SFC finishes, restart Windows.

Then check:

Settings → Windows Update → Check for updates

Recommended Advanced Repair Sequence

For persistent Windows Update corruption, a practical sequence is:

DISM /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

Restart Windows and try Windows Update again.

If the problem remains, reset the Windows Update cache/components and retest.

Method 13: Check for a Metered Connection

Windows may restrict some update activity on a metered network.

Open:

Settings → Network & internet

Select the active Wi-Fi or Ethernet connection and check:

Metered connection

If the network should not be metered, disable the option and retry Windows Update.

Do not change this setting on a limited-data connection without considering bandwidth usage.

Method 14: Temporarily Test Without Third-Party Antivirus or Firewall

Security products sometimes filter Windows Update connections or interfere with update files.

If troubleshooting points toward a third-party antivirus or firewall, temporarily pause its protection according to the vendor's instructions and test Windows Update.

Microsoft includes temporary antivirus/firewall testing among troubleshooting suggestions for certain Windows Update failures.

Important: Re-enable protection immediately after the test.

Do not permanently operate a system without security protection.

Method 15: Check Proxy Configuration

Press:

Windows + R

Type:

inetcpl.cpl

and review proxy-related LAN settings if applicable.

You can also inspect the WinHTTP proxy from an elevated Command Prompt:

netsh winhttp show proxy

If the machine should connect directly and an unexpected proxy is configured, investigate before changing it—especially on domain-managed corporate systems.

Method 16: Try a Different Network

If possible, temporarily connect the computer to another reliable network.

For example:

• Another broadband connection
• Another office connection
• Mobile hotspot for testing

If Windows Update immediately begins downloading, the original network may have:

• DNS issues
• Proxy restrictions
• Firewall filtering
• Routing problems
• ISP problems

This can help distinguish a Windows problem from a network problem.

Method 17: Check the Windows Update Error Code

Sometimes Windows eventually displays an error instead of remaining at 0%.

Common Windows Update codes include:

0x8007000d – Windows Update file/cache corruption can be involved.

0x800705b4 – Update operation took too long or was interrupted.

0x80240034 – Incomplete update or connectivity-related update problem.

0x800f0922 – Installation can fail due to space or servicing-related problems.

0x80070005 – Access/permission-related error.

0x80070002 – Required update files may be missing or installation failed.

0x80070422 – Windows Update service may be disabled or unavailable.

0x80073712 – Windows servicing/component files may be damaged or missing.

The exact repair should be based on the specific error rather than assuming every code has the same cause. Microsoft maintains troubleshooting guidance for Windows Update and upgrade error codes.

Method 18: Manually Install the Specific KB Update

If only one particular cumulative update is failing, identify its KB number.

For example:

KB50xxxxx

Search for the KB in the official Microsoft Update Catalog and obtain the package appropriate for the installed Windows version and architecture.

Manual installation can help determine whether the problem affects the general Windows Update download mechanism or the update package itself.

Method 19: Disconnect Unnecessary USB Devices

For major feature upgrades, temporarily disconnect unnecessary hardware such as:

• External hard drives
• USB storage devices
• Printers
• Scanners
• Docking devices
• Unnecessary adapters

Keep essential input devices connected.

This is more relevant when an update downloads successfully but hangs or fails during installation.

Method 20: Perform a Clean Boot

Third-party startup software or services can interfere with servicing.

A clean boot starts Windows with a reduced set of non-Microsoft startup components and can help determine whether third-party software is causing the problem.

Use clean boot primarily as a diagnostic procedure rather than as a permanent configuration.

Method 21: Check Group Policy in Business Environments

On domain-connected, managed, RDS, or business computers, Windows Update behavior may be controlled by:

• Group Policy
• WSUS
• Microsoft Intune
• RMM software
• Endpoint security
• Update management products

In such environments, do not assume the PC should directly contact Microsoft's public Windows Update service.

Check the organization's update-management configuration before resetting policies.

Windows Server Considerations

For Windows Server environments, especially production servers, avoid aggressively resetting update components without understanding the server's patch-management configuration.

Check whether updates are managed through:

• WSUS
• Group Policy
• RMM software
• Microsoft update-management services
• Third-party patch management

For servers running business-critical workloads, schedule troubleshooting during a maintenance window.

Windows 10 Important Support Note

Microsoft states that general support for Windows 10 ended on October 14, 2025. Windows 10 PCs can continue operating, but standard free security updates and technical support are no longer provided in the normal manner. Eligible systems should be evaluated for Windows 11 or an applicable supported servicing option.

Therefore, if a Windows 10 machine appears to be "not receiving updates," first confirm whether the installed edition and servicing arrangement are still entitled to the expected updates.

What Not to Do

Avoid these potentially harmful troubleshooting practices:

• Do not randomly delete files from C:\Windows.
• Do not delete the WinSxS folder.
• Do not permanently disable Windows Update.
• Do not permanently disable antivirus protection.
• Do not download unknown "Windows Update repair tools."
• Do not install update packages from untrusted websites.
• Do not randomly modify registry entries found in old internet tutorials.
• Do not reset Group Policy on a company-managed computer without authorization.
• Do not force shutdown while Windows displays an active update installation warning unless the system is genuinely unrecoverable.

Quick Troubleshooting Checklist

For most Windows Update stuck-at-0% problems, try this order:

1. Wait several minutes.
2. Restart Windows.
3. Verify internet connectivity.
4. Check free disk space.
5. Disconnect VPN/proxy temporarily if appropriate.
6. Run Windows Update Troubleshooter.
7. Verify Windows Update and BITS services.
8. Reset the SoftwareDistribution cache.
9. Reset Windows Update components.
10. Run DISM RestoreHealth.
11. Run SFC /scannow.
12. Restart and check for updates again.
13. Investigate the exact Windows Update error code.
14. Manually install the affected KB if appropriate.
15. Consider a repair installation if servicing corruption cannot otherwise be resolved.

Frequently Asked Questions (FAQ)

1. Why is Windows Update stuck at 0%?

Common causes include temporary servicing delays, network problems, insufficient disk space, a malfunctioning Windows Update service, corrupted update cache files, or Windows component-store corruption.

2. Is Windows Update really frozen when it shows 0%?

Not necessarily.

Windows may be preparing, verifying, checking prerequisites, or processing update metadata before the visible download percentage increases.

Wait for a reasonable period before resetting anything.

3. Can I restart my PC if Windows Update is stuck at "Downloading 0%"?

Generally, yes, if Windows is simply displaying Downloading 0% inside Settings.

A normal restart is one of Microsoft's recommended troubleshooting steps for stuck downloads.

This is different from forcibly powering off a computer while Windows is actively installing updates during startup or shutdown.

4. What is the SoftwareDistribution folder?

C:\Windows\SoftwareDistribution

is used by Windows Update for update-related data, including downloaded content and update information.

Renaming or clearing its update cache after stopping the appropriate services can resolve some update failures.

5. Is it safe to delete SoftwareDistribution?

Windows can recreate its update-cache contents.

However, stop the relevant update services first, and renaming the folder to SoftwareDistribution.old is often preferable during troubleshooting because it preserves the old contents temporarily.

6. What is the Catroot2 folder?

C:\Windows\System32\catroot2

contains data used by Windows cryptographic and update-processing components.

Resetting it is an advanced troubleshooting step and should not be confused with deleting arbitrary Windows system folders.

7. What command resets Windows Update components?

Microsoft documents a reset approach that stops Windows Update-related services, renames SoftwareDistribution and catroot2, and starts the services again.

Typical commands include:

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 Windows afterward.

8. What does DISM /RestoreHealth do?

DISM /Online /Cleanup-Image /RestoreHealth

checks and repairs corruption affecting the Windows component store used for servicing and system repair. Microsoft specifically documents DISM for Windows Update corruption and installation failures.

9. Should I run DISM or SFC first?

When troubleshooting component-store corruption affecting Windows Update, Microsoft's documented repair procedure uses:

DISM.exe /Online /Cleanup-image /Restorehealth

followed by:

sfc /scannow

and then Windows Update again.

10. Can antivirus software block Windows Update?

Third-party antivirus, firewall, endpoint-security, or web-filtering software can sometimes interfere with update communication or installation.

Temporary testing may be useful, but security protection should be restored immediately afterward.

11. Can a VPN cause Windows Update to remain at 0%?

Yes, depending on how the VPN handles routing, DNS, filtering, or proxy configuration.

Temporarily disconnecting the VPN is a useful diagnostic test.

12. Can low disk space stop Windows Update?

Yes.

Windows requires space for downloading, extracting, staging, installing, and potentially rolling back updates. Microsoft specifically recommends checking free disk space when updates are stuck.

13. Why does Windows Update return to 0% after restarting?

The previous download may have been discarded, the update cache may have been rebuilt, or Windows may be starting another download/verification cycle.

If this repeatedly happens, investigate the update cache, network, servicing components, and the exact error code.

14. Why does Windows Update work on another internet connection?

This strongly suggests the original connection may have a DNS, proxy, firewall, routing, filtering, or ISP-related issue.

It does not prove the Windows installation is completely healthy, but it provides an important troubleshooting clue.

15. What if DISM is also stuck?

DISM can remain at the same displayed percentage for a considerable time while processing the component store.

Avoid terminating it prematurely.

If DISM eventually produces an error, record the complete error code and troubleshoot that specific failure.

16. What if DISM says source files could not be found?

DISM may require an appropriate Windows repair source if it cannot obtain the required repair content automatically.

Microsoft supports specifying a suitable repair source with the /Source option.

The source should correspond appropriately to the Windows installation being repaired.

17. Can I manually download a Windows update?

Yes.

Individual Windows KB packages can often be obtained from Microsoft's official Update Catalog.

Always verify the KB number, Windows version, edition requirements, and architecture before installing a package manually.

18. Will resetting Windows Update delete personal files?

Resetting the Windows Update cache using the procedures described above does not normally delete documents, photographs, desktop files, or other personal data.

Nevertheless, important data should always be backed up before performing advanced operating-system repairs.

19. What if Windows Update still does not work after DISM and SFC?

Further investigation may include:

• Windows Update logs
• Event Viewer
• Specific update error codes
• Group Policy
• WSUS configuration
• Proxy configuration
• Security software
• Component-store health
• Manual KB installation
• In-place repair installation

Avoid jumping directly to a clean Windows installation unless less destructive repair options have been evaluated.

20. Does this guide apply to Windows 11 and Windows 10?

Most underlying troubleshooting concepts apply to both Windows 11 and Windows 10, although menu locations and support status differ.

As of 2026, Windows 10's normal support lifecycle is an especially important consideration when diagnosing missing updates.

Conclusion

Windows Update stuck at 0% is usually caused by a temporary update-service problem, connectivity issue, insufficient storage, damaged Windows Update cache, or corruption in Windows servicing components.

Start with simple fixes such as restarting the PC, checking internet connectivity and disk space, and running the Windows Update troubleshooter. If the problem persists, reset the Windows Update cache and components, then use DISM and System File Checker to repair Windows.

For business computers, servers, RDS environments, and domain-managed systems, investigate Group Policy, WSUS, proxy, firewall, endpoint-management, and patch-management configuration before making major changes.

Most importantly, use the exact Windows Update error code whenever one appears. The error code often provides a much faster path to identifying whether the underlying problem involves connectivity, permissions, servicing corruption, disk space, drivers, or Windows Update configuration.

Tags

#WindowsUpdate #Windows11 #Windows10 #WindowsUpdateStuck #UpdateStuckAt0 #WindowsTroubleshooting #WindowsRepair #WindowsUpdateFix #WindowsUpdateError #WindowsSupport #WindowsTips #WindowsUpdateRepair #SoftwareDistribution #Catroot2 #DISM #DISMRestoreHealth #SFC #SFCScannow #SystemFileChecker #WindowsUpdateCache #WindowsUpdateReset #WindowsUpdateService #BITS #WindowsServices #MicrosoftWindows #Windows11Update #Windows10Update #CumulativeUpdate #SecurityUpdate #WindowsPatch #PatchManagement #WindowsUpdateTroubleshooter #WindowsError #PCRepair #ComputerRepair #ITSupport #TechnicalSupport #WindowsAdministrator #SystemAdministrator #SysAdmin #WindowsCommands #CommandPrompt #WindowsMaintenance #WindowsSecurity #WindowsUpdateComponents #WindowsUpdateDownload #MicrosoftUpdate #WindowsUpdateFailed #WindowsUpdateNotWorking #WindowsKnowledgebase