Update crashed managed Chromebox... again

  • 1
  • Problem
  • Updated 3 years ago
  • Acknowledged
  • (Edited)
As in description, Chrome 44.0.2403.125. However, non-managed Chromebox, Chrome 44.0.2403.156, just rebooted RV player and kept on going. And I am not sure which update has caused the problem. Again, it seems $150 for management license was a waste of money because our managed devices were set to 'Disallow auto-reboots' after updates and they were limited to 44* Chrome version.
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb

Posted 3 years ago

  • 1
Photo of Byron

Byron, Keener

  • 9,658 Points 5k badge 2x thumb
Official Response
Darius, we just pushed a release that we have specifically configured to not restart Chrome. It is supposed to sit and wait for the next restart before it is applied. I don't know what to tell you other than we just shipped a release of our new Native Windows Player to QA today and it should be available publicly within a couple of weeks, and the Linux version will follow shortly thereafter. We need some options as we can't seem to reliably control what happens on Chrome App Players in some situations. In others it works great. We just can't predict when and where. We have reported the problems but unfortunately there is not much more that we can do at this point. I am not sidestepping responsibility here. This is out problem and we are working with Google to get it rectified and and at the same time we are shipping options, so please accept my apologies for what happened! Thanks!