404
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Nov 2024
404 points (99.0% liked)
PC Gaming
8668 readers
463 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
The thing is, my mobo was, as far as I can tell (based on the release date of the 1.0 version of its firmware), released in 2017. I didn't go out of my way to avoid TPM 2.0, I just bought recent hardware made by reputable manufacturers, and built a computer out of them. The fact that Microsoft arbitrarily decided a less than 4 year-old computer couldn't run on their new operating system is pretty galling.
Remember Microsoft support is in terms of businesses. A business will not buy parts from AMD or MSI and then proceed to build the computer, they buy prebuilt computers from manufacturers, and these are in fact forced to pick parts that support TPM 2.0 since Windows 10. Microsoft could not care less if you and I get hacked, because the fact is we don’t make Microsoft any money.
Also, chances are your motherboard does support TPM 2.0. Remember most manufacturers are lazy and don’t have a dedicated TPM module and instead use firmware TPM which depends on CPU. So even if your motherboard supports TPM 2.0, you need a compatible CPU.