I was on Beta build  60.0.3112.41 before switching to the Stable channel. 

Believe this was also an issue on the Dev channel.

*use

I have this problem on the same platform . I have also performed a recovery without any change in this behaviour.

While using this Beta release a restart to update arrow appeared so I made an error report(alt+i) before letting the the restart take effect in the hope it will provide some clue to the problem.

Same issue started with my Samsung XE300M22 about a week ago as well. So far, every time I get this message, turning the Chromebox off and back on let ChromeOS start. But the issue will start again on the next restart.

Tried waiting for several hours on the critical update wait screen on boot up but this had absolutely no impact.

Chromebox is on 60.0.3112.41 beta

Same on my Samsung Chromebox on Beta 60.0.3112.41.

I can start as follows:

- Start the machine with power button.
- Get the "Applying critical update" screen (which never goes away).
- Force restart using power button.
- Starts into welcome screen (user login).
- Log in.
- Screen goes black.
- Wait for 10-15 minutes.
- ChromeOS suddenly appears as normal.

I'm having this issue on Chromebox 3. White screen that never finishes, I even overnight.

Holding power button to force off, then rebooting, works. Not had to wait more than usual time for it to start up though.

OK, today the update to 60.0.3112.50 took about half an hour for the "Applying critical update" phase, and then nearly an hour for the black-screen phase. But it did upgrade OK.

I wonder if it's something to do with the /Downloads folder being full of hundreds of files (about 2GB), or because there's a crouton chroot. Could these things slow down the upgrade and/or startup?

Just manually updated to the latest Stable release.  Critical Error message back. Switched to the Dev channel. Same issue.

Now I have to press the on/off button to turn off Chromebox.  Then I press it again to boot and sign in.

Not a good thing to do every morning.

Please fix this hang up.  Thanks.

Yup, still happening. Beta channel.

There are multiple users reporting this problem on CBC.
#CBC-RS/TC-watchlist

https://productforums.google.com/forum/#!topic/chromebook-central/qFT5X-X6_3w

Happening for me on the stable channel, no chroot, nothing else on the ssd and on my Intel I5 samsung chromebox.  

I do have the same problem. Getting the "Applying critical update" message. Even after a night of doing this it hasn't come back. I need to power cycle and try. This is the second time happening. Mine is a Samsung with i5 processor. 

same problem as above "applying critical update" and circle goes around and around
turned off and on again and able to use normally
have chrome box XE300M22
thanks

Same issue with samsung chromebox.

If you are having this problem, please "star" this issue by clicking the star in the upper left corner. Star counts help with triage and prioritization.

No need to post a comment unless you have new information (but please star as well). Thanks!

Let me know if you want me to bring my stumpy in for diagnosis. -gps@

Isn't this likely a regression from the previous release? It's getting annoying that I have to leave my machine powered up 24 hours a day. Is anyone actually working on this?

Critical error failure to update Samsung Chromebox cropped up when Google Play Android support was added to Samsung Pro (Intel cpu) device as Chrome release moved from 59 to 60. Chromebook Pixel 2013 does not have this issue, neither does Samsung Pro 2016, however both devices took 2 updates (not 1) to complete the critical update. #gdgsea

Our office uses eight-8 black Samsung ChromBOXes i5.  Today, our fourth-4 or 50% of the eight-8 have become affected or infected with the 'Google white screen' perpetual update error. We can still unpluging the devices, waiting an hour (+/-),then re-power, which will re-boot these devices, until the user 'sighs out' signs out, the the error repeats.

Addtional problem's noticed:
-At the onset of the Google-white-screen, the users private password is displayed in the upper left corner on the screen for approx. 60-90 seconds.

-While seeming to work normally, YouTube videos will not open or play, guiding the user to download an adobe flashplayer update.

-One of our office Hisense ChoomeBOOKs, now has the Google white screen. It can not be turned on/off and reser, therefore, this hardware has been is broken.

Our office uses eight-8 black Samsung ChromBOXes i5.  Today, our fourth-4 or 50% of the eight-8 have become affected or infected with the 'Google white screen' perpetual update error. We can still unpluging the devices, waiting an hour (+/-),then re-power, which will re-boot these devices, until the user out' signs out, the the error repeats.

Addtional problem's noticed:
-At the onset of the Google-white-screen, the users private password is displayed in the upper left corner on the screen for approx. 60-90 seconds.

-While seeming to work normally, YouTube videos will not open or play, guiding the user to download an adobe flashplayer update.

-One of our office Hisense ChoomeBOOKs, now has the Google white screen. It can not be turned on/off and reser, therefore, this hardware has been is broken.

Ditto for all the above issues. Samsung Chromebox i5 asks to "install critical update". After 48hrs, I rejected the "Don't switch off" & restarted & seemed to work OK. Intermittent restart white screen issues etc. as above comments.. please help!

