Check this first
The short answer
If Settings still works, identify the stage, check connectivity and Windows-drive space, then complete a requested normal restart. Use diagnostics for repeated failures of the same update. After restarting, maintain power and record changes in the screen. A percentage or elapsed time alone cannot establish that a forced shutdown is safe.
- Settings opens: distinguish download, installation and a pending restart.
- Update screen after restart: maintain power and record wording, percentage and time.
- Repeated failure or download: compare the same update name, KB if shown and error code.
How long should you wait? Compare the stage and visible changes
Microsoft explains that duration depends on connection and update details. These branches combine visible changes with whether Windows can still be operated; they do not set a universal deadline.
- The percentage or wording changes: You have observed progress. Keep power connected and wait. A restart may begin another stage, so its percentage is not directly comparable with the previous screen.
- The percentage stays the same but Windows works: You can inspect the update name, connectivity and storage in Settings. A 0% or 100% reading alone does not mean the whole PC has stopped; use Steps 2–3.
- Nothing changes for a long time after restarting: Settings and diagnostics may be unavailable. Give the PC manufacturer the screen wording and elapsed time to assess recovery. A normal restart instruction for a working desktop is not an instruction to hold the power button.
The reviewed sources do not establish a universal 30-minute, one-hour or two-hour threshold for forcing power off. Spinning dots or fan noise alone prove neither successful progress nor a complete stall. Timed examples below illustrate recordkeeping; they are not device test results.
Official guidance behind these checks:
Choose your next check
Start with the row that matches your situation. Change one setting at a time so you can tell what helped.
| What you see | What to compare | Go to |
|---|---|---|
| Download remains at 0% or stops increasing | If the desktop works, inspect connectivity, space and update name. | Step 2 |
| Installation stays at one percentage or 100% | Distinguish a requested restart from a failed update. | Step 3 |
| Restart pending or restart required | Installation may be waiting for a normal restart rather than failing. | Step 3 |
| After restart: working on updates or do not turn off | Keep power available; record wording, percentage and time. Settings instructions do not apply here. | Step 5 |
| Undoing changes continues or startup repeats | Distinguish rollback in progress from repeated startup failure with a recovery screen. | Step 5 |
| The same update fails and downloads again | Record its name, KB, failure time and code before diagnostics. | Step 3 |
| The same update fails after diagnostics | If Windows works, compare repair output with the update outcome. | Step 4 |
| History contains both success and older failures | Compare the same update and current restart requirement. | Step 7 |
Check in this order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1: Record the current screen and update name
- Check whether Start and Settings open. If they do, open Settings → Windows Update and record the update name and whether it is downloading, installing or waiting for a restart. Record the KB number when shown; inspect Update history for previous outcomes.
- Use Windows + R → winver to record the Windows version and OS build only if Windows responds. Otherwise photograph the update screen using another device and record its wording, percentage and time.
- Compare another observation with the first. The 30-minute interval in the examples below is an observation interval, not a shutdown deadline. Connect a laptop to its appropriate power supply and leave ventilation unobstructed.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| Example: download 20% at 10:00, 55% at 10:30 | Progress is visible within the same stage. | Wait; use Step 3 when a restart is requested. |
| Example: 0% at both times, but Settings works | Progress is unconfirmed while Windows remains usable. | Check connectivity and space in Step 2. |
| Example: 100%, then restart and updates at 30% | The screen and stage changed. | A smaller percentage alone is not an update loop. Use Step 5. |
- Expected result or what you learned
- You can identify the screen, stage, update and elapsed observations.
- If something is wrong or unclear
- A BIOS, UEFI or firmware update screen requires the manufacturer’s instructions. Do not apply Windows recovery actions to it.
- How to undo changes
- Observation changes no settings. Remove account names and notifications from photos before sharing.
Step 2: For a stalled download, check connectivity and Windows-drive space
- Use this step only with a working desktop. Inspect Settings → Network & internet and compare several websites in a browser. If other sites also fail, use the related Wi-Fi internet-connectivity guide.
- Open Settings → System → Storage and inspect the drive containing Windows. Free space on another game drive is not automatically available to this update. Use any shortage amount shown by Windows; requirements vary with the update and device.
- If space is insufficient, review Temporary files or Cleanup recommendations and each item’s description. Preserve required Downloads and Recycle Bin files. Removing a previous Windows installation affects the option to return to that version; retain it if needed for recovery.
- After addressing the connection or space issue, choose Retry if offered. If the symptom persists and Start works normally, save work and use Power → Restart once, following Update and restart when offered. After startup, verify the same update in Step 7.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| Download advances after connection or storage changes | Progress followed that change. | Finish installation and any requested restart, then Step 7. |
| Other sites work and no space shortage appears, but progress is unchanged | Basic connection and capacity checks did not resolve it. | Use Step 3 diagnostics. |
| Updates are paused or controlled by your organization | Waiting may reflect settings or management policy. | Resume updates if you personally paused them on your own PC; otherwise ask the administrator. |
- Expected result or what you learned
- The download advances, or a connection/storage issue has been identified for attention.
- If something is wrong or unclear
- Other websites working does not rule out a problem specific to the update service. Check diagnostics and official information for the update.
- How to undo changes
- Restore a comparison network connection if changed. Deleted files are not restored by reversing a setting; preserve needed files before cleanup.
Step 3: Complete a pending restart, then diagnose repeated failure
- If Windows Update requests a restart, save work and use Restart now or Start → Power → Update and restart. Separate this pending action from installation failure. If the post-restart update screen appears, use Step 5.
- If the same update stalls or fails again after normal startup, open Get Help and run Windows Update diagnostics. Where offered, Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run provides another route.
- Record diagnostic findings and changes, follow the restart guidance, then use Settings → Windows Update → Check for updates. Compare the original name/KB. A diagnostic message saying repaired does not independently confirm installation.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| The target update succeeds after a normal restart | The restart completed or enabled installation. | Confirm history and current status in Step 7. |
| The same update fails after diagnostics | Diagnostics did not resolve the failure. | Record the code and results, then Step 4; see the related 0x800f081f guide for that code. |
| Diagnostics cannot open or require unavailable permission | The conditions for running them may not be met. | Ask your administrator; on a personal PC use Step 4 only with appropriate rights. |
- Expected result or what you learned
- The pending restart is completed and you can compare the same update again.
- If something is wrong or unclear
- If the PC repeatedly restarts without reaching the desktop, use Step 5 rather than starting repair commands here.
- How to undo changes
- There is no single undo button for diagnostic changes and installed updates. Preserve their names and times to investigate new symptoms.
Step 4: For repeated failure, read DISM and then SFC results
- Use these commands only when Windows can start normally. Back up important files. Search for Command Prompt, choose Run as administrator and review the elevation prompt. Ask the administrator if you lack permission.
- Run DISM.exe /Online /Cleanup-Image /RestoreHealth as one line. Keep the window open until it finishes. Do not start this concurrently just because an update percentage has not reached 100%.
- Only after DISM succeeds, run sfc /scannow with the space before the slash. Wait for verification to finish and record the final message. After both complete, restart normally and retry the same update.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| DISM succeeds; SFC reports no issue or successful repair | The system-file check/repair completed. | Restart and retry the update. Success leads to Step 7; recurrence to Step 6. |
| DISM ends with 0x800f081f or another error | Repair itself has failed, possibly involving unavailable repair files. | Record the full message; consult the code-specific guide or Step 6. Do not choose an arbitrary ISO as a source. |
| SFC cannot repair some files or perform the operation | Verification or repair remains incomplete. | Keep the output for Step 6; do not manually replace files in bulk. |
- Expected result or what you learned
- Repair output and update installation outcome are recorded separately.
- If something is wrong or unclear
- A command percentage that appears unchanged is not a reason to close its window. If it cannot finish and you need help, provide the message and elapsed observations.
- How to undo changes
- System-file repairs have no single undo action. Keep backups and command results.
Step 5: Handle an update or rollback screen after restarting
- For working-on-updates, do-not-turn-off or undoing-changes messages, maintain power and record wording, percentage and time. Rollback is a process, not installation success. For prolonged lack of change that needs intervention, contact the PC manufacturer with a photo and timing.
- If the sign-in screen is reachable but normal startup fails, locate your BitLocker recovery key before choosing Power → Restart while holding Shift to enter Windows RE. If Automatic Repair already offers Advanced options, use that entry instead.
- When startup failed after a recent update and Windows RE is available, open Troubleshoot → Advanced options → Uninstall Updates. If the preceding installation is known to be a quality update, review Uninstall latest quality update and follow its prompts. If the type is unknown, ask support rather than removing unrelated updates in succession.
- If Windows RE cannot be reached, consult your model’s recovery controls, an existing recovery drive or Microsoft’s Windows RE guidance. Do not repeatedly interrupt update processing to force recovery. If the key is unavailable or data is not backed up, explain that before choosing any reset.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| Wording/percentage changes, then the desktop returns | Startup completed; update success versus rollback is still unknown. | Compare the target update in Step 7. |
| Startup works after removing or undoing the update | Startup is restored, but that update is not installed. | Preserve data, record its name and check known issues in Step 7. |
| Recovery fails or requests an unavailable key | Recovery cannot be completed from the current information. | Give support the message, key ID and model. Never publish the recovery key itself. |
- Expected result or what you learned
- You regain startup and distinguish successful installation from rollback.
- If something is wrong or unclear
- If neither waiting nor recovery restores the desktop, stop repeating the same operation and contact the manufacturer or administrator.
- How to undo changes
- Removing an update also removes its fixes. After recovery, check official mitigation and reinstallation guidance. Do not bypass key preparation by disabling encryption or deleting data.
Step 6: If Windows starts but failures persist, assess same-version repair
- Consider this only when normal startup works and diagnostics/repair have not resolved the same update failure. Back up important files and arrange stable power, internet and enough time.
- Open Settings → System → Recovery → Fix problems using Windows Update → Reinstall now. Read the confirmation and choose OK when ready. This repairs the current Windows version while preserving apps, files and settings.
- Complete download, installation and the requested restart, then compare the original update in Step 7. If the option is missing, version, update prerequisites or management policy may limit availability; contact the administrator or Microsoft support.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| The original update succeeds after repair | Its installation has now been verified. | Save current status and history in Step 7. |
| The option is absent or repair download fails | This recovery path is unavailable or incomplete. | Record the Windows version and message for support; do not substitute a reset. |
| Repair completes but the same update fails | Repair alone did not resolve that update’s issue. | Use Step 7 for known issues and a support record. |
- Expected result or what you learned
- You can distinguish the repair outcome from the subsequent update outcome.
- If something is wrong or unclear
- If repair leaves you on a post-restart screen without returning to Windows, use Step 5.
- How to undo changes
- This repair has no one-click undo. Reset this PC is a different operation that can remove apps or settings.
Step 7: Verify the same update, pending restart and any recurrence
- Open Settings → Windows Update → Update history and compare the original name/KB with its success time. Inspect current retry or restart requirements too. An old failure row alone does not mean a new failure.
- If failure persists, open the Windows release health source below, choose your Windows version and search the KB or symptom. Match affected versions, environments and mitigation. Do not reuse another KB’s workaround; no matching entry does not prove hardware failure.
- For support, record model, winver version/build, update name/KB, screen, timing, code and diagnostics/DISM/SFC/recovery results. Supply logs privately to the official support contact requesting them; full logs can contain personal details.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| Target succeeded, with no matching pending action or new failure | Installation of that target is confirmed. | Finish; assess any different remaining update separately. |
| A pending restart remains | A restart is still required to complete application. | Use Step 3 and recheck after startup. |
| The same KB gains a new failure timestamp | The retry also failed. | Bring the combined results to known-issue guidance, Microsoft support or your administrator. |
- Expected result or what you learned
- The original target remains identifiable through installation verification.
- If something is wrong or unclear
- Up to date alone does not establish the installation history of a specific previously failed KB. Compare history and that update’s official guidance.
- How to undo changes
- Keep your records. If an update was removed for recovery, follow official resolution guidance before reapplying necessary updates.
When to ask for help
Start a support request with the screen wording, whether the desktop works and how long it has remained unchanged. Avoid forced power cuts, bulk update-cache deletion and disabling services or protection as first actions. Contact the PC manufacturer for startup failure or your organization’s administrator for a managed PC. Explain unbacked-up data before recovery or reset.
FAQ
What commonly needs checking when Windows Update will not finish?
During download, check connectivity and storage; after installation, check restart requirements. Repeated failures may require update or Windows repair. After restarting, application or rollback may take time. The percentage alone does not identify the cause.
Can I turn it off after one or two hours?
Time alone cannot decide that. With a working desktop, identify the stage and use normal restart or diagnostics as applicable. On the post-restart processing screen, maintain power and ask the manufacturer about prolonged lack of change.
Is the fix the same at 0% and 100%?
Use the stage rather than the number. A download, an installation waiting for restart and a post-restart update screen permit different actions. 100% does not by itself confirm that every stage is complete.
Do spinning dots or fan noise prove progress?
No. Compare wording or percentage changes and, after normal startup, the target update’s history. Animation alone cannot identify which installation work is advancing.
Does undoing changes mean the update succeeded?
No; it indicates rollback. After Windows returns, record the target’s history and any error. For prolonged lack of change or repeated failed startup, use Step 5.
How many gigabytes must be free?
Requirements depend on update type, optional features and current device state. Compare the Windows drive and the shortage shown by Windows, rather than relying on another game drive’s available space.
Does an old failure row mean the problem is unresolved?
Compare later success for the same name/KB and current restart requirements. A new failure timestamp after retry indicates recurrence; an old failure by itself does not.
Should I delete update files or reset Windows first?
Start with the stage, connection, space, normal restart and diagnostics. Cache deletion affects update/diagnostic state, while reset can remove apps/settings. Choose recovery from the actual results and preserve needed data.
Sources
English adaptation of the Japanese guide, preserving all diagnostic branches, steps, examples and recovery limits. Official sources explain the controls. The decision order and timed examples are editorial guidance, not measurements from tested PCs.
Microsoft: update duration and stalled progressMicrosoft: restarts and update historyMicrosoft: Windows Update diagnosticsMicrosoft: space required for updatesMicrosoft: reviewing cleanup itemsMicrosoft: DISM and SFC resultsMicrosoft: same-version repair and availabilityMicrosoft: accessing Windows REMicrosoft: startup recovery and BitLockerMicrosoft: removing an update from Windows REMicrosoft Learn: Windows release health and known issues