Thank you for helping to keep GamingOnLinux civil and safe!
Please tell us why you're reporting this content. Please note we store your IP address for all reports to help prevent spam and abuse. You can also email any complaints to: [email protected].
- Survive an elevator trying to eat you in co-op horror KLETKA when it releases February 19
- Draft code submitted to KDE Plasma turns it into a full VR desktop
- Proton Experimental brings updates for MonoGame, Rockstar Launcher and more
- Valve tweak Steam AI disclosure form for developers to clarify it's for content consumed by players
- No Rest for the Wicked co-op update lands on January 22 and it hit a big sales milestone
- > See more over 30 days here
- Casual/Social places for developer chatter
- simplyseven - Will you buy the new Steam Frame?
- eev - One-time logout
- Liam Dawe - Away later this week...
- Liam Dawe - Weekend Players' Club 2026-01-16
- grigi - See more posts
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
It's not the fault of the TPM2.0 basically every machine, since 2008 has one that can be manually activated.
Microsoft has a processor whitelist for Win11 and that one is at fault for this debacle.
I've done Win11 migrations for many customers and none of them had no TPM2.0.
Most of them had non-whitelisted CPUs.
Microsoft does say it in it's marketing though.
This is, because the reason behind the whitelist is complicated and thus unsuited for marketing.
At the time of establishment this whitelist contained only CPU's without known side channel attacks.
They really, really wanted to get rid of old side channel attacks for some reason.