
Recent Issues with Google Chrome on Windows 10 and 11
Recent reports indicate that PCs utilizing Windows 10 and Windows 11 with the Family Safety feature enabled are blocking access to Google Chrome. Following this development, both Microsoft and Google have advised users affected by this issue to unblock Chrome through the Family Safety mobile application to regain access.
New Bugs Identified by Microsoft
In a recent entry on Microsoft Learn, the tech giant from Redmond has confirmed the identification of two additional bugs affecting Chrome. The first issue pertains to the ineffectiveness of Family Safety in blocking Chrome as intended. Generally, parents utilize Family Safety’s web filtering feature to monitor and control browser access. Microsoft employs a backend blocklist that requires the latest versions of browsers to be specified for blocking.
Current Status of the Blocklist
Microsoft acknowledged that they have yet to include the latest version of Chrome, along with other browsers, on this blocklist. Consequently, these browsers remain accessible to children using managed PCs. The company has initiated steps to update this blocklist accordingly.
Crashing Issues with Chrome
Additionally, Microsoft has received numerous reports regarding crashes of Chrome and other browsers on systems where Family Safety is active. Users typically encounter a prompt stating, “You’ll need to ask to use this app, ”as part of the parental consent process. However, rather than displaying this message, many users experience an unexpected crash of the browser.
Suggested Workaround for Affected Users
Upon investigating this matter, Microsoft discovered that crashes occur when the Activity Reporting configuration within Family Safety is turned off. As a temporary workaround, the company recommends that parents enable this feature until a permanent solution can be implemented. Microsoft has committed to finding a more robust fix for these issues and will keep users updated with further information as it becomes available.
Leave a Reply ▼