Version 60.0.3112.80 (Official Build) (64-bit) Samsung ChromeBox i5

The workaround for me is when my chromebox is doing this: Hold its power button down for ~15 seconds.  This will force power it off.  Upon the next boot it skips the upgrade attempt.

As suggested by comment 25
His solution seems to have worked for my black chromebox XE300M22 as well

Prompted by comment 26. I went looking through the Chromium commit messages prior to June 22 comment number 1 (here). The stable channel has a 6 week release schedule. Backing up to May 11, 2017. 

Searching for commits related to FirmWare not updating. The mostly likely commit I could suspect is Chromium gerrit 505976 (Merged as ac3d7f5 ): eclass: cros-firmware: Create firmware updater script only if available. This took me a couple of hours sleuthing around.

Googler picking up this issue might want to know I didn't find any direct correlation specific to Samsung Chromebox series 3 models. Issue looks like an unintended coccinelle transformation.      

Deleted: IMG_20170814_170038.jpg 5.7 MB

	IMG_20170814_170038.jpg 5.7 MB View Download

Same problem here with several samsung i5 chromeboxes from a long ago google developer conference.  Started last week.  Sticks on 'critical update' message as per post 27.

same issue here

Doesn't support for this device end this month?

Maybe this is how they "get the word out".

Unfortunately I have a number of Chrome devices that are going to start dropping dead like this every few months.

I believe that support ends on March 2018.  However the device will still be usable it just won't get further updates/fixes. At any rate, I'd expect the device to at least be in a working state.

Which is a real shame.  The i5 versions of this chromebox are still among the fastest chrome devices and I've been able to pick up several for around $100.

Same problem here. It started when the machines upgraded to Stable version 60. The machines are managed via the ChromeOS Management Console. Our company uses 30 Samsung Chromeboxes from 2013. We are very happy with them. Very Fast. And we really want to keep using these machines for a few years. Even willing to pay for longer software updates. It is very bad for environmental reasons to make all these wonderfull machines obsolete.

This is getting silly now. All users of a Chromebox i5 seem to be affected but most of them are suffering in silence as they do not know about this page.

ChromeOS has become unusable as we have to boot, unplug, replug and reboot EVERY DAY......And we said Windows was hopeless!

I starred this weeks ago and still no updates via the stable or dev channels....Come on Google, you are letting us down,

You only have to press the off button and then press again 5 seconds later.

If I do that @comment 34 I get "Chome OS is not detected" (Grey Screen) and have to unplug and replug.

Even if you only have to do things your way, is that not unnaccepatable?...we actually bought a system that worked.

It varies. I turn it off and back on via the switch. Sometimes I have to do this 3 or more times. Sometimes I get the message that Chrome isn't detected and to plug in my USB stick to rebuild it. I don't recall the precise wording now on the last one. It isn't exactly the same every day. I do have to take multiple tries every day and it is getting pretty annoying though.

I totally agree @comment 36.....I really do not want to turn this into a chat page but as you say,it is getting pretty annoying.

Hopefully if we keep annoying Google, as much as they are annoying us..we might get some action.

Our Samsung Chromeboxes do not work, when we bought them, they did.  You have an obligation to make them fit for purchase. Please do something to help.

Thank you.

Sorry if this getting a bit 'chat page', but yes, we are getting deeply
frustrated by this issue. It's taking our office so much longer to start up
our Samsung Chromeboxes in the morning. USB recovery stick in, restart,
switch off, restart, press and hold...grrr.   Just checking with @comment
37 is there anything we can do to "keep annoying google", because if this
is it, it's pretty poor. Our Chromeboxes no longer work correctly, and we
really feel let down by a 'broken' operating system.

Totally agree with comments.  

Can anybody more knowledgeable than I say if this is being fixed / is likely to be fixed / is never going to get fixed???

It'd be nice if they could roll the OS back to the version of 59 that
worked until they straighten out the problems with the current version.

Chromeos version: 9765.45.0 / 61.0.3163.67

Noticed "Your system is applying a critical update. Please do not turn it off" message after soft reboot.

Repo steps:
1. sign in to the device.
2. click on uber tray - > shut down button to power of the device.
3. wait for few secons (~60 seconds).
4. Power on the device.

Result:
Getting "Your system is applying a critical update. Please do not turn it off" message.
Need to power off and power on again to fix this issue.

The same for my Samsung Chromebook. I did a PowerWhash and back to happen

Deleted: 15041107211781819748267.jpg 3.1 MB

	15041107211781819748267.jpg 3.1 MB View Download

Welp, I guess that saves me the 15 minutes of looking for my B840 chromebox to 'fix' this problem

Dupe of https://bugs.chromium.org/p/chromium/issues/detail?id=733014 ?

