Hi garlin , thank you for your comment. The image is working now just to update the MBR --> GPT.I'm running VMware Workstation 15.5.7 on W7. My laptop is a Lenovo Y50-70 with TPM 1.2.
While I've tried adding the software TPM 2.0 feature in VMware, it's a pain for me since it requires encrypting the entire VMDK and it's a performance hit. So I don't and must use the BypassTPM on every image.
My understanding is 24H2 doesn't enforce the TPM 2.0 bypass any differently.
I just used Rufus for my usb install. It has the option to bypass the requirements of windows 11.

Thx again; yes confirmed, those NTLite Preset settings allow one to bypass all Win11 hardware requirements except dual-socket/dual-core requirements, which one can do with older ESXi/vSphre v6.7.x1. The real problem is Rufus wants to use a "hidden" Windows\Panther\unattend.xml to implement the bypasses. There's nothing wrong with this strategy if you're not using your own autounattend.xml. Otherwise the two files can possibly conflict with each other.
If you don't have a licensed copy of NTLite it's still possible to integrate the same reg keys into boot.wim & install.wim. So there's no need to use these optional Rufus features.
2. There are VMware versions that can simulate a TPM 2.0 device, but you're required to enable disk encryption on the VMDK file.
Luego de hacer esto me funcionó en la version 24H2 de windows 11 ejecutandolo en virtualbox con disco duro virtual minimo 52GB. Dato: el modo EFI en virtualbox debe estar desactivado.El soporte nativo para la omisión de TPM y SecureBoot está disponible en NTLite v2.3.0.8394.
Se crearán claves de registro para LabConfig (original 3) y MoSetup.
View attachment 5721
Volver a aplicar tareas en todas las ediciones / Configurar - Ajustes
Seleccione "Configuración de Windows", omitiendo las demás imágenes de arranque. Aplique y listo.
View attachment 5722
editar: si usa setup.exe para instalar y sigue bloqueado por el requisito de TPM, aplique la configuración al host (C:\Windows) también

Is it possible that NTLite settings are not applicable to this version or not tested yet? Rufus was not tested, I want to use the installer for blank VM.
If anyone has the same issue... My problem was the VM CPU count. If VM has only one CPU / Core set, increment it to 2 or more. Also, NTLite's bypass settings worked.Hello everyone! I'm trying to make an ISO with TPM and Secure Boot requirements disabled, but it seems like not works.
These settings were applied to boot.wim (Windows PE, Windows Setup) and to install.wim. (original ISO name: en-gb_windows_11_consumer_editions_version_23h2_updated_oct_2024_x64_dvd_4728d672.iso, NTLite ver: 2024.12.10221 free)
View attachment 13477
Booting the completed ISO into Hyper-V looks like disabling RAM, TPM and Secure Boot requirements via NTLite not works. VM disk is empty, it will be a clean installation. VM settings allowed a W10 installation previously to a different vhd.
View attachment 13478Is it possible that NTLite settings are not applicable to this version or not tested yet? Rufus was not tested, I want to use the installer for blank VM.
Another common mistake is not assigning a minimum system disk size of 54 GB. Sometimes when you're making a tiny VM for testing purposes, you forget this Setup requirement.If anyone has the same issue... My problem was the VM CPU count. If VM has only one CPU / Core set, increment it to 2 or more. Also, NTLite's bypass settings worked.