Why Won’t My PC Restart? | Fix It Fast

Restart failures usually stem from pending updates, stuck services, driver faults, or power issues—work through the checks below to get Windows rebooting.

Your computer shuts down but never comes back, hangs on the spinning dots, or returns to the desktop without cycling. Restart glitches like these often trace back to Windows updates, a buggy driver, corrupted system files, Fast Startup quirks, or plain power delivery issues. This guide gets you to a clean reboot with clear steps and zero fluff.

Quick Clues: Symptoms, Causes, Fixes

Start with pattern spotting. Match what you see to a likely cause, then try the paired fix. Keep peripherals unplugged during tests, then add them back one by one.

Symptom Likely Cause Fast Fix
Stuck on “Restarting” screen Update hang or service deadlock Wait 10 minutes, then long-press power; boot, run Update troubleshooter, clear pending updates
Shuts down, never powers back Fast Startup or BIOS power handoff Disable Fast Startup; cold boot; check BIOS power settings
Instant power loss on restart PSU or motherboard issue Test wall outlet, power cable, strip; try a different PSU if possible
Restarts only in Safe Mode Third-party driver or service Clean boot, update or remove the culprit driver or app
Blue screen during restart Driver crash or bad system files Update drivers; run SFC and DISM; check crash code
Boot loops into recovery Damaged boot data Run Startup Repair; rebuild boot files

First Pass: Safe, Reversible Checks

Do A True Cold Boot

Choose Shut down, then cut power fully. On a laptop, hold the power button for 15 seconds with the charger unplugged. On a desktop, switch off the PSU and drain with a short press. Wait 30 seconds, then power on and retry Restart.

Unplug Everything Non-Essential

Pull USB hubs, docks, external drives, gamepads, and printers. Leave only keyboard, mouse, and display. A finicky USB device can stall the handoff that happens during a reboot.

Check For Pending Updates

Open Settings > Windows Update and finish any installs. If an update is stuck, pause updates, reboot, then resume. Recent servicing fixes have targeted WinRE and Reset features, so staying current helps restore repair tools you might need next.

Close Variant: PC Not Restarting After Update

When restart stalls right after Patch Tuesday, the update stack is the prime suspect. Try these steps in order.

Run The Windows Update Troubleshooter

Settings > System > Troubleshoot > Other troubleshooters > Windows Update. Apply any fixes it proposes, then reboot.

Flush The Update Cache

Open an elevated Command Prompt and run:

net stop wuauserv
net stop bits
rd /s /q C:\Windows\SoftwareDistribution
net start bits
net start wuauserv

Retry Windows Update, then try Restart again.

Fast Startup Quirks: Turn It Off During Troubleshooting

Fast Startup can skip parts of a full reboot. That speedup is fine until a driver or firmware needs a complete cycle. Toggle it off while you diagnose:

  1. Control Panel > Hardware and Sound > Power Options > Choose what the power buttons do.
  2. Click “Change settings that are currently unavailable.”
  3. Uncheck “Turn on fast startup (recommended).” Save.

Do a full Shut down, then power on. Test Restart again. You can switch Fast Startup back on later if everything behaves.

Repair Core Files With SFC And DISM

Corrupted system files can trip a reboot right as services unload or reload. Two built-ins fix this.

Run System File Checker

Microsoft’s System File Checker scans and repairs protected files.

cmd
sfc /scannow

Let it reach 100%. If it reports repairs, reboot right away.

Refresh The Windows Image With DISM

cmd
DISM /Online /Cleanup-Image /RestoreHealth

When DISM completes, run SFC again and restart.

Driver And Firmware Steps

Update Display, Chipset, And Storage Drivers

GPU and storage stacks touch the boot path. Pull the latest drivers from the vendor app or site. If the issue began after a driver update, roll back in Device Manager > Properties > Driver > Roll Back Driver.

BIOS Or UEFI Update

Board firmware governs ACPI power states and the restart flow. If your vendor lists a recent stability fix, apply it from within the vendor tool or from a USB stick per their guide. Avoid updating during a storm or on a weak battery.

Clean Boot: Find A Conflicting App Or Service

  1. Press Win+R, type msconfig, press Enter.
  2. On Services tab, tick “Hide all Microsoft services,” then click “Disable all.”
  3. Open Task Manager > Startup apps and disable non-critical items.
  4. Reboot. If Restart now works, re-enable items in batches to find the culprit.

Startup Repair And Boot Data Fixes

