Googlebook’s first update frees up to 6GB of RAM and fixes the Zoom crash

If you buy something from a link in this article, we may earn a commission. Learn more

Googlebook’s first software update is out, and the headline fix is memory. Build 17.CL3B.260622.286.R2 changes the NPU driver and trims AICore’s footprint, freeing 3 to 6GB of RAM on the 16GB models. On a machine where the AI stack is the point of the product, that memory was the tax. The tax just dropped.

The update is rolling out to all five launch models. Check for it under Settings, then System, then Software updates, then System update.

Context for the timing: the platform is six weeks old. The launch wave put five machines on sale from Acer, ASUS, HP, Lenovo, and Dell, priced as mainstream laptops rather than experiments, with the Lenovo 15 at $1,099.99 as the big-screen flagship of our bench coverage. Owners have had just long enough to build a list of complaints. This build reads like it was written from that list.

The RAM fix, model by model

Google names three machines for the largest recovery: the Acer Googlebook 14, the ASUS Googlebook 14, and the Lenovo Googlebook 15, the 16GB configurations our launch coverage tested. Between the NPU driver change and the AICore reduction, those models get 3 to 6GB back for applications, which on a 16GB laptop is the difference between the AI features running alongside a full browser session and the AI features evicting it.

Put the recovery in proportion: 3 to 6GB out of 16GB total is a fifth to more than a third of the machine’s memory, returned by a software update.

AICore is the system service that runs the platform’s on-device AI features, and its resident footprint was the standing cost of keeping those features ready. Trimming it without removing the features is the kind of fix that only shows up once a maker has real usage data from real owners, which is what six weeks of sales provides.

The rest of the changelog runs to roughly 30 fixes. The pattern across them is first-month hardware friction: crashes, black screens, and peripherals, on machines that have been in owners’ hands for weeks rather than months.

The fixes that will get noticed

Zoom backgrounds stop crashing. DRM video no longer blacks out on external monitors, a bug Google ties to the HP 14 and Dell XPS 13 specifically. Bluetooth audio lip-sync improves on those same two machines, BLE mice reconnect reliably, and a USB microphone fault is fixed.

Two fixes are Acer-specific: the keyboard and trackpad now behave after the machine comes out of tablet mode. A lock-screen PIN race condition is closed, the kind of bug that surfaces as an intermittent refusal of a correct PIN. A boot-slot fault that could strand a machine on the wrong system image is fixed as well, and the Linux Terminal picks up its own round of repairs for the developers who bought the Lenovo 15 as a coding machine.

Security, and what this build says about the platform

Underneath the fixes sit the November 1, 2026 security patch level, roughly 60 CVE fixes, kernel 6.18, and updated Ti50 firmware for the security chip. For a platform six weeks old, the cadence is the story as much as the contents: a monthly security rhythm and a public changelog, kept from the first update onward.

After the install, the build string in Settings should read 17.CL3B.260622.286.R2. If it reads anything earlier, the update has not landed yet and the manual check under Software updates is the way to pull it. Owners who bought on launch day have the most to gain here, because they have been running the buggiest build the platform will ever ship.

For shoppers still deciding, the changelog is a buying document now. A platform that publishes its fix list, keeps a monthly patch rhythm, and answers its first month’s complaint list in its first update is making the support argument that new laptop categories usually fumble. The hardware questions from launch week stand, and they are the right questions to keep asking through the holiday sales. The software ones just got shorter.

Our launch coverage of the ASUS 14 and HP 14 flagged the memory pressure and the peripheral rough edges as the platform’s early costs. This build answers both lists directly, which is what a first update is supposed to do.

The hardware story is still moving underneath the software one. Lenovo’s Duet M detachable keyboard has already surfaced in filings, pointing at typing away from the screen as the platform’s next accessory play, and the five launch makers built their Googlebooks as the start of a line rather than a one-off. A first update that lands six weeks in, with the RAM tax cut and the peripheral list answered, is how a platform argues it intends to stay.

Install it before judging the machine. A Googlebook that sat on the launch build is not the Googlebook this changelog describes, and the 6GB at the top of the range is too much memory to leave unclaimed.

Love our content? Sign up for our newsletter today. No ads, no spam, just links to our latest articles!