Additional notes: If the ChromeOS was already configured with auto-launch before updating to 70.0.3538.76, the update does not affect the Kiosk auto-launch process. This only occurs if you are trying to provision a new device with ChromeOS to begin Kiosk auto-launch while already on 70.0.3538.76.

Same here. This is very urgent! Looks like the next terrible step towards what was already predicted in issues  #869234  and  #870300 . 

Same here - super urgent!!!

Same here. Has tested both on older Chromebox and on Chromebits.

Any updates on this issue?

Did anyone hear from Google on this issue?

I starred this a few days back but wanted to add that this currently affects a number of our customers and probably will soon affect many more of them as well as most of our potential customers (that we advice to use Chrome devices).

We are really hoping for a timely response to this matter.

We also are experiencing these issues. Hoping for a fast resolution as we cannot roll-out Kiosk devices now. 

Same here, can't roll out new devices. Version 69 on has been nothing but headaches for Chromebit / Kiosk mode devices.

Why has no one from Google commented on this at all? I think I mis-categorized it, should be Kiosk rather than Platform > Apps but I don't think I can change that now.

+1, this is already affecting our customers and we're receiving concerned emails. This already happened once in recent months with a Chrome OS update. 

Same here, cannot auto-launch kiosk apps after updating to Chrome OS version 70 on multiple Chromebits.

Same here!

Still no update, not a word from anyone at Google. Class action lawsuit anyone?

This is now starting to begin affecting our business badly. It would be appreciated if at least the Chrome OS team could confirm it is not excepted behavior.

Had the same problem, could not roll back. Needed older version .bin file.
Here you can find older OS files - https://cros-updates-serving.appspot.com/

Shame on google. Was not easy to find.

@dizai...@gmail.com: Nice fine, do you have any instructions or links on how to manually roll back via an older .bin file? 

@kashmore / comment 16:


1. download the .bin file of version 69 (https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_10895.56.0_veyron-mickey_recovery_stable-channel_mickey-mp-v2.bin.zip)

2. Start the Chromebook Recovery Utility on a different PC:
https://chrome.google.com/webstore/detail/chromebook-recovery-utili/jndclpdbaamdhonoechobihbbiimdgai

3. Make sure you use the option "use local image":
https://lh3.googleusercontent.com/-D2kTW6ODDWc/VrGAgQNCOxI/AAAAAAAAIj8/dlW0ebvxdAc/s1600/Screenshot%2B2016-02-02%2Bat%2B11.16.19%2BPM.png

This wil prepare an USB stick you can use to reset your Chrome device to an older version.

4. Start you're device in recovery mode as described here in step 3:
https://support.google.com/chromebook/answer/1080595

That sounds exciting, but doesn't the device immediately update itself? If I'm not mistaking, the auto-update function can only be turned off on managed devices. And then we're back at square one...

Thank you for the instructions, sadly however it seems that the following comment is correct in regards to non-managed devices, ours instantly updated itself back to 70. This is still a problem for us. 

@kashmore / comment 19

It should not be a problem.
You can set up the Kiosk before it updates. It still works after the update. 
Problem was, that you could not turn it on, while in version 70.

"Additional notes: If the ChromeOS was already configured with auto-launch before updating to 70.0.3538.76, the update does not affect the Kiosk auto-launch process. This only occurs if you are trying to provision a new device with ChromeOS to begin Kiosk auto-launch while already on 70.0.3538.76."

Doesn't look like it has been fixed in Chrome OS 71

https://bugs.chromium.org/p/chromium/issues/list?can=1&q=os=chrome%20M=71%20status=Fixed&colspec=ID+Pri+M+Stars+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modified&groupby=&sort=&x=m&y=releaseblock&cells=tiles

It's still an issue for us also, has anyone been able to get any feedback from Google at all?

I see the issue on a ChromeBox.  Unfortunately the Box has a tendency to revert to factory settings after the updates happen and we lose all our settings.  I will try the instructions given by Richard. However I am concerned that there is no way to stop the device from updating as pointed out by kashmore and lindelauf.  

I was able to trick the Acer R11, into not updating, by initially connecting to a router that had no internet access. It complained when attempting to check for updates but then after re establishing internet access I could jump past the update check and directly to the login screen to press ctrl+alt+K.
Also lucky enough to find an image of V69 for the machine to revert. Thank you whoever you are.
After setup, and then allowing them to update, they continue to work on v70

Same issue got posted again last month: https://bugs.chromium.org/p/chromium/issues/detail?id=913951

No helpful info inside it though.

Seems like it is connected the the lack of the permission pop up after the initial restart. Since a machine setup on pre 70 continues to work, after updated, that setting must persist through the update.

We are also experiencing this issue with some of our customers. We use auto launching kiosk mode to display live public safety information in fire stations, emergency operations centers and dispatch  centers. We tried on our customers behalf to roll back to v69 using the bin provided above but the chromebox did not recognize the OS as a valid OS. Any word from Google on when this might be resolved or a hotfix may be released? 

Found a helpful link contained here https://www.reddit.com/r/PixelBook/comments/a0zs4a/is_there_any_way_to_downgrade_2_chrome_os_69
Hopefully you see your hardware listed.

I was able to get the correct image file via the Reddit link.  Thanks for sharing!  I successfully downgraded the OS and it stayed at 69 long enough for me to get the kiosk function to auto-launch properly.  I then upgraded to 71 and it was able to continue auto-launch properly.  I'm keeping my USB with OS 69 in case the system loses its data and settings again.