A SUPER EASY way to bypass Windows 11 hardware requirements for clean installs

hsehestedt · Oct 16, 2021

Highlights of this method:

1) No third-party tools are required.
2) No action required by user - boot from the install media and install as usual.
3) Won't affect any other aspect of setup or alter the final installation of Windows in any way.
4) Can be used standalone or integrated into other unattended install answer files.
5) Can be used with both BIOS and UEFI based systems.

Super simple:

Copy the text below into a text file and name the file autounattend.xml. Place that file on the root of your install media. If you are use an ISO image file, for example, to install to a VM, simply drop the file into the root of ISO image. For a thumb drive, simply drop it on the root of the thumb drive.

That's it!

Code:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>5</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>4</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
    </settings>
</unattend>

If you already use an autounattend.xml to automate Windows installation, simply add the 5 "RunSynchronousCommand" entries to your existing answer file.

How it works:

I was working with an answer file today when this idea suddenly came to me. I realized that while an answer file is normally used to automate the entire installation of Windows, there is no reason that it couldn't be used to to perform just one simple operation while leaving the rest of setup alone.

In this case, we are using the RunSynchronousCommand to run add several entries to the Windows PE registry. When you boot from your Windows install media, Windows PE is loaded to facilitate the installation of Windows. One of the very first things to happen after Windows PE is started is that an autounattend.xml is loaded if it exists and commands specified by RunSynchronousCommand entries are executed.

Since this is the only thing that we are doing in the answer file it won't affect any other aspect of the setup process. Also, it's worth noting that the only registry affected is the currently running Windows PE registry. It won't affect the final install of Windows in any way whatsoever.

Finally, a special shout out to @Kari whose excellent tutorials regarding unattended setup got me to the point where I had enough knowledge to even come up with this idea.

Enjoy!

RuLich · Oct 17, 2021

Windows cannot parse or process the unattended installation response file [I: \ autounattend.xml] for the [windowsPE] pass. The component or setting specified in the answer file does not exist.

Code:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>5</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>4</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
            <SetupUILanguage>
                <UILanguage>cs-CZ</UILanguage>
            </SetupUILanguage>
            <InputLocale>0405:00000405</InputLocale>
            <SystemLocale>cs-CZ</SystemLocale>
            <UILanguage>cs-CZ</UILanguage>
            <UserLocale>cs-CZ</UserLocale>
            <UILanguageFallback>en-US</UILanguageFallback>
        </component>
        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ImageInstall>
                <OSImage>
                    <Compact>true</Compact>
                </OSImage>
            </ImageInstall>
            <UserData>
                <ProductKey>
                    <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
                <Organization>Warforum</Organization>
            </UserData>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:c:/iso_files/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

This warning occurs when installing a loaded ISO in a Windows 10 environment. Or is it necessary to run the installation from usb?

It doesn't even work in VMware

So I create a boot usb and try a clean installation

hsehestedt · Oct 17, 2021

RuLich, could you clarify for me the precise steps that you are taking? You should copy the text into a text file. Make sure to use something like notepad that does not add any special formatting characters. Rename the file to "autounattend.xml" and make sure that there is no ".txt" or other extension at the end of the file name.

Place the file in the root of the physical drive (thumb drive, DVD, SD card, HDD, SSD, etc.) or in the root of the ISO image.

TIP: As an alternative, especially useful for installation with a VM, you could simply create a separate ISO image file rather than modify your existing installation ISO image. Just mount that ISO image as a second CD/DVD drive. This works because Windows setup will search each drive for autounattend.xml file.

IMPORTANT: There are some things that even this procedure will not workaround. For example, you still require a 2 core (or more) CPU, even if it is an unsupported CPU. In VMware or HYPER-V, make sure that your CPU is assigned a minimum of 2 cores.

I just tested with Hyper-V using both Gen 1 and Gen 2 virtual machine and it worked fine for me. Ironically, I just uninstalled VMware yesterday, but I'll reload it now and try it. Give me a few minutes to post results.

hsehestedt · Oct 17, 2021

RuLich - I see the problem - you have a bunch of stuff in your answer file that does not appear in the one that I posted.

I have not analyzed yours to determine where the problem is but I'll post a few tips for you in a few minutes.

In the meantime, please try my answer file exactly as it appears. I just tested it on VMware as well and it works for both UEFI and BIOS configs there.

RuLich · Oct 17, 2021

Thanks for the reply, but I'm using the "autounattend.xml" file for an unattended installation. I have a few more options to get around the TPM, but this one seemed best to me. But as I say, I will not give up unattended installations.

hsehestedt · Oct 17, 2021

RuLich - I have more info for you. First, take a look at the 2 screenshots below. First one is my answer file loaded in Windows System Image Manager, 2nd one is yours. Note how yours is completely incorrectly structured:

If you already have an answer file into which you want to integrate this solution, you could of course cut and paste the relevant section, however, to avoid errors, let me suggest doing it like this:

1) Run the Windows System Image Manager (where you probably created your existing answer file). Load your answer file into it.
2) Add Windows-Setup > RunSynchronous > RunSynchronousCommand to Pass 1 windowsPE. Add 5 of these just as you see in my file above. Note that you want to set the value "Order" to 1,2,3,4, and 5. Add one registry entry into the value called "Path" for each one. Refer to my sample to see what this looks like.
3) As always, expand all blocks and delete the light colored blocks (the ones with no data in them) and then choose Tools > Validate answer file to confirm that it finds no errors.
4) Save your answer file.

RuLich · Oct 17, 2021

Thanks for the reply, ok I'll try to fix it
PS: I've been doing everything as mentioned above for a long time and creating unattended installations with integrated programs and settings. My "autounattend.xml" file is functional, I also use "unattend.xml".
During the installation, I enter only where to install, name or password and I no longer have to click on anything, the installation is done with all my settings from VMware Workstation Pro.

hsehestedt · Oct 17, 2021

Thanks for the update, RuLich. I suspect that the only part that was malformed was the "RunSynchronousCommand" items. I wasn't doubting that the rest of your answer file works fine.

If you do need any help, just let me know. After all, I want this to work for you

A SUPER EASY way to bypass Windows 11 hardware requirements for clean installs

hsehestedt

Well-known member

My Computers

System One System Two

RuLich

Active member

My Computer

System One

hsehestedt

Well-known member

My Computers

System One System Two

hsehestedt

Well-known member

My Computers

System One System Two

RuLich

Active member

My Computer

System One

hsehestedt

Well-known member

My Computers

System One System Two

RuLich

Active member

My Computer

System One

hsehestedt

Well-known member

My Computers

System One System Two

Similar threads

Latest Tutorials

Latest Support Threads