Another way to bypass Windows 11 requirement checks (for a clean install)

There have been a number of methods noted already, so I'm not going to rehash those, but personally, I like this method. It will take a few minutes to do, but once done, you will have a Windows image that will bypass the Win 11 requirement checks without ANY actions being needed by the user. It is 100% transparent and setup will operate exactly as it always does.

When booting from Windows installation media, Windows setup runs under Windows PE (Preinstallation Environment). This is contained within the BOOT.WIM file. All that is needed is to modify the Preinstallation Environment registry. Note that this will have NO effect on the final Windows installation - no registry changes or changes of any kind will be made to the final installation.

To implement this method, use these steps:

1) Install the Windows ADK from here: https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install

NOTE: When installing the ADK, you will be shown a list of items that can be installed. You can choose to install only the Deployment Tools from this list. This makes the install quick and very small.

2) Open a command prompt by running the Deployment and Imaging Tools Environment in elevated mode (as Administrator). You will find this item in Start > All Apps > Windows Kits. Again, make sure to run this elevated (as Administrator).

TIP: When you open the Deployment and Imaging Tools Environment, you can issue a CD \ to change paths to the root of the volume. This makes the prompt at the command line much shorter and less obtrusive while you are working. Leave this window open until the very end. We will run all of the needed commands from the Deployment and Imaging Tools Environment.

NOTE: This environment is basically like any other command prompt, except that various variables and paths are set so that the tools we need such as DISM.exe and OSCDIMG.exe are in the path, ensuring that the latest version of these utilities is run from the ADK location.

3) We will now create the folders that we need for this project by running these commands. You can use other folders, but these are what I will use in my examples:

MD "C:\Project\ISO_Files" MD "C:\Project\Mount"

4) Mount your Windows ISO image and copy ALL files to C:\Project\ISO_Files.

5) Run the following commands. Note that you can copy and paste all these commands in at once if you wish.

dism /mount-wim /wimfile:c:\project\iso_files\sources\boot.wim /index:1 /mountdir:c:\project\mount reg load HKLM\offline c:\project\mount\windows\system32\config\system reg add HKLM\offline\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f reg unload HKLM\offline dism /unmount-image /mountdir:c:\project\mount /commit dism /mount-wim /wimfile:c:\project\iso_files\sources\boot.wim /index:2 /mountdir:c:\project\mount reg load HKLM\offline c:\project\mount\windows\system32\config\system reg add HKLM\offline\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f reg add HKLM\offline\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f reg unload HKLM\offline dism /unmount-image /mountdir:c:\project\mount /commit oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,b"c:\project\ISO_Files\boot\etfsboot.com"#pEF,e,b"c:\project\ISO_Files\efi\microsoft\boot\efisys.bin" "c:\project\ISO_Files" "c:\project\Windows.ISO" rd /S /Q "c:\project\iso_files" rd /S /Q "c:\project\mount"

NOTE: When the above commands have finished running, the updated ISO image file can be found as C:\Project\Windows.ISO.

I bet this is what creating the USB flash drive with Rufus does. It simply modifies the registry in advance and it is easier for beginners without any experience. Another option is the hybrid Windows 10/11 USB flash drive, but sadly it doesn't work in UEFI (GPT) mode for 22H2. It still works in Legacy BIOS (MBR) mode.

@hsehestedt There will be very few members will try this method if you did not know you can use Rufus to create a bootable USB flash drive that will bypass Windows 11 requirement.

If you are looking for a way to Create Windows 11 Bootable USB for Unsupported Computer. Don’t worry, because in this video, you will learn the easiest way to create a bootable USB for an unsupported Computer.

All hacks are discussed at the appropriate threads, no need to go into details. For 22H2 also stay disconnected from the internet. For a clean installation this allows you to create a local account instead of a Microsoft account (read thread for the additional steps required), and for upgrading it prevents Windows Update messing with your drivers and a hidden online compatibility check that fails the upgrade.

spapakons said:

I bet this is what creating the USB flash drive with Rufus does. It simply modifies the registry in advance and it is easier for beginners without any experience. Another option is the hybrid Windows 10/11 USB flash drive, but sadly it doesn't work in UEFI (GPT) mode for 22H2. It still works in Legacy BIOS (MBR) mode.

