Apparently this is specific to enterprise enrolled devices since consumer-owned devices lack the functionality of channel downgrade without powerwash.

Igor, I believe you have been working on some related things recently. Could you PTAL once you have spare cycles?

At times, a channel downgrade will result in a platform version upgrade. This usually happens when a milestone is pushed down to a stabler channel and the less stable channel hasn't moved to the next milestone just yet.

The actual logic for doing the powerwash seems to be based on a downgrading of the platform version but the UI powerwash message is based on downgrade of the channel.

My recommendation is to fix UI code to only mention powerwash if platform version is downgraded.

Steps to reproduce then would be:

1) restore a device to beta channel version 9765.78.0 (older than stable channel being served by Omaha).
2) Go through OOBE. Not clear here if issue is enterprise enrolled only but it definitely occurs on EE devices.
3) before update engine has a chance to upgrade device to current 62 beta channel release, change device channel to stable and check for updates. Device should be offered a newer stable channel 61 build.
4) device should finish installing stable release and show "reboot and powerwash" message at chrome://chrome.
5) device should not actually powerwash itself since platform version has incremented after the channel downgrade.

Expected result: channel downgrade and platform upgrade should not mention powerwash.

Actual result: chrome://chrome and system tray claim a powerwash is needed which causes user anxiety unnecessarily. No powerwash is actually performed.