[PROBLEM] Applying updates to ISO using NTLite

P

ParSec

New Member
Messages
18
Reaction score
2
I have started modyfing windows iso meybe a month ago using NTLite (done this before using windows server instead of ntlite but it was too much hustle for me plus some options were not even exposed to the user at all), in the begining all was good until something happened and after that even slightest modification and trying to boot iso on hyper-v vm I would get error "0xc000000f" (I have also tasted virtualbox and proxmox but the same error, so my understanding here is that it may not be hyper-v related issue).

I'm modyfing multi edition ISO of windows 11 23H2, I am trying to leave only 3 editions as those are the only ones I use (Home, Pro, Pro for workstations), I apply updates.

I also attach files needed to recreate my preset, any help appreciated, regex file is only for disabling windows animations, switching theme and disabling transparency in windows as far as I remeber (done this a while back and I have a lot of stuff on my head).

Temporary solution:
Use Hyper-V VMs in Generation 1 mode, 2nd generation for some reason throws error 0xc000000f but it boots fine on physical machines
 

Attachments

Last edited:
Yeah, I have removed those :D, meybe I'll try restoring them and see what happenes
 
So I got it down to the point that any update I do breaks the image, any idea?
 
And I need those updates because one of the things installed with updates is Winget and I plan installing most of the software thru that.
 
Apparently only vms are having those issues, when I boot installer on my pc, it has no problems whatsever.
 
Problem resolved, recreated VM as Generation 1, for some reason generation 2 does not work anymore with modified ISOs.
 
I can assure you, Hyper-V Gen 2 VMs work fine with NTLite ISOs. I am using this config to build images so I use this nearly every day.
 
Annie Ng said:
I can assure you, Hyper-V Gen 2 VMs work fine with NTLite ISOs. I am using this config to build images so I use this nearly every day.
Click to expand...
After more recent update it does not work anymore, I have checked on 4 different computers, generation 1 works, generation 2 used to work (I also used it), and not to be rude here but "it works on my machine" doesn't really help here, especially with my theory tested on 4 machines with Windows 11 (Home, Pro and 2x Pro For Workstations). Maybe share some information?

garlin said:
Gen 2 is UEFI-based, so that's probably the root cause.
Click to expand...
It wouldn't explain why it boots on all 4 computers with uefi enforced and secure boot enabled but not on hyper-v generation 2 VM. Magic is my only explanation for now. :D
 
Last edited:
ParSec said:
After more recent update it does not work anymore, I have checked on 4 different computers, generation 1 works, generation 2 used to work (I also used it), and not to be rude here but "it works on my machine" doesn't really help here, especially with my theory tested on 4 machines with Windows 11 (Home, Pro and 2x Pro For Workstations). Maybe share some information?


It wouldn't explain why it boots on all 4 computers with uefi enforced and secure boot enabled but not on hyper-v generation 2 VM. Magic is my only explanation for now. :D
Click to expand...
I am current on Windows 11 build 22631.3672 (latest as of writing) and it is running fine every day. Have you checked your Hyper-V and VM configuration?
 
ParSec said:
Everything is below
Click to expand...
Have you tried enabling virtualized TPM?

If TPM is not the cause, I would suggest you boot a vanilla Windows 11 ISO and see if the issue still exists. If vanilla Win11 boots fine, then you should re-start your modification bit-by-bit to pinpoint the offending change.
 
Annie Ng said:
Have you tried enabling virtualized TPM?

If TPM is not the cause, I would suggest you boot a vanilla Windows 11 ISO and see if the issue still exists. If vanilla Win11 boots fine, then you should re-start your modification bit-by-bit to pinpoint the offending change.
Click to expand...
Just to make sure tried it with and without.

Been there done that:
ParSec said:
So I got it down to the point that any update I do breaks the image, any idea?
Click to expand...
Here you go, and also:
ParSec said:
Problem resolved, recreated VM as Generation 1, for some reason generation 2 does not work anymore with modified ISOs.
Click to expand...

I'm not trying to be rude here but please read previous entries I wrote in the topic.
I forgot to mention but the same config worked before and stopped working after windows update.
 
Dear ParSec, I know you encountered an issue with Gen2 VMs, but I would clarify that the Generation is not an issue here.

I am not trying to be rude, but please understand it is the issue of your modified ISO but not Hyper-V.

It is up to you if you insist, but I am a counterexample here. The same ISO works just fine in my VM and laptop.
 
Last edited:
I just mentioned it is not in particular a problem of Gen 2, what I said above is that it is a problem of applying updates and I tried every possible option with DISM (compatible and ResetBase) and without DISM, with and without updating bootloader, my observation is that it boots on all 4 machines with UEFI enforced and secure boot enabled but on gen 2 VM it does not. I have never stated as a fact it is a problem of Hyper-V itself, I have shifted pretty quickly to NTLite itself.

I would like to mention also I am trying to find solution for future me (in case similar thing happens) and for others who encounter the exact same issue.
 
Annie Ng said:
Dear ParSec, I know you encountered an issue with Gen2 VMs, but I would clarify that the Generation is not an issue here.

I am not trying to be rude, but please understand it is the issue of your modified ISO but not Hyper-V.

It is up to you if you insist, but I am a counterexample here. The same ISO works just fine in my VM and laptop.
Click to expand...
Actually, out of curiosity which version of NTLite are you using?
 
I just re-installed my VM, and I see no problems with Windows Updates. Obviously, something in your image is blocking the booting of Windows in Gen2 guest.
 
You must log in or register to reply here.
Back
Top