Click to expand...

I've actually been in touch with the author of Rufus regarding this. They use one of two methods depending upon the circumstance. This method, or the use of an unattended answer file.

Question: I'm not quite understanding what you mean by a hybrid Win 10/11 flash drive. Could you tell me more about that since you have made me curious?

FreeBooter said:

@hsehestedt There will be very few members will try this method if you did not know you can use Rufus to create a bootable USB flash drive that will bypass Windows 11 requirement.

If you are looking for a way to Create Windows 11 Bootable USB for Unsupported Computer. Don’t worry, because in this video, you will learn the easiest way to create a bootable USB for an unsupported Computer.

Click to expand...

Yes, I am aware that most people will simply want to use a third-party tool like Rufus. I post this for those few individuals who want to know how to do this without third-party tools.

I do a LOT of things for which other tools are available without the use of those tools. It's helped me understand a great deal about how things work under the covers.

hsehestedt said:

I'm not quite understanding what you mean by a hybrid Win 10/11 flash drive.

Click to expand...

Take a standard Win 10 install USB and replace its install.esd (or install.wim) with one from the Win 11 install media.

Yep. Takes twice as much disk space to stage, but you can teach it anyone w/o DISM, reg commands, or answer files.

hsehestedt said:

Yes, I am aware that most people will simply want to use a third-party tool like Rufus. I post this for those few individuals who want to know how to do this without third-party tools.

Click to expand...

Even without the need to by-pass anything with Windows 10 back then, a lot of people use Rufus to make a bootable installer. Rufus just added the by-pass feature for Windows 11.

@hsehestedt would this work on an older Windows 7 computer i bought the other day ? Just curious ??

btw BypassStorageCheck is urban legend. Both Rufus and ventoy stopped supporting this non-existent reg key.

Since this is @hsehestedt thread, I don't mind hijacking it.
I have done a number of clean installs of 11 but not any on incompatible hardware. I've tried to stay away from it, but know I'm going to be faced with it sooner or later. I've read a few of the threads, but still am confused about a few things since I've never actually done it. I understand several of the various methods to do it, just not all ongoing ramifications of using incompatible hardware. Please bear with my ignorance here as I have several basic newbie questions.

1. If I clean install on incompatible hardware using this (or any method), I understand that the machine will get windows updates as usual, but when a version update comes down the pike, will it do its own compatibility check and fail until I download the new version iso, alter it, and manually upgrade to new version?

2. If I do a repair install on an incompatible machine, I have to use an altered iso for the same or later version, just as with any normal repair install. Is that right?

3. If I'm working on incompatible machine and need to get into advanced startup from boot media, does that iso have to be an altered one? I would think not, but I'm green as goose crap about this whole thing.

4. If I am clean installing windows on a compatible machine, do I need separate standard install iso media or is there any ramifications of using the same media as I've created for incompatible machines? Wouldn't subsequent version updates recognize that machine as being 100% compatible? Do I need separate install media depending on whether a machine is compatible or not?

I'm ducking my head in shame here for having to ask.

If you bypass compatibility check and install Windows 11 on unsupported computers you can do all updates without any issue. You are not offered the upgrade to a newer version, for example from 21H2 to 22H2. To upgrade to the newer version you must bypass compatibility check again or use the USB created with Rufus. Even then you must disconnect from the internet because at some point it does a hidden online compatibility check and fails. If you are disconnected it cannot do this check and proceeds without any issue. Staying offline also prevents Windows Update messing with the drivers and risking a BSOD. As already mentioned a hybrid Windows 10/11 USB flash drive is a standard Windows 10 one with the file \sources\install.esd (or .wim) replaced with the respective file from Windows 11 ISO. This since 22H2 works only for a Legacy (MBR) USB flash drive. It doesn't work for an UEFI (GPT) USB flash drive, so you either have to hack Registry (clean installation) or replace the appraiserres.dll file (upgrade) or use a USB created by Rufus.

flashh4 said:

@hsehestedt would this work on an older Windows 7 computer i bought the other day ? Just curious ??

Click to expand...

That method is for a clean install, so no, it won't work for upgrading from Win 7.

