[remirk]

It is quite normal that things break on the Windows Insider Preview builds from time to time right?

I'm pro Free Software, and therefore anti-Microsoft, but isn't it possible that, because of the changes to URL requests, they just haven't implemented support for having a difference standard browser? And that it may come in the upcoming weeks?

This would be an all-time low for Microsoft. It would give them a lot of hate. I find that hard to believe to be honest.

[nyuszika7h]

No, this is not an Insider build issue. Blocking apps from sneakily changing the default browser without user content is one thing. But in Windows 11 RTM, they specifically went out of their way to make it a lot harder to change your default browser (or any default app), by forcing you do to it separately for each protocol and file extension. This led to non-malicious apps (e.g. Firefox) pursuing an alternative method to avoid users having to jump through hoops.

It's quite interesting that if it's such a big security vulnerability Microsoft hasn't patched it in all these years, but when suddenly a browser maker wants to act in the users' best interests it's a "critical security vulnerability" that must be patched immediately.

Yes, malware could theoretically abuse the same loophole. But they simply cannot lie to our faces and say this is being blocked only to prevent malware when they've intentionally made it harder for users themselves to change the setting as well.

[plorkyeran]

The entire reason that the edge protocol exists in the first place is to bypass the user's desired default browser and open the URL in Edge instead. The fact that you could ever override that and make it open in your desired browser was pretty clearly a bug that accidentally made the feature less user hostile than intended.

[gavinray]

  > It is quite normal that things break on the Windows Insider Preview builds from time to time right?

I run the Dev channel [1] (most frequent releases). And I don't think I've ever had anything actually break.

Mostly it just makes my computer unusable every time they push an update, because it uses 100% disk capacity trying to background install while system is live. The background updates usually take 4-6 hours.

I also run Edge Dev and I HAVE had features break entirely on Edge, twice. Usually fixed within 1-5 days.

  [1]: DON'T DO THIS! You cannot downgrade to Beta/RC from Dev, and it's the only channel that's like this!
       Read the fine print. I receive updates sometimes multiple times a week and it's terrible.

[flyinghamster]

I have no problems believing it. They've been quietly turning the screws for twenty years now (beginning with Windows XP activation). And whenever they're called out for it, they double down. Where else have I seen that strategy lately?

[aksss]

Canonical is next on list?