In 2025, many Windows users relying on Microsoft’s parental control system, Microsoft Family Safety, encountered a widespread issue: Google Chrome wouldn’t open, or would shut down immediately after launching. This problem has since been acknowledged and fixed by Microsoft, but the root causes, real-world impacts, and workarounds remain useful for users dealing with parental controls on Windows.
What Was the Problem?
Microsoft Family Safety is a suite of parental control tools included with Windows that lets guardians set web filters, app limits, screen time, and more. Its web filtering and activity reporting features are primarily built around Microsoft Edge, the company’s own browser.
In June 2025, users began reporting that:
- Google Chrome wouldn’t open on Windows devices with Family Safety enabled.
- Chrome would crash or quit on launch, even if it had previously been approved.
- Other non-Microsoft browsers were sometimes affected as well.
- Attempts to launch Chrome didn’t always trigger approval prompts for parents.
Initially, it appeared to coincide with a Chrome vulnerability disclosure, leading some to suspect intentional blocking of older, unpatched Chrome versions. However, the behavior persisted across current versions, indicating a deeper issue in Family Safety’s filtering logic.
Why It Happened
Microsoft eventually explained that:
- Family Safety’s web filtering feature flags non-Edge browsers to require parental approval.
- During routine updates to Family Safety’s internal block/allow lists, a bug caused newer versions of Chrome — including previously approved ones — to be treated as unapproved.
- This caused Family Safety to block those versions outright rather than simply requesting parental permission.
- In some cases, Chrome would immediately close because the system didn’t handle the approval prompt correctly.
This unintended behavior was not universal, but many Windows 10 and Windows 11 systems with Family Safety enabled experienced it.
Microsoft’s Fix
In February 2026, Microsoft confirmed that the issue had been resolved via a service-side update — meaning users don’t need to manually download anything to fix it. Devices simply need an internet connection to receive the update automatically.
According to Microsoft:
✔ The bug was fixed internally in early February 2026.
✔ Fixes are rolling out over several weeks to affected devices.
✔ No manual action is required for most users.
✔ If a device still shows symptoms, connecting it to the internet should allow the update to reach it.
For users who can’t connect easily — such as school devices — Microsoft suggests enabling Activity Reporting in Family Safety, which ensures approval requests can flow correctly to a parent or guardian, letting them allow Chrome when prompted.
Community Solutions and Workarounds
While the fix rolls out, users and community helpers offered several useful tips:
⚙ Microsoft Answers Forum Suggestions
According to a community thread on Microsoft’s official support platform:
- Check Family Safety settings at https://account.microsoft.com/family and ensure Chrome isn’t blocked under “Content Restrictions.”
- Temporarily disable “Block inappropriate browsing” to allow Chrome.
- Some users suggested resetting Chrome’s settings (Settings → Reset → Restore defaults) if it still refuses to open.
- IT teams managing school devices reported that Family Safety’s filtering targets non-Edge browsers by design, making Chrome harder to keep open on children’s accounts.
Tips for Parents or Guardians
If you’re managing Family Safety for a child’s account:
To allow Chrome:
- Sign in at family.microsoft.com with your organizer (parent) account.
- Click your child’s profile.
- Go to Content Filters → Apps & Games.
- Find Chrome and set it as allowed.
- Ensure Activity Reporting is turned on — this may be required for approvals to work properly.
If Chrome still doesn’t open:
- Double-check that the child’s profile in Microsoft Family Safety isn’t still marked as requiring approval for new apps.
- Disable filtering temporarily, then re-enable it once Chrome is approved.
- Make sure Family Safety itself is up-to-date and connected online.
Final Takeaways
- The Chrome-blocking issue was not malicious, but rather the result of a bug in Microsoft Family Safety interacting poorly with non-Microsoft browsers.
- Microsoft has already fixed the issue with a backend update that devices receive automatically.
- Parents and administrators can still manage permissions manually if needed via Family Safety settings.
Even in complex systems like parental controls, unexpected bugs can disrupt everyday tools like web browsers. Fortunately, in this case the problem was acknowledged and resolved without long-term harm. Users affected should check their settings and ensure devices are connected to the internet to receive the necessary fixes.