I know that other upgrade methods are out there, but below are my personal notes on ways to install Win 11 on technically unsupported hardware, both upgrade and clean installs.

NOTE: As was previously stated, there are other ways mo do this. I am just personally a fan of avoiding third-party utilities (it's a quirk of mine) so all these methods are without any third-party utilities:

---------------------
This document describes how to install Windows 11 on systems that do not technically meet the Windows 11 hardware requirements. Before we even begin, I would like to point out that there are other methods not covered here to accomplish this task. For example, the "Rufus" utility can create installation media to allow for installation on unsupported hardware. However, the goal with this document is to provide methods to install Windows 11 without the need for any third-party utilities.

* CLEAN INSTALLATION PROCEDURES *

IMPORTANT: Be sure to read both PART 1 and PART 2 below. Part 1 describes how to bypass the initial Windows hardware requirements. Part 2 describes how to create a local user account and bypass the need to login with a Microsoft account later on in the installation.

* PART 1 - This section describes how to bypass the initial hardware requirements for Windows 11. *

Note: All methods below have the same goal, which is to set registry entries in Windows PE to bypass the Windows setup requirements. This will NOT affect the final installation of Windows. It only affects the registry entries of Windows PE which is loaded in memory during setup. As soon as the first reboot during installation occurs, these registry entries are lost, having already served their purpose.

* Method 1 - Updating the Windows BOOT.WIM Registry *

Personally, this is my preferred method because it is 100% transparent to users. When booting from Windows installation media, Windows setup runs under Windows PE (Preinstallation Environment). This is contained within the BOOT.WIM file. By updating the registry for this environment, installation will look exactly the same as always and no answer file is need, nor is any other action required by the user.

This method requires a little bit of work to implement, but once the Windows image is updated, no action is needed by the user.

To implement this method, use these steps:

1) Install the Windows ADK from here: Download and install the Windows ADK

NOTE: When installing the ADK, you will be shown a list of items that can be installed. You can choose to install only the Deployment Tools from this list. This makes the install quick and very small.

2) Open a command prompt by running the "Deployment and Imaging Tools Environment" in elevated mode (as Administrator). You will find this item in Start > All Apps > Windows Kits. Again, make sure to run this elevated (as Administrator).

TIP: When you open the Deployment and Imaging Tools Environment, you can issue a "CD \" to change paths to the root of the volume. This makes the prompt at the command line much shorter and less obtrusive while you are working. Leave this window open until the very end. We will run all of the needed commands from the Deployment and Imaging Tools Environment.

NOTE: This environment is basically like any other command prompt, except that various variables and paths are set so that the tools we need such as DISM.exe and OSCDIMG.exe are in the path, ensuring that the latest version of these utilities is run from the ADK location.

3) We will now create the folders that we need for this project by running these commands. You can use other folders, but these are what I will use in my examples:

MD "C:\Project\ISO_Files"
MD "C:\Project\Mount"

4) Mount your Windows ISO image and copy ALL files to C:\Project\ISO_Files.

5) Run the following commands. Note that you can copy and paste all these commands in at once if you wish.

dism /mount-wim /wimfile:c:\project\iso_files\sources\boot.wim /index:1 /mountdir:c:\project\mount
reg load HKLM\offline c:\project\mount\windows\system32\config\system
reg add HKLM\offline\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\offline\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\offline\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\offline\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\offline\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f
reg unload HKLM\offline
dism /unmount-image /mountdir:c:\project\mount /commit
dism /mount-wim /wimfile:c:\project\iso_files\sources\boot.wim /index:2 /mountdir:c:\project\mount
reg load HKLM\offline c:\project\mount\windows\system32\config\system
reg add HKLM\offline\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\offline\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\offline\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\offline\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f
reg add HKLM\offline\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f
reg unload HKLM\offline
dism /unmount-image /mountdir:c:\project\mount /commit
oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,b"c:\project\ISO_Files\boot\etfsboot.com"#pEF,e,b"c:\project\ISO_Files\efi\microsoft\boot\efisys.bin" "c:\project\ISO_Files" "c:\project\Windows.ISO"
rd /S /Q "c:\project\iso_files"
rd /S /Q "c:\project\mount"