Just to be clear for anyone new to this: there is nothing you can do to fix it. What you need to do is a) star this issue (top left) and b) wait for Google Chrome OS poeple to sort it out.

Confirmed that this is overwhelmingly affecting Samsung Chromebox Series 3 devices running M60.

Exactly the same behaviour here. Samsung i5 Chromebox 3. After 2 hours in the update screen, I rebooted and everything seems to work.

Same here... Samsung Chromebox 3 Celeron B840.

Please fix ASAP.

Only computer used by my 89 years old father, and chosen by its reliability... Until now.

Come on you Google people, do your job as promised... and provide us the solution in a timely manner.

Thanks in advance, 

Same problem here too. Stable Channel. 

Just started for me. Performed a recovery and Chromebox worked until I cold booted it. Some of the suggestions here worked for me (notably, turn off and turn on right away). Very annoying since this is the main Internet browser system for the family.

Recovery shows device as STUMPY OLIVE A-C 0203

Version 60.0.3112.80 (Official Build) (64-bit)
Platform: 9592.71.0 (Official Build) stable-channel stumpy
Firmware: Google_Stumpy.2.102.0
Channel: Stable
Blink: 537.36 (@)
V8: 6.0.286.46
Build date: Thursday, July 27, 2017

Amazing this has gone on so long. My Samsung Chromebox started having this problem a few days ago. Using the power button to go off/on is the only way I can get to the password screen. Also found out my password manager, LastPass, no longer works, just shows the extension with the message "This extension may have been corrupted."

Comment 55 - I suspect your Lastpass issue may be a different problem. I had the problem described here for at least a month. I have been using Lastpass for a couple of years. I have had no corruption issues.

Thanks, You are probably right. It seemed strange to me that when my
chromebox started getting the continuous critical update last week,
LastPass failed on both my chromebox and chromestick and after a
powerwash and reinstall, LastPass has the same failure. Also odd is my
Windows 10 Chrome LastPass works perfectly. I really don't know what to
think.

It appears that the Lastpass problem is not associated with the critical
update problem. See here
https://forums.lastpass.com/viewtopic.php?f=12&t=268795&start=200 . This
article suggests a get around which has worked for me.

Thanks for your help. I will look at LastPass instead of Chrome OS.

I'd imagine that the tough part is all the people who got this and have
since presumed their chromebox is defective and tossed it.

I'm very surprised this has gone on as long as it has without at least a
rollback to the version that worked.

tbroch@ per bhthompson@ this is a dupe of https://bugs.chromium.org/p/chromium/issues/detail?id=733014. Can you please confirm?

Hello guys, same here with my CBX Stumpy (i5 samsung).
Please big G engineers fix ASAP!

Alex

Nope, no luck for me, switched to beta channel, updated to 61.0.3163.80, and still get "Applying critical update" when I restart. Has this patch been applied to this build or should I switch to Dev channel?
Thanks.

Pull the plug again, reinsert and reboot.  Should work after that.  Mine
hung on the restart after applying the update as well.  That fixed it.

Thanks, gave that a try (pulled power cable for 60 seconds), still no luck. It's been sitting on "applying critical update" for 10 minutes, did you get the "critical update" applied then were able to restart? It's looking suspiciously like it's still going nowhere...

The "Applying Critical Update" message only appears every other boot.  I suspect the comments claiming their Chromeboxes are fixed are mistaken, as they will see the message at next boot.

The simplest work around is to simply use the keyboard combination to put your Chromebox to sleep.  Don't power off.  When the fix comes down the pike, the work around will be unnecessary.

Well, I was already on the dev channel to see if that would do anything
(which it didn't), I started the box, went to update and it updated, then
it asked for a restart.  I restarted and it hung on critical update,
probably because it was still running the dev load from last week and
hadn't applied the update.  I pulled the plug and started it again and it
was good after that.

Dang. Spoke too next restart after applying latest Chrome beta channel update CBX i5 (Google I/O machine) still has the the critical error after latest update. Saw this fix and assumed it had landed (wrong). 
https://bugs.chromium.org/p/chromium/issues/detail?id=733014#c44

The fixes referenced in  crbug.com/733014#c44  landed in

chan   : platform rev  : chrome rev
------------------------------------ 
dev    : 9901.7.0
beta   : 9765.57.0
stable : TBD after testing dev/beta

CBX i5 (stumpy) is currently on:

chan   : platform rev  : chrome rev
------------------------------------ 
dev    : 9901.5.0      : 62.0.3202.8
beta   : 9765.53.0     : 61.0.3163.80
stable : 9592.71.0     : 60.0.3112.80

Should hit dev soon I'd think.

Thank you the referenced fixes landed today on my machine in version 61.0.3163.110 (Official Build) beta (64-bit). Its really great to switch my Chromebox on and it just works. Cheers.