The catastrophe of NTLite

ENVIE_Maine_72

New Member
Messages
8
Reaction score
0
I've been managing the reinstallation of 150 PC (DELL Optiplex 3050), and I decided to use NTLite to speed up the process.
I was confident I could use it to obtain the updates and automatize that step, but everything went wrong.

Wether it is the integration of updates, or of drivers, nothing works as intended.
When I load the W11 Pro image and I go in the Updates tab, I don't find all the updates that are supposed to be found when using Windows Update on the DELLs I'm operating. It seems that the updates proposed are related to the machine I'm running NTLite on, wich is stupid if that ends up being correct. Speaking of wich : the distinction between "Mounted images", "Live install", and "Image history" is absolutely chaotic. I don't fucking know what "mounted" means in the context of NTLite, nor Live instal, wich indicates a problem or UI design (and perception of what someone else than you can understand, and I'm not even mentioning the semantic paradoxes involved, wich seems to echo the dual purpose of NTLite to catch the image of a running OS and/or to edit an ISO).

Anyway, back to my description of the problem :
1 - When I search for updates automatically in the "Updates" tab, I just have a tiny amount of updates proposed. And the "installed" or "downloaded" means nothing to me. Installed ? What do you mean ? What the heck does this mean ? You can't install them given that I'm tweaking an ISO -_-.
2 - The updates on the right panes are useless : nothing correspond to what I'm looking for. I have the names of the KB packages I'm trying to add to the image, and I don't find them, while I can perfectly find them on the Microsoft Updates Catalog.
3 - When I search for updates automatically, NTLite constantly rewards me with an error message saying that the temp updates folder (automatically created by NTLite) is corrupted or some file is not readable. I've triple checked, the NTLite folder in question has always the correct NTFS rights.
4 - Secondly (and that might be related), when I add the .CAB I downloaded from the MUC, I have a similar error message saying "This file is corrupted or not usable" (in french). I wasn't able to add a single .CAB with success, all always failed despite even reinstalling NTLite in a repertory with no space, and using a renamed TEST.CAB that I had put at the root of the C:\ drive.

For the drivers :
5 - When I add the folder containing all the drivers I have exported from one of the machines (used as a master), it correctly add them in the list and seems to be integrating them in the final ISO. But as soon as I reload the ISO or the presets I saved, nothing appear anymore. It seems that as for the updates, the right pane must be used to find some drivers actually present on the actual running machine, and that's god damn confusing.
6 - Adding the previous drivers on the top of it result in an error message about corruption or readability, and nothing appears in the list.
7 - I never managed to reach a healthy W11 installation with a NTLite ISO where the drivers were integrated ; most of time I had "Installation failed" messages during W11 setup, and I could not check of the drivers were correctly installed. On the few ISO that worked and were I reached the desktop, I don't remember if I had correctly integrated the drivers or not given the problem #5 (absence of entries in the list of drivers).

Failure of installation :
8 - I only managed to reach the desktop for a few attempts, mostly at the begining of using NTLite during my "tests", and shortly after, all my attempts to add things (updates or drivers) resulted in constant failure, with various sources of problem, going from "Installation failed" (with no details) to BSOD with "Recovery [...] nvstor.sys" messages that achieved to drain all my energy.

You have to understand that I had the time to install more than a hundred of PC, by a natural mean (with normal ISO, and Rufus or Ventoy), during all the testing phases with NTLite I made on a separate PC ! You can imagine the number of attempts I have tried with no success, hoping for it to finally work so I could speed up the rest of the PC to install !! You can count those NTLite attemps in dozens, and finally I have installed all the PC without it...

So, the purpose of my message here is a mix of troubleshooting and feedback, and a message in the bottle : please do something with your software because as it is, it is an horrendous experience that I have to qualify as non viable in an IT structure. I'm a little technician with a large but not that deep knowledge, I can edit ISO, inject things, but I'm desperate and powerless in front of the absurdity of NTLite's UI and the catastrophy of its constant failures.

Keep in mind that I'm so persevering and strong mentally (not to say dedicated to do my work correctly and to learn) that I have tried DOZENS of time, recompiling ISOs each time. You have to accept, at least, that my message is not thrown easily at your face nor done with disrespect for your product. I did my best, and my feedback is that no matter the tons of webpages I've read, nothing seems to beat the opacity of NTLite.
 
Last edited:
1 - When I search for updates automatically in the "Updates" tab, I just have a tiny amount of updates proposed. And the "installed" or "downloaded" means nothing to me. Installed ? What do you mean ? What the heck does this mean ? You can't install them given that I'm tweaking an ISO -_-.
Installed means it's installed into the target, for image that can mean partially installed, integrated.
Downloaded means... downloaded, not yet installed.

Your tone is unjustified, is it really so confusing what installed or downloaded means, but I'll reply to all like this first message does not exist.

2 - The updates on the right panes are useless : nothing correspond to what I'm looking for. I have the names of the KB packages I'm trying to add to the image, and I don't find them, while I can perfectly find them on the Microsoft Updates Catalog.
For example?
Which Windows image (exact version from the status bar) and which KB is missing, not found?
Important is did you start the update downloader after loading the image or just randomly picked some from the supported update list?

3 - When I search for updates automatically, NTLite constantly rewards me with an error message saying that the temp updates folder (automatically created by NTLite) is corrupted or some file is not readable. I've triple checked, the NTLite folder in question has always the correct NTFS rights.
Never heard of that, but it's finally something to go by. Please repeat the action and when it happens, attach the log.
Menu - Send logs, just include the main ntlite.log (and to be safe previous session ntlite.log.bak)

4 - Secondly (and that might be related), when I add the .CAB I downloaded from the MUC, I have a similar error message saying "This file is corrupted or not usable" (in french). I wasn't able to add a single .CAB with success, all always failed despite even reinstalling NTLite in a repertory with no space, and using a renamed TEST.CAB that I had put at the root of the C:\ drive.
Send me a link to that CAB and I'll test it, it's possible it's not supported, Windows updates have various formats and not all are supported.
Or you meant CAB format for a driver? Extract those to a folder and add that instead, send me a link, it could support those.
Main pathway of driver integration is INF drivers with their acompanying files inside its dir.

For the drivers :
5 - When I add the folder containing all the drivers I have exported from one of the machines (used as a master), it correctly add them in the list and seems to be integrating them in the final ISO. But as soon as I reload the ISO or the presets I saved, nothing appear anymore. It seems that as for the updates, the right pane must be used to find some drivers actually present on the actual running machine, and that's god damn confusing.
What do you mean nothing appear anymore, you would like previously integrated drivers to be on the driver integration queue/list?
They can be found in Components - Drivers, with all the other drivers in Windows.
Hm, to add an existing drivers list section on the drivers page, not a bad idea - but let's first see if that's what you meant.
When you try to add same drivers to the image, are they detected as existing?

Not sure what you meant by confusing right-side hardware checklist, feel free to suggest ideas.

6 - Adding the previous drivers on the top of it result in an error message about corruption or readability, and nothing appears in the list.
You didn't read carefully, they are existing, not corrupted.
If you see differently, give me an example which driver when I add it works, then when I try to readd it says corrupted.

7 - I never managed to reach a healthy W11 installation with a NTLite ISO where the drivers were integrated ; most of time I had "Installation failed" messages during W11 setup, and I could not check of the drivers were correctly installed. On the few ISO that worked and were I reached the desktop, I don't remember if I had correctly integrated the drivers or not given the problem #5 (absence of entries in the list of drivers).
Then skip those bad drivers, doesn't mean if a tool can integrate that your job is not to filter what is being integrated.
Find the driver that breaks your machine and avoid it.

Failure of installation :
8 - I only managed to reach the desktop for a few attempts, mostly at the begining of using NTLite during my "tests", and shortly after, all my attempts to add things (updates or drivers) resulted in constant failure, with various sources of problem, going from "Installation failed" (with no details) to BSOD with "Recovery [...] nvstor.sys" messages that achieved to drain all my energy.
Do you have a preset demostrating that, is it one of these attached?

You have to understand that I had the time to install more than a hundred of PC, by a natural mean (with normal ISO, and Rufus or Ventoy), during all the testing phases with NTLite I made on a separate PC ! You can imagine the number of attempts I have tried with no success, hoping for it to finally work so I could speed up the rest of the PC to install !! You can count those NTLite attemps in dozens, and finally I have installed all the PC without it...
Same here X10 and I never saw an issue, means nothing. For example if you just ignore that a bad driver breaks your install, all else is pointless.
It's easy to blame a tool, of course, especially one that allows so much to do.

So, the purpose of my message here is a mix of troubleshooting and feedback, and a message in the bottle : please do something with your software because as it is, it is an horrendous experience that I have to qualify as non viable in an IT structure. I'm a little technician with a large but not that deep knowledge, I can edit ISO, inject things, but I'm desperate and powerless in front of the absurdity of NTLite's UI and the catastrophy of its constant failures.
Gladly would fix all that you prove repeatable, by all means it's in my interest.
So if you have patience, reply to my replies above where not solved.
 
Last edited:
all that you prove repeatable
You know everything I said is repeatable given that it has been experienced in reality, by exporting drivers from a machine and downloading .CAB from a website, and that I could give you those drivers and .CAB. But you're a dickhead, a fanboy of his own program with absolutely no self-analysis.

So if you have patience, reply to my replies above where not solved.
Everything you said is not a solution and a runaway from the reality. I don't have patience with dicks like you, but I'll give you a shot.

Your tone is unjustified, is it really so confusing what installed or downloaded means, but I'll reply to all like this first message does not exist.
I already said, and I'm reformulating for the denier you are, that "installed" can mean installed on the future target, or installed on the actual machine we're running NTLite. You know, you perfectly know, that your software fucking scan the actual setup of the machine and that it explains why the updates proposed on the right panes are related to THAT machine, and that it is fucked up given that we're not supposed to only make ISO based on the actual machine, but we want most of time to create an ISO for another machine. And you keep denying like a kiddo.

Then, there's a problem with french translation (the english is also problematic). I'll give you a screenshot in attachment, were you can see that :
- the first section has the name of the image we're loading.
- the second section has the name "Déployée", wich means deployed, wich means NOTHING intelligible given that deployed is supposed to mean "installed on the future targets". In computing, deployment is the act of installing on one or several machine. HOWEVER, in your software, it seems to mean (and I don't know, and it's confusing, dickhead), that it is the ISO "loaded" in cache. So, "Cached" or "Modification in progress" would be more suitable.
- the last section is called "Lecture seulement" wich means "Reading only", and is even more confusing. I don't fucking know the f**k it means. We're supposed to have an ISO loaded, eventually an other section were there is the list of recent ISOs loaded, and we end up with a fucking mess.

For example?
Which Windows image (exact version from the status bar) and which KB is missing, not found?
All the ones of the Microsoft Updates Catalog, moron.
I could not find any of the KB packages of the target machine (the ones installed with Windows Updates once W11 is installed), whereas I could find them on the MUC. Are you on drugs, to say me that your right pane is listing all updates of the MUC ? Are you high, to say that the updates NTLite lists aren't related to the actual machine, wich explains why we can't see the rest of the updates available for any machine ?

Never heard of that, but it's finally something to go by. Please repeat the action and when it happens, attach the log.
No, I won't debug your sh*t. I'm gonna just say you to GO ON THE MUC, AND TRY ANY .CAB.
And shut your fucking mouth during the process, for god sake.

Send me a link to that CAB and I'll test it, it's possible it's not supported, Windows updates have various formats and not all are supported.
Or you meant CAB format for a driver?

No no, you are going to do some efforts to debug your program.
And when I was talking about drivers, I was talking about .INF.
Anything loaded in your program is always rejected like vomit. It's not a question of "incompatibility", given that THEY ARE CORRECTLY INSTALLED ON THE TARGET MACHINE.

If NTLite can't integrate any .CAB or .INF we give it, it's your problem, not ours.
And don't say me "I don't have this problem", you probably never tested your software outside or your little dev environment like 99,99% of developpers.

Now I'm gonna end this torture : you're joking with me, and I'm not your fool. You made ZERO EFFORT in that conversation to test by yourself, see by yourself, admit by yourself. I'm not gonna waste my time with an umpteenth prententious programmer who can't accept critics.

The way your program is designed reflects the way you avoid thinking and seing reality.

I'm gonna save that webpage, and store it in the collection of negative interactions I had with people like you since the twenty last years. Don't bullshit on me and my "aggression", I made all the efforts to :
- test your sh*t a hundred times,
- post a long message here with full details, that your ruined with sophism and reversions.
- use many respectful thoughts ("message in a bottle", etc), emphasized on the positive.
- and yeah, finally used the terms with you, because you're like the vast majority of people : full of prentention and contempt.

What do you mean nothing appear anymore,
Seriously, fucking dickhead ? The verb "to disappear" needs a traduction ?

You didn't read carefully, they are existing, not corrupted.
And how am I supposed to know that, given than I have no visual return in your shitty software interface, wich is as empty in that situation as your mind here ?

Then skip those bad drivers
Wash your dirty mouth.

Do you have a preset demostrating that, is it one of these attached?
Yeah, as attached in the second message a posted here in this thread when responding to a more respectful user than you.
PROOF THAT YOU DON'T READ AND IS TRAPPED IN YOUR DELUSION.

It's easy to blame a tool
It's easy to do the fanboy when you don't read and deny everything.

> End of the public execution.
 

Attachments

  • 2026-09-29_15h-50m-54s_NTLite.jpg
    2026-09-29_15h-50m-54s_NTLite.jpg
    134.5 KB
Last edited:
Process for you to replicate the problem :

1. Dowload an official ISO of W11 25H2. I won't give it.

2. Load the Professional edition in NTLite.

3. Go in the "Update" tab, and watch carefull how the updates proposed in the right pane are not all the ones listed in the MUC.

4. In the MUC, type one of these packages :
Intel - Other hardware - Intel(R) 200 Series Chipset Family LPC Controller (B250) - A2C8
Intel - Other hardware - Intel(R) 200 Series Chipset Family PCI Express Root Port #5 - A294
Intel - Other hardware - Intel(R) Xeon(R) E3 - 1200 v67th Gen Intel(R) Core(TM) Host BridgeDRAM Registers - 590F
INTEL - System - 111970 120000 AM - 10.1.1.38
INTEL - System - 1032016 120000 AM - 10.1.1.38
Intel Corporation - Display - 31.0.101.2114

5. Observe how you can find them in the MUC.

6. Observe how you CAN'T find them in NTLite.

7. Try to import them in NTLite.

8. Observe the failure.

9. Go in your bathroom.

10. Observe yourself, and cry.

11. Export drivers from any PC around you (DO NOT TAKE YOUR ACTUAL MACHINE) with the command :
dism /online /export-driver /destination:%USERPROFILE%\Desktop\drivers_exported

12 Import half of them them in NTLite's drivers tab (on the main machine where you previously opened it).

13. Observe how it fails to import them.

IF IT SUCCEEDS :

14. Save the actual setting in NTLite (create a preset).

15. Close the "project" in NTLite (unload the image).

16. Reload the Professional edition with the preset.

17. Now, load the other half of the drivers.

18. Observe the mess.

19. Go back in your bathroom, lock the door.
 
Last edited:
Important is did you start the update downloader after loading the image or just randomly picked some from the supported update list?
We can't access the "Updates" tab (or menu) if we don't load any ISO in NTLite.
That's a new proof you're on drugs.

When I load an image and access the Updates menu, on the top tabs, there is "Last updates" ("Dernières mises à jour" in french), wich helps to find last updates for the ISO. On the right, there is what I call "the right pane".

In the "Last updates", of course I won't find any of the updates I want to integrate, given that the software isn't supposed to know on what machine is supposed to be installed the ISO and what specific additional updates will be installed.

In the right pane, I should have access to all the MCU catalog. There is not "compatibiliy" question. How the f**k would you establish compatibility of .CAB when they can perfectly be installed on the machine by using Windows Update ??? If you have problems of compatibility in NTLite's code, it is because of your programming skills.

.CAB aren't supposed to be "incompatible" or "not injectable" in an ISO.
 
20$ he's gonna make me believe that not having access to the MUC full list of packages in NTLite is normal, despite the very essence of that software to be able to pre-integrate updates for machines where we deploy the ISOs. -_-
 
Back
Top