Watching Windows Update sit at 100 percent for an hour is nerve-wracking, but in most cases the update is actually finished and only the final cleanup or reboot step is dragging. The percentage counts files copied, not the whole job, so the last stretch can involve driver migrations, registry work, and disk operations that show no progress at all. Your first and most important action is to do nothing: give it at least an hour, longer on older machines with spinning drives, before you touch anything. Interrupting a nearly finished update is the one move that reliably turns a delay into real damage.

While you wait, rule out the classic blockers that stall the final phase. Unplug unnecessary USB devices such as printers, external drives, and docks, since a misbehaving peripheral can hold the installer at the finish line indefinitely. Make sure the laptop is plugged into power and has a stable connection, and check that the system drive still has free space, because the cleanup phase needs room to work. These are the same calm, sequential checks we advocate in our look at the SRE book's second edition: verify the environment before blaming the software.

If several hours pass with zero change, the Windows Update troubleshooter is the safest intervention. On a working system, run it from Settings under Troubleshoot; it can clear stuck download caches and repair broken update components without touching your files. You can also open the Services app and restart the Windows Update service itself, which sometimes unfreezes a stalled finalization. Both of these are non-destructive, which matters, because at this stage preserving the half-applied update is far better than forcing it.

When the machine is completely unresponsive on the updating screen, a forced restart becomes the reluctant next step, and it is less dangerous than it feels. Hold the power button until the machine shuts off, wait thirty seconds, and power it back on; Windows is designed to resume or roll back an interrupted update, and it will usually pick up where it left off. If it boots normally, check the update history to see whether the update completed or needs another attempt. Only consider this after the waiting period, never as a first response.

For updates that fail repeatedly at the same point, reset the update components manually. Stop the Windows Update and Background Intelligent Transfer services, rename the SoftwareDistribution and Catroot2 folders so Windows rebuilds them fresh, then restart the services and check for updates again. This clears the corrupted download cache that causes most repeat failures, and it keeps your files and apps untouched. The repeatable-repair mindset from our guide to automating repetitive work is exactly what this is: a documented procedure you can run the same way every time.

Prevention turns this from a recurring scare into a non-event. Schedule updates for times when you can leave the machine alone, keep at least a comfortable margin of free space on the system drive, and create a restore point before major feature updates so you always have a way back. If an update keeps failing on your hardware, pausing updates for a short while and letting the next cumulative release arrive often resolves the incompatibility on its own. Updates stuck at 100 percent feel broken, but patience plus the right sequence of checks resolves nearly all of them without data loss.