Could not mount cryptohome means the Chromebook couldn't open the protected local storage for your profile. Restart once, but if the error persists, a Powerwash may be needed to rebuild the local setup.
That reset erases local files, so stop before resetting if this Chromebook holds important files with no backup copy.
The message can appear alongside a password-verification warning even when the Google Account works elsewhere. Repeatedly changing that account's password isn't the same thing as repairing its local profile.
In this guide
1. Restart and read the complete sign-in message
Turn the Chromebook fully off using its power control, then turn it on again. Closing the lid only puts it to sleep. At sign-in, check the keyboard layout and enter the password carefully once more.
Read the last line of the warning. Could not mount cryptohome identifies a local-profile opening failure. A wrong-password message, a network sign-in screen, or a restriction set by work or school needs a different response.
Check whether you can still access your account through a session already open on another trusted device. That helps you tell an account problem apart from trouble opening this Chromebook's local files.
Don't sign out of a working session just to perform this check.
If the Chromebook starts normally after restarting, back up important local files to a separate drive or cloud storage. If the same error returns immediately, move on rather than repeating password changes.
2. Decide whether this is your device to reset
Before resetting an organization-owned Chromebook, involve its administrator. Give them the full message, the affected account, and whether any other account can sign in.
They can decide whether to remove a profile, wipe the device, or re-enroll it.
For a personally owned Chromebook, check whether another existing user can sign in. If another user can sign in, the Chromebook can still open at least one profile. That doesn't explain why yours failed, but it narrows the problem.
If another user works, ask them to protect their own local files before any device-wide reset. A Powerwash affects the Chromebook's local data for all users, not just the profile showing the error.
Guest browsing, if available, can give temporary web access. It won't open the affected user's private Downloads folder. Use it to keep working online while deciding what to do. It can't recover files from the locked profile.
For broader startup trouble before you even reach sign-in, the Chromebook startup guide covers a different stage. This page assumes ChromeOS loads and the profile fails to open.
3. Check your backups before removing anything
Use a working device to check your existing cloud files in Google Drive. Open the folders and confirm that the particular documents you need are present. A filename remembered from Downloads doesn't mean a cloud copy exists.
Check external drives and any separate backups too. Browser settings that were synced and files stored in Google Drive are different from files saved only on the Chromebook.
Google's factory-reset instructions warn that Powerwash erases local settings, apps, and files, including Downloads. Files already on Google Drive or an external drive aren't erased by that reset.
I'd stop here if an irreplaceable file exists only inside the locked profile. Ask the manufacturer or your organization's support team about the data before authorizing an erase.
If the data is safely backed up or you accept losing the local copy, continue with a profile removal or Powerwash. A reset working for someone else doesn't mean your local files will survive it.
4. Consider removing only a secondary profile
For a personal Chromebook with a removable secondary user, the sign-in screen offers a smaller change than wiping every account. Select the affected profile, open the menu beside its name, and choose Remove this user. Confirm the removal.
Removing a profile deletes its local data from this Chromebook. The Google Account continues to exist after local removal. Use this route only after making the backup decision in the previous section.
Add the person again from the sign-in screen and try signing in. If the new local profile opens, check that information saved through sync returns and download needed cloud files again.
Files that existed only in its old local Downloads folder won't return.
The owner account can't be removed this way; changing the owner requires a device reset. Managed Chromebooks can also hide the removal option. If Remove this user isn't available, don't try to bypass the administrator's controls.
This rebuilds just the profile you removed, though it won't fix every cryptohome error. If removal isn't suitable or the newly added profile still fails, the next supported step for a personal device is Powerwash.
5. Powerwash the personal Chromebook from sign-in
At the signed-out screen, hold Ctrl + Alt + Shift + R, then select Restart. In the box that appears, select Powerwash, then Continue, and follow the onscreen instructions.
This step erases local data, so continue only once you've accepted losing those files. On completion, connect to your network, then use the intended owner account for sign-in. The first account used after setup becomes its owner.
One owner on Google's forum confirmed that Powerwash restored access after this exact message. Use your backups as the plan for getting files back.
Check sign-in before spending time reinstalling apps or adding every other user. Open Files and verify your cloud documents separately from the new Downloads folder. Reaching the desktop shows that ChromeOS opened the new local profile.
6. Escalate a failure that survives the reset
If a freshly reset Chromebook produces the same error, tell its manufacturer your model, the full error message, and that Powerwash didn't fix it. Ask whether to reinstall ChromeOS with recovery or have the storage checked next.
Recovery reinstalls ChromeOS and also erases local data. The Chromebook factory-reset guide explains Powerwash and its backup requirements.
Use the manufacturer's recovery instructions for your exact model rather than switching into developer mode.
A managed Chromebook should return to its administrator at this point. Report whether the failure affects just one account or every account tried after the reset.
That distinction gives them a clearer starting point than another password reset.
The Short Version
Restart once and confirm the cryptohome message. Check backups and management before deleting a profile or using Powerwash. Powerwash can restore sign-in, but it erases local data.
A failure after a fresh reset needs manufacturer or administrator help.
Checked November 12, 2026.
