Unable to remove Post-Setup Commands (installer files)

[Anonymous Internet User]

Hi,

I can't figure out how to remove unneeded Post Setup Commands. I delete them from the list using the Remove button up on top of the Window, save the Preset, reload and they're all back. Even if I delete them and build the ISO, it has multiple installers.

I added new installers but I can't remove the old ones which results in multiple installers running after installation. Thanks!

View attachment 12029

 

[garlin]

After you delete the unwanted files, are you hitting Apply to update the image? The older files are staged, and NTLite needs to know if it has permission to remove them by you applying changes.

 

[Anonymous Internet User]

Yes, even after hitting Apply, all old files reappear. I think I found a solution though: removing them from NTLite is not enough, they have to be removed from /resources/$OEM$ directory. Not sure if this is by design or a bug, but unless the files are deleted from there, they will reappear and will get added to the image.

 

[Mr. Yu]

I suggest that you only extract win/esd and load it into ntlite. At the beginning, ntlite cannot directly import iso(Outdated 7lite). I never use official iso files, only mandatory files.
If your virtual machine or installation tool does not support direct use of wim/esd, you can use the smallest iso installation program, keeping only the necessary files for the installation process.
I created a mind map for this and uploaded it as an image, You can copy the install.win of win7-win11 to sources and package it as iso.View attachment 12032

 

[Anonymous Internet User]

I suggest that you only extract win/esd and load it into ntlite. At the beginning, ntlite cannot directly import iso(Outdated 7lite). I never use official iso files, only mandatory files.
If your virtual machine or installation tool does not support direct use of wim/esd, you can use the smallest iso installation program, keeping only the necessary files for the installation process.
I created a mind map for this and uploaded it as an image:

Not sure what you mean, it works fine for me, always have. This is the first problem I had with NTLite. It's solved by deleting the files from the resources/$OEM$ directory, easy enough.

Case closed

 

[garlin]

This is sort of an ongoing bug with some NTLite versions, where detection of previous Post-Setup files isn't working as expected. As you've noted, wiping out the $OEM$ folder will force a cleanup.

 

[Anonymous Internet User]

No big deal once I know how to deal with it Thanks!

 

[Mr. Yu]

Your method will generate a lot of junk files during use. There may be more serious problems in the future than your current one.
My method is a template that is universal and efficient, using only necessary files. I hope it will be convenient for your future use of ntlite.

 

[garlin]

Your method will generate a lot of junk files during use. There may be more serious problems in the future than your current one.
My method is a template that is universal and efficient, using only necessary files. I hope it will be convenient for your future use of ntlite.

Please stop providing bad advice. OP is using NTLite as it's intended, but this is a recurring bug introduced in the March 2024 redesign of how NTLite handles extra content to be included on the ISO. There have been several fixes, but not all problem cases have been identified.

If you want to use a different method for managing images, that's your decision. But don't casually inform users they are creating "serious problems" when both they and NTLite are following the normal steps for an ISO-based image setup.

 

[Anonymous Internet User]

Your method will generate a lot of junk files during use. There may be more serious problems in the future than your current one.
My method is a template that is universal and efficient, using only necessary files. I hope it will be convenient for your future use of ntlite.

I doubt, what "serious problems"? It works fine as far as I can tell and this is just a small hiccup, easily fixed.

 

[Mr. Yu]

Yes, this is more convenient for me and may not be suitable for everyone, but it is definitely not the wrong approach.

 

[Annie Ng]

I added new installers but I can't remove the old ones which results in multiple installers running after installation. Thanks!

I remember I hit this issue recently too, though I cannot remember the version when I saw this issue. It seems the issue is "$OEM$\$$\Setup\Scripts\SetupComplete.cmd" not updated after you attempt deletion of entries, and NTLite reads content from this file to populate the "After Logon" page.

If you modify the content of "SetupComplete.cmd" and delete the appropriate lines, NTLite would read the new content when you edit the WIM.

I doubt, what "serious problems"? It works fine as far as I can tell and this is just a small hiccup, easily fixed.

Don't worry, there are no serious problems.

 

[Mr. Yu]

But don't casually inform users they are creating "serious problems" when both they and NTLite are following the normal steps for an ISO-based image setup.

I doubt, what "serious problems"?

Don't worry, there are no serious problems.

I just realized that you think I mean "dangerous", but I mean "more complex problems", and the word "serious" also means "bad", which is a translation issue.
I don't know if there may be any further minor issues in the future. Microsoft not only modifies "install. wim" every time it updates, but also modifies the steps and files in the installation tool. My method can make installation more "simple and efficient", such as skipping the step of entering keys.
I should check the translation again after each translation.