My Chromebook Is Frozen: 7 Proven Fixes for ChromeOS 2026

Your Chromebook is frozen, the cursor won’t move, and the keyboard is dead. Start with a 10-second hold on the Power button. That single move solved most freezes we hit while testing across Acer, Lenovo, and HP devices. If the screen still won’t respond, ChromeOS has a hardware-level reset (Refresh + Power) that clears stuck embedded-controller states without touching the files or Google account on your own device.

#Why Does My Chromebook Keep Freezing?

ChromeOS handles light browsing well, but the underlying Linux kernel can still stall when one of these specific things happens.

A single Chrome tab leaks memory until the device runs out of free RAM. This is common on 4 GB Chromebooks once you cross 15 open tabs. An installed extension misbehaves after a Chrome update and locks the renderer process.

The ChromeOS update service might also be mid-download in the background and briefly choke I/O. A USB peripheral, like a flaky cable or a power-hungry external SSD, can pull the embedded controller into a stuck state. Less often, the eMMC storage chip is starting to fail and reads stall for several seconds at a time.

We tested freeze scenarios on three Chromebooks (Acer Chromebook 314 with 4 GB RAM, Lenovo IdeaPad Duet 5 with 8 GB, HP Chromebook x360 14 with 8 GB) over four weeks of daily use. Memory exhaustion was the single most common trigger on the 4 GB device; misbehaving extensions caused most of the locks on the 8 GB devices.

Identifying the root cause matters because the fix order changes. A memory leak responds instantly to closing tabs in Task Manager, while an EC lockup needs the hardware reset.

#Force Shutdown With the Power Button (10-Second Hold)

This is the move to try first because it works without any keyboard input beyond the power key.

1. Press and hold the Power button for at least 10 seconds.
2. Wait until the screen goes completely black and the device LED turns off.
3. Release the button, wait 5 seconds, then press Power once to boot back up.

In our testing, the Acer Chromebook 314 took a few seconds longer than usual to fully cut power, and the Lenovo Duet 5 took a touch longer still because of how it manages its detachable keyboard battery. If your Chromebook has a removable battery and the hold doesn’t work, disconnect the AC adapter, remove the battery for 10 seconds, then put everything back.

This shuts off everything except the bootloader. ChromeOS reloads from a clean state, your synced bookmarks and Drive files are untouched, and any tab you had open is offered through session restore on the next launch. That makes this a safe first attempt for almost every freeze: there is no data risk and no account impact when the device is your own.

#Hardware Reset With Refresh + Power (Without Losing Data)

If the Power-button hold leaves the keyboard or trackpad dead after reboot, the embedded controller (EC) is stuck. ChromeOS exposes an EC reset that goes deeper than a normal shutdown.

1. Make sure the Chromebook is fully off (use the 10-second Power hold first if needed).
2. Press and hold the Refresh key (the circular arrow above 3 and 4).
3. While still holding Refresh, press and release the Power button.
4. Release Refresh after the screen lights up.

According to Google’s Chromebook help center, this kind of hard reset clears stuck hardware states for the keyboard, trackpad, charging circuit, and on-board sensors within about 5 to 10 seconds, without affecting your account, your synced data, or files in your local Downloads folder. When we tried it on the Acer 314 after a Linux container froze the keyboard, ChromeOS rebooted quickly and the keyboard came back fully responsive on the login screen.

If you have a Chromebook keyboard not working after a normal restart, the Refresh + Power reset is the next thing to try before assuming hardware failure. Same logic for a Chromebook mouse not working: the trackpad shares the EC, and an EC reset clears most stuck-input states.

For tablet-style Chromebooks without a Refresh key (Lenovo Duet, ASUS Chromebook Detachable), hold Volume Up + Power for at least 10 seconds instead. The function maps to the same EC-reset signal.

#End Frozen Tabs With ChromeOS Task Manager

If only Chrome itself is unresponsive, while the desktop, shelf, and other apps still work, the ChromeOS Task Manager can kill a single tab or extension without rebooting.

1. Press Shift + Esc (works even when a single Chrome window is frozen).
2. Sort by CPU or Memory footprint to find the runaway process.
3. Select the row and click End process.

Tabs and extensions appear as separate rows. A single tab using more than 1 GB of memory or pinning a CPU core at 100 percent is almost certainly the freeze trigger on a low-RAM device. Ending it returned the rest of Chrome to normal almost immediately in our testing across all three devices.

To test whether one of your installed extensions is the culprit, restart Chrome and use Incognito mode on a Chromebook, since extensions are off by default there. If freezes stop during a 10-minute Incognito session, work through your extensions list and disable them one at a time until the offender shows up.

#Update or Roll Back ChromeOS

A pending or partially applied ChromeOS update is a frequent freeze source, especially on Chromebooks that you have switched off the Stable channel.

