windows-10-to-windows-11-feature-image

Microsoft Shows Users How To Bypass Its Own Requirements

Microsoft has been under fire for its stringent Windows 11 requirements which prevented many users from upgrading, even on modern PCs. However, the company has finally relented, publishing a simple registry edit that allows millions of more users to upgrade from Windows 10 to Windows 11.

In what can only be described as an unusual development, Microsoft has announced a method whereby users can bypass requirements for TPM 2.0 and newer CPUs to upgrade to Windows 11. It must be noted that the older version of TPM (v1.2) is still required.

Microsoft published details of a registry edit on its Ways To Install Windows 11 webpage that allows users with PCs running older CPUs to upgrade to Windows 11 on the proviso that at least TPM 1.2 is supported and enabled:

Microsoft Registry Edit Details

This will open the way for millions of more users to upgrade to Windows 11 and appears to be a face-saving move from Microsoft. The Redmond giant has stood firmly by its stringent Windows 11 requirements, even in the face of a massive backlash, and by officially condoning this registry edit can now say it hasn’t eased the requirements but merely offered a workaround. The result, however, is the same.

There are other registry edits floating around the web that allows users to bypass the TPM requirement altogether but these are not sanctioned by Microsoft and may well come back to bite the user on the bum.

As far as I am aware, this move from Microsoft is a first. I cannot recall any previous situation whereby Microsoft has officially sanctioned a registry edit to bypass its own requirements. It seems that by constantly standing by its stringent Windows 11 requirements, Microsoft painted itself into a corner.

Please be aware that all other Windows 11 requirements still apply:

  • Processor: 1 GHz or faster with 2 or more cores on a compatible 64-bit processor or System on a Chip (SoC)
  • Memory: 4 GB RAM
  • Storage: 64 GB or larger storage device
  • System Firmware: UEFI, Secure Boot capable

Most machines already running Windows 10 should meet those basic requirements.

12 thoughts on “Microsoft Shows Users How To Bypass Its Own Requirements”

  1. I find it odd that Microsoft does not supply a patch, which users could safely use. Smells like the left and right hand have fumbled the ball, Mindblower!

  2. I am bi-modal with my computers: that is I operate both Macintosh and Windows machines. While Apple has some limitations on 8+ years old machines that cannot tolerate the latest OS upgrade, the fact that Windows 11 cannot be installed on a four year old HP Envy machine is a disgrace. Only MS can create a hodgepodge mess after creating enormous expectations with Windows 11. total madness.

    1. That is because M$ so admires and wants to be like applesauce. so now you can’t update anything. Just like Apple. But I just did what you said you can’t do an 8-year-old HP Laptop.
      I only had to turn on things that were required.

      1. Well I might not have been clear on my example with HP. My reference to Apple was that I have an 8 year old Mac that cannot be updated to the latest OS anymore, so I felt that OK 8 years old, I give them a pass.
        But for Windows 11 I have a FOUR year old desktop whose CPU is listed on MS’s “don’t fly” list and cannot be updated to Windows 11. I think a 4 year old machine is still “young/middle aged” and it is unfair to leave it in the dust. Of course I can use it for quite a while but I am frosted that I can’t take advantage of the highly touted new OS. Appreciate your reply just wanted to be clear, and I’m glad you were able to get it done.

  3. Last week you stated the Microsoft 11 had made errors in checking your computer to get Microsoft 11. My computer said that Windows 11 will work. Yesterday, windows 11 sent me the program to test if the windows 11 will install. It said no. So you had better check your download of for windows 11. Thank you for your effort. I am trying to tell you this since other people will try your download and later find you it was wrong.

    1. Frank appreciate your reply. I don’t recall saying MS made error in checking whether Window 11 could be installed. I ran MS Windows 11 installer checker and my PC failed. I may have inferred that they made an “error” in launching their highly touted new OS but I didn’t say the failure install was a problem. In fact W11 will not run on my HP CPU which is only 4 years old. To me that is a mistake. Error in marketing but the software won’t run on my machine. Period.

  4. I used this method to install Win 11 as an upgrade on my laptop that meets all requirements except for the processor which is a Ryzen 5 2500U. Even with the bypass in place, I could only do the upgrade by mounting the ISO and running the setup from it. The upgrade assistant would still not allow it. Even doing that, I got a warning that I might not be able to receive updates. However, so far, I have gotten two updates and the updates for Defender without issue.
    I did a full system backup of Win 10 with the AOMEI Backupper so I can return to 10 if problems arise.

  5. Hmmn, am I reading too much into this latest message after I ran PV Health checkup: “This PC doesn’t currently meet all the system requirements for Windows 11. Get the details and see if there are things you can do in the PC in Health Check app.” ? Maybe this was there all along and I didn’t notice it, but if it’s new, it might be the result of the the chorus of complaints they have received by mishandling the launch of a highly discussed OS? Sure sounds like the door is ajar just a crack.

    1. Hey Murray,

      That message wasn’t there all along, it is a new thing. The original PC Health Checkup tool was not only inaccurate but also did not provide any indication of why the PC failed the requirements test. Microsoft withdrew that original tool and replaced it with the new one which now provides details of why a PC fails the test.

  6. Well at least I’m not imagining things. The error message did say that my CPU was the issue and when I checked with HP they said my CPU was on the “no fly” list. I suppose I screwed just the same but I do really appreciate your reply.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top

WHY NOT SUBSCRIBE TO OUR NEWSLETTER?

Get great content like this delivered to your inbox!

It's free, convenient, and delivered right to your inbox! We do not spam and we will not share your address. Period!