Chrome OS 84 was a relatively substantial update for Chromebook users and so far we have not seen any major issues or bugs in the software. Unfortunately, a brief annoying issue has recently appeared and it prevents users from signing in to their Chromebooks. While most of us have incorrectly set our password and Chrome OS has told us that it is invalid, this new bug fixes the error, even if the password is correct or has been updated.
When I open my chromebook, I try to log in, but it tells me that the password is invalid or not recognized, even though the same p / w can open my gmail okay if I continue as a ‘guest’. I tried to change the password once in my gmail but the chromebook does not accept it yet.
Chromebook Support Forum
The forum thread now has dozens of “me too” comments, but it seems that the developers of Google have found a solution to get things up and running again, while a more permanent fix is in the works. Keep in mind, these “fixes” require you to wash your Chromebook powerfully, which will result in the loss of local data that you may have stored. If you’re like me, that’s not a problem. I keep my stuff in the cloud, but I understand that the average user does not change or reset the devices all the time like we do. That said, there are two methods to overcome this problem and both will require a powerwash. If your content deletes all the local data you have, you can go with method number one which washes power from the lock screen. Here is the official passage of the Community Manager.
Powerwash
Powerwashing your device erases all information on your Chromebook’s hard drive, including all files in the Downloads folder. For more information, see the article Restoring Your Chromebook to Factory Defaults. If you have all your files backed up to Google Drive or an external storage device, follow these steps:
- push in and hold Ctrl + Alt + Shift + r.
- Select Restart.
- Select in the box that appears Powerwash> Continue.
- Follow the steps that appear and sign in with your Google Account.
- Note: The account you sign in to after setting up your Chromebook will be the owner account.
2-day Wake
Save your files by keeping your Chromebook awake for 48 hours first. If you have files in your Downloads folder, files that are not secured to Google Drive or an external storage device, follow these steps:
Make sure your charger or adapter cables are fully plugged in, both to your Chromebook and to the wall. Log in as a guest on your device that is experiencing this issue. Update your settings:
- Select links Apparatus.
- Select Power.
- Select “When low” next to “While charging” and “While on battery” Keep showing.
- Under “Sleep when cover is closed”, disables this
- Keep your appliance awake with the lid open for 48 hours without shutting it down.
When 48 hours have elapsed, exit guest mode and log in to your account. Once logged in, make sure you have backed up all your files:
- Press Ctrl + s.
- Enter a name for your file at the bottom.
- In the left column, select where you want to save your file, such as Google Drive.
- Select Save.
Factory reset your Chromebook and make sure your Chromebook’s operating system is updated to the latest version.
Shop best Chromebooks from 2020 to date on Chrome Shop
This fixing feels a bit hacky for sure, but my guess is that this is the fastest, least-intrusive way for users to get back on track while developers push out the final fix. If you see this step two that you need to make sure your Chromebook is up to date, tell me that the fix is already in place and that you just need to reset it to implement it. It’s a little inconvenient to leave your Chromebook awake for 48 hours, but it’s better than the alternative of losing important files. If you are following these procedures and still have issues, developer can use your feedback. To send feedback and share system info, press Alt + Shift + i or press your power button and hold and click on feedback. Included in the description, # M84Login, so the report will be quickly filtered to the right developers. Chrome OS devs take login issues very seriously and this particular bug got the highest level of priority for this very reason. Drop a comment below and let us know if you have this issue and the repair that worked for you.
