Yesterday, Google announced the first preview of its CloudReady-based project, Chrome OS Flex. So I just had to take a quick look. It’s a weird combination of polished and incomplete, with some features working properly and some missing in action. I suspect your results will vary considerably depending on the hardware. But at least you can test it first via a USB environment if you want.
I, perhaps stupidly, chose not to do that. Instead, I used Google’s instructions to create the installer USB key and then blew away the Windows install on an older HP EliteBook x360 14. The install process took about 5 minutes; I’m pretty sure I spent a bit more time than that just creating the USB installer.
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
If you’re familiar with Chrome OS and Chromebooks, you get the idea: Google’s free (for now?) tool turned this once very expensive Windows PC into a very expensive used Chromebook.
And at first glance, I was pretty impressed, since most of the high-level functions seemed to work just fine. Each time I touched a key on the keyboard, for example, it would light up. I could tap Print Screen to take a screenshot, just like in Windows (where Chrome OS uses a special keyboard shortcut). The touch screen works fine, and it seems to know that a smartpen would work (based on a taskbar icon) but I don’t have one to test that. And when I tapped the Mute function key, an onscreen overall indicated that the sound muted. Nice.
But as I used it more, I started to discover the issues. Mute “worked,” but the volume keys did not, and when I tried to play a YouTube video, oops: I found out that sound didn’t work at all. The HP’s fast fingerprint reader is unavailable in Chrome OS Flex, too, forcing me to type my long Gmail password to sign in. Or I can set up a PIN, which can only be 6 characters, not the four I prefer. Oof.
I’ve only just started playing with it, so I don’t have a handle on how well power management might work, or what the battery life is. But it’s clear this is a good idea, assuming Google (and/or its hardware partners) can overcome some of the driver issues. I don’t want to use a PC without sound, obviously. Chrome OS is a nice choice for an older computer that may or may not run the latest software, and that’s especially true if you mostly run web apps.
And while I’m sure this is coincidental, it is perhaps notable that Google shipped this preview on the same day that Microsoft released “new experiences” for Windows 11 that include a preview of Android app compatibility. But where Windows 11 is relegated to 1000 apps from the lackluster Amazon Appstore for Android, Chrome OS Flex should eventually provide access to the Google Play Store. (It doesn’t right now, however.)
Regardless, Chrome OS Flex is also technically more compatible with PC hardware than is Windows 11, since it will run (and maybe run perfectly) on PCs that don’t meet Microsoft’s arbitrary hardware requirements for Windows 11.
I may try installing Chrome OS Flex on a different PC to see whether the hardware compatibility is a bit better. But even in this early stage, it’s an interesting solution, albeit one with a few missing pieces.
dftf
<p><strong>"[…] Microsoft could just build a Windows 11 Basic edition"</strong></p><p><br></p><p>I argued the same-thing at the time <em>Windows 11 </em>system-requirements were revealed: they should have offered a "Windows 11 for Legacy PCs" edition, that would forgoe features like the Android app support, Auto HDR, DirectStorage, and other future "high-performance" features, like those based-around 3D and VR. It should still require a 64-bit CPU and 4GB RAM, but permit a <em>DirectX 10</em> compliant GPU or later, and the older TPM 1.2 standard (along with not requiring a TPM), and still support booting on legacy BIOS. Only qualifying PCs would get to install it; if a PC were capable of running the full <em>Windows 11</em>, you’d be limited to that.</p><p><br></p><p>As <em>Microsoft</em> are <em>not </em>doing so it’ll be interesting to see where people turn-to, once <em>Windows 10 </em>support ends (for the main editions) come October 2025. I can see <em>Chrome OS</em> being a bigger-draw than people suddenly moving to something like <em>Ubuntu </em>or <em>Linux Mint</em>, and were people going to move to <em>macOS</em> then they would either have already done-so — but given the price-differences, I can’t see people moving that-way, compared to just buying another cheap device with <em>Windows 11</em> preinstalled. (And other options, like <em>ReactOS</em>, just aren’t viable and likely never will be…).</p>
dftf
<p>You can probably use <em>Xbox Cloud Gaming</em>, too — I think all that requires is a modern web-browser, as making it a website, rather than an app, is how they got-around <em>Apple’s</em> ban to offer it to iOS users</p>
dftf
<p>It’s funny how Paul criticises that the "fingerprint reader is unavailable", as he clearly wants the greater-security that would offer, but then says "I can set up a PIN, which can only be 6 characters, not the four I prefer".</p><p><br></p><p>So with one of the most-secure options not being-present your alternative is… to use a less-secure method, and actually wish they offered an even-less secure version of that method? #MakesSense !</p>