Easy2Boot v2.10a Beta available with Win11 support

The new E2B Beta is here.

It adds a \_ISO\WINDOWS\WIN11 folder.

I have also speeded up the loading of the Main Menu if you have lots of files in the \_ISO\WINDOWS\xxxx folders. The Main menu no longer shows you how many payload files are present as they are no longer counted.

I installed a version of Win11 using VBox and E2B legacy and agFM UEFI64 successfully.

To update, just extract the files onto your USB drive.

Bypass the Win11 Compatibility check

To avoid the Win11 'compatibility check' you can install Win11 using WinNTSetup.

If you install to a Virtual Machine, the 'compatibility check' is skipped.

Or you can run these commands as soon as Setup is loaded to skip the checks:

1. Press SHIFT+F10 to open a command window

2. Type these command lines

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

3. Close the cmd shell and continue running Setup.

You could cut and paste these lines into a RemoveChecks.cmd file and keep the file somewhere on your E2B drive. Then run it from the cmd shell in step 2.

E2B (not agFM) can automatically run a .cmd file, just give it the same filename as the Win11 ISO, e.g.

\_ISO\WINDOWS\WIN11\Windows11Pro_Trial.iso
\_ISO\WINDOWS\WIN11\Windows11Pro_Trial.cmd

This does not work under Ventoy - only E2B and agFM v1.72f Beta and later.

The version I had was Pro and I used an XML file with a Win10 Pro PIDKEY.

On testing further however, although it bypasses the checks OK on a Legacy boot to E2B, Setup does not list any Windows Editions in the OS list and just shows 'No images are available' if an XML file without a PIDKEY entry is used.

To avoid this, when prompted by E2B to run the ISO for Setup\Repair - press ENTER quickly so that an XML file is not used or pick a Win10 Pro xml file or you can just place the Win 11 ISO in any folder except one of the \_ISO\WINDOWS\xxxxx folders and also the .cmd file with the same name as the ISO and it will not use an XML file.

An alternative process which avoids the registry hack method is to create a new 'hybrid' ISO by loading a Windows 10 ISO into an ISO editor such as PowerISO and replace the \sources\install.wim file with the install.wim file extracted from the Win11 ISO.

Possible bug in Win11 MBR Setup: If you Legacy boot to Setup and delete the existing the hard disk MBR partitions, Setup refuses to then install to the blank disk. You must reboot and try again on the blank disk.

If you want to set up a Local Account (not a Microsoft email account) then unplug the Ethernet cable before Setup runs and do not connect to WiFi when later prompted. This applies to Pro. For Home, see next blog post.