> Sounds like that was not what happened here, Windows did some ugly hack (up to and including ‘relying on a Chrome.exe process name’, like, come on) and in fac

> Sounds like that was not what happened here, Windows did some ugly hack (up to and including ‘relying on a Chrome.exe process name’, like, come on) and in fact doesn’t even have a “make request then approve in Settings” workflow, so yeah Windows is the bad guy here. Google is still a little bit bad - you’re fucking up my UI by forcing a self-promotion button into my tab bar, that’s not cool - but overall this situation is a point against Microsoft. I suspect Chrome was misusing an API, because according to the article "the worst was reserved for users on the enterprise version of Windows. For weeks, every time an enterprise user opened Chrome, the Windows default settings page would pop up. There was no way to make it stop unless you uninstalled the operating system update. It forced Google to disable the setting, which had made Chrome more convenient." Enterprise maybe didn't like settings getting changed that way (conflict with group policy?). If it was constantly opening new windows, it's probably because it was constantly calling an API (probably in the wrong or an undocumented way). So it would make sense to change how the API works based on a known bugged application.