How to Bypass Windows 11 System Requirements in One Command

Win0x · Feb 13, 2025

I created this PowerShell script at work to make my life easier by bypassing Windows 11 system requirements, allowing Windows 10 to upgrade via Windows Update to the latest Windows 11 version. It also works for upgrading an unsupported Windows 11 system to a newer version.
I've tested this on multiple machines with great success. After running this script, you should also be able to upgrade using a Windows 11 ISO by running setup.exe directly.

What This Script Does

Bypasses Windows 11 hardware checks, including TPM, Secure Boot, RAM, and CPU restrictions.
Removes Windows Update compatibility restrictions, allowing upgrades through Windows Update.
Disables the "System Requirements Not Met" watermark.
Attempts to block telemetry and compatibility scans that could revert the registry changes in future updates.
Targets the latest Windows 11 24H2 update

How to Use

1. Open PowerShell as Administrator
2. Run the following command:

Powershell:

iwr -useb "https://raw.githubusercontent.com/Win11Modder/Win11-Req-Bypass/main/Win11_Bypass.ps1" | iex

3. Restart your computer

Notes

The script also tries to prevent Windows Updates from restoring blocked registry values by disabling automatic tasks related to CompatTelRunner.exe. This should help ensure that major version upgrades continue to install normally. However, if Microsoft introduces new restrictions or makes major changes, I'll try to update the script accordingly.

For issues related to Windows Update freezes, cache problems, or failed updates, I have also added a Windows Update reset feature. This can be executed using the -r parameter:
Unfortunately, this option does not work when running the script via iwr | iex, so you must first download the script from GitHub manually.

GitHub Repository: Win11-Req-Bypass

Use at your own risk, and let me know if you run into any issues!

Feedback is appreciated!

kelper · Feb 13, 2025

Is the github thing yours or are you just pinching it?

Tester · Feb 13, 2025

Might want to add to readme that if no powershell script has ever run on target machine, and is disallowed, that people run something like this first:
powershell Set-ExecutionPolicy RemoteSigned
before running the ps1 script.

Edit:
Tested the script (without -r) in an empty test vm with a fresh 23h2, that did not get offerd to update to 24h2 yet.
Without rebooting the machine, will directly find the update.

Win0x · Feb 13, 2025

kelper said:
Is the github thing yours or are you just pinching it?

Yes, this is my alt account. My main GitHub account is mostly work-related, and I didn’t want to mix this project with it, so I created a new account. I might post more similar projects in the future

Tester said:
Might want to add to readme that if no powershell script has ever run on target machine, and is disallowed, that people run something like this first:
powershell Set-ExecutionPolicy RemoteSigned
before running the ps1 script.

Edit:
Tested the script (without -r) in an empty test vm with a fresh 23h2, that did not get offerd to update to 24h2 yet.
Without rebooting the machine, will directly find the update.
View attachment 125277

Yes, goo point! I've added this to the README. However, this does not affect execution when running the script via iwr | iex, since PowerShell treats it as a direct command rather than a script file. When using iwr | iex, PowerShell doesn't check the execution policy because it processes the script in memory instead of saving it as a .ps1 file.

garlin · Feb 13, 2025

Welcome to ElevenForum.

Several of your script's HW bypass reg keys are ignored (useless) in a live upgrade scenario. Those keys only apply to clean installs.

BypassTPMCheck
BypassRAMCheck
BypassSecureBootCheck
~~BypassCPUCheck~~

When WinPE Setup runs, it checks for any HW bypass keys and doesn't look at any cached compatibility data. The reason is you may be installing to a clean disk which doesn't have any Windows folder. Only the first 3 keys listed above are real, all other purported Bypass* keys are bogus.

I hope you can test a script without any of those keys, and confirm they have no effect on the upgrade process. This topic has been covered by Paul Batard (Rufus) and Michael Niehaus (OOFHours) in more detail.

