Why Is Microsoft Family Safety Suddenly Blocking Chrome and How Can You Fix This Frustrating Issue?

Is Your Chrome Browser Crashing Due to Microsoft Family Safety? Here's the Ultimate Solution That Actually Works

Microsoft's Family Safety feature has been blocking Google Chrome from running on Windows devices since early June 2025, affecting thousands of users worldwide. This issue stems from a bug in Microsoft's parental control software that mistakenly flags Chrome as unsafe, causing the browser to crash immediately upon launch or fail to open entirely.

The problem first surfaced on June 3, 2025, when users began reporting that Chrome would either crash within seconds of opening or refuse to launch at all. What made this particularly confusing was the complete absence of error messages, leading many users to suspect malware infections on their computers. The issue specifically affects Chrome versions 137.0.7151.68 and 137.0.7151.69, while other browsers like Firefox and Opera remain completely unaffected.

Understanding the Root Cause

Microsoft Family Safety is designed to protect children online by filtering inappropriate content, managing screen time, and monitoring internet activity. However, a glitch in the system began treating Chrome as a blocked application when content filtering was enabled. This created significant problems for families and educational institutions that rely on both Chrome and Family Safety for their daily operations.

The issue appears to be related to Microsoft's content filtering mechanisms, which work most effectively with Edge browser and Microsoft Store applications. When users attempt to run Chrome with Family Safety active, the system incorrectly identifies it as a potential security threat and prevents it from functioning.

Impact on Users and Institutions

The blocking issue has had widespread consequences, particularly affecting:

• Educational institutions where students commonly use Chrome for schoolwork
• Families who depend on both Chrome and parental controls
• IT administrators managing multiple devices with Family Safety enabled

According to Chromium engineers, the problem caused a 2.5x increase in Chrome uninstall rates on June 3rd as frustrated users attempted to resolve the issue by reinstalling the browser. This surge normalized by June 7th, but the underlying problem persisted for weeks without an official fix from Microsoft.

Proven Solutions and Workarounds

Official Microsoft-Recommended Fix

The most reliable solution involves adjusting Family Safety settings through these steps:

1. Navigate to https://familysafety.microsoft.com or open the Family Safety mobile app
2. Select the affected child's profile
3. Choose one of these options:
   • Option A: Go to the Edge tab and disable "Filter inappropriate websites"
   • Option B: Navigate to Windows tab → Apps & Games → Unblock Chrome specifically

Alternative Workaround

Some users have successfully bypassed the block by renaming Chrome's executable file:

1. Open File Explorer and navigate to "C:\Program Files\Google\Chrome\Application"
2. Right-click on "Chrome.exe" and select "Rename"
3. Change the filename to "Chrome1.exe" or similar
4. Launch Chrome using the renamed file

While this method works, it represents a temporary solution that highlights potential security vulnerabilities in Microsoft's filtering system.

The Broader Implications

This incident has reignited discussions about browser competition and potential anti-competitive practices. The fact that only Chrome is affected while Edge continues to function normally has led some users to question whether this is truly an accidental bug or a strategic move to promote Microsoft's own browser.

The situation puts parents and educators in a difficult position: they must choose between maintaining web safety controls or allowing access to their preferred browser. Disabling the "filter inappropriate websites" option restores Chrome functionality but removes all content restrictions, potentially exposing children to harmful online content.

Current Status and Microsoft's Response

As of late June 2025, Microsoft has not provided a permanent fix for this issue. The company has remained largely silent about the problem, offering only the workarounds mentioned above through support channels. Google's Chrome team has confirmed that the issue originates from Microsoft's Family Safety controls and has provided guidance to affected users, but cannot resolve the problem independently since it stems from Microsoft's software.

The ongoing nature of this problem continues to affect users worldwide, making it essential for affected individuals to implement one of the available workarounds while waiting for an official resolution from Microsoft.