Feels like a good case for an antitrust complaint if you ask me.

> Microsoft has introduced a bug into Family Safety that specifically targets the Chrome browser and prevents it from functioning on Windows.

In isolation this is understandable. Bugs happen, and it happens at the worst time. But Microsoft has a pattern on dark patterns to pump up the Edge usage, and cant help but this this is somewhat planned.

I am blocking Microsoft through my personal data safety protocol.

Our product once suffered from a faulty Windows Defender update, and as I remember, it took about two weeks for Microsoft to fix it. During those two weeks, our product was barely usable for many users because access to a file system was slowed down to a crawl.

So, two weeks before the fix might not be that unusual for them.

I think this is a legitimate bug. But also that Microsoft is taking its sweet time to fix it.

My family safety feature is called linux.

> Other browsers like Firefox or Opera appear to be unaffected, and some users have even found that renaming Chrome.exe to Chrome1.exe works around this issue.

How is this possibly unintentional?

I wonder if this is related to the errors I saw this week, when I tried to install Chrome on my kid's computer. Apart from all the popups that discouraged switching to Chrome, the installer failed to run with an obscure error message.

Luckily I recalled there is an offline installer, and when I downloaded that, it worked like a charm.

Definitely feels like Microsoft is reverting to old ways recently. Did LLMs bring back excessive greed?