Oct 31, 2022
Artifacts in google sheets
Details
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
Nov 3, 2022
I have no clue why that fixed it, but for me, that worked.
Diamond Product Expert lagagnon recommended this
Helpful?Upvote Downvote
Oct 31, 2022
Silver Product Expert Martin Whitehead recommended this
Helpful?Upvote Downvote
Oct 31, 2022
The workaround was to move that device temporarily onto Beta channel where the issue did not present itself on the M106 release (Beta channel us usually one release ahead of the Stable channel). I would not recommend using Developer channel as this is more likely to be unstable.
By moving the Chromebook back onto Stable channel it will not roll the version of ChromeOS back but wait until the Stable channel matches the version number on the device. If you want to get the device back to the current Stable release of ChromeOS you can use the Chrome Recovery Utility extension.
Original Poster Adam Kortus marked this as an answer
Helpful?Upvote Downvote
All Replies (4)
Oct 31, 2022
Hi Adam Kortus
Please see if disabling hardware acceleration in chrome:flags resolves your issue.
- Mike
Oct 31, 2022


The workaround was to move that device temporarily onto Beta channel where the issue did not present itself on the M106 release (Beta channel us usually one release ahead of the Stable channel). I would not recommend using Developer channel as this is more likely to be unstable.
By moving the Chromebook back onto Stable channel it will not roll the version of ChromeOS back but wait until the Stable channel matches the version number on the device. If you want to get the device back to the current Stable release of ChromeOS you can use the Chrome Recovery Utility extension.
Original Poster Adam Kortus marked this as an answer
Nov 8, 2022
I managed to switch to beta and update to 108 which seemed to fix the issue. I then switched back to stable and its rolled me back to 107.0.5304.92
Is it fine to leave my chromebook in beta, I've never done this before?
Last edited Nov 8, 2022
Nov 8, 2022
On option would be to continue on Beta channel until the Stable channel moves onto M108 then think to move back if the issue is resolved.
I have no clue why that fixed it, but for me, that worked.
Diamond Product Expert lagagnon recommended this
Nov 16, 2022
Tinkering with hardware acceleration settings (which was suggested elsewhere) did not help.
Switching to Beta channel seems to have solved the issue.
Switching to Beta channel seems to have solved the issue.