[PROBLEM] Applying updates to ISO using NTLite

I am sharing preset at current stage, I only changed base ISO from win 11 23H2 MultiEdition English International v2 to win 11 23H2 MultiEdition English US v2 since I started this whole topic.

Here is the list of updates being applied if you wish to help me test it:
View attachment 12058
 

Attachments

I tried your preset, and Windows installs and boots properly in my Gen 2 VM. So, your preset is not the problem, but something else in your system that may interfere with Hyper-V.
 
I am doing some tests, for now everything works, I think I found culprit but I'm not gonna say exactly what, cause I'm unsure.
 
Well, yeah, checking option to update bootloader causes the error, I will use fresh install of windows and see what happens. I know it works on physical machine so why not be my own lab rat.
 
ParSec said:
Well, yeah, checking option to update bootloader causes the error, I will use fresh install of windows and see what happens. I know it works on physical machine so why not be my own lab rat.
Click to expand...
It also worked for me when I unchecked the option: "bootloader".

Now the question remains: why does it work on the physical machine and not on the virtual one with the "bootloader" active?
 
Sorry for not saying anything for a longer time, had some personal business to attend but I have managed to confirm that it is indeed NTLite fault. I used a machine at work with older version of the software and bootloader update worked fine, can't say anything more because I already departed from there and not planning on going back :) Maybe, just maybe it has something to do with verification of the bootloader by windows and something is missing.
 
ParSec said:
Sorry for not saying anything for a longer time, had some personal business to attend but I have managed to confirm that it is indeed NTLite fault. I used a machine at work with older version of the software and bootloader update worked fine, can't say anything more because I already departed from there and not planning on going back :) Maybe, just maybe it has something to do with verification of the bootloader by windows and something is missing.
Click to expand...
We are waiting for the solution to the problem.
 
You must log in or register to reply here.
Back
Top