How To - NTLite Download Updates Feature

pmikep

Active Member
So I read the Documentation. It's a little bit out of date, since now there is a 4th Option under Tools: Remove Reinstalls. I don't understand what it does, and the text pop up isn't clear to me.

Anyway, why I'm primarily here is to suggest that the "Install Updates" option be grayed out whenever a non-Live image is loaded. For when I have a wim loaded and I click on "Install Updates," I get a message asking me if I want to Close the current Session. I infer from this that the Tool "Install Updates" is supposed to be a way to update a Live image.
 

pmikep

Active Member
For grins I am starting with a fresh Win8.1 Pro. I have it loaded in NTLite and am using the Update Tool. In the "State" column, I noticed that some downloads are listed as "Downloaded" with a check mark next to them anyway. Others are listed "Existing - Downloaded" with no checkbox.

Seems to me that both are the same. They've been downloaded. So what don't I understand here? Never mind. It turns out that I had mistakenly modified my base iso (even tho I have it titled "KEEP") and that modified ISO already had some KB's in it.


Also, I will renew my request for a global checkbox that says "Do not select missing Updates." That's because I purposely do not download every update. (I don't need KB's for Secure Boot (freezes NTLite, Surface, etc.) And so I don't enable them in the download list. But every time I come back to the list, as I'm doing today, those Missing items are automatically selected for download by NTLite. And then I have to go through and uncheck them, 'cause I still don't want them.
 
Last edited:

ceo54

New Member
What if the updates also need to be integrated into boot.wim and Winre.wim ? does the NTLite integrates the updates in those images too, if the update package contains the elements for those images ?
 

nuhi

NTLite developer
Staff member
What if the updates also need to be integrated into boot.wim and Winre.wim ? does the NTLite integrates the updates in those images too, if the update package contains the elements for those images ?
You can automate boot.wim integration on the Apply page, or load it like any other image, it is listed on the Source page.
For WinRE there is no automated option yet, so you would need to load it yourself from within the image (Explore Mount Directory), it's the:
.\Windows\System32\Recovery\winre.wim

Will add an option to do that in sequence like for boot.wim in one of the next versions.
If you get any issue mounting it directly from a mount, then copy it aside first and return back after integrating. This can be automated with scripts, including NTLite operation, see ntlite /?
 

pmikep

Active Member
I don't know if I should start a new topic or ask here in a reply. Question: What will NTLite's Update feature do after MS stops officially supporting Win7?

For example, say that I have NTLite check for Updates for Win7 in March 2020, after MS support has stopped? Will NTLite be able to query a Microsoft server? Will nuhi mirror the last list of updates? (That is, will updates still be available?)

And what happens if a user clicks the "Trim" button? Will NTlite say "Hey, there are no more official updates, so I'm deleting all the updates that you previously downloaded"?
 

ege914

Active Member
I don't know if I should start a new topic or ask here in a reply. Question: What will NTLite's Update feature do after MS stops officially supporting Win7?

For example, say that I have NTLite check for Updates for Win7 in March 2020, after MS support has stopped? Will NTLite be able to query a Microsoft server? Will nuhi mirror the last list of updates? (That is, will updates still be available?)

And what happens if a user clicks the "Trim" button? Will NTlite say "Hey, there are no more official updates, so I'm deleting all the updates that you previously downloaded"?
another question will ntlite support enterprise updates untill 2023
 

nuhi

NTLite developer
Staff member
pmikep, when MS stops adding updates for something, it's simple enough to leave it in the updates list, so I won't be removing Win7 updates of course. It's a bit different with older Win10s, they keep on updating those and no one is using it, that is not worth the trouble.

ege914, if Win7 base keeps getting updates, be it just for Enterprise if it works on Client OS, I'll continue maintaining those as it's an important platform, unlike Win10 1507, 1511, 1703, 1709, and soon 1803, those won't be getting updates as newer Windows ISO base is like an update to them that has no downsides.
 

garlin

Active Member
Win7 updates newer than January 2020 are only available for Extended Security Update (ESU) licensees -- which is a yearly subscription paid to MSFT service partners. While you can manually search for them on Microsoft Update Catalog, you'd have be licensed or use the obviously not legal bypass to install.

The updates will be delivered through all the usual update delivery processes, including SCCM Current Branch, WU, WUfB, and WSUS. The update will be programmed to look for the MAK activation on the endpoint, and it will install on only those systems together with the MAK key.​

That doesn't make clear if you can integrate ESU-branded patches, but it may be like more recent Dec/Jan rollups where it insists on a live install even after it was previously integrated. I think there's no worse case for not managing a ESU list, because it's most likely a small set of monthly rollups will catch up ESU users no matter how late they start. Also, you would need separate lists for pre- and post-EOS patch sets.
 
Top