Chrome was closing down for Family Safety and Microsoft already has the solution from the cloud

Microsoft has solved a known failure in its parental control service Family Safety that, for months, prevented many Windows users from opening Google Chrome and other browsers. The correction was deployed from the service side in early February 2026, so the equipment must connect to the Internet to receive the automatic update and stop experiencing the sudden closures or the inability to launch the browsers.

Family Safety is the tool with which Microsoft wants families to control use times, filter content, manage app permissions and receive activity reports; its purpose is legitimate, but implementation can be fragile when interacting with fast-evolving software. If you want to review the official service capabilities, Microsoft describes it on its product page: Microsoft Family Safety.

The first signs of the problem emerged in late June 2025, when users began to complain in forums and communities that Chrome did not start or unexpectedly close on Windows 10 22H2 and Windows 11 22H2 or later. Among the public conversations that documented the failure are threads in the Microsoft Answers forum and in Reddit, as well as in Google Chrome support forums: thread in Microsoft Answers, reports in Reddit and Google support forum.

According to the official explanation, the origin of the failure was in the web filtering logic of Family Safety and in the management of the so-called "block list" that Microsoft maintains. In theory, protection blocks unallowed browsers and asks parents for permission when a child account tries to use one other than the authorized one. In practice, when an installed browser was updated to a new version, that version did not always fit the rules of the list and the system ended up blocking or closing browsers that used to work normally. Microsoft has detailed the problem and its evolution in the health panel of Windows versions, for example in this entry on Windows 11: Note on Windows release health (22H2) and in the subsequent update: comment on the resolution.

The applied correction is "service-side," that is, Microsoft adjusted the settings and lists on its servers to remove the cause of the lock without necessarily requiring a local update of the operating system. This means that, if your computer showed the symptom, it is enough to connect it to the Internet and wait for it to receive the remote update., as indicated by the company: deployment began in early February 2026 and should reach all affected devices in the following weeks.

If for any reason a computer cannot connect to the network to receive automatic correction, Microsoft recommends activating the "Activity reporting" option in the Family Safety configuration of the device. With this active mechanism, parents receive permission requests on a regular basis and can allow for newer versions of browsers manually, which serves as a temporary solution until the arrangement arrives via service. Windows's own health documentation collects this alternative and the instruction to connect to receive the solution.

Beyond the patch, this incident leaves two practical lessons for families and administrators: on the one hand, parental control tools that depend on centralized lists and signatures can be broken when applications are frequently updated; on the other, solutions that are applied from the server are convenient to correct errors without action by all users, but require devices to be online. If you have devices managed at home, you should check that they are connected to the Internet and check the Family Safety settings to confirm that the monitoring and permissions work as you expect.

If the problem persists after connecting and waiting, the usual ways pass by reviewing the configuration of the family account on the web or in the Microsoft Family Safety app, request the uninstallation and reinstallation of the affected browser (always considering the security of the user data) or, ultimately, contact the Microsoft support for personalized help. It is also useful to consult community threads where other users have described symptoms and provisional solutions: in addition to the link to the Microsoft forum, reports on Reddit and Chrome forums can give clues on specific cases.

In short, the massive browser lock caused by the interaction between browser updates and Family Safety filtering rules already has official solution. Connect the equipment to the Internet to receive the arrangement; if you cannot, activate the activity notification so that parents manually authorize new versions of the browsers. And if you keep seeing unexpected closures after that, contact the support and share records or catches to speed up resolution.