Number of Update passes for Windows 10 22H2?

WWE_Fan69

New Member
Messages
18
Reaction score
0
Hi, I think i am possibly going crazy here trying to figure this out!
A bit of background on my problems:
I am using a fresh Windows 10 22H2 image created my Windows Media Creator tool, I load it all up, convert it from .ESD to .WIM, remove unnecessary versions, leaving just Windows 10 Pro, I load this up, enable a few features, save that to the image, then comes the problem... updates!

The first "pass" as I call it grabs 10 updates and saves the image, now EVERY SINGLE extra time I check for updates it keeps showing updates Ive previously integrated, different amount of updates at a time.

A few days ago I spent the entirety of WWE RAW on Netflix checking for and supposedly applying updates (I mean, sure it was only on just over 2 and a half hours, but still) and I got tired after that , but it kept showing updates to apply.. HOW many rounds of updates does it take to fully update a Windows Image please??
 
Please attach your preset, after removing any user passwords or license key.
 
Please attach your preset, after removing any user passwords or license key.
Hi, I have just re-done the process again and this time documented it, there are a lot of preset files as it took a few rounds, then it kept showing the same updates to integrate again..

Before preset = convert .ESD > .WIM
1 = enabled a few features & trimmed all non-needed editions.
2 = first round of updates (13 found) & saved image.
3 = second roundof updates (6 found) & saved image.
4 = third round of updates (4 found) & saved image.
5= fourth round of updates (4 found) & saved image.
6= fifth round of updates (4 found again) & saved image.
etc...
 

Attachments

1. When NTLite creates a new install image, a random GUID is assigned for tracking purposes. The image's GUID doesn't reveal any personal details, so it doesn't require obscuring. NTLite wants to understand if the GUID matches the last one written to the preset. Updating the same image will generate a different GUID, so it can be safely ignored by you.

2. I think you're getting the wrong idea on the concept of layered presets (which is a valid NTLite technique). Normally you would layer different action types in a separate preset, like one preset only contains updates, and another only contains component removals.

Instead you're combining several different month's of Monthly Updates, which isn't necessary. Monthly Updates (aside from one-off Security Updates like the Intel MMIO firmware fix), are cumulative. This implies the next latest Monthly Update in the sequence entirely replaces the previous updates (least for W10 releases).

If you have January 2025, then December 2024 is no longer required. This also implies with Jan 2025, then Nov 2024 isn't needed.

Monthly Previews are early releases of next month's updates, provided for early testing. You either select a schedule of following each Monthly update, or each Monthly Preview, but not both of them.