NOTE: When the above commands have finished running, the updated ISO image file can be found as C:\Project\Windows.ISO.


* Method 2 - Using an Autounattend.xml Answer File *

Note: The answer file provided here does nothing except to bypass the Windows 11 system requirements.

If you want to create an answer file on your own, these are the steps to include the entries that bypass Windows 11 system requirements.

Create a new answer file or modify an existing answer file with the following entries:

Add the component Microsoft Windows Setup\RunSynchronos\RunSynchronousCommand to Pass 1 windowsPE.

Set the following values:

Order: 1
Path: reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f

Repeat the above steps 4 more time (for a total of 5 "RunSynchronousCommand" entries) with the following entries:

Order: 2
Path: reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f

Order: 3
Path: reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f

Order: 4
Path: reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f

Order: 5
Path: reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f

* Method 3 - Manually Modify the Registry for Windows Setup *

Begin installation of Windows from your installation media. At the first static screen where Windows setup requests information from you during setup, press SHIFT + F10 to open a command prompt.

Type regedit and hit ENTER. Add the following entries:

HKLM\System\Setup\LabConfig BypassTPMCheck reg_dword 0x00000001
HKLM\System\Setup\LabConfig BypassSecureBootCheck reg_dword 0x00000001
HKLM\System\Setup\LabConfig BypassRAMCheck reg_dword 0x00000001
HKLM\System\Setup\LabConfig BypassStorageCheck reg_dword 0x00000001
HKLM\System\Setup\LabConfig BypassCPUCheck reg_dword 0x00000001

Close the Registry Editor and the command prompt. Continue installation normally.

* Method 4 - Using a .reg file *

Create a file with the extension .reg. Place the following text between the bars (----) into that file. Don't include the "----" lines.

----
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig]
"BypassTPMCheck"=dword:00000001
"BypassSecureBootCheck"=dword:00000001
"BypassRAMCheck"=dword:00000001
"BypassStorageCheck"=dword:00000001
"BypassCPUCheck"=dword:00000001
----

Save the file, making sure to use a ".reg" file extension. Example: Bypass.reg

Drop this registry file onto your install media. After starting setup, when you reach the first static screen where information is requested by setup, press Shift + F10 to open a command prompt. Navigate to the drive letter where the .reg file is located and then run it. You can run it by simply typing the name of the file and pressing <ENTER>. Close the command prompt and continue installation of Windows as usual.

* Method 5 - Using a Batch File *

Create a text file with the extension .bat. Example: Bypass.bat. Place the following six lines in that file:

@echo off
reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f > NUL
reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f > NUL
reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f > NUL
reg add HKLM\System\Setup\LabConfig /v BypassStorageCheck /t reg_dword /d 0x00000001 /f > NUL
reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f > NUL

NOTE: The "> NUL" simply suppresses the output from being displayed for "silent" operation.

Drop this file onto your install media. After starting setup, when you reach the first static screen where information is requested by setup, press Shift + F10 to open a command prompt. Navigate to the drive letter where the .bat file is located and then run it. You can run it by simply typing the name of the file and pressing <ENTER>. Close the command prompt and continue installation of Windows as usual.


* Part 2 - This section describes how to create a local account during installation and *
* bypass the requirement to logon with a Microsoft account in Windows 11 Pro. *

* If you have a network connection *

When you reach the screen where you have a choice to "Set up for personal use" or "Set up for work or school", select "Set up for work or school" and click on "Next".

On the next screen, select "Sign-in options", then "Domain join instead". Don't worry, we are not joining a domain!

On the next screen, supply the local user name that you want to create and then continue through setup as normal.

* If you do NOT have an Internet connection *

When you reach the screen where Windows wants to connect you to a network to create a local user account, press SHIFT + F10 to open a command prompt, and then run "OOBE\BypassNRO". The system will reboot. After rebooting, you will start back up at the screen asking you to select the correct keyboard layout. When you get back to the "Let's connect you to a network" screen, you will have an option to select "I don't have internet". Choose that option. On the next screen, select "Continue with limited setup". Enter your local user account name, and then continue with setup as usual.

* UPGRADE INSTALLATION PROCEDURES *

* Method 1 *

