Heads up, my dear victims of the tech monopoly! Microsoft has done it again and this time it’s killed Chrome on Windows using its “family safety” feature. And here comes the good part: they’ve been dealing with this mess for more than two weeks and they act as if nothing is happening. Really, Microsoft? Really, honestly?

Let’s see, explain this to me properly. It turns out that since the beginning of June, Microsoft’s Family Safety feature (the one parents and schools use to control what kids see) has started randomly blocking Chrome. Users complain that the browser closes on its own or simply won’t open. And Microsoft just sits there, all carefree, as if it had nothing to do with it.

Let’s see, let’s see, this is getting interesting. The Chrome folks have investigated the matter and confirmed that yes, Microsoft has introduced a bug in Family Safety that specifically targets Chrome. Specifically! It doesn’t affect Firefox, it doesn’t affect Opera, only Chrome. What a coincidence, right? This smells fishy in the worst way.

And I ask myself: is this a real bug or is it another of Microsoft’s “coincidences” to mess with Google? Because, let’s be honest, Microsoft has a track record longer than a day without bread of doing weird things to steer people away from Chrome.

Don’t tell me it’s not remarkable that the “temporary” solution is to rename Chrome.exe to Chrome1.exe. Rename it! As if it were 1995 and we were hacking the system with MS-DOS tricks. This is crazy, but it works, which is what bugs me most.

The other solution is to disable the “inappropriate websites” filter in Family Safety. Sure, because the solution to Microsoft blocking Chrome is to let kids access any website. Very smart, Microsoft. Very smart.

Let whoever is surprised that Microsoft does this raise their hand. Because I’ve lost count of how many times Microsoft has tried to sabotage Chrome. Fake prompts, invented AI answers, popups that look like malware, surveys on the Chrome download page… They’ve even used Bing to trick people into thinking they were on Google!

This is crazy, but in the bad way. Microsoft has spent years trying to get people to use Edge instead of Chrome, and when normal marketing doesn’t work, they resort to these tactics that border on desperate. And the worst part is they do it using a “family safety” feature. Family safety! As if blocking Chrome were for the good of the children.

Let’s see, explain this to me: if Microsoft really cared about children’s safety, wouldn’t it be better to improve Edge instead of sabotaging Chrome? Because in the end, what they’re doing is using children as an excuse for their particular war against Google.

Really? Really, honestly? Because they’ve had this problem for more than two weeks and Microsoft hasn’t said a word. The Chrome folks have confirmed it’s a Microsoft problem, users complain in the forums, and Microsoft just acts like it has nothing to do with it. Very professional.

And here comes what makes me angriest: this especially affects schools and families that use Microsoft 365. In other words, Microsoft is harming precisely its own customers. Because of course, if you have Family Safety enabled and you use Chrome (which is the most used browser in the world), you’re left without a browser. Great.

This smells like a big, big legal mess. Because one thing is competing fairly and another very different thing is using operating system features to sabotage the competition. This is no longer aggressive marketing; this is abuse of a dominant position.

What bugs me most is that Microsoft has more than enough resources to make Edge better than Chrome. They have money, they have talent, they have technology. But instead of investing in improving their product, they’d rather sabotage the competition’s. And that, dear geeks, is what losers do.

And that’s the end of today’s anticompetitive drama, my dear Chrome users. Microsoft proves again that when they can’t win fair, they play dirty. See you in the next one, there’s sure to be more trouble (and Microsoft is probably behind it).

A virtual hug and remember: if it isn’t broken, don’t touch it… unless you’re Microsoft and you want to mess with Google.