Windows Update Stuck or Failing: A Safe Diagnostic Sequence
Identify whether the problem is downloading, installing or restarting before changing update components.
- Identify download, installation and restart separately
- Prepare a backup and enough working time
- Check connection and space without damaging files
- Use the official troubleshooter, then inspect the result
- Check known issues and compatibility holds
- Treat repair commands and recovery as separate decisions
- Confirm success rather than hiding the failure
- Questions about this guide
- Further reading
- Related help
- Read next
- Tell us about your own situation.
- Services
- Resources
- Company
- Get in touch
Identify whether the problem is downloading, installing or restarting before changing update components. A download that is not progressing, an installation that returns an error and a computer that will not return from a restart are different problems. Start by identifying the stage and exact message. An unchanged percentage alone does not tell you whether work has stopped. This guide prioritises official tools, backup preparation and decisions you can verify. It avoids indiscriminate command scripts and the assumption that every update failure needs a factory reset. On a work-managed device, policy and your administrator also matter. Record the update name, error code and failure stage. Check connectivity, available storage and pending restarts when Windows is usable, then follow the official troubleshooter for that symptom. Do not repeatedly cut power during installation or delete update folders using an unverified script. Identify download, installation and restart separately Open Windows Update when the desktop is available and note whether the update is downloading, installing, awaiting restart or reporting failure. Record the KB identifier, Windows version and exact code. A feature update and a routine quality update are not the same change. During a restart, percentages may pause while work continues. The appropriate action depends on the current screen and Microsoft’s instructions for that state. There is no single waiting time that proves every device is stuck. Distinguish a Windows update from a manufacturer firmware update before considering any interruption. The KB identifier separates that update from other changes around the same time. Record whether Windows rolls back and returns to the desktop or remains at a startup screen. Those situations determine whether the next step is update diagnosis or restoring startup first. Prepare a backup and enough working time Before retrying a significant update, check that important files are backed up and can be opened from that copy. Keep encryption recovery information available. Save open work and choose a time when a restart will not interrupt a call or essential task. Use stable power and the correct laptop charger. If the computer already loses power, reports storage errors or overheats, address that reliability problem before repeating installation. Update failure can be a consequence of another fault rather than the original cause. Check connection and space without damaging files If Windows rem
The update percentage has stopped. Should I switch off?
A percentage that has not moved does not always mean the work has stopped. Check whether it is a Windows update or a firmware update, follow the official guidance for that situation and avoid forcing repeated interruptions.
Why isn’t the newest feature update offered to me?
The timing of the rollout, compatibility safeguards or your organisation's policy may apply. Check the official release information rather than forcing an installation that has been held back for your setup.
Does reinstalling Windows guarantee updates will work?
No. Storage faults, unstable power, compatibility and network or policy limits may all still be there afterwards. Protect your files first and find out the actual cause.