This is an Intel Core Ultra laptop, not a Windows machine. Even so, it matters to anyone who buys, supports, or deploys PCs. A launch-week "bricked out of the box" report is the kind of failure that makes IT teams hesitate over a new platform.
What owners are reporting
At least four Redditors have reported that their Acer Googlebook 14 units are stuck in a boot loop. The laptop shows an "Updating" screen for a few seconds, restarts, and shows the same screen again, cycling indefinitely.
The pattern appears to start during initial setup. One owner described the sequence this way:
- They booted the laptop and connected their phone.
- The laptop prompted for an update, and they accepted it.
- For about an hour the laptop showed the Acer screen for a few seconds, then "updating" for around ten, and repeated that.
Android Headlines described the loop as a restart roughly every 15 seconds. Its account of the trigger differs slightly. In that report, the user restarted the laptop to continue setup and then got stuck on the "updating your device" screen. The accounts agree on the symptom but not on exactly what set it off.
Recovery didn't help either
The recovery environment didn't help at least one owner. The recovery screen reported no internet partition, so internet recovery wasn't possible. Only USB recovery was offered, and there were no files to use for it. The owner said "It's been bricked even before it was used."
TweakTown and VideoCardz also report that some affected buyers returned their laptops to Best Buy, with some choosing different Googlebook models instead. These are individual decisions. Nothing reported so far points to a recall, a replacement program or a retailer-wide policy.
The Google employee's suggested workaround
Google employee Mishaal Rahman replied on Reddit. As Android Authority describes it, he suggested unplugging all USB devices, then holding Escape and F2 and quickly pressing the power button to enter the recovery menu. From there, users unlock the bootloader via Advanced > Unlock bootloader, then re-lock it after the device boots again. TweakTown adds a final step: choosing to boot from the internal disk.
Treat this as a suggestion, not an official fix. Reports say it hasn't worked:
- One owner said they tried to unlock and relock the bootloader with no change.
- TweakTown says at least one owner couldn't find the unlock or relock options at all.
- Android Pure's summary says owners with an Acer unit stuck on the Updating screen should raise a warranty claim instead of experimenting with the bootloader. That is that outlet's advice, not guidance from Google or Acer.
Bootloader changes are not trivial. Unlocking a bootloader generally changes a device's security posture, so it's reasonable to be cautious. That is general industry knowledge and not part of the reporting.
What isn't known
The reporting leaves several things open:
- Cause: nobody has identified why the loop happens, and no update or build number has been named.
- Scale: the number of affected devices remains unknown. TweakTown notes that at least one Acer Googlebook 14 owner completed the update without problems.
- Other models: Android Headlines says it hasn't happened with other models, at least not that have been reported. That is an absence of reports, not proof.
- Response: no official fix has been announced, and I found no formal statement from Google or Acer.
One unrelated item turned up in my search. There is a separate Acer Community thread about Chromebook Plus Spin 714 boot loops after a Chrome OS update. Nothing connects it to the Googlebook reports, so I wouldn't read anything into it.
The product involved
The Acer Googlebook 14 is the cheapest of the five Googlebook models launched and the only convertible. Acer's own materials give the model number as GP714-91N and say it runs Googlebook OS. Specs include:
- Intel Core Ultra 7 355 or Core Ultra 5 325 processors. (Acer's release lists both options.)
- A 14-inch 2880x1800 OLED touchscreen.
- Up to 32 GB of LPDDR5X memory.
- Up to 512 GB of PCIe Gen 4 NVMe storage.
- A Google Titan-C security chip. (Acer lists it as a system-integrity layer.)
Acer lists North American availability in October 2026 starting at USD 899. Those details identify the machine. Nothing in the reports ties the loop to any particular hardware component.
Practical guidance
If you're thinking of buying one: the reports are an early cluster, not a measured failure rate. It's reasonable to wait for official acknowledgement or a fix before buying. If you do buy, keep the return window in mind and be ready to use it.
If your unit is looping:
- Note the model (GP714-91N), the point in setup where you accepted the update, and the exact screen sequence.
- Write down any recovery message, such as the missing internet partition, and any menu options that don't appear.
- Contact Acer, Google support or your retailer for device-specific next steps.
- If you try Rahman's recovery steps, treat them as an unconfirmed suggestion. They may not work, and the unlock and relock options may not appear.
The wider lesson
A platform's first week is when reliability is judged hardest. A failed first-boot update is especially damaging because the owner has no working system to troubleshoot from. Missing internet recovery and missing downloadable USB recovery files, as one owner described, would make that worse.
The same questions come up on Windows hardware: how robust is the first-run update path, and is there a published recovery image when it fails? If a vendor can't answer those on day one, buyers will notice. The facts here are still thin. Four reports, no cause and no fix aren't a verdict on Googlebook. The next step is for Google or Acer to say something official, and so far the reporting shows no such statement.