Install Windows 11 v25H2 on an unsupported pc hardware avoiding error message "This pc can't run Windows 11".

Hello Everyone, Welcome.
Special Thanks to @Kari and ChatGPT.

This project should run setup.exe from WinPE boot disk to install windows 11 on an unsupported pc hardware avoiding error message "This PC can't run Windows 11".


With reference to topic in link from this website WinPE - Create a Custom Windows Install USB dated Feb 22 2022.
Follow the code in this stated link to enable PowerShell in WinPE, copy and paste the commands to elevated PowerShell:. Notice that you can copy all commands at once, and paste them all to elevated PowerShell, which will then run them one by one. Please refer to WorkFlow in Live/Current OS given below.

1.First extract Windows 11 v25H2 iso to folder Win11_Source on any internal drive/partition.

2.Download and install both Windows 11 ADK (Assessment and Deployment Kit), and Windows PE add-on for the ADK, installing ADK first from links below:-

3. When both ADK and WinPE add-on have been installed, open an elevated ADK Deployment and Imaging Tools Environment, a special mode of Command Prompt.
You will find it in Start > All Apps > W > Windows Kits: {Replace D: with correct usb letter in your pc}

copype amd64 C:\WinPE_amd64
MakeWinPEMedia /UFD C:\WinPE_amd64 D:

4.C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>MakeWinPEMedia.cmd /UFD C:\WinPE_amd64 D:
WARNING, ALL DATA ON DISK DRIVE D: WILL BE LOST!
Proceed with Format [Y,N]?Y
Formatting D:...

Setting the boot code on D:...

Copying files to D:...


Success

5.C:\Windows\system32>mkdir C:\Mount\Scripts

6.C:\Windows\system32> Mount-WindowsImage -ImagePath "C:\WinPE_amd64\media\sources\boot.wim" -Index 1 -Path "C:\Mount"

7. WinSetup.cmd,SetupW11.ps1 are to be saved in C:\Mount\Scripts

C:\Mount\
├── Windows\
├── Program Files\
├── Scripts ← MUST BE HERE
└── startnet.cmd is under Windows\System32

WinSetup.cmd runs in startnet.cmd to execute SetupW11.ps1

Contents of WinSetup.cmd(Copy following lines and paste in notepad to save as>All files>Winsetup.cmd)

@echo off
rem
rem Run PowerShell script to start Windows Setup
rem
cls
echo.
echo Starting windows Setup...
powershell -ExecutionPolicy bypass -file "X:\Scripts\SetupW11.ps1"

Contents of SetupW11.ps1 (Prepared with the help of ChatGPT)

Write-Host "Searching NTFS drives for Win11_Source..." -ForegroundColor Cyan
Start-Sleep -Seconds 1

# Search only NTFS partitions (avoid FAT32 WinPE)
$path = Get-Volume |
Where-Object {$_.FileSystem -eq "NTFS"} |
ForEach-Object {
$candidate = "$($_.DriveLetter):\Win11_Source"
if (Test-Path $candidate) { $candidate }
} | Select-Object -First 1

if (-not $path) {
Write-Host "Win11_Source folder NOT found on any NTFS drive!" -ForegroundColor Red
pause
exit
}

Write-Host "Found folder: $path" -ForegroundColor Green
pause

$SetupFile = Join-Path $path "setup.exe"

if (-not (Test-Path $SetupFile)) {
Write-Host "setup.exe NOT found inside Win11_Source!" -ForegroundColor Red
pause
exit
}

Write-Host "Starting Windows Setup from: $SetupFile" -ForegroundColor Yellow
pause

