Table of Contents
Why Was Google Chrome Blocked by Windows Family Safety and When Was It Fixed?
Timeline and Background
Microsoft resolved a persistent technical conflict affecting Google Chrome users on February 10, 2026. The issue surfaced in early June 2025, when parents using Windows Family Safety’s web filtering feature discovered their children couldn’t launch Chrome. The browser either crashed immediately or failed to open entirely, affecting devices running Windows 10 22H2 and Windows 11 22H2 or later.
Root Cause
The web filtering component within Family Safety prompts children to request parental approval before using non-Microsoft browsers. However, a flaw in the system caused it to block new versions of previously approved browsers. When Chrome updated to versions 137.0.7151.68 and 137.0.7151.69, the filtering mechanism misidentified these releases as unapproved applications and prevented them from running.
Microsoft maintains a blocklist that requires manual updates whenever browsers release new versions. During the lag between Chrome’s updates and Microsoft’s blocklist modifications, the parental control software treated legitimate browser versions as potential threats requiring approval.
Temporary Solutions
Two workarounds emerged before the official fix. Users could rename the chrome.exe file to chrome1.exe, which bypassed the blocking mechanism. Alternatively, parents could access familysafety.microsoft.com or the Family Safety mobile app, select their child’s profile, navigate to the Windows tab under Apps & Games, and manually unblock Chrome.
Microsoft acknowledged the problem officially on June 24, 2025, adding it to the Known Issues section of the Windows Health dashboard for Windows 11 24H2.
Resolution Details
Microsoft deployed a server-side fix beginning in early February 2026. The company confirmed the resolution on February 10, 2026, updating its support documentation to reflect the change. The fix requires no user action beyond maintaining internet connectivity, as the update deploys automatically through Microsoft’s servers.
For devices unable to connect online, Microsoft recommends enabling the “Activity reporting” feature within Family Safety settings. This allows parents to receive and approve browser access requests manually, providing an offline management option until the automatic fix can be applied.
The rollout extends over several weeks to reach all affected devices globally. Microsoft expects complete deployment by late February or early March 2026, ending an eight-month disruption for families relying on both Family Safety protections and Chrome as their preferred browser.