In early June 2025, reports began surfacing that Microsoft’s Family Safety feature—widely used by parents and schools for online content filtering—was unexpectedly preventing Google Chrome from launching on Windows machines. Anecdotal accounts and support threads suggest that when Family Safety is enabled, Chrome either crashes immediately upon opening or refuses to launch altogether, while other browsers like Firefox or Opera remain unaffected.

The issue appears to have first been noted around June 3rd, 2025, when a handful of users on forums and social media began sharing complaints that Chrome would close itself or fail to start when Family Safety was active. One parent recalled trying to help their child access homework resources, only to find Chrome unusable, despite other browsers operating normally. In some school environments—where Microsoft 365 subscriptions often enforce Family Safety settings—the sudden breakdown of Chrome threatened to derail lesson plans reliant on web-based tools.

Google’s Chrome support team acknowledged the problem, with a Chrome support manager (identified only as Ellen T.) reportedly confirming that “for some users, Chrome is unable to run when Microsoft Family Safety is enabled.” While the precise technical root cause has not been publicly detailed by Microsoft, early investigations point to an unintended interaction between Family Safety’s filtering mechanisms and Chrome’s executable signature or launch process.

Several community-sourced workarounds quickly circulated:

• Renaming the executable: Some users discovered that renaming chrome.exe to chrome1.exe bypassed the block, allowing Chrome to launch normally. While this hack restores functionality, it is far from ideal for non-technical users and may break future auto-updates or integrations.
• Disabling “filter inappropriate websites”: Within Family Safety settings, turning off the web filtering feature appears to allow Chrome to run again. However, disabling this filter essentially removes the primary protective barrier Family Safety provides, leaving younger users free to navigate any online content.
• Switching browsers: Some families and institutions have defaulted to Firefox or Opera until a fix arrives. Though functional, this shifts users away from Chrome’s ecosystem—potentially undesirable for those reliant on Chrome-specific extensions, syncing, or enterprise deployments.

These stopgap measures highlight a tension: parents and schools rely on Family Safety to enforce safe browsing, but the bug forces a choice between maintaining controls or restoring typical browsing workflows.

At the time of writing (June 20, 2025), Microsoft has not publicly announced a timeline for a patch. Inside Microsoft support channels, guidance seems limited to advising affected users of the above workarounds, without committing to a broader remediation schedule.

Meanwhile, in Chromium’s bug tracker, a Chrome engineer noted on June 10th: “We’ve not heard anything from MSFT about a fix being rolled out. They have provided guidance to users who contact them about how to get Chrome working again, but I wouldn’t think that would have a large effect.” The absence of detail or timeline from Microsoft has left IT administrators and parents in limbo, unsure if they should disable Family Safety entirely or await a resolution.