Skip to main content
1997245
1997245
Level 1.5: Cupcake
October 12, 2026
Question

Latest update is crashing all my Chromebooks at work one by one.

  • 6 replies
  • 52 views
  • Translate All • Beta, powered by Gemini

Multiple Chromeboxes are fatally crashing and cannot be restored with Recovery after the last update.
Units affected so far are the Asus Chromebox 3 TEEMO D7-A3B-B4Z-S5A-A92 and Acer Chromebox CXI3 D15Q1

Stable beta, nothing will bring them back to live. Maybe for a short term but they auto update and die again. Stable even mentions that the mirror image is outdated. I just downloaded a minute ago.

Why is Google allowing this?! It started last week.
We have a few spare chromebooks and after that it is over. 
I am so done with this system. They just end production machines at will and do not seem to notice or care at all.

Not more ChromeOS for me, I am out. This does not belong in a professional setting!!!!!!

6 replies

Lynda
LyndaCommunity Manager
Community Manager
October 12, 2026

 ​@1997245  I'm really sorry to hear you're experiencing these issues.

Because this behavior is likely nuanced to your specific environment and could require log analysis to resolve, I highly recommend raising a ticket with our dedicated Technical Support team so they can investigate this with you directly.

Here are the best next steps to get this resolved:

  1. Submit a Support Ticket: Our team is available 24/7 to help get you back up and running. You can find step-by-step instructions on how to raise a ticket here:
    https://support.google.com/cameyo/answer/16400244#zippy=%2Ccustomers-onboarded-on-or-after-march

  2. Run and Attach Diagnostics: If possible, please run a quick diagnostic check on an affected device and attach the output to your initial ticket so the engineers can begin reviewing it immediately. More information on how to do this here: https://support.google.com/chrome/a/answer/6270826?sjid=176119543062165249-EU

  3. Check Your Extended Support Settings: While the two device models you mentioned have extended support available until 2028, this must be manually enabled. Could you double-check if you have officially opted into extended support within your Admin Console? You can find the steps to check and enable this setting here: https://support.google.com/chrome/a/answer/14328032

Please let us know how you get on, the community is here if you need any further help along the way!

Translate • Beta, powered by Gemini
    1997245
    1997245Author
    Level 1.5: Cupcake
    October 12, 2026

    Support portal does not have the topic hardware/ChromeOS… How to file it?

    Translate • Beta, powered by Gemini
    Lynda
    LyndaCommunity Manager
    Community Manager
    October 12, 2026

    Hi ​@1997245 

     

    Here are the steps you’d follow:

    1. Sign In & Select Organization:
      Log into the Google Cloud Console Support Page using an account provisioned with Support Administrator or Cloud Support Editor IAM privileges. Use the project/resource dropdown picker at the very top of the console toolbar to select the Organization resource or specific project associated with your Chrome Enterprise/ChromeOS entitlements.
    2. Navigate to Cases:
      From the main left-hand navigation pane, select Support and click on Cases.
    3. Initiate New Case:
      Click the Create Case button located near the top of the interface.

     

    Use the following structural filters to route your ticket cleanly to the Google Chrome Enterprise team: 

     

    Support Field Component Selection Strategy / Detail Needed
    Product Family Select Chrome Enterprise or Chrome / Maps / Workspace Partners 
    Category / Component Drills down to ChromeOS. Choose this to differentiate from Chrome Browser or Google Workspace issues.
    Sub-Component / Feature Refine by selecting the exact operational vector (e.g., Device Management / Enrollment, Active Directory Integration, Operating System Crash/Kernel, Flex, or kiosk deployments).

     

    Hope this helps!

    Translate • Beta, powered by Gemini
      1997245
      1997245Author
      Level 1.5: Cupcake
      October 12, 2026

      Hi,

      Thanks for the instructions. I followed them: I went to Support → Cases in the Google Cloud Console and selected our organization (intervlag.nl) in the resource picker. I can’t create a case there, though. The page shows two messages:

      “You don’t have permission to view cases for the currently selected resource.”
      “Support cases will be listed here. Creating cases for the selected project is not available with your current support plan.”

      So it looks like our account doesn’t have the Support Administrator or Cloud Support Editor role at the organization level, and our Cloud support plan doesn’t allow technical cases. Our Chrome Enterprise / ChromeOS entitlement may not be linked to Cloud Support at all.

      Should I add the IAM role and/or a Cloud support plan? Or should Chrome Enterprise / ChromeOS cases go through the Google Admin console (admin.google.com → Help → Contact support) instead?

      Thanks!

      New instructions were too complicated for me and also for Claude ai.
      I am logged in as an owner of my workspace owner, but these are unmanaged Chromeboxes. This update crashes them on my Gmail as well. I do not understand why I need to go through this bureacratic wall. You can tell me honestly, shall I bin them? I cannot run a business at the mercy of Google while paying top dollar. I do not understand what my money is going towards this way.

      Translate • Beta, powered by Gemini
      Lynda
      LyndaCommunity Manager
      Community Manager
      October 12, 2026

      Hi ​@1997245 it sounds as if you do not have the right admin access; but yes try the admin.google.com → Help → Contact support as a workaround for now. However we would always suggest atleast 1 user within your organisation be set up with adequate privileges to contact support.

      Translate • Beta, powered by Gemini
      1997245
      1997245Author
      Level 1.5: Cupcake
      October 12, 2026

      Yeah you would think ‘owner’ would suffice, but apparantly that does not follow logic anymore these days.

      Translate • Beta, powered by Gemini
      Terms & ConditionsAccessibility statement