josephm101 / force-windows-11-install

Modifies Windows 11 installation ISO to bypass compatibility checks both pre and post installation

Force-Windows-11-Install

Please note: If you plan to make a bootable USB with the Windows 11 installer, please consider using Rufus instead. It will handle patching the installer, and it gets updated more often.

Win11-TPM-RegistryBypass

This tool creates a modified Windows 11 installer ISO using an existing one, containing a registry hack that bypasses the setup-time compatibility checks, as well as an experimental patch that forces feature updates and in-place upgrades to install, ignoring incompatibilities.

Looking for Windows 11 ISOs? Head over to UUP Dump to download the latest Dev build of Windows 11 and create a bootable ISO. Need help? You can start here.

I am also developing a command-line interface tool for UUP Dump, so that you can download the latest update package for a given channel, and generate an installable ISO for use with this script. Using just a single command. Requires Python 3 and the requests module. You can check out the project here.

Extras:

Looking for some Windows 11 hacks? I have some mod scripts on another repository, Windows11_Mods.

---

Please note that this tool does not allow Windows 11 to be installed on 32-bit (x86) platforms.

Windows 11 is a 64-bit-only OS, and therefore will not work at all on older architectures such as 32-bit (x86). If you are unsure what architecture your system is, press Win+R, type cmd, and press Enter. Then copy and paste the following command in command prompt: wmic cpu get DataWidth. If you get 64, you have a 64-bit processor, and can run Windows 11.

---

How it works:

This workaround injects three keys into the registry of the Windows Setup environment in the boot.wim file in the Windows 11 ISO that force the installer to skip TPM, Secure Boot, memory and CPU checks, allowing the user to install Windows 11 using the original installer. There are extra switches that can be passed for more in-depth patching, such as one that allows for forcing Windows Updates and in-place upgrades to skip compatibility checks; see extra switches for more.

A Windows 10 ISO is not required for this method.

Why?

The installer for Windows 11 checks for both TPM and Secure Boot, and will not install on "unsupported" processors. However, many of the devices that don't have TPM, Secure Boot, or a compatible processor, are perfectly capable of running Windows 11.

Usage

TIP: It's recommended to copy or move the Windows 11 ISO image to the same directory as the script to make things easy, as there can be some bugs with images located outside of the directory. If you have any issues with the script, please do not hesitate to open an issue.

NOTE: There is an issue with reading and writing files on external drives.

• In the repository directory, run env.bat. This will open up a new elevated PowerShell window in the repository. You may be prompted by UAC (User Account Control) to grant administrative privileges to PowerShell. Click Yes.
• Type .\Win11-TPM-RegBypass.ps1 in the PowerShell window, but don't hit Enter just yet.
• Follow up with -Source. This is where you're going to define the location of the Windows 11 ISO you want to use. TIP: If your Windows 11 ISO is not in the same directory as the script, you can locate the ISO with File Explorer, select it, then click "Copy path" in the File Explorer ribbon, or hold down Shift and right-click the file, the click "Copy as path" in the context menu. (Windows 10)

• Lastly, we need to define -Destination; the output ISO. You can make it short and sweet, and it doesn't need to be a full path (the new ISO would be created in the repository directory in that case).
• Make sure all file paths are surrounded with quotation marks to avoid potential issues.

Your final command should look something like this:

.\Win11-TPM-RegBypass.ps1 -Source "22000.100.210719-2150.CO_RELEASE_SVC_PROD2_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO" -Destination "Win11-New.iso"

• Now you can press Enter. The script should start running, and provided everything works correctly, you should now have a new bootable Windows 11 ISO image without the TPM or Secure Boot restrictions during install. However, if you also want to inject a patch into the

Extra switches

Note that any options that modify install.wim may result in the process taking longer. If the Windows image contains more than one edition, you will be asked to select one or more editions to modify. Any editions not selected will not be included in the final image.

Modifications

• -InjectVMwareTools - Injects the VMware tools installer into the install.wim image to run when the system boots for the first time. VMware needs to be installed on your system, and the VMware Tools ISO needs to exist in its application folder.
• -InjectPostPatch - (EXPERIMENTAL) Injects a script into the install.wim image to run when Windows 11 boots for the first time. The modifications that the script makes are intended to force upgrades that are done through Windows Update, as well as in-place upgrades, to succeed regardless of compatibility status. It does this by forcing the upgrade tool to bypass the compatibility checks that would otherwise cause the installation/upgrade to fail.
• -PrepareUpgrade - (EXPERIMENTAL) Modify the current system to bypass compatibility checks to allow in-place upgrades using the modified ISO. Can be called on its own (no other parameters), or otherwise run after generating the ISO. See below for more information. Note: If doing an in-place upgrade using setup.exe from a Windows 11 ISO image, do NOT disable the downloading of updates. This seems to result in a TPM error. The reason is currently unknown.
• -UndoPrepareUpgrade - (EXPERIMENTAL) Undo the changes made by -PrepareUpgrade, if there are any. Can only be called by itself.

