Issue When Creating ISO install Win11 on Win10

The error message is accurate and not a bug or problem of NTLite. If your computer doesn't meet the requirements then it won't install Windows 11. You can bypass those requirements by integrating some registry keys which are available everywhere on Google, or by using NTLite's bypasses, which can be found by using the search button on this forum as it has been discussed frequently.
 
Bypassing HW requirements (TPM, SecureBoot or RAM check) is not performed by Unattended mode.

For licensed users, NTLite has the Bypass options under Settings / System. But if you can find the registry file that does the same thing, it can be integrated into boot.wim. Or use Rufus to make your USB drive, and it has a built-in option to bypass HW checks.
 
The error message is accurate and not a bug or problem of NTLite. If your computer doesn't meet the requirements then it won't install Windows 11. You can bypass those requirements by integrating some registry keys which are available everywhere on Google, or by using NTLite's bypasses, which can be found by using the search button on this forum as it has been discussed frequently.
Bypassing HW requirements (TPM, SecureBoot or RAM check) is not performed by Unattended mode.

For licensed users, NTLite has the Bypass options under Settings / System. But if you can find the registry file that does the same thing, it can be integrated into boot.wim. Or use Rufus to make your USB drive, and it has a built-in option to bypass HW checks.
I tried to bypass it, but still can't get rid of that error.
Note: My hardware is fully qualified. Also, if I don't enable Unattended, no errors arise.
 
This error message can also apply when your assigned Windows partition is smaller than 54 GB.

Unattended mode has no effect on Bypass settings; most likely you have errors in the disk layout, and Setup is picking the wrong partition to install Windows. Can you attach your autounattend.xml file? (After removing any user passwords or license key).
 
This error message can also apply when your assigned Windows partition is smaller than 54 GB.

Unattended mode has no effect on Bypass settings; most likely you have errors in the disk layout, and Setup is picking the wrong partition to install Windows. Can you attach your autounattend.xml file? (After removing any user passwords or license key).
Yes. I understand this problem, and I provide hard drives larger than 54GB
I send the XML file.

Mod note: Redacted user passwords from preset.
 

Attachments

This preset doesn't have a disk layout. How are you selecting the target disk? Is this a single drive PC?
 
This preset doesn't have a disk layout. How are you selecting the target disk? Is this a single drive PC?
I deployed it on vCenter, the drive is not the problem. And as I said, if the Unattended feature is not enabled, the ISO file I created will work normally.
 
I don't have any experience with vCenter, but have extensively used VMware Workstation to test multiple images (and user presets). For testing, you should try installing the same ISO on a physical PC to confirm if vCenter is introducing its own changes.

The only way I can bring up this error message on Workstation is through two different methods:
1. Failure to enable BypassTPM, BypassRAMCheck keys in boot.wim, or by adding reg commands from autounattend.xml.
From WinPE, open a CMD window with Shift-F10. Run regedit, and check:​
Code:
HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup\BypassTPMCheck
HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup\BypassSecureBoot
HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup\BypassRAMCheck

2. Failure to provide a 54 GB or larger sized Windows partition.
Run diskpart:​
Code:
select disk 0
list part
 
Back
Top