Once you delve into the technical specifics of Secure Boot and the TPM, it’s actually not that unusual. I wrote more detail in another comment on this post, but the TLDR of it is that Secure Boot is meant to enforce the integrity of the boot procedure to ensure that only approved code runs before the Windows kernel gets control, and the TPM 2.0 is meant to attest to that. Together, they make it possible for anticheat to tell if something (like cheating software) tried to rootkit Windows as a way to evade detection.
I don’t agree with the requirement, but it’s not a pointless requirement or some grand conspiracy to make people buy new hardware.
Once you delve into the technical specifics of Secure Boot and the TPM, it’s actually not that unusual. I wrote more detail in another comment on this post, but the TLDR of it is that Secure Boot is meant to enforce the integrity of the boot procedure to ensure that only approved code runs before the Windows kernel gets control, and the TPM 2.0 is meant to attest to that. Together, they make it possible for anticheat to tell if something (like cheating software) tried to rootkit Windows as a way to evade detection.
I don’t agree with the requirement, but it’s not a pointless requirement or some grand conspiracy to make people buy new hardware.