To illustrate the point:
Jan 2025 Preview > Jan 2025 Monthly > Dec 2024 Preview (trick question, since Dec doesn't get a Preview) > Dec 2024 Monthly > Nov 2024 Preview > Nov 2024 Monthly

3. Basically, you can just start over with a new preset and only include the non-superseded (outdated) updates below:

KB5019180 (Intel MMIO Security)
KB5048652 (Dec 2024) -> superseded
KB5049981 (Jan 2025)
KB5011048 (.NET 4.8.1)
updateplatform.amd64fre (Defender Platform)
mpam-fe.exe (Defender signatures)
KB5045933 (Nov 2024 .NET 4.8.1) -> superseded
KB5045936 (Nov 2024 .NET 4.8) -> superseded
KB5046905 (Nov 2024 Setup Dynamic Update)
KB5048160 (Nov 2024 .NET 4.8 Preview) -> superseded
KB5048161 (Nov 2024 .NET 4.8.1 Preview) -> susperseded
KB5049613 (Jan 2025 .NET 4.8)
KB5049621 (Jan 2025 .NET 4.8.1)

Microsoft.UI.Xaml.2.8.x64.appx
Microsoft.VCLibs.x64.14.00.Desktop.appx

Microsoft.WSL_2.3.26.0_x64_ARM64.msixbundle -> why ARM64?
Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle

4. Every new month, you can drop the previous month's updates. .NET updates don't always release on a strictly monthly schedule, sometimes they skip a month or two.

5. For some reason, you've selected the ARM64 (non-Intel) version of Windows Subsystem for Linux. Was this in error?
 
1. When NTLite creates a new install image, a random GUID is assigned for tracking purposes. The image's GUID doesn't reveal any personal details, so it doesn't require obscuring. NTLite wants to understand if the GUID matches the last one written to the preset. Updating the same image will generate a different GUID, so it can be safely ignored by you.

2. I think you're getting the wrong idea on the concept of layered presets (which is a valid NTLite technique). Normally you would layer different action types in a separate preset, like one preset only contains updates, and another only contains component removals.

Instead you're combining several different month's of Monthly Updates, which isn't necessary. Monthly Updates (aside from one-off Security Updates like the Intel MMIO firmware fix), are cumulative. This implies the next latest Monthly Update in the sequence entirely replaces the previous updates (least for W10 releases).

If you have January 2025, then December 2024 is no longer required. This also implies with Jan 2025, then Nov 2024 isn't needed.

Monthly Previews are early releases of next month's updates, provided for early testing. You either select a schedule of following each Monthly update, or each Monthly Preview, but not both of them.

To illustrate the point:
Jan 2025 Preview > Jan 2025 Monthly > Dec 2024 Preview (trick question, since Dec doesn't get a Preview) > Dec 2024 Monthly > Nov 2024 Preview > Nov 2024 Monthly

3. Basically, you can just start over with a new preset and only include the non-superseded (outdated) updates below:

KB5019180 (Intel MMIO Security)
KB5048652 (Dec 2024) -> superseded
KB5049981 (Jan 2025)
KB5011048 (.NET 4.8.1)
updateplatform.amd64fre (Defender Platform)
mpam-fe.exe (Defender signatures)
KB5045933 (Nov 2024 .NET 4.8.1) -> superseded
KB5045936 (Nov 2024 .NET 4.8) -> superseded
KB5046905 (Nov 2024 Setup Dynamic Update)
KB5048160 (Nov 2024 .NET 4.8 Preview) -> superseded
KB5048161 (Nov 2024 .NET 4.8.1 Preview) -> susperseded
KB5049613 (Jan 2025 .NET 4.8)
KB5049621 (Jan 2025 .NET 4.8.1)

Microsoft.UI.Xaml.2.8.x64.appx
Microsoft.VCLibs.x64.14.00.Desktop.appx

Microsoft.WSL_2.3.26.0_x64_ARM64.msixbundle -> why ARM64?
Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle

4. Every new month, you can drop the previous month's updates. .NET updates don't always release on a strictly monthly schedule, sometimes they skip a month or two.

5. For some reason, you've selected the ARM64 (non-Intel) version of Windows Subsystem for Linux. Was this in error?

Ahh right... Now it makes sense!
Ever since the days of Windows 98SE Ive just been used to selecting all updates, restart if necessary, then another check, select and install all!

I'll have to watch out for this in future and no longer click the select all option :-)

By the way, thanks for the info about the presets, Ive never used them before, just delete them afterwards, but now I shall be making full use of them moving forward :-)
 
EDIT:
Nope, it STILL isn’t working..

Take the screenshot for example, the items under the Apps & Features part, EVERY TIME I scan for updates, these come available, even though Ive selected them over 8 different times, but every time I scan for updates, these are shown and wont install..

Now the rest of it, NONE of them show they are preview updates, I must have run and searched for updates 10 or 12 times, in fact all day yesterday I was trying to get this sorted but IT WONT WORK!!!!

Can somebody PLEASE kindly show me a working tutorial of what I need to do to make a fully updated Windows 10 image as I am pulling my hair out here, if I'd known Id have this much problem I'd have saved over £300 by not purchasing NTlite!!
I JUST WANT IT TO WORK AS ITS SUPPOSED TO!!!

I'm sorry I'm getting upset, but I've wasted so many hours & days trying to accomplish this, buit it seems like something ALWAYS breaks and I've NEVER ever got a fully updated windows image in the 6+ years I've used this!!
Screenshot 2025-01-20 11.53.24.png
 
- KB2267602 is for the Defender Engine, which is updated every month but keeps the same KB number.
- The next three are optional UWP packages to allow you to use winget package manager, if needed to install software later.

In both cases, you haven't checked them so they're not queued for processing. Any uninstalled update is offered again for your review.

The bottom third of your list are Superseded updates, which are saved in your NTLite's cache folder. NTLite doesn't apply them since they're now replaced by more current KB's, but then doesn't automatically remove those files since you might have a reason to use them again.

You can clean up the cache folder, by opening NTLite's own settings and clicking Trim on Downloaded updates cache. All updates you haven't previously checked to add, or installed in the current image will be purged.
 
Back
Top