Windows 11 is now more than a year and a half old, and one of its main problems continues to bring users upside down: the requirements. Despite being an update to Windows 10, Microsoft changed many of the mandatory requirements to be able to install the operating system and also make use of the main functions of this OS. One of the most controversial is TPM, the security chip that motherboards have and that, without it, it is not possible to run Windows 11. The problem comes when the system itself is not able to recognize this chip, even though it really exists.
Microsoft is constantly updating its operating system by adding new functions, features, and fixes. Moment 2 is the last update that has arrived introducing some functions that were left in the pipeline in 22H2. However, along with these new features also come all kinds of bugs and problems that cause from performance problems (a recurring bug with SSDs) to much more serious stability problems on the PC.
In addition, Windows 11 has been dragging, for more than a year (specifically, since June 2022), a problem that prevents users from making use of the system’s security improvements. This bug makes Windows Defender may not be able to detect the TPM chip in the system. And, therefore, it shows us an error like the following all the time.
This error appears on all types of computers, even new PCs which, of course, do have TPM 2.0 available and enabled. We can check this very easily by running the “tpm.msc” program.
This bug appears in all versions of Windows, even Insider Previews, the beta versions that Microsoft brings to users to experiment with changes and fixes. And, when it appears, it prevents us from enabling certain Windows Defender security features that depend on this TPM chip. But this is not the worst, and it is that, if Windows is not capable of detecting the presence of this chip, in addition to not using it to protect our data, it is possible that we will even be left without being able to update.
How to fix the problem
But the worst thing is not having this problem, but Microsoft can’t fix it. The company has been trying to solve this compatibility problem for 9 months now, and the only thing it achieves, month after month, is filling the company’s forums with user posts reporting this problem.
The reason for this problem is not very well known, but not even Microsoft is able to solve it. It will probably continue to try to kill it, at least within the Insider Preview program, to try to make it possible for eligible users to take advantage of the advanced security features of the operating system. And most importantly, don’t run into incompatibility issues later.