Other switches

• -VerboseMode - Enable verbose output, which isn't much
• -GuiSelectMode - Shows a GUI for selecting multiple editions to modify as opposed to the CLI-based selection method
• -HideTimestamps - Disable printing the amount of time it took to complete a process

Prepare Upgrade feature (required for in-place upgrades on unsupported systems)

.\Win11-TPM-RegBypass.ps1 -PrepareUpgrade will only modify the current Windows installation.

.\Win11-TPM-RegBypass.ps1 -Source [source] -Destination [destination] <Other parameters> -PrepareUpgrade is a one-liner that will perform modifications to the current Windows installation after generating the ISO.

---

Set-WindowsInsiderRing.ps1

Forcibly change the Windows Insider ring (and enable Windows Insider if it is disabled). The script needs to be run as an administrator.

Options

• -Dev - Set ring to Dev
• -Beta - Set ring to Beta
• -ReleasePreview - Set ring to ReleasePreview

---

Win11-ImageBuilder (Obsolete)

Win11-ImageBuilder has been marked obsolete, and is no longer maintained. For the documentation on the tool, navigate here.

---

Background

Following the announcement of Windows 11, many users were rather discouraged to discover the new TPM, CPU and Secure Boot restrictions imposed by Microsoft for Windows 11 in an attempt to block devices lacking these features from installing and running it, and encouraging them to buy newer, and possibly more locked-down/restrictive devices. This has left a lot of otherwise enthusiastic users in the dark, with virtually no way to upgrade without buying a new machine sporting a CPU newer than 2018, as well as the aforementioned features. However, it's been proven time and time again that on many devices that Microsoft considers unsupported, the Windows 11 experience was comparatively normal, with few to no issues. Microsoft claims that their reasons for enforcing these restrictions have to do with both compatibility and security. Additionally, they claim that many of the older devices that Windows 11 was tested on tended to have issues resulting in BSoD (Blue Screen of Death) errors, and other instabilities and issues. However, many people running Windows 11 on these so-called incompatible devices didn’t report any major issues at the time of writing despite some missing features such as virtualization. While it’s not exactly recommended to run Windows 11 on an incompatible device (especially if it’s a daily driver), it certainly is possible to bypass Microsoft’s restrictions to allow installing or upgrading to Windows 11.

Included binaries

Binary name	Description	Source
7z.exe	7-Zip CLI interface	Source
oscdimg.exe	OSCDIMG - Used for rebuilding ISO images after processing (Pulled from the Windows 10 ADK)	Source

force-windows-11-install's Issues

No ESD Support

So as you know, Windows 11 is being completely gay by not allowing computers with great specs (like my own - Alienware Area51 R7) machine to run the operating system.
Even though I have secure boot and TPM firmware support both enabled, plus exceeding the ram, storage and CPU requirements in addition to having a Windows insider account. They still say my PC cannot run Windows 11. Microsoft initially let me in to the preview June 24th. And now reverted me back to the release preview channel. And I've been in the Dev channel since Windows 8.1.
Suffice it to say, your script is the only one out there which will let me truly run a fresh copy of Windows 11 from boot. But I can't use it with ESD files. Which is the only way Rufus will let me create a bootable USB and run it in UEFI mode using fat32 with secure boot enabled.
Once you are able to add ESD support, I'll totally be able to recommend this to anyone. Thank you so much for building this tool. It's greatly appreciated. Win support works real well. I have a spare machine that can run those files without any problems.

error with Win11-ImageBuilder.ps1

Error in:

PS C:\Users\Herb\Desktop\Force-Windows-11-Install-main> .\Win11-ImageBuilder.ps1 -Source "Win.iso" -Destination "winbk.iso"

