Chromebook Won’t Turn On or Charge
A completely unresponsive Chromebook is an immediate cause for concern. Begin with the power source. Unplug the charger from both the wall and the Chromebook, wait 10 seconds, and reconnect everything firmly. Try a different wall outlet and, if possible, a different USB-C charger to rule out a faulty power adapter. If the device shows no sign of life—no LED light, no fan noise—a hardware reset is the next step. This clears temporary glitches in the hardware memory. Perform a hard reset by holding the Refresh key (circular arrow) and tapping the Power button. Release the Refresh key. For Chromebooks with detachable keyboards, press and hold the Power button for at least 10 seconds. If successful, the device should power on.
If the Chromebook turns on but gets stuck on a black screen, white screen, or the Chrome OS logo, you’re likely dealing with a software hang. First, try forcing a shutdown by holding the Power button for 10 seconds, then restarting. If the problem persists, you may need to enter Recovery Mode. To do this, hold Esc + Refresh, then press the Power button. Release all keys when you see the recovery screen. From here, you can press Ctrl + D to try enabling Developer Mode (which will wipe local data), or follow on-screen instructions to recover the OS using a recovery USB drive created on another computer.
Wi-Fi and Connectivity Issues
A Chromebook without the internet is severely limited. Start with basic troubleshooting: turn Wi-Fi off and on via the quick settings panel (bottom-right clock). Forget the problematic network by clicking the Wi-Fi icon, selecting the gear icon next to your network, and choosing “Forget.” Then reconnect by entering the password again. This clears corrupted connection data. If the issue is across all networks, power cycle your router and modem. Unplug them for 30 seconds, then restart.
For persistent problems, check for IP address conflicts. In the Wi-Fi network settings, under your connected network, ensure “Configure IP address” is set to Automatic (DHCP). If you suspect a DNS problem, change it to Google’s public DNS: 8.8.8.8 and 8.8.4.4. Network hardware on the Chromebook can also glitch. Perform a network reset by going to Settings > Advanced > Reset settings > Reset network settings. This clears all networks and paired Bluetooth devices. As a last resort, a Powerwash (full reset) will wipe all network configurations.
Chromebook Running Slow or Freezing
Sluggish performance often stems from resource overload. First, check your system resources. Press Search + Esc to open the Task Manager. Look for tabs, extensions, or apps consuming excessive CPU or Memory. Click on the column headers to sort by usage. Close any unnecessary, resource-heavy processes by highlighting them and clicking “End process.” Extensions are a common culprit. Manage them by typing chrome://extensions/ in the Omnibox (address bar). Disable non-essential extensions, especially ad-blockers, VPNs, and grammar checkers, to see if performance improves.
Ensure your Chromebook is updated. Outdated OS versions can have bugs and lack performance optimizations. Go to Settings > About Chrome OS > Check for updates. Restart to install any pending updates. Next, examine your storage. While Chrome OS is cloud-based, low local storage (under 10% free) can hinder performance. Check storage at Settings > Device > Storage. Delete unnecessary offline files, cached data, and downloads. For persistent freezing, perform a Hardware Reset (Refresh + Power tap) as outlined earlier. If a specific website freezes the browser, press Shift + Esc to open the browser’s own task manager and terminate that tab’s process.
Touchpad, Keyboard, or External Device Problems
An unresponsive touchpad or keyboard can be infuriating. First, rule out a simple software lock. For the touchpad, ensure it hasn’t been disabled by accident. Press Search + Shift + P to toggle the touchpad on and off. For the keyboard, check for sticky keys by pressing Search + Shift + S to toggle screen capture mode, which can sometimes interfere. Clean around the keys and touchpad with compressed air to remove debris.
If specific keys don’t work, use the on-screen keyboard to test. Go to Settings > Advanced > Accessibility > Manage accessibility features > Enable on-screen keyboard. This can help determine if it’s a hardware or software issue. For external mice or keyboards, try a different USB port or unpair and re-pair Bluetooth devices. If the built-in hardware remains faulty, a Powerwash can sometimes resolve driver-level corruption. If problems continue after a reset, it is likely a physical hardware defect requiring repair.
Audio Not Working or Sound Issues
Start with the basics. Check the physical volume buttons on the keyboard. Ensure the volume is unmuted and turned up. Click the system tray (clock) and use the volume slider. Test with multiple apps—a YouTube video, a local MP3 file—to see if the issue is app-specific. For external speakers or headphones, ensure they are properly connected and selected as the output device. Click the volume icon in the system tray and choose the correct output device from the list that appears.
Dive into the audio settings by going to Settings > Advanced > Accessibility > Audio. Ensure no mono audio or other settings are enabled that could distort sound. A crucial step is to clear the cached audio data. In the Omnibox, type chrome://settings/content/sound and remove any sites that might be blocking sound. If audio is crackling or distorted, perform a hard reset (Refresh + Power) to reset the audio driver. For persistent issues, a Chrome OS Reset via Powerwash is the next step, as it reinstalls the core OS audio framework.
App Problems and Android/ Linux Issues
For problematic Android apps, first ensure the Google Play Store is updated. Go to Settings > Apps > Google Play Store > Manage Android preferences > Play Store version. Force stop the misbehaving app via Settings > Apps, select the app, and choose “Force stop.” Clear the app’s cache and data from the same menu—this resets the app without deleting your account. If an Android app crashes constantly, check for updates in the Play Store, or uninstall and reinstall it.
Linux (Crostini) problems often require a different approach. If your Linux container won’t start, the virtual machine may have corrupted. Go to Settings > Advanced > Developers > Linux development environment and click “Restart.” For more serious issues, back up your Linux files (use the Backup and Restore option in the same menu) and then “Remove” the Linux environment. Re-adding it creates a fresh container. Ensure your Chromebook has sufficient storage and RAM for Linux operations, and that you’ve granted necessary permissions to the container in Chrome OS settings.
Screen and Display Glitches
A flickering, distorted, or improperly scaled screen is often fixable. First, adjust screen resolution and scale. Go to Settings > Device > Displays. Ensure the resolution is set to “Native” or the recommended setting. Adjust the “Display size” (scaling) slider for comfortable reading. For external monitors, use the “Mirroring” or “Extended display” options judiciously, and try different cables or ports. If the screen flickers, a temporary graphics driver issue is likely. Perform a Hardware Reset (Refresh + Power) to reinitialize the display hardware.
For persistent graphical artifacts or tearing, a Powerwash can resolve deeper OS corruption. In rare cases, a corrupt browser flag can cause issues. Type chrome://flags in the Omnibox, search for “GPU” or “Overlay,” and try resetting any altered flags to “Default.” Be cautious here, as changing flags can cause instability. If the physical screen is cracked, has dead pixels, or shows persistent lines, this is a hardware failure requiring professional screen replacement.
Chrome OS Update Failures and System Errors
A failed update can leave your Chromebook in a limbo state. If an update gets stuck, first ensure you have a stable internet connection and at least 30% battery (plug it in). Restart the Chromebook and check for updates again via Settings > About Chrome OS. If the update continues to fail, you likely have a corrupted local update file. You will need to use the Chrome OS Recovery Utility. On a working computer, install this extension from the Chrome Web Store. Use it to create a recovery USB drive (8GB minimum). On your Chromebook, boot into Recovery Mode (Esc + Refresh + Power), insert the USB, and follow prompts to reinstall Chrome OS from scratch. This process, while effective, will erase all local data.
For specific error messages like “Chrome OS is missing or damaged,” Recovery Mode is the only solution. Always ensure your critical files are synced to Google Drive. To prevent update issues, avoid shutting the lid or powering off during an update, and maintain at least 2-3 GB of free local storage for the update process to complete smoothly.
Google Account Sync and Login Problems
Account sync errors prevent your bookmarks, extensions, and settings from loading correctly. First, verify your internet connection. Click your account picture in the bottom right and see if there’s a sync error notification. Go to Settings > You and Google > Sync and Google services. Click “Manage what you sync” and ensure “Sync everything” is on, or selectively enable items. A common fix is to turn sync off and on again. Choose “Pause sync,” wait a moment, then re-enable it.
If you cannot log in at all, double-check your password at accounts.google.com on another device. Ensure you are using the correct account for this Chromebook (like a work vs. personal account). On the login screen, use “Browse as Guest” to get online, then check for Chrome OS updates—an outdated OS can cause login bugs. For persistent “This device is managed” or enterprise policy errors, the Chromebook may be enrolled in Chrome Enterprise. It must be unenrolled by the organization’s admin. If it’s your personal device, a Powerwash from Recovery Mode will remove any erroneous management.
Bluetooth Pairing and Connectivity Failures
Bluetooth issues are often about resetting the connection cycle. Start by ensuring the Bluetooth device is in pairing/discoverable mode. On the Chromebook, click the system tray, select Bluetooth, and turn it off for 10 seconds, then back on. Forget the problematic device by clicking the gear icon next to it and selecting “Remove.” Then attempt to pair it again as a new device.
Interference from USB 3.0 devices or crowded Wi-Fi channels (2.4GHz) can disrupt Bluetooth. Try moving other wireless devices away. Reset the Chromebook’s Bluetooth adapter by going to chrome://bluetooth-internals in the Omnibox. In the “Adapter” section, you may find an option to restart the adapter. As with Wi-Fi, a full network settings reset (Settings > Advanced > Reset settings) will clear all Bluetooth pairings. If one specific device fails, test it with another phone or computer to rule out a fault with the peripheral itself.