ERROR_FAIL_RESTART (0X00000160): Fix Windows Restart Failure

What's Actually Happening Here

Error 0X00000160 (ERROR_FAIL_RESTART) means Windows tried to restart—maybe after an update, driver install, or manual reboot—but something blocked it. The OS couldn't complete the shutdown sequence. The restart operation literally failed because a process refused to terminate, a driver locked up, or system files got corrupted mid-transaction.

I've seen this most often after a Windows Update that gets stuck at "Getting Windows ready" or when you click Restart and nothing happens—the screen hangs, or you get a spinning circle that never resolves. Sometimes it's a leftover app from a failed uninstall. Let's fix it.

The 30-Second Fix: Kill the Stuck Process

This works about 40% of the time. Windows itself tells you a restart failed because something won't close. You can force it.

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Go to the Processes tab. Look for any app with a status like "Not responding" — usually a browser, a game launcher, or a VPN client.
3. Right-click that process and choose End task. If it won't die, right-click again and pick End process tree.
4. Now try restarting: Win+R, type shutdown /r /t 0, hit Enter.

The reason this works: the restart sequence first tries to gracefully close user-mode processes. If one hangs, Windows waits—and eventually times out with this error. By killing it manually, you remove the bottleneck.

If the restart succeeds here, you're done. If not, move on.

The 5-Minute Fix: Clean Boot and Check Drivers

When a single process isn't the culprit, the problem is likely a third-party service, driver, or startup program that blocks the restart. A clean boot isolates the system to only Microsoft services.

1. Press Win+R, type msconfig, hit Enter.
2. In the System Configuration window, go to the Services tab.
3. Check Hide all Microsoft services at the bottom. Then click Disable all. This keeps Windows' own services running—don't touch those.
4. Go to the Startup tab and click Open Task Manager. Disable every startup item listed.
5. Click OK in msconfig, then Restart. If the error disappears, a third-party service or driver caused it.

To narrow it down: re-enable services one by one (half at a time) and restart until the error returns. The last batch you enabled is where the culprit lives. I've seen NVidia display driver services and old VPN adapters trigger 0X00000160 specifically.

Still stuck? Next step.

The 15+ Minute Advanced Fix: System File Repair and Windows Restore

If clean boot didn't help, the issue is deeper—corrupted system files, a broken registry key, or a Windows component store that's hosed. This is my go-to when the first two fail.

Step 1: Run SFC and DISM

These two commands fix most file-level corruption. Open Command Prompt as Administrator (Win+X → Terminal (Admin)). Run them in order:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

sfc checks protected system files and replaces bad ones from a local cache. DISM repairs the component store that sfc relies on—if DISM fails, the store itself is damaged. That usually means a repair install (below).

After both complete, restart. If 0X00000160 still appears, we go nuclear.

Step 2: Check for Pending File Rename Operations

Windows sometimes marks files for deletion on next boot, and if that operation fails, the restart can't proceed. The culprit is often PendingFileRenameOperations in the registry.

1. Open Registry Editor (Win+R, type regedit).
2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
3. Look for a multi-string value named PendingFileRenameOperations. If it exists, right-click and Delete it.
4. Warning: Only delete this if you're confident no pending update needs it. If you just installed a Windows update and got this error, deleting it will skip that update—which might be fine if the update is broken anyway.
5. Close Registry Editor and restart.

Step 3: Use a Restore Point or Repair Install

When nothing above works, you're looking at a system state that's too damaged for quick fixes. Two options:

• System Restore: Boot into Safe Mode (hold Shift while clicking Restart from the login screen). Go to Troubleshoot → Advanced Options → System Restore. Pick a point before the error started. This reverts system files and registry without touching your documents.
• Repair Install (In-place Upgrade): Download the Windows 11/10 ISO from Microsoft's site. Run setup.exe from inside Windows, choose "Keep personal files and apps," and let it reinstall the OS. This replaces every system file while preserving your data. It's the nuclear option that works 99% of the time.

The reason step 3 works: a repair install rebuilds the entire Windows boot stack—drivers, services, registry—from a known-good source. If a driver or system file was corrupted in a way SFC can't fix, this overwrites it cleanly.

Prevention

Once you've fixed 0X00000160, a few habits reduce the chance of it returning:

• Don't force shutdown during updates. Wait 10 minutes before holding the power button.
• Uninstall software properly via Settings → Apps, not by deleting folders.
• Run sfc /scannow monthly—think of it as a dental checkup for your OS.

If you hit this error again, you'll know the drill: kill the process, clean boot, then go deep. You won't need this guide twice.