NTLite v2026.5.11080 unable to uncheck "Prompt for any key before booting"

[JosephChinKS]

In this latest version of NTLITE, I noticed if you create a new OS or apply a template, there would be a note "Selected directory from which to create an ISO file contains mounted images. If you have pending changes, make sure the image is unloaded and saved before making the ISO, otherwise continue." Also at the bottom, when creating the ISO, i am unable to uncheck the "Prompt for any key before booting."

Anyone encountered this before?

 

[nuhi]

Mounted image is loaded for changes, it's a Windows imaging fact.
You need to Unload (or Apply) with save changes (or Discard, depending what you want) before creating ISO so changes are not just in the mounted (temporary) location, but the actual file contained in the ISO.

As for Prompt for any key, that's default Windows behavior.
What currently the tool has a bug is that when you uncheck that option that rarely anyone unchecks, Create ISO is also unchecked.
Fixed in the next version, should be out monday/tuesday, if you are blocked by it, contact me for a pre-release.

 

[Anonymous Internet User]

Hi,

Why does this happen now? Something changed in latest Windows? I never saw this message before. This is very confusing. I still don't understand what this message is trying to tell me. I'm trying to Apply and Save the image and create the ISO at the same time, it used to work before. What do I need to do? Just ignore this message?

And yes, I use the option to uncheck "Prompt for any key before booting" all the time.

Thank you!

 

[Anonymous Internet User]

Oh... so this is new too?



I still don't get it. Is this a two-step process now?

1) Unload and save the image
2) Load the image back and create the ISO

But, even if I do it this way: unload and save the image, then load it right back and just go straight to Apply, without touching anything, I still get the same error message.

Yeah, I don't understand this. Help!

 

[nuhi]

Hi,

Why does this happen now? Something changed in latest Windows? I never saw this message before. This is very confusing. I still don't understand what this message is trying to tell me. I'm trying to Apply and Save the image and create the ISO at the same time, it used to work before. What do I need to do? Just ignore this message?

And yes, I use the option to uncheck "Prompt for any key before booting" all the time.

Thank you!

That was always like that, added info to https://ntlite.com/docs/image/

Oh... so this is new too?



I still don't get it. Is this a two-step process now?

1) Unload and save the image
2) Load the image back and create the ISO

But, even if I do it this way: unload and save the image, then load it right back and just go straight to Apply, without touching anything, I still get the same error message.

Yeah, I don't understand this. Help!

Watch some videos here https://ntlite.com/docs/guides/videos/
You are imagining changes.

 

[Anonymous Internet User]

I've done this several times over the last four years and I never saw this message and I always applied changes and built the ISO at the same time and it always just worked.

I loaded my last build from March this year.


The Unload Image dialog looked like this in that version:


So, that's a change already.

And when I build the ISO I do not get that message. It just saves the image and builds the ISO, so this has changed too, this is not imaginary.


Something has clearly changed since March this year. Today is the first time in four years that I see that message.

 

[nuhi]

See in th

I've done this several times over the last four years and I never saw this message and I always applied changes and built the ISO at the same time and it always just worked.

I loaded my last build from March this year.

View attachment 16023

See that same principle "Save existing changes to the image". Now open the new one and enjoy in more options in one place.

Also those options are not new, they were just Apply - page exclusive, now surfaced to have same manually as well, not requiring Apply to reach image workflow.

 

[Anonymous Internet User]

Before I would simply go to "Apply" which saved the changes to the image and created the ISO in one step without any errors showing and, when done, I would unload the image, quit NTLite and there was no dialog and no need to "Save existing changes to the image" because the image was already saved during the Apply stage, before the ISO was created and all current changes were present in the final ISO. That's how it worked so far.

This error is new, I never needed to unload the image and save changes prior to creating the ISO:

"Selected directory from which to create an ISO file contains mounted images. If you have pending changes, make sure the image is unloaded and saved before making the ISO, otherwise continue."

If I unload the image and "Save existing changes to the image", then load the image again and try to create an ISO without applying any changes, I only apply my last preset, I still get that error message.

I know the linked videos and they do not help as they're outdated. The second video (Tech YES City) shows Windows 11 build and he does exactly what I'm talking about: he simply applies the changes and creates the ISO in one final step (no unloading and saving changes needed before creating the ISO) and he's not getting any errors or warnings. This is how it worked so far.

The bottom line is" why am I seeing this new error and what am I supposed to do? Just ignore it and go ahead?

 

[nuhi]

Oh, you mean that message is on the Apply page... I misunderstood that it's on the Create ISO started from the Image page.

Will fix that error, it should appear only on the manual Create ISO while image has mounted editions.

Thanks, sorry for being blind.

 

[Anonymous Internet User]

Oh, you mean that message is on the Apply page... I misunderstood that it's on the Create ISO started from the Image page.

Will fix that error, it should appear only on the manual Create ISO while image has mounted editions.

Thanks, sorry for being blind.

No worries So, for now, it can be safely ignored? Because everything seems fine when I just go ahead apply and create the ISO.

Thank you!