omg... it was that simple.... have just tested that and have the same outcome as you.. with the w10 boot etc both OS's work perfectly... didnt even think to try that as i thought the boot.wim only worked with same and older.... thank you so much for that... cant believe it was such a simple...
im beginning to think something just breaks when you do the merging the Win 10 and 11 into one WIM, and using the Win 11 boot.wim to load them, as i havent been able to get it to work like that whatso ever, and ive been banging my head for weeks now and not really getting anywhere
nothing created on the disk, even removing the script and changing the setup.exe back im just getting your machine does not meet requirements so now im just totally confused
yeah, what i mean is with this script in there it fails completely saying the pc doesnt meet requirements and when i look at the disk after running it it is setting the disk to uninitilaized with no partitions/volumes, without the script loaded it shows the disk select page which once selected...
after loading a partition tool to have a look at what it did it appears its left me with an unintialized drive, which im guessing is why windows doesnt recognise it?
Does this make it load any drivers differently? once ive renamed that file it stops at the hard drive screen asking for disk drivers, im just testing this in a Hyper-V VM and looking in NT Lite it says disk drivers for Hyper-V are found so seems strange?
before i did that script above it loaded...
do you need to do anything special to make it run? i have added the script to system32 and the files to the root, but it doesnt do anything with the drive section.. do i need to define a partition insite ntlite?
i tried that at one point but was getting errors that when i googled suggested issues with GPT/MBR, so i took it back off, is there a way to force it to convert the disk to GPT no matter what?
ive tried around 10 different setups so far, thats the one im sitting at that im having the issues mentioned above, just with a standard image with win10 intergrated into the win11 wim
I havent made any changes to the images whatsoever from the original iso's from Microsoft
Extracted the Home/Pro WIM's from W11 and W10 and then used imagex to merge them into one WIM then applied unattend using NTlite and complied to an iso
Original images work perfectly merged/automated image...
These images work perfectly on thier own though, its only once they have been through NTLite / intergrating into one WIM file that they break... does NTLite remove drivers it thinks arent required or something like that? Also Win 11 Home breaks whereas Win 11 Pro works both from the same...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.