Blackbird From this point onward, patches and upgrades to Win11 may be released without any assurance they won't fail (or even brick) "unsupported" machines, whereas in the past MS may have expended some effort to prevent that. They may even insert code to prevent further updates/upgrades from installing on such systems. From here on out, it's 'user beware' for those running Win11 on unsupported equipment.
They can release patches that will not work on unsupported configuration; however, but intentionally bricking pre-existing installs is a major No-No, and I'm fairly certain that they won't do that.
They are trying to push Win 11, and those running on unsupported HW are still boosting the Win 11 numbers. I'm not sure what is the most common missing feature that makes PC non-supported -- I thinks it's either an older CPU or lack of TPM 2.0. I tend to think CPU would be a more serious requirement, but if they didn't enforce it before, they should not start it now. Or if they plan to do it, they should communicate it well in advance, and it should only apply to new features. With respect to TPM 2.0, methinks they could ignore it altogether as long as long as the user clicks some acknowledgement about understanding significantly decreased security because of the lack of TPM, or the lack of TPM 2.0.