There is a special kind of dread reserved for the blue “Restarting” screen that does not restart. The spinning dots are frozen, the fan may be quiet or roaring, and your HP laptop has been sitting there for an hour. Maybe two. Touching it feels wrong — every instinct says never interrupt an update — but at some point waiting becomes the worse option. Here is how a technician handles it: a disciplined waiting period first, then a safe forced recovery, then the fixes that stop it happening again.
HP laptops hit this more than average because of how their firmware interacts with the Windows restart handoff: Fast Boot settings, HP’s own update agents, and chipset drivers that do not fully support the restart signaling Windows expects. None of that means your laptop is broken. Follow the order below and do not skip the waiting step — roughly half of “stuck” updates are just slow ones. For the general step-by-step version of this fix, see our comprehensive restarting-fix guide .
One more thing before you start: note exactly what the screen shows. A spinning circle of dots that still animates means Windows is alive and possibly working; a completely frozen frame with no animation for over an hour means it is truly hung. Also check whether the Caps Lock key still toggles its light — if it does, the system is responsive underneath and patience is the right call. These two observations take ten seconds and prevent the most common mistake: force-restarting a healthy update mid-install.
Why this happens
- Genuinely slow servicing: Large updates can sit on “Restarting” for 45+ minutes while the servicing stack works — this looks stuck but isn’t.
- HP Fast Boot firmware setting: Aggressive fast-boot skips initialization steps the update’s restart sequence expects, stalling the handoff.
- Conflicting HP update agents: HP Support Assistant or HP BIOS Update utility running during the Windows restart competes for firmware access.
- Outdated chipset/storage drivers: Old drivers mishandle the power-state transitions during restart.
- Stuck pending operations: A previous failed install left
PendingFileRenameOperationsor reboot flags that deadlock the restart. - USB peripherals interfering: Docking stations, external drives, and USB hubs can block the restart handshake on HP firmware.
- Corrupt update payload: A partially downloaded update that passed verification can hang when it tries to apply.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: The disciplined wait — confirm it is really stuck
Do not touch anything for the first hour. Seriously.
- Plug in the charger — a battery dying mid-restart is the one thing that can turn this into a real disaster.
- Watch the hard drive activity light (if your HP has one) or listen for disk sounds. Activity means it is working.
- Wait a full 60 minutes on first occurrence. Feature updates legitimately take this long on spinning disks and older SSDs.
- If the spinner is completely frozen and there has been zero activity for over an hour, it is hung — proceed to Fix 2.
Fix 2: Force the shutdown safely
The last resort that is safer than it sounds.
- Press and hold the power button for 10 full seconds until the laptop powers off completely.
- Unplug the charger, wait 30 seconds (this drains residual power and clears the hung state), then plug back in and power on.
- Windows will either resume the update, roll it back automatically (“Undoing changes made to your computer”), or boot normally.
- If it rolls back, that is a success — the system protected itself. Now fix the cause before retrying (Fixes 3–6).
Fix 3: Disconnect everything and retry
Peripherals are a top HP-specific cause of restart hangs.
- Shut down fully, then unplug all USB devices: docks, hubs, external drives, printers, even the mouse if you can spare it.
- If you use an HP docking station, connect the charger directly to the laptop instead.
- Power on, go to Settings > Windows Update, and retry the update with only the charger attached.
Fix 4: Update HP drivers and BIOS before retrying
HP publishes driver updates that specifically fix restart-handoff issues.
- Open HP Support Assistant or visit HP Support , enter your model, and install all BIOS, chipset, and storage updates.
- Restart after each BIOS update (HP’s installer will guide you — never interrupt a BIOS flash).
- With firmware current, retry the Windows update. Updated firmware handles the restart signaling correctly.
Fix 5: Clear the stuck update state in WinRE
If Windows boots to the desktop but the update immediately tries and hangs again, clear the deck first.
- Hold Shift while clicking Restart to enter the Windows Recovery Environment.
- Go to Troubleshoot > Advanced options > Command Prompt.
- Run:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old(usedir C:to confirm the drive letter in WinRE). - Select Continue to boot normally, then check for updates fresh. Guidance for recovery-environment repairs is also documented at the Windows update support hub .
Fix 6: Disable Fast Boot in BIOS/UEFI
HP’s Fast Boot can stall the update restart handoff.
- Restart and press F10 repeatedly to enter BIOS Setup.
- Navigate to Advanced > Boot Options and disable Fast Boot.
- Save and exit (F10), boot to Windows, and retry the update.
- You can re-enable Fast Boot afterward if boot times matter to you — but leave it off during update days.
Fix 7: Run the update manually from the Microsoft Update Catalog
Bypass the flaky automatic path entirely.
- Note the KB number from Settings > Windows Update > Update history.
- Download it from the Microsoft Update Catalog .
- With peripherals disconnected and HP utilities closed, run the installer and let it handle the restart itself.
Closing
A stuck “Restarting” screen on an HP laptop is scary but survivable: wait the hour, force the shutdown if it is truly hung, then fix the underlying cause — usually peripherals, firmware, or a poisoned cache — before retrying. The one rule that never changes: charger plugged in, always. A power loss during the restart phase is the only version of this problem that can genuinely brick a machine. And if the forced recovery lands you in the “undoing changes” loop instead of a clean boot, our undoing-changes recovery guide covers that next step.
