Windows

How to Fix a Frozen Computer (Without Losing Unsaved Work)

A frozen computer tests your patience in a very specific way. The mouse cursor might still move, but nothing responds to clicks. Or the screen is completely static. Or one application is hanging and dragging everything else down with it. Whatever form the freeze takes, the instinct to hold the power button is understandable — but it's a last resort, not a first one.

There's a logical progression of recovery attempts that preserves your best chance of salvaging unsaved work. Follow these in order.

Step 0 – Wait 60 Seconds

Genuine freezes and temporary unresponsiveness look identical. Windows can become temporarily locked while processing a large file, running a disk check, handling a memory spike, or applying a background update. If the hard disk activity light on your PC is still blinking, or if you can hear the drive working, something is still happening — give it a full minute before concluding it's frozen. Interrupting a background disk operation mid-way can cause data corruption.

Step 1 – Force Open Task Manager

Press Ctrl + Shift + Esc. This keyboard shortcut opens Task Manager directly, bypassing the frozen UI. If Task Manager opens, go to the Processes tab, look for any process with "Not Responding" next to its name or with abnormally high CPU/Memory usage, select it, and click End Task. Often a single application is the culprit and killing it unfreezes everything else.

Alternatively, Ctrl + Alt + Delete opens a security screen — from there, click Task Manager. This path sometimes works when desktop input is locked because it triggers a different interrupt level.

Step 2 – Restart Windows Explorer

If the desktop itself is frozen but Task Manager opened, the Windows Explorer shell process may have crashed. In Task Manager, click File → Run new task, type explorer.exe, check "Create this task with administrative privileges," and click OK. This restarts the desktop environment without touching your open applications or their unsaved data.

Step 3 – Keyboard-Only Recovery Shortcuts

If the mouse cursor won't respond but keyboard input still works:

  • Alt + F4 closes the active window — useful if one frozen application is blocking everything
  • Windows key + D minimizes all windows and shows the desktop
  • Windows key + R opens the Run dialog — you can launch taskmgr from here
  • Alt + Tab switches between open applications — sometimes a frozen foreground app is blocking keyboard input to everything else

If the frozen application is saving data (you can see disk activity), let Alt + F4 wait for it to finish rather than forcing closure immediately. The application may be in the middle of a save operation and simply not responding to the UI while it completes.

Step 4 – Force Restart (Last Resort)

If nothing else has worked after 3–5 minutes, hold the power button for 5–10 seconds until the machine shuts off. This bypasses the normal shutdown sequence and guarantees any unsaved work from that session is lost. It also carries a small risk of file system corruption if the disk was mid-write, though modern SSDs and Windows' journaled file system significantly reduce this risk compared to older hardware.

After forcing a shutdown, Windows will usually run a disk check on next boot. Let it complete — it repairs minor file system inconsistencies caused by the abrupt shutdown.

Recovering Unsaved Work After a Crash

Many applications auto-save recovery data that survives forced shutdowns. When you reopen:

  • Microsoft Word/Excel/PowerPoint: Recovery pane opens automatically on next launch with auto-saved versions. Also check C:\Users\[Name]\AppData\Local\Microsoft\Office\UnsavedFiles
  • Notepad/Notepad++: Notepad doesn't auto-save. Notepad++ maintains session backups in C:\Users\[Name]\AppData\Roaming\Notepad++\backup
  • Google Chrome (tabs): Chrome restores your previous session automatically when it detects an unclean shutdown. Look for the "Restore session" prompt or press Ctrl + Shift + T
  • Adobe apps: Check Edit → Preferences → File Handling for auto-recovery interval and location

Why Freezes Happen and How to Reduce Them

One-off freezes are normal — occasional memory allocation failures or driver glitches happen. Frequent freezes indicate an underlying problem:

  • Overheating: Check temperatures with HWMonitor. CPU above 90°C under load causes thermal throttling that can manifest as freezing. See our overheating guide.
  • Failing RAM: Run Windows Memory Diagnostic (search for it in Start) or Memtest86 from a bootable USB. Faulty RAM is a common cause of random system freezes.
  • Disk issues: Run chkdsk C: /f /r from an elevated Command Prompt (will scan on next restart). A failing HDD causes freezes as the system waits on stuck read operations.
  • Driver conflicts: Check Event Viewer → Windows Logs → System for errors timestamped at the time of the freeze. Driver fault entries (source: "Application Hang" or specific driver names) point to the culprit.
💡 Best Prevention

Enable autosave in every application that supports it. Save every 10–15 minutes as a habit. Use OneDrive or Google Drive for active documents — they create version history that survives any crash, no matter how sudden.