> ## Content Index > Fetch the complete content index at: https://techbytefix.com/llms.txt > Use this file to discover other available public pages before exploring further. # Fix Windows Update Stuck at 0% Without Breaking Windows - URL: https://techbytefix.com/windows-update-stuck-0-percent/ - Published: 2026-10-24T00:04:00.000Z - Updated: 2026-10-24T00:04:00.000Z - Author: Jake Whitman - Tags: Troubleshooting Windows Update at 0% is often still working, not frozen. Wait at least 30 minutes while checking network and disk activity; if there is no activity and the status does not change, restart normally, run the Windows Update troubleshooter, and then reset update components if needed. These steps apply to Windows 10 and Windows 11 and are designed to preserve your files. ## Is Windows Update really stuck at 0%, or should you wait longer? A 0% display does not prove that Windows has frozen. Windows can remain at 0% while it checks the update, measures available storage, prepares files, or waits for a connection. Save your work, connect the PC to power, and leave the update screen open while you check for activity. ```text Windows Update remains at 0% ``` Symptom This symptom appears on the Windows Update page while Windows is checking, downloading, preparing, or installing an update. Wait at least 30 minutes before interrupting a normal update attempt. For a large feature update, a slower computer, or a slow connection, waiting longer can be reasonable. Check these signs: - Open Task Manager with `Ctrl` \+ `Shift` \+ `Esc`, select **Performance**, and watch **Ethernet** or **Wi-Fi** for network traffic. - Watch **Disk** activity in Task Manager. Sustained activity can mean Windows is preparing or unpacking update files. - Open File Explorer and confirm that the system drive has free space. A nearly full drive can leave the update apparently motionless. - Look for changing status text on the Windows Update page, such as checking, downloading, installing, or pending restart. - Try opening a normal website in a browser to confirm that the connection works. If network or disk activity continues, or the status changes occasionally, let Windows continue. If the display remains at 0% with no network or disk activity, the same status persists after a long wait, or Settings becomes unresponsive, use the fixes below. Do not hold down the power button unless Windows is completely unresponsive and a normal restart is impossible. ![A Windows 11 computer shows the Windows Update screen while an update downloads.](https://tse1.mm.bing.net/th?q=Windows%2011%20Update%20screen%20downloading%20update&w=624&h=352&c=7) ## Which Windows versions and situations do these fixes apply to? These steps cover supported Windows 10 and Windows 11 installations using Windows Update through the Settings app. Running the troubleshooter requires a normal user account. Stopping services, renaming update folders, and running repair commands require an Administrator Command Prompt. Save open documents before changing anything. A normal restart closes unsaved applications, so make sure your work is saved first. The cache reset does not remove personal files. A backup is sensible before major system repair, especially if the computer has other problems, although the first checks do not alter your documents. Check these conditions before repairing Windows Update: - If the connection is marked as metered, Windows may delay or limit downloads. Review the network’s metered-connection setting before retrying. - Disconnect a VPN temporarily if it is interfering with Microsoft’s update servers. Pause third-party antivirus web filtering only if you can do so safely, and turn it back on after testing. - Check available space on the Windows drive. - A work or school computer may be controlled by Windows management policies. Those policies can defer updates, require a maintenance window, or block manual repairs. An interrupted earlier update, damaged update cache, security software, and connection restrictions can all produce the same 0% symptom. Start with the least disruptive checks. ## What should you try first without risking your files? Start with the connection and power, then use Windows’ built-in repair tool. Do not begin by deleting system folders or forcing the PC off. 1. Save your work and connect the computer to AC power. If you are using a laptop, leave the lid open so it does not sleep during the update. 2. Confirm that the internet works in a browser. If possible, disconnect and reconnect to Wi-Fi, or try a wired connection. Turn off a VPN temporarily and check whether the update can proceed. 3. Check free space by opening **Settings > System > Storage** in Windows 11, or **Settings > System > Storage** in Windows 10\. Remove only files you recognize as safe to remove; do not manually delete Windows system folders. 4. Run the built-in troubleshooter. ```text Windows 11: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run Windows 10: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter ``` Settings path 1. Apply any repair that Windows recommends, then restart normally from **Start > Power > Restart**. A normal restart lets Windows close services and write pending changes correctly. 2. After signing back in, return to Windows Update and select **Check for updates**. The troubleshooter can repair a service configuration, clear a temporary condition, or report that it found nothing. If it reports no problem and the update still sits at 0%, continue to the cache reset. If Settings or the entire desktop is unresponsive, wait for disk activity to stop before trying a normal restart. Force-shutting down during an active installation is riskier than restarting from Windows. ## How do you reset Windows Update when the basic fix fails? Reset the update cache only after checking the connection and storage, running the troubleshooter, and trying a normal restart. This procedure stops update-related services, renames two cache folders, and starts the services again. Renaming is safer than deleting because Windows can create fresh folders while the old contents remain available for diagnosis. Do not run these commands in a regular Command Prompt. Use an Administrator Command Prompt, and do not interrupt the commands while services are stopping or starting. 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 hold update files open. ```cmd net stop wuauserv net stop bits net stop cryptsvc net stop msiserver ``` Command Prompt (run as Administrator) The expected result is a message that each service was stopped. If a service says it was not started, continue unless Windows reports an access or dependency error. 1. Rename the update cache folders. ```cmd ren %systemroot%\SoftwareDistribution SoftwareDistribution.old ren %systemroot%\System32\catroot2 catroot2.old ``` Command Prompt (run as Administrator) The expected result is normally a return to the prompt without a success message. If a folder cannot be renamed, close Settings and other update-related tools, restart, and try again. 1. Start the services again. ```cmd net start wuauserv net start bits net start cryptsvc net start msiserver ``` Command Prompt (run as Administrator) The expected result is a message that each service was started. If Windows reports an access or dependency error, keep the exact message for diagnosis rather than repeating the commands. 1. Restart Windows normally, then open Windows Update and select **Check for updates**. If the update moves beyond 0% or installs successfully, the cache reset addressed the immediate problem. If it remains at 0%, continue with component and system-file repair. Do not delete random contents from `C:\Windows`, and do not use third-party repair tools as a substitute for these built-in checks. If Windows itself appears damaged, run component repair before repeating the update. In the same Administrator Command Prompt, run DISM first and wait for it to finish: ```cmd DISM.exe /Online /Cleanup-Image /RestoreHealth ``` Command Prompt (run as Administrator) A successful run commonly ends with a message saying that the restore operation completed successfully. If it reports an error, keep the exact message for diagnosis. Then run System File Checker: ```cmd sfc /scannow ``` Command Prompt (run as Administrator) SFC reports whether it found and repaired corrupted files, found corruption it could not repair, or found no integrity violations. DISM repairs the Windows component store that SFC relies on; SFC checks protected system files. Use DISM and SFC when the cache reset does not resolve the problem or Windows appears damaged, not as the first response to a brief 0% display. These commands can take time, so do not close the window merely because progress pauses. ## How do you know the update is fixed, and what if it keeps returning to 0%? After the restart, verify the result instead of relying on a brief change in the percentage. 1. Open Windows Update and check for a pending restart or another available update. ```text Windows 11: Settings > Windows Update > Update history Windows 10: Settings > Update & Security > Windows Update > View update history ``` Settings path 1. Look for the update listed as successfully installed. Also open **Settings > System > About** and check the Windows edition and version. A successful installation may require another restart before the version information changes. 2. If the update is still offered, perform one clean restart and try it again. Keep the computer plugged in, leave the connection available, and temporarily remove a VPN from the test. Do not repeatedly reset the cache after every attempt; first record what Windows reports. If the same update repeatedly returns to 0%, copy its name and knowledge base number, if shown, and search for that specific update in the Microsoft Update Catalog. Download the package that matches your Windows version, edition, architecture, and update number. Install it only when those details match; an incompatible package can fail or be refused. If Windows shows an error code, record the complete code and the update name before trying more fixes. The code narrows the cause far better than the 0% display alone. Search Microsoft’s support documentation for that exact code, or use it when requesting support. On a work or school computer, contact the administrator instead of resetting services or installing a catalog package. Management policies, WSUS, Intune, security software, or a scheduled maintenance window may control the update. An administrator can check policy, deployment status, and server-side logs. If the update history says **Failed**, the error code is the next useful piece of information; if it says **Pending restart**, restart normally before attempting another repair. ![The Windows 11 Update screen shows a pending restart after an update.](https://tse1.mm.bing.net/th?q=Windows%2011%20Update%20screen%20restart%20pending&w=624&h=352&c=7) ## Conclusion Wait while network or disk activity continues. If Windows Update remains at 0% after the basic checks, use the troubleshooter, then reset the cache from an Administrator Command Prompt and run DISM followed by SFC when Windows appears damaged. Record the update name and error code, and send those details to an administrator for a managed work or school computer. ## Frequently Asked Questions ### Can I turn off my PC when Windows Update is stuck at 0%? Use \*\*Start > Power > Restart\*\* when Windows is responsive. Avoid holding the power button during an active installation or while disk activity continues. Force-shut down only when the computer is completely unresponsive and a normal restart is impossible. ### Will resetting Windows Update delete my files? Renaming \`SoftwareDistribution\` and \`catroot2\` resets temporary update data; it does not delete your personal documents. Close applications first, use an Administrator Command Prompt, and do not delete unrelated folders under \`C:\\Windows\`. ### Why does Windows Update stay at 0% even though my internet works? Windows can be checking the update, waiting on storage, preparing files, using a damaged cache, or being restricted by a VPN, security product, metered connection, or work policy. Network access alone does not prove that every update component is functioning.