Windows 11 users encountered a confusing bug, it can not detect the TPM module on some processors, especially the AMD R7 5800X3D, which is very popular among the gamer community, this problem caused some trouble for those who want to upgrade to Windows 11 legally.
A large number of Windows users, mostly AMD users and a few Intel users, have reported to Neowin that they have encountered an issue that for some reason has prevented their PCs from passing the “TPM certification”, making them unable to install and run Windows 11 properly. The 5800X3D seems to be more susceptible than other processors. In some cases, users reported that they were able to pass TPM authentication after switching to a different CPU.
One person who encountered this bug wrote: “After upgrading my CPU from Ryzen 5 2600 to Ryzen 7 5700X, the Windows Secure Chip app reports ‘Authentication: not supported’, but the settings show that the TPM module is ready. ” He added: “When I switched back to the old Ryzen 5 2600, everything was fine.”
Another affected user on Reddit after upgrading from a 5800X to a 5800X3D said, “I’ve searched the web and there are a lot of people who experience the same problem with the 5800X3D and no one knows why or how to fix it. Some people do buy the standalone TPM module (and fix it), but why would I do that when the Ryzen 5800 has an onboard (most motherboards enable fTPM support)?”
Microsoft is aware of the issue and officially states that AMD’s TPM certification may fail with error code “0x80070490”, but there is no solution at this time:
TPM proves inapplicable to AMD platforms using ASP fTPM
TPM proofs for AMD platforms using ASP firmware TPM may fail with error code 0x80070490 on Windows 10 and Windows 11 systems. there is no update available to resolve this issue.
TPM proof failure with error code 0x81039001
Some devices may intermittently fail TPM attestation in Windows Autopilot pre-preconfigured technician flow or self-deployment mode with error code 0x81039001 E_AUTOPILOT_CLIENT_TPM_MAX_ATTESTATION_RETRY_EXCEEDED. For Windows Autopilot devices deployed in self-deployment mode or pre-preconfiguration mode, this failure occurs during the "Secure Hardware" step. Subsequent pre-provisioning attempts may resolve this issue.