Google is working to solve certain chromeos devices affecting certification issues, preventing affected users from signing into their clever and classic accounts.
As the company tells one in one Recently updated event report On the Google Western territory status dashboard, these certification failures affect the ongoing versions in the edition of 16328.55.0 with Chrome browser version 139.0.7258.137.
in issues Are Do not disturb alone Fill Clever and classic educational partner access to platforms that are used to manage the access to digital resources.
Classlink More than 3,000 school systems in 50 American states and 42 countries are used by more than 22 million students and employees, while clever Used by over 110,000 schools, including 95 largest 100 districts (about 60% of American students).
“Google, a service that works with clever, is experiencing issues with users who are unable to login using their Google Credentials for those updating Chromeos 139,” also “clever Told users In a separate event report on its official status page.
“It is preventing users from being able to login to their clever account. We are monitoring the issue and will provide the situation updates as they are available.”
The same certification problem also affects 2-phase verification (2SV) processes for some users, potentially blocks access to certain Google services that require increased safety authentication.
Woarkarounds are available until a fixed roll out
While its engineering teams are conducting automatic tests on a potential solution before issuing the fix to the affected users, Google shared two temporary reforms that can help those affected work around authentication failures.
The first administrators need to roll back their chromos installations back to the previous M138 version, using detailed instructions given. This google support document,
To do this, they have to undergo the following steps:
- Sign in Together Administrator Account of Google Administrator Console.
- Go to the menu> Device> Chrome> Settings> Device Settings (Who needs to be Mobile device management Administrator Privilege).
- To apply settings on all devices, leave the selected top organizational unit. Otherwise, select a child organizational unit,
- Go Device updated settings And click Auto-update settings,
- For Allow the device to update the OS version automaticallychoose Allow update,
- For Target versionSelect a CHROMEOS version.
- For Roll back to the target versionchoose Roll back os,
- Click Roll back os And then click save,
To verify that the devices of the affected users have successfully rolled back, administrators would have to sign in a managed chromos device belonging to the organizational unit where the rollback was enabled. Then, they should go to the settings and examine the OS version about the chromos dialogue.
Alternatively, they can also modify Loginaauthenticationbehavior setting To use the “authentication through the default gaia flow”, which bypasses the problematic authentication route, causing these ongoing failures.
The company said, “Fix is undergoing automatic test. Once completed, engineering will validate the results and we will make the fix available to users.” “Currently we do not have ETA for the version with fixes to be available. We will provide an update on Thursday, 2025-08-28 17:30 US/Pacific.”
The passwords broke in 46% of the atmosphere, almost doubled by 25% last year.
Picus Blue Report 2025 Now get a wider look at more conclusions on prevention, detection and data exfIs.
