I posted this below, but I suspect the scoping for Chrome.exe was done because Chrome was misusing an API. According to the article: "the worst was reserved f

I posted this below, but I suspect the scoping for Chrome.exe was done because Chrome was misusing an API. 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. It wouldn't be the first time Windows changes how something works based on application name [0]. Keep in mind there's also more than just the documented Win32 API exposed to applications on Windows (and who knows if Chrome was misusing these undocumented ones) [1]. [0] https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41363 https://devblogs.microsoft.com/oldnewthing/20031224-00/?p=41... [1] https://learn.microsoft.com/en-us/sysinternals/resources/inside-native-applications https://learn.microsoft.com/en-us/sysinternals/resources/ins...