Well you did claim that, but thank you for correcting. So that warning is bad for a developer because of confused and annoyed users, but in terms of actual user restriction it's not super bad. If defender is set to be too aggressive, that's a one time change, so about on par with Android. And for the normal (I think? Did the default change?) setting you just use run anyway. That's far away from how iOS makes it impossible.

Edit: Everything I can find says that taking away the "run anyway" button is not default. If a user or their sysadmin changes that setting I don't really blame Microsoft.

No, this is what I claimed:

> I'd be okay giving Microsoft whatever they wanted on the Windows app store as long as they loosened their grip on being able to run what you want, from where you want, without their explicit blessing.

I am talking about their grip on what you're allowed to run with or without their blessing, not that you "can't run unsigned binaries at all". They have a tightened grip, in that without their blessing, running what you want is an exercise in futility for 99% of users.

> Edit: Everything I can find says that taking away the "run anyway" button is not default. If a user or their sysadmin changes that setting I don't really blame Microsoft.

It's exactly what I experienced when running an unsigned binary in a fresh Windows 11 VM with the default Defender settings, which are all on by default. This is how SmartScreen works by default with binaries it doesn't like.

Okay, that new default is a significant worsening.

> what I claimed

Your first comment was fine. Your response to nandomrumber was the problem. They asked about "can't run" and you gave a big list of situations that are interference but not "can't run".