wrong configuration?

E

Einst

New Member
Messages
4
Reaction score
0
I'm pretty new to using NTLite so its very possible I did something that messed up script. Anyway, not sure how long it should take to create the image but had it running over night and its still going. Checked Task Manager and its been stable CPU usage 3-7% and 40mb...ish memory.

Going to close it down and give it another go.
 

Attachments

  • ntlite_Photo1.png
    ntlite_Photo1.png
    50.9 KB
As a general rule, disable Defender or any real-time security scanner because they will slow down file processing by a lot.
 
Looks like it is freezing on Remove nonessential editions (Windows home 10). Defender is disabled as well. I actually have it disabled normally with Malwarebytes as my main defender (but also disabled).

I did have 1 error message for the Windows Package Manager not present. Which is fine, just need to make sure and not select that on next try. Any thoughts before I try this again?
 

Attachments

  • NonEssential removal.png
    NonEssential removal.png
    48.3 KB
winget is optional.

You might want to try this in reverse:
Take a clean ISO, and first remove all non-essential editions as the only action. Find out if that's problem on its own.
 
Ok good to know on the winget. I'll remove that next build.
I did unmount and cleared all previous cache images. Just started another round. I thought I had previously removed everything but is kind of weird. It looks like it is not removing the x86 images. But I'll take a look next one if this fails. Typically how long does it normally take generate an iso start to finish
 
Processing time increases based on how many components are removed, and if you're processing multiple images in parallel.

Normally what I do with a multi-edition ISO that only has one edition that's worth editing, is to first export a single image from the ISO to a new WIM file or overwrite the existing WIM. This way, NTLite doesn't spend a lot of time processing (or re-processing) files it doesn't need to worry about.

Part of the slow speed is the WIM library does file de-duplication, and it can be tedious to perform file checks to see if other images can share the same files you're writing. Starting from a single-edition WIM eliminates this overhead.
 
Alright got things figured out. The extraction of the original wim did the trick. One thing I think would be better is to overwrite though. By extracting individually you are not able to generate an iso with it. So creating a bootable image gets a bit wonkier.

I might go back through 1 more time and give that a try. Going to be using this for deployment purposes so spend the time now so I don't have to worry about all the mumbo jumbo later.

I did remive the Winget but still received a message about a missing package now. Still a few more things to play around with.
 
You must log in or register to reply here.
Back
Top