Tester · Feb 13, 2025

Did not know that! I always download the script / read it, before running it. I never run script from internet directly.

Anyway after installing on my test machines, this option is grayed out:

I would suggest making a second ps1 script, to run after installation, to revert some of the settings back.

Powershell:

$WinUpdatePath = "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"
Remove-ItemProperty -Path $WinUpdatePath -Name "ProductVersion" -Force
Remove-ItemProperty -Path $WinUpdatePath -Name "TargetReleaseVersion" -Force
Remove-ItemProperty -Path $WinUpdatePath -Name "TargetReleaseVersionInfo" -Force
Restart-Service -Name wuauserv -Force

After this, the option is back available for the users again.

Win0x · Feb 13, 2025

garlin said:
Welcome to ElevenForum.

Several of your script's HW bypass reg keys are ignored (useless) in a live upgrade scenario. Those keys only apply to clean installs.

BypassTPMCheck
BypassRAMCheck
BypassSecureBootCheck
~~BypassCPUCheck~~

When WinPE Setup runs, it checks for any HW bypass keys and doesn't look at any cached compatibility data. The reason is you may be installing to a clean disk which doesn't have any Windows folder. Only the first 3 keys listed above are real, all other purported Bypass* keys are bogus.

I hope you can test a script without any of those keys, and confirm they have no effect on the upgrade process. This topic has been covered by Paul Batard (Rufus) and Michael Niehaus (OOFHours) in more detail.

Thanks for the information! I knew that these keys didn’t directly affect Windows Update, but I wasn’t completely sure about their impact when using setup.exe, so I decided to include them just in case. The BypassCPUCheck value is a leftover from when the LabConfig registry modifications first started circulating.

I'll remove those unnecessary keys sometime this week. If you have any links to discussions on this topic I’d really appreciate it.

Tester said:
Did not know that! I always download the script / read it, before running it. I never run script from internet directly.

Anyway after installing on my test machines, this option is grayed out:
View attachment 125289

I would suggest making a second ps1 script, to run after installation, to revert some of the settings back.

Powershell:

$WinUpdatePath = "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" Remove-ItemProperty -Path $WinUpdatePath -Name "ProductVersion" -Force Remove-ItemProperty -Path $WinUpdatePath -Name "TargetReleaseVersion" -Force Remove-ItemProperty -Path $WinUpdatePath -Name "TargetReleaseVersionInfo" -Force Restart-Service -Name wuauserv -Force

After this, the option is back available for the users again.

Good observation! I'll update the script with a solution for this sometime this week. Setups I frequently work with, this option is usually disabled by default, so it didn’t really stand out to me as an issue.

garlin · Feb 13, 2025

Bypassing Windows 11 hardware requirements, revisited

As I stated previously, bypassing the Windows 11 hardware requirements can be done, but that doesn’t mean it’s a good idea. And I stand by that. But based on a couple of Twitter threads…

oofhours.com

[core] add option to bypass TPM 2.0/Secure Boot/RAM requirements for … · pbatard/rufus@b043db3

…Windows 11 ISOs * If 'Extended Windows 11 Installation' mode is selected, the system registry hive of 'sources\boot.wim' is patched to add the Setup\LabConfig registry keys that...

github.com

Non-existent bypass key · Issue #1990 · pbatard/rufus

Checklist I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered. I performed a search in the issue tracker for similar issues using keywords relevant...

github.com

Steve C · Feb 14, 2025

See Bypass Windows 11 System Requirements on Unsupported PC

dacrone · Feb 14, 2025

This one .cmd is all I ever run. Never had any computer have issues installing via iso mounted inside windows (upgrade from win 7, win 10 or from 22h2 to 24h2)

MediaCreationTool.bat/bypass11/Skip_TPM_Check_on_Dynamic_Update.cmd at main · AveYo/MediaCreationTool.bat

