You are currently viewing 
<span class="bsf-rt-reading-time"><span class="bsf-rt-display-label" prefix="Reading Time"></span> <span class="bsf-rt-display-time" reading_time="2"></span> <span class="bsf-rt-display-postfix" postfix="mins"></span></span><!-- .bsf-rt-reading-time -->Chromebook users can’t get past the Google Play ToS when setting them up

Chromebook users can’t get past the Google Play ToS when setting them up

Share the Tech Love (Andrew Myrick)
2022-05-17 18:51:49

What you need to know

  • A new bug is preventing users from setting up new or restored Chromebooks.
  • The bug appears when reaching the Google Play Terms of Services page in the setup process.
  • There’s no official fix for the issue yet, but there are a couple of workarounds.

While we’re big fans of Chrome OS and Chromebooks around these parts, that doesn’t mean the platform isn’t without its flaws. Google is hard at work, implementing features that should have already been available, along with a few that you wouldn’t expect.

But the last thing you would want to deal with when setting up a Chromebook after a Powerwash or out of the box is a random bug. Unfortunately, it seems that’s exactly what’s happening to some users, as first reported by Android Police. When going through the initial setup process, you might not be able to get past the “Google Play Terms of Service” screen.

Users in the r/ChromeOS community have run into a “Something went wrong” error message when reaching the aforementioned screen. Making things even more frustrating is that there doesn’t seem to be any mention of what is actually wrong. The only description offered when seeing the error page is “Google Play Terms of Service cannot be loaded. Please check your network connection and retry.” And as you might expect, clicking the Retry button continues to put you back in the same place as before.

(Image credit: u/mik9900)

We ran into this issue on one of our Chromebooks that was going through a fresh setup after entering Developer Mode. At the time, it was just attributed to the fact that Developer Mode is extremely buggy and could have been causing the issue. A simple forced restart (pressing and holding down the power button) managed to get things back in working order after the Chromebook was back up and running.

Source Link

Leave a Reply