Windows 11 ISO

sebbernard

Member
Messages
40
Reaction score
3
Hello, for some time now, I install Windows on VMware, capture the ISO once my Windows is customized to my liking, and keep it on a USB flash drive. Basically, it exports a .wim file which I then swap into a Windows 10 ISO to keep the Windows 10 interface. Everything works great.

If I take the exact same .wim file, which is Windows 11, and put it into the Windows 11 ISO, the installation crashes at 10%? Yet the .wim file works perfectly fine in the Windows 10 ISO.

Does anyone have an idea? I only added Wi-Fi drivers and a post-setup script after login... that's it.

Thank you !
 
Thanks, but when i use this i have a error '' selected boot image did not autheticate ''

in win10 iso with same install.wim all work good
 
Hello, for some time now, I install Windows on VMware, capture the ISO once my Windows is customized to my liking, and keep it on a USB flash drive. Basically, it exports a .wim file which I then swap into a Windows 10 ISO to keep the Windows 10 interface. Everything works great.

If I take the exact same .wim file, which is Windows 11, and put it into the Windows 11 ISO, the installation crashes at 10%? Yet the .wim file works perfectly fine in the Windows 10 ISO.

Does anyone have an idea? I only added Wi-Fi drivers and a post-setup script after login... that's it.

Thank you !
Sounds like you are definitely using the "Legacy Boot" option. I capture all my install.wim files in VMware. But here is the key, you need to run your ISO through NTLite and choose "Legacy" prior to that ISO ever getting installed in VMware. Then, after you capture your install.wim file with DISM in VMware, swap your original install.wim with the one you just captured in VMware. Then, run it back through NTLite and choose the "Legacy Boot" option a second time. That is how you make it stick.
 
Legacy Boot options changes which of the WinPE Setup clients, legacy or the newer "Modern" app are used. Legacy is more tolerant of how older sysprepped or captured images are updated and will install them. The new Setup client is notoriously picky about install images and can stop halfway thru the install.

For Secure Boot, there's a separate issue where you need to start with a source image with the latest Monthly Updates (ESU for W10). Within the updates, later versions of the boot manager files are provided to the image. NTLite tries to pull those files and replicate them them into the ISO's top folder and boot.wim.

If you have already applied CA 2011 revocation, your UEFI now enforces a minimum version of the boot manager using the SVN number. Any boot file which is below the current SVN is rejected for security reasons. So you should find the latest updates and apply them to the image. If your PC has never done the revocation step, then it doesn't care what version of the boot files are present.
 
Legacy Boot options changes which of the WinPE Setup clients, legacy or the newer "Modern" app are used. Legacy is more tolerant of how older sysprepped or captured images are updated and will install them. The new Setup client is notoriously picky about install images and can stop halfway thru the install.

For Secure Boot, there's a separate issue where you need to start with a source image with the latest Monthly Updates (ESU for W10). Within the updates, later versions of the boot manager files are provided to the image. NTLite tries to pull those files and replicate them them into the ISO's top folder and boot.wim.

If you have already applied CA 2011 revocation, your UEFI now enforces a minimum version of the boot manager using the SVN number. Any boot file which is below the current SVN is rejected for security reasons. So you should find the latest updates and apply them to the image. If your PC has never done the revocation step, then it doesn't care what version of the boot files are present.
This is why I never get my starting ISO from Microsoft. When I stopped doing that, my problems went away.
 
Back
Top