When installing Windows 11 as an upgrade, Windows will make use of the file \sources\appraiserres.dll to determine the system requirements for installation. To bypass the system requirements, you can replace that file with a fake appraiserres.dll file.

Delete or rename the original \sources\appraiserres.dll file on your installation media. Replace the file that you deleted or renamed with a fake appraiserres.dll. You could simply create a text file and rename it to appraiserres.dll. If you prefer, you could also just grab the appraiserres.dll from a Windows 10 distribution.

You can now run setup from the root of the installation media to begin an upgrade install.

* Method 2 *

NOTE: If you follow the steps in method 1, you do not need to follow the steps outlined in method 2.

You can bypass just the TPM 2.0 and supported CPU requirements for an upgrade installation by making the following change to the registry:

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup]
"AllowUpgradesWithUnsupportedTPMOrCPU"=dword:00000001

You can make this into a .REG file if you wish. Then, simply double-click that file to merge the contents into the registry. If you want to do this, open notepad, paste in the following lines between the "----" lines (not including those lines), and save it to a file with a .REG extention, then double-click that file to make the registry change:

----
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup]
"AllowUpgradesWithUnsupportedTPMOrCPU"=dword:00000001
----

NOTE: This registry setting bypasses the need for a supported CPU and a TPM 2.0 but a TPM 1.2 would still be needed. If you still do not meet this requirement, then please follow the steps in method 1 instead.

References
==========

If anyone is curious why I have this insistence on doing stuff without third-party utilities, it was so that I could learn to do these things myself and script the procedures, allowing me to write my own program to automate all these tasks.

That in turn allowed me to write my own program that automates just about every task that I can think of related to Windows image management and deployment. Here is what the main menu of my program looks like. From the menu, you can see that it can perform a lot of tasks.

I'm impressed by your work on this and by your program, WIM Tools.

But I don't see any advantage to anyone else (other than you, I mean -- I understand your motivation for writing this procedure up) in doing it your way. I don't use any third-party stuff for my installations on non-compliant hardware. I follow the two-step procedure that takes about 15 seconds all told:

1) Create an empty text file and name it appraiserres.dll. (5 secs)
2) When the installation has started and written its directory to C:\, and while there's still a taskbar visible, open the installation directory, and substitute the empty appraiserres.dll file for the original. (10 secs)
3) Proceed with the installation.

hsehestedt said:

References
==========

Ways to install Windows 11 - Microsoft Support

Learn how to install Windows 11, including the recommended option of using the Windows Update page in Settings.

support.microsoft.com

Click to expand...

You have to realize that people come here for a quick solution and not to learn these things. It should be something that involves a couple of mouse clicks or so. They don't share the same interest of learning these things. They just want to solve their issues as quickly and painless as possible.
Looking at those notes, it looks very discouraging to do go with this method when Rufus already made it easy for everyone.

@hsehestedt .......... thanks for the info !! For now i will leave it as is ! Appreciate it ...........

Wisewiz said:

I'm impressed by your work on this and by your program, WIM Tools.

But I don't see any advantage to anyone else (other than you, I mean -- I understand your motivation for writing this procedure up) in doing it your way. I don't use any third-party stuff for my installations on non-compliant hardware. I follow the two-step procedure that takes about 15 seconds all told:

1) Create an empty text file and name it appraiserres.dll. (5 secs)
2) When the installation has started and written its directory to C:\, and while there's still a taskbar visible, open the installation directory, and substitute the empty appraiserres.dll file for the original. (10 secs)
3) Proceed with the installation.

Click to expand...

In 22H2 you must also disconnect from the internet the whole time or it will fail.

OK, Y'all. I made up my mind I'm finally going to attempt this on an old laptop. I think I've gotten answers to all the questions I asked except one regarding compatible machines.

#4. If I am clean installing windows on a compatible machine, do I need separate standard install iso media or is there any ramifications of using the same media as I've created for incompatible machines? (I'm taking the easy way out and use the Rufus method) I want to be able to bypass bitlocker device encryption on Home and use local account unless a user wants a MS account) Wouldn't subsequent version updates recognize that machine as being 100% compatible? Do I need separate install media depending on whether a machine is compatible or not?