Updates when using UUP dump

Cloudy

New Member
I'm a little confused about updates when using UUP dump with NTLite. Let's say I grabbed the Windows 11 Insider Preview 10.0.22000.160 (co release) under "Latest Beta Channel build", and choose to include updates. Looking at the list of updates there, those are different from the ones I would see when using the updates feature in NTLite. Does the Insider Preview already have these integrated, so it would be redundant to add them again? Or should I still add both sets of updates (UUP and NTLite processing)? I notice with the Dev version there are no updates available. Just experimenting, not familiar with how it all works, thanks.
 
Hi,

in short:
get any UUP you want, NTLite will provide latest updates.

Details:
For example the one that you mentioned, 10.0.22000.160
The .160 part is the cumulative update version.
Find the highest number when downloading an image if you want the UUP to integrate updates, or what I suggest:
Pick any 22000 UUP image, but don't integrate updates, choose to skip those, so you get the 22000.1 clean image.
Copy that image and update it with latest updates through NTLite.
Use the original image as the basis for all future updates, that way there is less to download and process each month.

Another method is to download the image from Microsoft here, then use that as the update basis and you're a bit more assured that the files are properly assembled.

One caveat. Sometimes there are newer updates on UUP than what is available publicly on Windows Update Catalog, and thus NTLite.
I don't suggest installing those updates anyway, quite often they turn out to be unstable or replaced in a few days with newer ones when they hit the Update Catalog.
 
So can NTLite be made to download UUP content not released to public yet? NTLite doesn't recognize Windows 11 AggregatedMetadata.cab and DesktopDeployment.cab when downloaded separately from UUP dump, but it recognizes those files when they are part of all-in-one LCU package. Without 2 files, updates will not apply.
 
So can NTLite be made to download UUP content not released to public yet? NTLite doesn't recognize Windows 11 AggregatedMetadata.cab and DesktopDeployment.cab when downloaded separately from UUP dump, but it recognizes those files when they are part of all-in-one LCU package. Without 2 files, updates will not apply.
1. That's unlikely to be supported, because NTLite follows two core principles:
- Only download files from direct MS sources.​
- Don't build a dependency on a 3rd-party service it doesn't manage, or have direct influence over.​

The last part applies to websites like UUP dump and store.rg-adguard.net. While you're free to acquire files from different sources, NTLite isn't going to integrate this process this for you. There's plenty of room for (ahem) 3rd-party scripts.

Suppose NTLite had UUP dump support... everyone would loudly complain to nuhi and this forum, every time it stopped working.

2. NTLite supports the servicing of images and intact MSU/CAB updates. NTLite does its own unpacking of the LCU content, so there is no context for you providing these files separately.
 
I just realized LCU's do not update Windows Apps at all, not even UWP VC++ gets updates from LCU. You can only update Windows Apps through Microsoft Store and/or store.rg-adguard.net .
 
There are two types of UWP apps: System Apps and inbox Windows Apps. Windows Apps are updated through WU or Store downloads.
System Apps are replaced by LCU changes. Anything marked non-removable is by default a System App.
 
You'd think some major "System-like" UWP Apps, such as UWP VC++, would also get updates or become System Apps.

I don't want to make another thread to ask whether NTLite supports MSIX UWP integration. It allows for it in Updates section, but I am not able to get any of integrated UWP Apps, such as Mozilla Firefox and NVidia Control Panel, to work when integrated offline.

I also noticed that updated versions of UWP Apps require integration of newer dependencies, such as XML 2.8 instead of XML 2.7, which also binds those updates UWP Apps to the newer dependencies. Does that mean dependency on older versions, such as XML 2.7, are revoked?

RG AdGuard generator actually provides links to official MS Store MSIX packages on MS servers. The generator is 3rd party, but links it generates are not.
 
UWP libraries are updated on demand, if you're using Store or the App Installer to install new packages, based on what's listed in the manifest's base requirements. Unlike non-UWP frameworks, older generations are not superseded and will exist side-by-side similar to what happens with normal .NET and VC++ runtimes.

App bindings are highly specific, and spelled out in the package's AppxManifest.xml.

I find the rg-adguard website is unhelpful for new users. This script pulls all the pre-req packages at the same time for an app.
PowerShell GUI for Downloading Microsoft Store Apps - W10_11StoreApps.ps1
 
So Win11 UWP Apps that can be safely removed without any chance of LCU's bringing them back are all under "Apps" category + both VC++ packages + both Net Native + XML 2.4 + XML 2.7. They are all in "Program Files\WindowsApps".
 
Windows 11 23H2 Net Native framework packages, VC++ packages, XML 2.4, and XML 2.7 are grouped under "System Apps" in NTLite, but they exist in "\Program Files\WindowsApps", not "\Windows\SystemApps". Some specific files from VC++ packages exist in some "\Windows\SystemApps" sub-directories (as dependencies), but not as packages.
 
Back
Top