cmd /c "`"$SetupFile`""

# Final pause so WinPE window stays open after running Setup
Write-Host "If Windows Setup did not start, review above messages." -ForegroundColor Magenta
pause

Contents of Bypass.cmd

reg add "HKLM\SYSTEM\Setup\LabConfig" /v "BypassTPMCheck" /t REG_DWORD /d 1

reg add "HKLM\SYSTEM\Setup\LabConfig" /v "BypassRAMCheck" /t REG_DWORD /d 1

reg add "HKLM\SYSTEM\Setup\LabConfig" /v "BypassSecureBootCheck" /t REG_DWORD /d 1

reg add "HKCU\SOFTWARE\Microsoft\PCHC" /v "UpgradeEligibility" /t REG_DWORD /d 1

reg add "HKLM\SYSTEM\Setup\MoSetup" /v "AllowUpgradesWithUnsupportedTPMOrCPU" /t REG_DWORD /d 1

reg add "HKLM\SYSTEM\CurrentControlSet\Control\BitLocker" /v "PreventDeviceEncryption" /t REG_DWORD /d 1

reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v "BypassNRO" /t REG_DWORD /d 1 /f

We are editing startnet.cmd in boot.wim by following cmd command run as administrator.

7 C:\Windows\System32>notepad C:\mount\Windows\System32\startnet.cmd

startnet.cmd(Delete the original contents and paste these line and Click file>save.

wpeinit
powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

echo Running Bypass script...
call X:\Scripts\Bypass.cmd

echo Running Windows Setup launcher...
call X:\Scripts\WinSetup.cmd

echo All operations complete.





WorkFlow in Live/Current OS (First mount boot.wim and then run powershell as administrator to add following packages to boot.wim)

POWERSHELL COMMAND TO MOUNT Boot.wim

PS C:\Windows\system32> Mount-WindowsImage -ImagePath "C:\WinPE_amd64\media\sources\boot.wim" -Index 1 -Path "C:\Mount"

To enable PowerShell in WinPE, copy and paste the following commands to elevated PowerShell:. Notice that you can copy all commands at once, and paste them all to elevated PowerShell, which will then run them one by one:


PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WMI.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-WMI-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\WinPE-WMI_en-us.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-WMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-NetFX.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-NetFx-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\WinPE-NetFX_en-us.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-NetFx-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-Scripting.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\WinPE-Scripting_en-us.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-PowerShell.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-PowerShell-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\WinPE-PowerShell_en-us.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-PowerShell-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-StorageWMI.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\WinPE-StorageWMI_en-us.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-DismCmdlets.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.
PS C:\Windows\system32> Dism /Add-Package /Image:"C:\Mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\WinPE-DismCmdlets_en-us.cab"

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26100.1

Processing 1 of 1 - Adding package WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1
[==========================100.0%==========================]
The operation completed successfully.

PS C:\Windows\system32>Dismount-WindowsImage -Path "C:\mount" -Save

Note:-

FIX COMMON DISM ERRORS (Please backup imporant data and then delete unwanted or additional mountpoints.)

Error 0xc1420114 — Mount folder not empty
rd /s /q C:\mount
mkdir C:\mount

Clean stuck mount points (Clean abandoned mounts)
dism /cleanup-mountpoints

Error: The WIM is already mounted
dism /get-mountedwiminfo
dism /unmount-wim /mountdir:C:\mount /discard

Access denied
Run CMD as Administrator.

Error 87 — incorrect option
Check for typos.


WorkFlow in WinPE environment...

Starting windows Setup...
Searching NTFS drives for Win11_Source...
Found folder: E:\Win11_Source
Press Enter to continue...:

Please find all files including html file having conversation with ChatGPT created by single file extension in browser Edge.

Thank you very much.

Shorter solution:

1. DISM mount boot.wim, index #2

2. reg load HKLM\TEMP mount_dir\Windows\System32\config\SYSTEM

3. reg add HKLM\TEMP\Setup\MoSetup /v BypassTPMCheck /t REG_DWORD /d 1 /f
....
repeat with other Bypass commands

4. reg unload HKLM\TEMP

5. DISM unmount boot.wim, and commit changes.

6. Copy updated boot.wim to USB drive.

These reg values have zero effect in WinPE. They can only be applied in the specialize pass. AllowUpgrades is only used for in-place upgrades, it does nothing for WinPE installs.

You're taking a very long detour by installing PS support in WinPE, when none of that is actually required for setup unless you intend to write custom WinPE scripts which execute before calling Setup.exe. Nothing inside of the PS script can't be done by a normal batch file.

Don't always believe in the AI... it's a terrible genie.

Thanks @garlin, I have verified above scripts.

Or just mount the Windows 11 ISO file and run setup.exe /product server. Simple!

garlin said:

Shorter solution:

1. DISM mount boot.wim, index #2

2. reg load HKLM\TEMP mount_dir\Windows\System32\config\SYSTEM

3. reg add HKLM\TEMP\Setup\MoSetup /v BypassTPMCheck /t REG_DWORD /d 1 /f
....
repeat with other Bypass commands

4. reg unload HKLM\TEMP

5. DISM unmount boot.wim, and commit changes.

6. Copy updated boot.wim to USB drive.

These reg values have zero effect in WinPE. They can only be applied in the specialize pass. AllowUpgrades is only used for in-place upgrades, it does nothing for WinPE installs.

Code:

reg add "HKCU\SOFTWARE\Microsoft\PCHC" /v "UpgradeEligibility" /t REG_DWORD /d 1
reg add "HKLM\SYSTEM\Setup\MoSetup" /v "AllowUpgradesWithUnsupportedTPMOrCPU" /t REG_DWORD /d 1
reg add "HKLM\SYSTEM\CurrentControlSet\Control\BitLocker" /v "PreventDeviceEncryption" /t REG_DWORD /d 1
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v "BypassNRO" /t REG_DWORD /d 1 /f

You're taking a very long detour by installing PS support in WinPE, when none of that is actually required for setup unless you intend to write custom WinPE scripts which execute before calling Setup.exe. Nothing inside of the PS script can't be done by a normal batch file.

Don't always believe in the AI... it's a terrible genie.

Click to expand...

Thanks. I have been using your codes (from your earlier posts) for months to install Windows 11 on my unsupported PC successfully except that I was injecting codes into both index 1 and index 2 of boot.wim. From now on I will omit index 1 and use index 2 (setup phase) only in my batch file. Thanks again.

O.P.’s post may be good for those trying to learn coding extensively.

Edit
Please read in post #1 as
7. Bypass.cmd, WinSetup.cmd,SetupW11.ps1 are to be saved in C:\Mount\Scripts

Also next step is 8 not 7

8. C:\Windows\System32>notepad C:\mount\Windows\System32\startnet.cmd

I always found this script easy to use:

Welcome,
Download boot. wim (ready for this project) from link below and replace boot. wim in sources folder of usb boot disk D : (replace this drive letter with your usb drive letter) made after step 4.
The link is

Thank you all for sharing your valuable time.

Sounds unnecessarily convoluted. Have you tested it using your boot.wim ? Might be wise to flag it if you havent already

wimlib-imagex.exe info "path_to_your_wim" Index_number --image-property "FLAGS=9"

I havent used setup.exe for a while it would get upset if it couldnt find an image in boot.wim with flag 9.

Thanks @SIW2,
Yes, I have tested in my pc. It runs first Bypass. cmd to apply registry tweaks. It then searches for extracted folder named in step 1, Win11_Source, So we can install any edition of Windows 11 v25H2 on an unsupported pc hardware.
Please have a look at the end of post#1, WorkFlow in WinPE environment.

replace boot. wim in sources folder of usb boot disk

Click to expand...

It then searches for extracted folder named in step 1, Win11_Source,

Click to expand...

If the usb stick is the installation media, why do you need an extracted folder. You could just search for setup.exe on the usb stick

I dont know why you are going all around the houses. There are much simpler methods for unsupported machines

All of this can been done (multiple bypasses), using a single unattended file. Which the user copies to their USB drive, without needing ADK.

SIW2 said:

If the usb stick is the installation media, why do you need an extracted folder. You could just search for setup.exe on the usb stick

I dont know why you are going all around the houses. There are much simpler methods for unsupported machines

Click to expand...

No, usb disk is boot disk of ADK with powershell support only. It does not have installation files.
This is all about installing Windows 11 v25H2 on an unsuppored pc hardware from WinPE boot disk prepared from ADK.
Once we prepare this WinPE boot disk, we can use it on any version, OS build of Windows 11 iso provided it is extracted to a folder in any internal drive or partition before booting from this boot disk.
It also offers previous version of setup which saves old installation files and data in windows.old folder.

The unattended file has worked to bypass HW requirements since W11. You're free to think of other methods to solve the problem, but we're informing you this is not a simpler (or faster) than other published methods.

Wow, that was an amazingly convoluted way to do what I can do from scratch in 5 minutes max.

The old fashioned way (unattended file) with no image modifications. You can do a disk layout, by uncommenting the <!-- / --> lines.

If you must do it using winpe and an extracted folder why not put all the commands in startnet.cmd .Isnt that easier ?

Not sure why you need to use powershell. It can be found by batch for example

for %%i in (A B C D E F G H I J K L M N O P Q R S T U V W X Y Z) do (
if exist "%%i:\fartyname.txt" set LETT=%%i
)

As stated above by @garlin, the most efficient way is to use Autounattend.xml file, which you can do lots of other things beside bypassing unsupport PC. Ex: Create Local user, install third party programs, remove apps that you consider as bloatware, configure settings etc...

By the way, Rufus also create unattend.xml uder the folder: sources\$OEM$\$$\Panther

About your project: No need to mess around with boot.wim
You already had bypass.cmd, just copy this file to the root folder of the installation USB
boot up -> SHIFT+F10
then type:
echo list volume | diskpart
identify the drive letter containing Windows Installation USB. Then navigate to it.
type to run bypass.cmd
Continue with setup.

I welcome each comments,
This project is 100% successful. It is clean, and reliable to use forever once prepared. Individual pc user creats this boot disk in his/ her own pc.
I tried to create a WinPE boot disk with powershell support, adding dependencies from code given in tutorial by @Kari, adding a file named Bypass. cmd which runs from startnet.cmd before main script could execute which searches and installs Windows11v25H2 on an unsupported pc hardware. This project seems to be convoluted but as I have explained contents of each file Bypass.cmd, WinSetup.cmd,and SetupW11.ps1 and added workflow of each command it has become convoluted. But it is once for ever preparation. As microsoft releases new iso of Windows 11 with new version, os build just change the contents in Win11_Source folder in any partition in internal drive.
Suggestions by @garlin and @SIW2 are important as they are experts in this subject. Definitely we can minimize the command lines in Bypass.cmd by removing some keys which are unwanted or not working in WinPE boot disk.
Also I am working on project which does this job without powershell support as suggested by @SIW2.
Answer Files in WIM TOOLS by @hsehestedt are admirable, it is super easy way to use one of the answer files without renaming it.User can add as many answer files as he can. Just select description of an answer fle, type index number and done.
Just for curiosity, I created this project with support from ChatGPT and after a long conversation, I could create this project successfully. If interested, anyone can have a look at html file, I have attached in zip folder.
Believe, this is 100% successful, clean, reliable and forever.
Common pc user might find this project interesting.
But I am very much thankful to this website, team working with it, though this project is not appreciated by respected senior VIP members.
I always wanted to find new ways to install Windows 11 on an unsuppored pc hardware. Please note that I am not suggesting best and easy method. It can be an extra or alternate way but can not be alternative to other super easy ways like Rufus, WIM TOOLS and many others.
Again thanking everyone.

Welcome everyone,
Just installed Windows 11 Pro Insider Canary Build 28020.1362 (26H1) on my laptop with unsupported hardware using WinPE boot disk created by this project.

Device name DESKTOP-5S9BD2T
Processor Intel(R) Core(TM) i3-5015U CPU @ 2.10GHz (2.10 GHz)
Installed RAM 6.00 GB
Device ID 9D9A6EF6-53CD-4EDE-BE06-7720B4301D83
Product ID 00330-80000-00000-AA741
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro
Version 26H1
Installed on ‎17-‎12-‎2025
Evaluation expires on ‎11-‎08-‎2026 23:39
OS build 28020.1362
Experience Windows Feature Experience Pack 1000.26100.278.0