Security warning
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning
message. Do you want to run C:\Users\Herb\Desktop\Force-Windows-11-Install-main\Win11-ImageBuilder.ps1?
[D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"): r
C:\Users\Herb\Desktop\Force-Windows-11-Install-main\Win11-ImageBuilder.ps1 : A parameter cannot be found that matches
parameter name 'Source'.
At line:1 char:26

• .\Win11-ImageBuilder.ps1 -Source "Win.iso" -Destination "winbk.iso"

•                      ~~~~~~~
  

  • CategoryInfo : InvalidArgument: (:) [Win11-ImageBuilder.ps1], ParameterBindingException
  • FullyQualifiedErrorId : NamedParameterNotFound,Win11-ImageBuilder.ps1

System Requirements

What are the system requirements for using this tool?

For example, can I just use a computer with a Windows 7 Ultimate 32-bit before operating this?

Dont use the variable name $Verbose

https://stackoverflow.com/questions/65700615/powershell-a-parameter-with-the-name-was-defined-multiple-times-for-the-command

Renaming it to $Verbose2 fixed it for me

Many errors when running script. Bypass did not work.

Hello, I am getting the following errors when running the script. The new ISO does not bypass TPM check.

22H2 Error input string was not in a correct format

boot.wim patched. Took 00:00:37
Cannot convert argument "bytes", with value: "force-windows-11-install", for "WriteAllBytes" to type "System.Byte[]":
"Cannot convert value "force-windows-11-install" to type "System.Byte[]". Error: "Cannot convert value
"force-windows-11-install" to type "System.Byte". Error: "Input string was not in a correct format."""
At C:\Users****\Downloads\Force-Windows-11-Install-main\Win11-TPM-RegBypass.ps1:835 char:5

• [System.IO.File]::WriteAllBytes($sb_mark, $CONTENT)
  

• ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : NotSpecified: (:) [], MethodException
  • FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument

Please explain what the Base64 line is

Hello

I tried to decode the Base64 line but cannot.

Please explain what it is. Im not gonna run unknown code on my system

Don't trust precompiled binaries without at least attribution

I don't trust precompiled binaries in so-called open-source projects which don't publish their sources and build instructions or at least attribution to where to get original trusted sources or binaries. For example, many will assume by the name 7z that those files are associated with 7zip. But lots of malware are just renamed files made to look like something benign as a vector.

Please document all precompiled binaries in this project so people can get the correct versions of the binaries from a trusted source or build the binaries from source code.

How to delete the commands from the computer

Hello i have a problem with these scripts because i would like to completely remove them cus i wanted to install new windows 10 but i accidently clicked the command to stop. how to remove it (also the script "Get windows 11 on 'unsupported' device.)

unable to run scripts in powershell

You need to enable scripts in powershell

powershell -ExecutionPolicy Bypass -File Win11-TPM-RegBypass.ps1 -Source {iso path file} -Destination [iso path final ]

-PrepareUpgrade flag doesn't work on Build 25977

After running .\Win11-TPM-RegBypass.ps1 -PrepareUpgrade and also without disabling the downloading of updates.

Avoid Windows 10/11 flavor issues with mount-windowsimage

Hi,
Good workaround project. Very helpful.
Successfully tested with 22533.1001.220107-2122.RS_PRERELEASE_CLIENTMULTI_A64FRE_EN-US.ISO. btw. mount-windowsimage is Windows flavor dependent and fails with "Windows cannot verify the digital signature for this file" when opening Windows 11 boot.wim with an older, non-compatible Windows 10 version. Try this:

$DismPath=<use default path or path to latest dism.exe>
# [...]
# Mount-WindowsImage -ImagePath $BootWIMFilePath -Index $BootWimImageIndex -Path $WIMScratchDir
$DismPath\dism.exe /mount-image /Imagefile:$BootWIMFilePath /Index:$BootWimImageIndex /Mountdir:$WIMScratchDir
# [...]
# Dismount-WindowsImage -Path $WIMScratchDir -Save
$DismPath\dism.exe /unmount-image /Mountdir:$WIMScratchDir /commit

Update and stuck on bootscreen

Hi, me again. Everything was chugging along just fine till I updated last night, today I am stuck at the boot screen. Any ideas? Thanks!

ISO Image not found

23H2 failed, still need TPM2.0

Win11-New.iso is generated successfully.

But TPM still cannot be bypassed:

Love this tool!

But you can just use Rufus now, and it gives a little menu before you burn the iso to bypass the requirements and stuff.

Does this script can be adapted to do the same for the windows server 2022 ISO ?

I would like to know if it would be easy to do the same for windows Server 2022 to make it installable on old machine ?

Source or Destination contains whitespace, is empty or null

This is the error I get. Kindly resolve. Thank You.

Still get "TPM 2.0" requirement error

When I mount the newly created ISO (original ISO I obtained from Microsoft official site) and run setup.exe, I still run into the same error...