My kid has parental control setup for his Windows account. Since the latest update of Minecraft, he can’t sign-in to Minecraft bedrock anymore. Other users on the web have reported the same problem. If he doesn’t sign-in, the game starts fine (i.e. he can play but as a new “guest” user). Error we get is the “drowned” one.
Tried to reinstall Minecraft entirely, log off, log-in and tried for multiple days. Error still occurs.
Linked issues
duplicates 1
Comments 2
Thank you for your report!
We're tracking this issue at MCPE-230429, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Ah nice, someone already reported it. 🙏 Same issue here. Summarised:
Subject: Error Code “Drowned” for Child Accounts in Minecraft After Latest Patch
Issue occurred around the latest Minecraft Bedrock patch and affects only the child accounts within our Microsoft Family group.
Issue Description:
My two children have been unable to sign in to Minecraft using their Microsoft accounts since the update.
The error message displayed is “Drowned”, and the login process fails.
The affected accounts are managed child accounts within our Microsoft Family group.
Adult accounts in the same family group can sign in and play without any issues.
The problem only started after the latest Minecraft patch. Everything worked perfectly fine before that.
Troubleshooting Attempts:
Restarted devices and the game
Checked parental control and Xbox service settings
Tried signing in an out of the Xbox app and Microsoft Store
Unfortunately, none of these steps resolved the issue. Many users have reported the same problem online, specifically with child accounts since the recent update. It appears to be a systemic issue possibly related to current parental control mechanisms or the patch itself.
I kindly ask you to investigate and let me know whether this is a known bug and if a fix is planned. Alternatively, I would appreciate any specific guidance on how to resolve the issue.