If Windows enters a loop or never hands off from firmware, use the recovery tools. From the sign-in screen, hold Shift while choosing Restart to reach Advanced startup. Pick Troubleshoot > Advanced options > Startup Repair. If repair fails, open Command Prompt in the same menu and rebuild boot files:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Power Chain Checks

Laptops: Battery And Charger

Use the original charger. Run a battery reset: power off, unplug, hold power for 20 seconds, reconnect, then start. Look for swelling, random power cuts, or charging LED oddities.

Desktops: PSU, Case Switch, And Cables

Test a known-good outlet and cable. If the system powers off on restart but stays off, the PSU may be tripping under transient load. Swap in a spare unit if available. Reseat the front-panel header; a sticky reset switch can pull the line low during boot.

Event Viewer: Prove The Root Cause

Press Win+X > Event Viewer. Check Windows Logs > System. Filter for Kernel-Power, Kernel-Boot, and User32 events around your restart attempts. A repeating driver name or service timeout gives you the next lead.

When Windows Tools Are Unavailable

If USB input fails inside recovery on some builds, plug in a PS/2 keyboard if the board has a round port, or use a different build of a USB recovery drive. Vendors sometimes publish hotfixes for WinRE input problems; updating from the desktop restores normal controls.

Second Table: Fix Commands And When To Use Them

Command Or Tool What It Does Use It When
SFC /scannow Repairs system files Random crashes, failed restarts
DISM /RestoreHealth Repairs the Windows image SFC finds issues repeatedly
Startup Repair Fixes boot configuration Loops into recovery or black screen
Bootrec commands Rebuilds boot records Missing OS entries or boot errors
Clean boot Isolates third-party conflicts Restart fails only with services loaded

Extra Wins: Small Tweaks That Matter

Turn Off “Fast Startup” Only During Diagnosis

Leave it off while testing. Once the machine restarts cleanly several times, you can enable it again if you want faster boots.

Remove Overclock Profiles

Reset CPU, GPU, and RAM to stock. Marginal OCs often pass a cold start but trip on a warm restart.

Scan For Malware

Open Windows Security, run a Full scan. Some malware hooks into shutdown and restart flows.

When To Reinstall

If SFC, DISM, Startup Repair, driver updates, and clean boot all fail, a repair install keeps your files while replacing Windows. Use the Media Creation Tool to build the installer, run setup from the desktop, and pick “Keep personal files and apps.” Plan an image backup first.

Command Line Restarts That Bypass The Shell

If the Start menu restart fails, use command line calls that ask Windows to reboot directly. Open an elevated Terminal and try one of these options:

shutdown /r /t 0
shutdown /g /t 0
shutdown /r /fw /t 0

/g restarts apps that registered for it. /fw requests firmware settings on next boot, which is handy when you need to reach UEFI to change a setting.

UEFI, TPM, And BitLocker Notes

Changing storage mode, Secure Boot, or TPM settings can prevent a normal reboot until Windows reconfigures itself. If you plan to switch between AHCI and RAID, or toggle Secure Boot, make a record of your BitLocker recovery key first. After changes, pause to let Windows enumerate devices and complete any driver install prompts before trying another restart.

Dual-Boot Setups And Hibernation Files

On a system that also boots Linux, Fast Startup leaves the Windows volume in a hibernated state. Mounting that volume from the other OS flags it dirty and can corrupt metadata, which later derails a reboot. Keep Fast Startup off on dual-boot rigs and always shut down cleanly before switching systems.

When It Points To Hardware

If restarts fail even outside of Windows, check parts. Reseat RAM and GPU, clean dust from slots, and try one memory stick at a time. Watch CPU temps in firmware. A tired PSU or a failing NVMe drive can trigger a restart drop. If pulling a device restores clean restarts, you found the path.

Safe Mode Tricks That Help

From the sign-in screen, hold Shift while selecting Restart. Choose Startup Settings and press 4 for Safe Mode or 5 for Safe Mode with Networking. Once in, remove drivers or software you suspect, run SFC and DISM, and try a restart from there. If Restart succeeds only in this state, you still have a third-party hook to remove.

Why Restart Differs From Shut Down

Shut down turns everything off; Restart tears down and spins back up in one chain. That timing stresses drivers and power rails in ways a cold start does not. That is why flaky USB hubs, marginal OCs, and half-installed updates often show up only during a restart cycle.

Printable Checklist: From Quick To Deep

  1. Cold boot and unplug extras
  2. Finish or clear updates
  3. Disable Fast Startup
  4. Run SFC then DISM
  5. Update or roll back drivers
  6. Clean boot
  7. Startup Repair and bootrec
  8. Power chain tests
  9. Repair install