Before deciding to do a clean install of Windows 11, or upgrading to Windows 11 from Windows 10, we need to have a basic understanding of the Trusted Platform Module (TPM) and what it means in relation to Windows 11 requirements. In this article we will explain the basics of TPM:

  1. What is TPM?
  2. Do I have TPM 2.0 and how do I know?
  3. Can I still upgrade to Windows 11 if I do not have TPM 2.0?
  4. How to bypass TPM 2.0 to update an older computer to Windows 11.

What is TPM?

TPM is an acronym for Trusted Platform Module. It has been around for over 20 years and the previous version TPM 1.0 has been in computers since about 2005. In June of 2015, the Trusted Computing Group (TCG) approved the 2.0 specification ISO/IEC 11889:2015 later in the year. In the past, TPM has been a separate hardware chip on the motherboard, but TPM 2.0 now allows companies like Intel and AMD to incorporate TPM into their chipsets rather than requiring a separate chip. TPM allows for effective management of cryptographic algorithms including Bitlocker, Windows Hello, and others. In a nutshell it's designed to improve and enhance security.

Do I have TPM 2.0 and how do I know?

Chances are you have TPM. If your computer is newer than 5 years you most likely have TPM 2.0. Anything prior is probably TPM 1. But it's easy to check what version you have.

  1. Click your start button or search option and type Windows security to bring up the Windows Security menu.
    Screen Shot of the Windows Security Menu

  2. Click Device Security
    Device Security Screen

  3. Click Security Processor Details
    Details about TPM

In the specifications section, you'll see the specification version you are running (in this case you can see I have TPM 2.0).

What if it says I have TPM 1.0 or 1.2? Can I still upgrade to Windows 11?

The default answer is No. The installation process will fail.

However, there is a way to work around the TPM 2.0 requirement, but I do have reservations. The biggest questions are:

  1. Should you bypass Windows TPM 2.0 requirement?
  2. Do you want to bypass Windows TPM 2.0 requirement?

We'll first post the work-around and then I'll offer my opinion on why you should not bypass the TPM 2.0 requirement.

How to bypass TPM 2.0 for Windows 11

Disclaimer - This involves editing the computer registry. If you are unfamiliar with this, you should NOT attempt this. You should always backup your registry prior to making any changes. Ozzu, its authors and contributors are not accountable for any damage to your computer from improper registry edits. Also note this work-around was provided by Microsoft so it is safe if executed properly.

Here are the steps on how to bypass the Windows 11 TPM 2.0 requirement:

  1. Press Win +R to open Run and type regedit. Click OK or press Enter to open the Registry Editor.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup from the top bar.
  3. Right-click the main panel and select Create a new DWORD (32-bit) Value.
  4. Give it the name: AllowUpgradesWithUnsupportedTPMOrCPU.
  5. Set its value to 1. Click OK.
  6. Exit the registry editor.

Your PC has now bypassed the Windows 11 TPM 2.0 restrictions and you can now upgrade to Windows 11.

Should I bypass the TPM 2.0 requirement?

In a word - NO. Here is why I think you should not do this:

  • TPM 2.0 is there to help provide much-needed security.
  • TPM 2.0 has been available on computers sold after 2016.
  • If your computer is older than 2016, it is most likely out of warranty and has outdated hardware, and it's time to start thinking about a new one. I just personally would not recommend bypassing TPM 2.0.

I hope you've found this article helpful.

Credits

https://support.microsoft.com/en-us/topic/what-is-tpm-705f241d-025d-4470-80c5-4feeb24fa1ee
https://www.microsoft.com/security/blog/2015/06/29/governments-recognize-the-importance-of-tpm-2-0-through-iso-adoption/
https://www.maketecheasier.com/safely-bypass-tpm-windows/

This page was published on It was last revised on

Contributing Authors

1

1 Comment

  • Votes
  • Oldest
  • Latest
Commented
Updated

I actually have an interesting situation. Currently, I am still using Windows 10 because of this.

When I used the Windows compatibility tool it said I only had TPM 1.2. I looked into it further and my hardware in fact supported enabling TPM 2.0, but my motherboard manufacturer Asus never appeared to have finished their user interface to allow you to toggle TPM 2.0 to be enabled for the Asus Maximus VIII Hero motherboard. It seems that in slightly newer versions of the motherboard they finally did create the option to toggle TPM 2.0 on, but mine did not have it. However, the motherboard behind the scenes did support enabling TPM 2.0. Long story short, I found an extremely complicated and perhaps dangerous way to update the firmware without having that option in the menu interface. After using AMI to setup an IFR extractor in UBU to get the configuration file offset, I was able to effectively write to the BIOS the configuration change I needed. Again extremely dangerous, but I did take the chance and it worked. I was able to force the Asus Maximus VIII Hero motherboard to have TPM 2.0 enabled so that Windows 11 could actually utilize it.

Now when I run the compatibility tool it in fact says I have TPM 2.0, but it says my CPU is not compatible:

Intel Core i7-6700K CPU not Windows 11 compatible

My CPU is:

Intel Core i7-6700k CPU @ 4.00ghz

Everything I have read says my CPU is more than capable of running Windows 11, for example, these threads:

https://answers.microsoft.com/en-us/windows/forum/all/intel-core-i7-6700k-cpu-400-ghz-processor-windows/406bc2a0-858c-460e-9f13-6b1b114c3989
https://www.reddit.com/r/WindowsHelp/comments/o7yjgl/windows_11_cant_support_intel_core_i76700k/

Anyway, I am curious if your workaround above would get me around this CPU requirement. Many believe Microsoft got this wrong not to include some of these CPUs like the one I have.

  • 0
    I noticed the option to bypass TPM 2.0 was called AllowUpgradesWithUnsupportedTPMOrCPU. Notice the OrCPU in the name itself, that is why I am thinking it probably will work! — Brian Wozeniak
  • 0
    The registry work-around is supposed to bypass CPU requirements as well as TPM — Mark Bowker
add a comment
0