Universal MCT wrapper script for all Windows 10/11 versions from 1507 to 21H2! - AveYo/MediaCreationTool.bat

github.com

Win0x · Feb 14, 2025

dacrone said:
This one .cmd is all I ever run. Never had any computer have issues installing via iso mounted inside windows (upgrade from win 7, win 10 or from 22h2 to 24h2)

MediaCreationTool.bat/bypass11/Skip_TPM_Check_on_Dynamic_Update.cmd at main · AveYo/MediaCreationTool.bat

Universal MCT wrapper script for all Windows 10/11 versions from 1507 to 21H2! - AveYo/MediaCreationTool.bat

github.com

This method works but takes a different approach than mine. My script focuses on simplicity, just one command to enable the latest version upgrade through Windows Update

Win0x · Feb 19, 2025

Just updated the script! A few improvements based on feedback:

Removed unnecessary registry entries that weren’t needed for Windows Update upgrades.
Added an interactive menu to set, customize, or remove the Windows Update target release.

Let me know if you run into any issues or have more suggestions!

DornoDios · Feb 24, 2025

Thank you SO much for this! I was scouring the internet looking at the various ways to upgrade my Windows 10 machine to Windows 11. I'd prefer that it be able to use Windows Update for feature updates in the future, so I'm really glad to find this.

Hopefully it still works in October 2025 as I don't plan to update from Windows 10 until they literally force me to.

AK6DN · Feb 24, 2025

So Microsoft has just removed MORE CPUs from the officially supported Win11 compatibility list ...

Microsoft trims more CPUs from Windows 11 compatibility list

OEMs blowing dust from the processor stock cupboard, beware

www.theregister.com

So some systems running Win11 now may not be 'compatible' with Win11 24H2 going forward in the future.

pseymour · Feb 24, 2025

AK6DN said:
So some systems running Win11 now may not be 'compatible' with Win11 24H2 going forward in the future.

Literally the 2nd paragraph says, “We should reiterate that this warning is to OEMs only, not end users or corporations.”

gedi · Feb 27, 2025

Hello, I tried to run the script on a Win10 PC with both the default 24H2 release and also 23H2, but after downloading the W11 update through windows update, while installing I get an error message about my PC not being "ready" for Win11 (not exactly 100% the same message with the 2 different releases, but the result is the same).

Any ideas?

Thanks!

Win0x · Feb 27, 2025

DornoDios said:
Thank you SO much for this! I was scouring the internet looking at the various ways to upgrade my Windows 10 machine to Windows 11. I'd prefer that it be able to use Windows Update for feature updates in the future, so I'm really glad to find this.

Hopefully it still works in October 2025 as I don't plan to update from Windows 10 until they literally force me to.

Thanks! I don’t think Microsoft will ever fully block these workarounds—if they were going to, they probably would have done it already. It’s already tricky enough for most regular users. The methods might change over time, but I’ll keep my script updated as needed

dacrone · Feb 27, 2025

gedi said:
Hello, I tried to run the script on a Win10 PC with both the default 24H2 release and also 23H2, but after downloading the W11 update through windows update, while installing I get an error message about my PC not being "ready" for Win11 (not exactly 100% the same message with the 2 different releases, but the result is the same).

Any ideas?

Thanks!

run the one i linked in post #10

gedi · Feb 28, 2025

Worked great, thanks!

Jake R · Feb 28, 2025

Is there a way to prevent the "What needs your attention" prompt?

My work has about 150 PCs that need to be upgraded to Windows 11 that are not technically supported but can be upgraded via this method, and it doesn't seem to get past 35% installed unless this prompt is accepted, making this task much more time-intensive.

How to Bypass Windows 11 System Requirements in One Command

Member

What This Script Does​

How to Use​

Notes​

My Computer

Well-known member

My Computers

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

New member

My Computer

Active member

My Computers

recently made a series of cow puns

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

New member

My Computer

Similar threads

What This Script Does

How to Use

Notes