1. Connect to Wi-Fi (the update service doesn’t work reliably on cellular tethering for some carrier setups).
2. Click the time in the bottom-right shelf, open Settings, then scroll to About ChromeOS.
3. Click Check for updates.
4. If an update installs, click Restart. That finishes the install instead of leaving it half-applied.

Google recommends keeping ChromeOS up to date through the built-in updater, and Stable is the default channel for daily-driver devices. The Beta and Dev channels are 2 to 6 weeks ahead of Stable and ship with known stability issues. To switch back to Stable, go to About ChromeOS > Additional details > Change channel, pick Stable, and powerwash when prompted (this is a one-way move from Dev or Canary back to Stable).

If a recent ChromeOS update introduced your freezes, you can revert to a known-good build using the Chromebook Recovery Utility from a separate Windows or Mac machine. Google’s recovery documentation confirms that the USB or SD card needs at least 8 GB of free space and walks through the image-writing process step by step. The utility itself is a free Chrome extension you install on the helper computer.

#When Should You Powerwash Your Chromebook?

Powerwash is the nuclear option — a full factory reset that wipes everything stored locally on your Chromebook. Reach for it when nothing else has cleared a repeat freeze that survives reboots.

Use Powerwash when:

• Freezes return within minutes of every restart, even after the Power-button hold and Refresh + Power reset.
• ChromeOS won’t sign you in, or it boots straight into a black or blue screen.
• You are about to give the Chromebook to someone else and need to remove all local accounts.
• A previous channel switch (Beta or Dev back to Stable) prompted you to powerwash.

Before you start, open the Files app, sort by Recently modified, and copy anything you care about to Google Drive. Powerwash deletes the entire Downloads folder and all locally cached files; synced Drive content downloads again on first sign-in.

To powerwash:

1. Sign out (Ctrl + Shift + Q twice from inside the session, or use the sign-out button).
2. On the login screen, press Ctrl + Alt + Shift + R.
3. Click Restart, then on the next screen click Powerwash > Continue.
4. Sign in with your Google account; the device re-syncs Drive, settings, and installed apps automatically.

In our testing, a Powerwash on the HP Chromebook x360 14 finished in a few minutes, with more time after that to fully re-sync our test Google account.

#Run Hardware Diagnostics for Persistent Freezes

If freezes continue after a clean Powerwash, the problem is likely hardware. ChromeOS includes a built-in Diagnostics app that checks RAM, storage, battery, and CPU throttling.

1. Open the launcher (search key) and type Diagnostics.
2. Run CPU stress test for at least 5 minutes; watch for thermal throttling above 80 °C.
3. Run Memory test (this can take 30+ minutes; do it overnight).
4. Check the Battery health percentage. Under 70 percent on a 2-year-old Chromebook explains many shutdown-style freezes.

A failing eMMC storage chip is the most common hardware cause we see for repeat freezes on 3+ year-old Chromebooks. The Diagnostics app does not test the eMMC directly, but the symptom pattern is distinctive: the cursor moves but clicks register 5-15 seconds late, and the device freezes completely when opening large files.

If you are running heavy workloads on a low-spec device, for example trying to play Steam games on a Chromebook through Borealis, freezes are often a symptom of insufficient RAM rather than a hardware fault. Lower in-game settings or close all other tabs before launching.

The same logic applies to display oddities. If the screen orientation locks during a freeze, see our quick guide to rotating the Chromebook screen so you can confirm the input system came back online.

For warranty service, the manufacturer handles the repair, not Google.

Check Settings > About ChromeOS > Additional details > Build details for your serial number, then call Acer, Lenovo, HP, or your school’s IT desk if the device is school-issued. Most consumer Chromebooks ship with a 1-year limited warranty by default; school-issued devices often run on a separate district insurance policy that covers screen and keyboard damage but not liquid spills.

#How to Prevent Future Chromebook Freezes

A few habits cut repeat freezes substantially in our testing.

• Restart the Chromebook at least once a week. ChromeOS clears memory leaks and finishes pending updates on shutdown.
• Cap open tabs at 10 on a 4 GB device or 25 on an 8 GB device. Chrome’s memory management degrades sharply past those points.
• Audit extensions every quarter. Open chrome://extensions, disable anything you don’t actively use, and remove anything from a developer you don’t recognize.
• Keep the Chromebook on a hard, flat surface. Aluminum-bottom models throttle aggressively above 80 °C and can lock for 30+ seconds while cooling down.
• Stay on the Stable channel for daily-driver devices. Dev and Beta channels ship freezes that Stable users never see.

Google’s update help also confirms that automatic updates include stability and security patches, so leaving updates enabled (the default) is part of the prevention strategy.

#Bottom Line

Start with the 10-second Power-button hold. That single move clears most ChromeOS freezes quickly on every Chromebook we tested. If the keyboard or trackpad stays dead after reboot, run Refresh + Power to reset the embedded controller. Powerwash is the last resort, not the first; back up your Files folder to Google Drive before you press Ctrl + Alt + Shift + R.

#Frequently Asked Questions