Checking for updates during OOBE appears to be nonfunctional
Reported by
willg...@gmail.com,
Dec 20 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9086.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2951.0 Safari/537.36 Platform: 9086.0.0 (Official Build) dev-channel edgar Steps to reproduce the problem: 1. Setup device for first time or powerwash 2. Get to the step where it checking for updates What is the expected behavior? Updates get downloaded and applied during OOBE process What went wrong? Throbber spins briefly with a checking for update message. Nothing happens after that and you just proceed with the setup process. Updates don't happen until after setup and you're on the desktop. Did this work before? N/A Chrome version: 57.0.2951.0 Channel: dev OS Version: 9086.0.0 Flash Version: Chromecast and Google Home apparently does update during setup and it would be great if Chrome OS would do the same. So many issues like the boot loop bug and others could be avoided if the device was up to date before a user actually logged in.
,
Dec 29 2016
#CBC-RS/TC-watchlist
,
Feb 23 2017
It's a difficult tradeoff. Forcing an update during OOBE slows the first run process a lot. It's also especially costly for schools and enterprises where they're often bringing up a lot of devices at once. Some of these users also have their fleet pinned to older versions (for a variety of reasons) and forcing updates during OOBE breaks the ability to do that. The current rule should be (roughly): * If device is running M52 or older -> update during OOBE. * Otherwise allow OOBE to complete and do update in the background. Is that currently not happening?
,
Feb 24 2017
According to bug description, these devices are on dev channel which does not support forced AU at OOBE. You need to move to Stable channel and this will do the powerwash too
,
Mar 3 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 Deleted