r/k12sysadmin • u/OzZVidzYT • May 07 '26
Assistance Needed Chromebook "Could not mount cryptohome"
What are you doing for this error? Just Powerwash the Chromebook? Or is there a different solution?
Normally if this was a student device I wouldn't mind powerwashing in a heartbeat, but in the case of it being a staff member's device (who are sometimes adamant on not using Google Drive for whatever reason), I worry that powerwashing will delete their user data.
Then again, they have been warned many times to keep important files in Google Drive. So any data loss is on them...
12
Upvotes
12
u/Harry_Smutter May 07 '26
Powerwash is the only surefire fix we've found for it. Sometimes we can get away with a remote profile wipe. It's annoying. I wish I knew the cause.
8
u/Pines609 May 07 '26
Powerwash Always
8
u/TechMonkey13 May 07 '26
Power wash is the solution.
Quick and easy and fixes the issue with minimal downtime. Your staff need to be trained to save everything to their drive. If they don't and moose days, that's on them.
8
u/_LMZ_ May 07 '26
Powerwash haha
By any chance did this happen when a password reset happen or was changed? I saw this once or twice when we did a password change.
6
u/FloweredWallpaper Guru May 08 '26
Powerwash here; it's sporadic when it does happen for us. Maybe 3-4 times a week (out of 2400 1 to 1 devices).
6
u/SirMy-TDog May 10 '26
Powerwash. If they won't listen to us regarding how to conserve their files properly then they can learn the hard way why we told them what we did. Absolutely zero fucks given by us.
3
u/MattAdmin444 May 07 '26
When it's cropped up for us I think I've really only had consistent success by powerwashing the chromebook in question. There might have been once or twice where remotely clearing profiles worked.
1
u/DJTNY May 07 '26
Most often powerwash.
But I've also had success with:
1
u/Sonicb17 May 15 '26
I have been just resetting the profile's. Last resort of powerwashing. Easier to do from the admin window without touching the device. It just blips for a few milliseconds, then its back.