ISO boot fails in VirtualBox

G

Gary Seven

New Member
Messages
2
Reaction score
0
Hello all. This is my first post here. Been using NTLite for around two years now mostly out of curiosity and fun. Since about two updates ago (or maybe just the last one a few weeks ago) I've noticed that my iso builds simply fail to boot inside a Virtualbox vm. This has happened with both Win10 and Win11 iso's downloaded directly from MS, and the LTSC variants as well. I don't know if I'm doing something wrong or there may be a bug in the software, but I am including my last autogen preset for your perusal.

The error mode is always the same, upon startup of the vm Virtualbox complains about a missing boot file or boot image. I should mention that if I untick the "EFI OS" box inside the vm's settings, I can boot up the iso but obviously not in UEFI mode.

After several days it occurred to me to inspect the autosaved file and found towards bottom an entry called <Task>deledition_boot.wim_01_9_64</Task>.
After removing this line I generated another iso and this time it booted up fine inside the vm.

My question to all is, what am I doing wrong here?

Edit: Using NTLite v. 2025.3.10351
 

Attachments

Last edited:
Hello,

Here is a list of ideas and tips:

- first let me ask did you say that it boots EFI if you don't delete Windows PE edition on boot.wim?
That would be first, that it's needed, usually only the Setup edition on boot.wim is needed.

- make sure to retest with the latest version, there was a change regarding boot sector.

- This could be that Windows updated the SecureBoot certificate lock on that VM.
To confirm try creating a fresh VM in parallel and see if it has the same issue.

- Then try the Update Boot Managers option in NTLite Updates page toolbar when integrating latest cumulative update if it makes a difference.

Thank you for the feedback.
 
nuhi said:
- first let me ask did you say that it boots EFI if you don't delete Windows PE edition on boot.wim?
That would be first, that it's needed, usually only the Setup edition on boot.wim is needed.
Click to expand...
No, what I meant was if I don't use the "EFI OS's" option inside the Virtualbox vm, the iso indeed boots. I will check if I'm deleting the Win PE edition when I generate iso on my next test.
nuhi said:
- make sure to retest with the latest version, there was a change regarding boot sector
Click to expand...
I am on the latest version.
nuhi said:
- This could be that Windows updated the SecureBoot certificate lock on that VM.
To confirm try creating a fresh VM in parallel and see if it has the same issue.
Click to expand...
I am a Linux guy. So my host is Linux Fedora with the guest vm (in this particular case) Windows. I have created/deleted the vm's a dozen times trying to troubleshoot this problem. I'm sorry, I'm not a crack at this type of software (NTLite). Not a complaint or a criticism, mind you (truth is I find this software rather fascinating).
nuhi said:
- Then try the Update Boot Managers option in NTLite Updates page toolbar when integrating latest cumulative update if it makes a difference.
Click to expand...
Super sorry to be so dense here. I simply cannot find this option inside the the NTLite interface.
 
You must log in or register to reply here.
Back
Top