ChromeOS Flex installation fails in predictable ways. After setting up dozens of older laptops with ChromeOS Flex — and watching it fail on a fair few — I have catalogued the specific failure points into three stages: USB creation, boot, and post-boot installation. Most issues are resolved in under ten minutes once you know which stage failed and why.
This page is organised from the earliest failure point (cannot create the USB) to the latest (installed but something does not work). Jump to the section that matches your symptom. If you have not yet checked whether your model is compatible, start with our ChromeOS Flex compatibility guide — some machines have known issues that no amount of troubleshooting will resolve.
| Symptom | Stage | Most Likely Cause |
|---|---|---|
| Recovery Utility freezes or fails to download | USB creation | Network issue or Chrome extension conflict |
| USB created but "No bootable device" on target machine | Boot | Boot order, UEFI/Legacy mismatch, or Secure Boot |
| ChromeOS logo appears then screen goes black | Boot | GPU driver incompatibility |
| Installer cannot find internal storage | Installation | SATA mode set to RAID instead of AHCI |
| Wi-Fi not available during setup | Installation | Unsupported Wi-Fi chipset |
| Touchpad or keyboard unresponsive | Installation | Model-specific input driver missing |
Stage 1: USB Creation Issues
The Chromebook Recovery Utility (a Chrome browser extension) is the official tool for creating ChromeOS Flex USB installers. It works well on most machines, but it has specific failure modes that are easy to fix once identified.
Recovery Utility fails to download the image
The utility downloads a large image file (typically 3-5 GB). If your internet connection is unstable, the download can fail silently. Disable any VPN or proxy, temporarily disable other Chrome extensions that might interfere with network requests, and retry. If downloads still fail, use the alternative method: download the recovery image directly from Google's serving builds page (chromiumdash.appspot.com), then use Rufus (Windows) or Etcher (cross-platform) to write the image to your USB drive.
USB drive not recognised by the utility
The Recovery Utility is picky about USB drives. It requires at least 8 GB and can fail on drives with non-standard partition tables (common after use with Ventoy, Linux installers, or multi-boot tools). Fix this by fully wiping the drive: on Windows, open Disk Management, delete all partitions on the USB drive, create a single FAT32 volume, then try the Recovery Utility again. Alternatively, use diskpart with the clean command for a complete wipe.
USB creation completes but verification fails
If the utility reports a verification error after writing, the USB drive itself may be faulty. Try a different drive — older or counterfeit drives often have unreliable flash memory. USB 3.0 drives from reputable manufacturers are strongly recommended for reliability and speed.
Stage 2: Boot Errors
The USB is created, but the target laptop does not boot from it — or boots partially and then stops. For general USB boot problems that apply across all operating systems, see our USB boot troubleshooting guide. Below are the ChromeOS Flex-specific issues.
Laptop ignores the USB entirely
Enter BIOS/UEFI setup (typically F2, F10, F12, Del, or Esc during power-on — the key varies by manufacturer). Verify that USB boot is enabled and that the USB drive appears in the boot priority list. On some machines, you must press a specific key (often F12) for a one-time boot menu rather than changing the permanent boot order. If the USB does not appear at all, try a different USB port — rear or USB 2.0 ports are more reliably detected by older firmware.
UEFI vs Legacy boot mismatch
ChromeOS Flex USB media is created in UEFI mode by default. If your laptop's firmware is set to Legacy-only boot, the drive will not appear or will fail to start. In BIOS setup, look for "Boot Mode" or "UEFI/Legacy" and switch to UEFI or "Both." Machines older than about 2012 often have Legacy BIOS only — if there is no UEFI option at all, ChromeOS Flex may not boot on this hardware.
Secure Boot blocking
ChromeOS Flex officially supports Secure Boot, but some older Secure Boot implementations (particularly early UEFI firmware from 2012-2014) reject the ChromeOS Flex bootloader. Temporarily disable Secure Boot in BIOS setup and retry. If it boots successfully with Secure Boot off, you can re-enable it after installation on most machines — or leave it disabled if the machine is only running ChromeOS Flex.
ChromeOS logo appears then black screen
This typically indicates a graphics driver problem. The ChromeOS Flex kernel cannot initialise the display adapter correctly. Common on machines with certain NVIDIA Optimus configurations or very old Intel GMA chipsets. Try pressing Ctrl+Alt+F2 to switch to a text console — if text appears, the issue is the graphical driver specifically. Unfortunately, this often means the machine is incompatible with ChromeOS Flex. Check the decertified models list for your specific model.
Stage 3: Install-Time Failures
You have booted successfully into the ChromeOS Flex live environment, but something fails during the actual installation or initial setup process.
Internal storage not detected
The installer cannot find the laptop's internal hard drive or SSD. This is almost always a SATA controller mode issue. Reboot into BIOS setup and look for the SATA mode setting — it may be under Advanced, Integrated Peripherals, or Storage Configuration. Change it from RAID or IDE to AHCI. Save and reboot into the ChromeOS Flex USB again.
Wi-Fi not available during setup
ChromeOS Flex requires an internet connection to complete initial setup. If Wi-Fi is not available, the most likely cause is an unsupported wireless chipset — Broadcom and some Realtek chipsets are particularly problematic. Check our Wi-Fi and driver checklist to identify your chipset. Workarounds: use a USB-to-ethernet adapter, tether from an Android phone via USB cable, or use a USB Wi-Fi adapter with a chipset known to work with ChromeOS (Atheros or Intel-based adapters are safest).
Installation freezes or shows write errors
If the installation process hangs or reports disk write errors, the internal storage device may be failing. Boot from a Linux live USB and run sudo smartctl -a /dev/sda (install smartmontools first if needed) to check the drive's SMART health data. A failing drive will show reallocated sectors, pending sectors, or an overall health status of "FAILED." Replace the drive before attempting any OS installation — an SSD upgrade resolves this and massively improves performance.
Model-Specific Gotchas
Certain laptop families have recurring issues that are specific to their hardware or firmware. These are the most common ones I have encountered across refurbishment projects.
HP ProBook and EliteBook (2012-2016)
HP business laptops from this era often have a BIOS setting called "Legacy Support" that must be disabled for UEFI boot. Additionally, the "Boot Order" menu separates UEFI and Legacy devices into different lists — make sure you are looking at the UEFI list. Some HP models also have a "Sure Start" feature that resets BIOS changes on reboot; you may need to disable Sure Start before your settings persist.
Acer Aspire (2013-2017)
Acer laptops frequently ship with a BIOS supervisor password set by default (often blank — just press Enter). Without entering the password, some BIOS settings are greyed out. Secure Boot on Acer often requires setting a supervisor password before the Secure Boot toggle becomes available. The boot key is typically F2 for BIOS or F12 for the boot menu, but some models require pressing Fn+F2 or enabling "F12 Boot Menu" in the BIOS before the boot menu key works.
Toshiba Satellite and Tecra (2011-2015)
Toshiba machines frequently have a "CSM" (Compatibility Support Module) setting that must be enabled for USB boot on UEFI systems. The keyboard shortcut for the boot menu is F12 on most models, but it must be enabled in BIOS first — look for "USB Boot" and "Boot Menu" options. Some Toshiba Satellite models have a known issue where the internal Wi-Fi card enters a power state that ChromeOS Flex cannot wake it from — a USB Wi-Fi adapter is the practical workaround.
Dell Latitude and Inspiron (2012-2017)
Dell machines generally have excellent UEFI implementations. The most common issue is that Dell's BIOS defaults to RAID mode for the SATA controller, even on machines with a single drive. Change to AHCI as described above. The one-time boot menu key is F12 on all Dell laptops.
When to Try Linux Instead
ChromeOS Flex is a good choice for web-focused machines with straightforward hardware, but it is not the most compatible option. If you have hit multiple issues from the list above, consider switching to lightweight Linux. Specifically:
- 32-bit processor: ChromeOS Flex does not support 32-bit CPUs at all. Linux distributions like antiX and Puppy Linux do.
- Less than 4 GB RAM: ChromeOS Flex is sluggish with 2 GB. Lubuntu and MX Linux are comfortable at 2 GB.
- Problematic Wi-Fi chipset: Linux has broader driver support and can install entirely offline. ChromeOS Flex cannot complete setup without internet.
- Legacy BIOS only: Most Linux distributions support legacy BIOS boot. ChromeOS Flex has inconsistent support for machines without UEFI.
- GPU incompatibility: Linux offers multiple display drivers and fallback options. ChromeOS Flex has a fixed driver stack with no alternatives.
See our ChromeOS Flex vs Linux comparison for a detailed decision guide, and the boot time comparison to see how the two perform on similar hardware. The lightweight software pack provides a curated set of applications that run well on older machines under Linux.