+ Bernie, owner of 65
+ vineeths, owner of REKS
+ RBS

I know it's late in the 65 game but REKS is popular in EDU and we're in the middle of testing season. If a kiosk app vendor certifies against 65 right now and REKS devices can't actually get 65 and we bump fix to 66 this could be a big issue for customers.

@Victor: can you try pinning the device to 64 and see if it will update then? If it does get 64 will it then cleanly update 64 to 65?

+ vineeths for real

Victor, never mind about 64 > 65, I see customer has already tried.

Also worth noting that USB recovery to 65 *DOES WORK* for customer.

Victor, can you gather the recovery log from USB restore to 65? It should show the same firmware update attempt though I believe AU uses the *old* OS firmware update tools while recovery will use the current version which may be the issue here.

Jay, on comment#3, I checked on a test Lenovo N22 device and recovery does not work for me.
It has failed with error message "An unexpected error has occurred. Please refer to this URL ... "
https://drive.google.com/open?id=1xCm5oFhx4ptciYRM1bV01z6uyOs4ojdl

From the recovery log, looks like it fail on the same step: 

###

Syncing filesystems before changing boot order...
Finished after 0 seconds.
Updating Partition Table Attributes using CgptManager...
Updated kernel 2 with Successful = 1 and NumTriesLeft = 6
Checking /mnt/stateful_partition/unencrypted permission.
RemovePackFiles Failed
Touch(/mnt/stateful_partition/.install_completed) FAILED
Starting firmware updater (//usr/sbin/chromeos-firmwareupdate --mode=recovery)
Command: //usr/sbin/chromeos-firmwareupdate --mode=recovery
Starting Google_Reks firmware updater v4 (recovery)...
 - Updater package: [RO:Google_Reks.7287.133.81 RW:Google_Reks.7287.133.103 / EC:reks_v1.1.3597-0d4ba53]
 - Current system:  [RO:Google_Reks.7287.133.19 , ACT:Google_Reks.7287.133.19 / EC:reks_v1.1.3597-0d4ba53]
 - Write protection: Hardware: ON, Software: Main=ON EC=ON
ERROR: Failed to load keysets for signature [LENOVO].
ERROR: Execution failed: ./updater4.sh (error code = 1)
Finished after 5 seconds.
Failed Command: //usr/sbin/chromeos-firmwareupdate --mode=recovery - Exit Code 1
Firmware update failed (error code: 1).
Rolling back update due to failure installing required firmware.
Successfully updated GPT with all settings to rollback.
PostInstall Failed

###

drive link to recovery log: https://drive.google.com/open?id=12XEIjBeoa2BTZrEAv7JP8-6LEFfuLpR2

This seems like a dupe of https://buganizer.corp.google.com/issues/77910689 internally.

Hello team, any update on this issue? CDW is also affected by this problem, they need to update the devices for deployments. Any update or ETA is appreciated.

We have fixes for this in the pipeline and hope to be able to resolve this soon.

Experiencing same issue with Lenovo N42 as well. Four cases at our org so far.

#CBC-RS/TC-watchlist

Hi, we're working to get this resolved before the middle of next week.

Current workarounds include:
- From admin console, pin device to 64 so it gets a relatively recent update without hitting the 65 update issue.
- USB recover the device to 65. This works but is not a scalable solution as it requires touch of each device. If you need to do this on more than a handful of machines we'd recommend just waiting until fix is in production.

jayhlee,

Does USB recovery method update CB to version 65.0.3325.209 (most current) or 65.0.3325.184 (older minor version)?

m32,

It updates the CB to 65.0.3325.184. I just updated a few N22 that had 58 to 65.

izzyjz,

Please try to "CHECK FOR UPDATES" from About Chrome OS in settings. What results?

While I can't speak for izzyjz, we've had the same issue ongoing with 90 new chromebooks (all Lenovo N42-20's), and if the issue is the same it goes as follows:

-Click "CHECK FOR UPDATES"
-Chromebook says "Updating your device" with a Percentage counter that goes all the way up to 100%
-Chromebook states that it is up to date, but the "Restart Your Device" button never appears, as it does on other models in our Parish
-Upon restart, Chromebook version shows it at what it was before (Version 65.0.3325.184 (Official Build) (64-bit))

I'm getting the same results as brasen.d when trying to update my CB beyond 65.0.3325.184.

I'll click on "CHECK FOR UPDATES" and it'll go through the process but it won't update to 65...209.

The Stable channel for most Chrome OS devices was first updated from 64.0.x.x to 65.0.3325.167 on Monday, March 19, 2018. Given the conventional six week autoupdate timetable of the Stable channel, we should see an update on or near Monday, April 30, 2018.

izzyjz, brasen.d,

Please, one more check. Open Task Manager. Do you have a running process, "Utility: Patch Service"? 

Thanks, Mike B.

let's hold off on more comments for now, Google Engineers are very aware of the issue and expect to have a fix next week. 

This no longer blocks stable, fix is in place all that is left is to push it. 

[Auto-generated comment by a script] We noticed that this issue is targeted for M-65; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-65 label, otherwise remove Merge-TBD label. Thanks.

FYI, 10323.67.6 / 65.0.3325.209 or 10452.74.0 / 66.0.3359.137 should be pushing to REKS devices now which resolve this issue.

Rockin' 10452.74.0 / 66.0.3359.137 on my N42 since 05/03. Grateful, Mike B.

Can confirm that we are able to update to 66.0.3359.137 on our end as well. Thank you for your assistance. Sorry about the post jacking. 

I am encountering this issue on Samsung Chromebook 1st gen.
Previously I was on version 67.0.3383.0, could not update although I had even tried powerwashing. Then I tried the recover utility from my Windows laptop and was able to change the version to 67.0.3396.99, However there is another update now and the same problem happens.