Old chromebooks stopped working today??

[PotNoodleTech]

Ooh weird one we've had all our old Prowise Chromebooks stop working today no one can log on - just goes straight back to the login screen.

 

Anyone else seen this? I am assuming google have changed something to do with out of date chromebooks without telling us!!

[ovenchips]

Just checked some of our oldest stock (2016~ HP G5), all still seem to be working OK, signing in fine.

[timbo343]

Ooh weird one we've had all our old Prowise Chromebooks stop working today no one can log on - just goes straight back to the login screen.

 

Anyone else seen this? I am assuming google have changed something to do with out of date chromebooks without telling us!!

 

Do you have an idea of how old these Chromebooks are?

[PotNoodleTech]

Theyre 2018 enrolled but I get the feeling that they were sitting around on prowise's shelf before we bought them as they ran out of google support in 2020!!!

 

It's weird the older dells we have are working and just enrolled some HP G6's successfully.

 

Only seems to affect the prowise ones.

[sigma]

Ooh weird one we've had all our old Prowise Chromebooks stop working today no one can log on - just goes straight back to the login screen.

Anyone else seen this? I am assuming google have changed something to do with out of date chromebooks without telling us!!

No unexected items in the bagging (filtering) area?

[PotNoodleTech]

No unexected items in the bagging (filtering) area?

 

I don't think so - If it was that should affect all our chromebooks not just the one model?

[sigma]

I don't think so - If it was that should affect all our chromebooks not just the one model?

 

Strictly speaking, yes, but there'll be something "different" somewhere.

[Julian]

We have had our Chromebooks, stop wireless connecting! They needed a Chrome O/S update. USB to ethernet adater, for wired networking, to run the update, solved the problem, mostly. Some did need a powerwash, and then a reload of settings from Google.

[DCGIT]

We've had the same issue today aswell on 2 x HP Chromebook 14 Chromebooks running chrome version 76.

[PotNoodleTech]

We've had the same issue today aswell on 2 x HP Chromebook 14 Chromebooks running chrome version 76.

 

Sounds exactly like what I am having I think the prowise ones were on 83 or 86 a bit newer but still old and now unusable by the look of it!

[DCGIT]

I've just tested with a USB to Ethernet Adapter as suggested previously in the thread, but this has made no difference, appears that Google have done something that has stopped certain models being able to work etc.

[simpsonj]

I received an email from Smoothwall that Google are phasing out MV2 Extensions starting June 2024, so anything under ChromeOS 127 will no longer be supported by Smoothwall via the Google store (You have to install their own hosted app instead). Not sure if that's related?

[tom_newton]

Chrome 88 will be a bare minimum for Chrome soon with the MV3 changes. Sadly I suspect you may be fighting a losing battle with these devices.

[PotNoodleTech]

Hi Tom - I literally cant find any info from google on OS versions under 88 stopping working - are you aware of any information they've put out?

[FN-GM]

I am assuming google have changed something to do with out of date chromebooks without telling us!!

 

To be fair, Google publish their support lifecycle of Chromebooks years in advance.

[tom_newton]

The new extension rules (manifest V3) are only supported post 88 - https://developer.chrome.com/docs/extensions/develop/migrate#:~:text=displaying%20a%20warning.-,Manifest%20V3%20is%20supported%20generally%20in%20Chrome%2088%20or%20later,information%20for%20individual%20API%20members.

The transition away from MV2 starts in June

https://developer.chrome.com/blog/resuming-the-transition-to-mv3

 

So not a hard "no support" but it is going to be tricky to get extensions that work, and I suspect other things will follow shortly after

[timbo343]

The new extension rules (manifest V3) are only supported post 88 - https://developer.chrome.com/docs/extensions/develop/migrate#:~:text=displaying%20a%20warning.-,Manifest%20V3%20is%20supported%20generally%20in%20Chrome%2088%20or%20later,information%20for%20individual%20API%20members.

The transition away from MV2 starts in June

https://developer.chrome.com/blog/resuming-the-transition-to-mv3

 

So not a hard "no support" but it is going to be tricky to get extensions that work, and I suspect other things will follow shortly after

 

Cheers Tom *goes off to find out how many Pre ChromeOS 88 devices are in our trust*

[PotNoodleTech]

Cheers Tom *goes off to find out how many Pre ChromeOS 88 devices are in our trust*

 

Yep my old ones were on 86 so I guess that's those dodo

[AndrewPowell]

Any update on this from anyone? We have had the exact same thing happen. Around 60 devices have suddenly stopped working.

I can't even de-provision them. I've tried through a hotspot, no ball. Tried deprovisioning, no ball. Can't powerwash, can't reset, can't seem to do anything with them

Two different brands, Acer and Viglen, versions 76 and 84 respectively.

They are doing exactly the same as you described, straight back to login screen after entering password.

 

Really hoping someone has something further to add, would be amazing.

 

Yes we know we need to replace, and its in the pipeline, but the cost requires levels of approval.

[PotNoodleTech]

Any update on this from anyone? We have had the exact same thing happen. Around 60 devices have suddenly stopped working.

I can't even de-provision them. I've tried through a hotspot, no ball. Tried deprovisioning, no ball. Can't powerwash, can't reset, can't seem to do anything with them

Two different brands, Acer and Viglen, versions 76 and 84 respectively.

They are doing exactly the same as you described, straight back to login screen after entering password.

 

Really hoping someone has something further to add, would be amazing.

 

Yes we know we need to replace, and its in the pipeline, but the cost requires levels of approval.

 

Have had no answers from google and they are the only people who can really answer.

 

anyone got a contact at google they could ask for us??

[timbo343]

Have had no answers from google and they are the only people who can really answer.

 

anyone got a contact at google they could ask for us??

Have you tried Oli Trussel?

[Primus]

I'm really surprised so many members are running devices that haven't had an OS update in years - are you also running Windows 7?

 

- - - Updated - - -

 

Have had no answers from google and they are the only people who can really answer.

 

anyone got a contact at google they could ask for us??

 

Would you not just expect Google to point you to their EOL policy?

[timbo343]

I'm really surprised so many members are running devices that haven't had an OS update in years - are you also running Windows 7?

 

- - - Updated - - -

 

 

 

Would you not just expect Google to point you to their EOL policy?

 

Windows 7!? More like Vista at times

[FN-GM]

I'm really surprised so many members are running devices that haven't had an OS update in years

 

I was thinking the same thing. Security is super important. Not to mention the risk of things suddenly stopping working and disrupting teaching and learning.

[timbo343]

I was thinking the same thing. Security is super important. Not to mention the risk of things suddenly stopping working and disrupting teaching and learning.

In all seriousness though, SLTs are sometimes ignorant to the fact that we as advisors tell them about insecure devices running outdated software. It's only until the devices stop working do they actually care like, crap we need to do something about this.

 

For example, some of our schools still have very old iPads which no longer support newer apps, just like how ChromeOS is going and it's only then schools have their hand forced.

 

In a way i say bravo to Google enforcing this on their devices.

 

Although schools will say, you never told us, they always seem to have an excuse.