> It doesn't seem like they are making any effort to block versions that don't cause crashes.

See the Tweet I linked, Windows does have a mechanism to only block a specific range of version numbers that are known to cause issues, and they have used that on StartIsBack/StartAllBack before, but the most recent Windows build simply blocks StartAllBack*.exe without any bounds on the version.

The developer can get around the block by changing the filenames of course but that's not really the point, if Microsoft is being actively hostile towards this kind of customisation now then they're just going to keep breaking it on purpose.