Skip to content
SYS.OK — diagnostic bench online 463 guides // 9 modules // updated Aug 2026

ChromeOS 151 gets a patch for the stutter it caused

A graphite laptop half open on a dark desk, its screen glow spilling onto the desk

Google rolled out a maintenance patch for ChromeOS 151 on August 20, just a week after the milestone reached the Stable channel. If your Chromebook has felt slightly off since updating: laggy window snaps, a jumpy stylus, odd flicker in web apps, this is the fix, and it’s a good one to grab today.

Google pushed ChromeOS version 16733.54.0 (browser 151.0.7922.168) to the Stable channel on August 20, 2026, fixing four bugs that slipped into last week’s ChromeOS 151 rollout: a window manager freeze when snapping into split screen, stylus and touch input lag on convertibles, flickering in WebGL and WebGPU web apps, and a Bluetooth audio crash on waking from sleep. Check for updates in Settings and reboot to install it.

What actually broke in ChromeOS 151

When ChromeOS 151 reached Stable on August 13, it shipped with a stack of security fixes and a GPU cutoff for older ChromeOS Flex hardware. It also carried a handful of smaller regressions that only surfaced once the update reached a wide pool of devices. Chrome Unboxed traced part of the problem to a race condition in the Aura compositor, the piece of ChromeOS that handles how windows get drawn and repositioned on screen. Snap two windows into split view or flip through virtual desks quickly enough, and the compositor would occasionally hang for a moment before catching up.

Convertible owners got a separate annoyance: a polling delay in the touch and stylus input subsystem, which showed up as tracking lag and the occasional phantom gesture on the shelf. Anyone leaning on WebGL or WebGPU, whether that’s a design tool, a progressive web app, or cloud gaming through a service like the ones covered in our best Chromebooks for cloud gaming guide, could also see the graphics buffer fall out of sync and flicker mid-session.

Man checking for a ChromeOS update on his laptop while drinking coffee

A narrow fix, but a fast one

None of this comes close to the eighteen CVEs patched in the original 151 release. What stands out is the turnaround: Google shipped 16733.54.0 about a week after the jank started showing up in user reports, which is quick by ChromeOS point-release standards. The same patch fixes an edge case where a Chromebook would drop or crash its Bluetooth audio connection after waking from sleep with a paired LE headset, the kind of glitch that looks like a hardware fault if you don’t know it’s software. If that sounds familiar, our Chromebook Bluetooth troubleshooting guide is worth a look no matter which version you’re running.

Chromebooks on the Long Term Support track sit this one out entirely, since LTS-144 doesn’t include ChromeOS 151 at all. Everyone else should expect more patches like this one going forward. ChromeOS already ships fast, and the pace only picks up from here: Chrome moves to a two-week release cycle starting with Chrome 153 on September 8. Small regressions are part of the cost of that speed, but Google has generally been quick to clean them up.

What Chromebook owners should do

Open Settings, click About ChromeOS in the sidebar, then Check for updates. Your device should pull down version 16733.54.0 and ask for a quick reboot to finish installing it. If nothing shows up right away, our guide to updating ChromeOS manually covers what to do when the download stalls. On a managed Chromebook at school or work, the timeline depends on your admin’s update policy, so the fix may take a little longer to land.

If you’d been chalking up stuttery split-screen work, a laggy stylus, or a Bluetooth headset that keeps dropping to a bad day rather than a bug, it’s worth checking your version number before troubleshooting further. Anything still on 151 without the .54 build is running the release with these known issues.

Chriss

Chromebook repair specialist at chromebookfixes.com. Every guide is tested on real devices before it is published.

Did this fix work for you? Report back

Tell us the model and what step fixed it — it helps the next reader. Your e-mail is never shown.