Windows 7 - Issue w/KB3191566 + Build with all optional components integrated

[LoneCrusader]

Trying to build a Windows 7 ISO with everything integrated. There seem to be several discussions of this floating around the net, but all differ on this or that, mainly revolving around the issues with the KB3125574 Update Rollup.

It would be nice to see a detailed guide for this "Add everything" scenario, with notes on what order to do things in to see that all the updates are working together as they should and also with notes about keeping NTLite happy along the way. (One method had instructions for using direct HotFixes rather than the KB3125574 Rollup, but NTLite didn't like these HotFixes.) I've had to run five or six trial-and-error builds already only to find that this or that will not work if something else was already done first.

So, I assembled a collection of things that needed to be integrated on a first pass before adding the KB3125574 Rollup package and other later updates. Attempted to run the first pass. One of these, the optional WMF 5.1 package, reported that KB2809215 was skipped during the process.

"Integrating: KB2809215 6.1.1.1 - Package is not applicable to this image."

Since I had no updates with that KB number, I had to dig for a bit until I realized it was packed inside KB3191566. Came across this discussion here.

I decided I would try manually adding the stand-alone KB2809215 on my "first pass" and add the KB3191566 package on a "second pass."

Manually adding KB2809215 this way worked without issue (why does this work while it claims to not be applicable when part of the other package...)?

But now, when I go back to make my "second pass," NTLite blocks KB3191566 as "Existing item" because of KB2809215 existing inside of it.

There has to be a better way to handle this...

 

[garlin]

WMF 5.1 (KB3191566) was released as a MSU file. I presume you extracted the following CABs:

Windows6.1-KB2809215-x64.cab
Windows6.1-KB2872035-x64.cab
Windows6.1-KB2872047-x64.cab
Windows6.1-KB3033929-x64.cab
Windows6.1-KB3191566-x64.cab

KB2809215 is a WMF 3.0 hotfix, there's no problem integrating it since it's not actually WMF 5.1 itself (KB3191566 CAB). For the 2nd pass, you're presumably adding KB3191566 CAB, and not the original MSU?

For my W7 presets, I've never seen 9215 as a separate item until I researched integrating WMF 5.1.

When you say "Add everything" scenario, is this a "Everything including the kitchen sink" approach with every known W7 update?
I can tell you that strategy fails because W7 patch dependencies are a horrible mess. It's better to stick to a known good list.

There's a ton floating on this board (use the Search function), everyone's got an opinion. I probably posted least two presets.

 

[Clanger]

Windows 7 is very finicky. I had to do several passes with wumt+wsusscn.cab to fully satisfy WU to w7 EOL, even then i had a fair few "not applicables". Its not something i care to repeat. For all its downsides windows 10 is much easier to service.

For the record i used all .msu's, not the cab files links generated by wumt.

 

[LoneCrusader]

No, I'm using the .MSU versions of both.

On my first attempt (using Win7AndW2K8R2-KB3191566-x64.msu), NTLite failed to integrate the package because it claimed KB2809215 was "not applicable to this image." (I'm assuming the entire package fails if part of it fails, since it's the first update listed in the install order inside the KB3191566 .MSU file.)

After searching for info on KB2809215 I found your posts that I linked, and found that KB2809215 existed as a stand-alone update.

So, I started from scratch again, removed Win7AndW2K8R2-KB3191566-x64.msu and used Windows6.1-KB2809215-x64.msu in the "first pass" instead, planning to use Win7AndW2K8R2-KB3191566-x64.msu in a "second pass."

This was successful for Windows6.1-KB2809215-x64.msu (NTLite does not claim it isn't applicable and successfully integrates it); however, now when I try to use Win7AndW2K8R2-KB3191566-x64.msu in a "second pass," NTLite rejects it, claiming it is an "existing item," only because KB2809215 is a component inside of it. (NTLite fails to realize that the rest of the package is NOT an "existing item.")

Regarding "Add everything" - I mean adding all of the optional components and features (i.e. RDP, WMF, DCA2.0, AD LDS, RSAT, VirtualPC, WorkFolders, Server Essentials Connector, Agent, NTBackup, Windows Help, etc). Supposedly the KB3125574 Update Rollup package has fixes for some of these that do not get installed unless these components have been installed prior to using it.

"Every update" is not necessarily necessary, especially not those that are superseded (unless one wants to go the "Without KB3125574" route, which caused NTLite to label every single HotFix in that category as "Unreadable or unsupported file"), and I don't really care what Windows Update shows or doesn't show so long as I know things have been properly integrated.

 

[LoneCrusader]

I decided to try again using the Win7AndW2K8R2-KB3191566-x64.msu package without pre-adding the standalone KB2809215. This time paid very close attention to the screen when this update was being processed. NTLite only displays output for KB2809215 since it's the first package in the update, but it appears to me that this one was actually successful, and I believe one of the other .CABs inside the package that runs afterward may be causing the issue instead.

Some further digging on the subject led to a mention at MDL that one of these, KB2872047, may be a problem and may be unnecessary. Another source seemed to indicate that the .NET Framework needs to be updated before updating WMF.

garlin Also noted that you listed a .NET update package prior to the WMF update in this list. Is this just coincidence, or is it a prerequisite?

You mentioned extracting the .CABs earlier... I assume this means I can extract CABs manually from .MSU files and NTLite can still process them independently in cases when this becomes necessary?

 

[garlin]

Both 2035 & 2047 are technically not required.

W7 defaults to WMF 2.0, and installing 3.0 or 4.0 requires an optional update. WMF 5.1 doesn't require any previous versions, but Win7AndW2K8R2-KB3191566 has to account for them. Therefore it includes additional updates for earlier versions. If you don't have them, those updates cannot be applied.

https://devblogs.microsoft.com/powe...rtial-installation-without-net-framework-4-5/

• KB 2823180 – [it's really 9215] Fixes event forwarding, access to en-US cmdlet Help in localized Windows builds, and Windows serviceability issues that occurred in WMF 3.0.
• KB 2872047 – Maintains PS Module Path during installation and uninstallation, if WMF 3.0 is already installed on the computer.
• KB 2872035 – Maintains PS Module Path during installation and uninstallation, if WMF 3.0 is not already installed on the computer.

MSMG covers this in the MDL thread a page later. On my system, only 9205 & 1566 are installed. Which means the post-setup attempt to add the other updates made no difference. 3929 is an outdated SHA-2 update, superseded by the monthly rollup.

I went back and tried several combinations of the individual CAB's, and while you can build an integrated image w/o .NET installation -- it won't install correctly. Instead W7 setup hangs in random places. Forcing a reboot reveals W7 rolling back updates as "corrupted" -- including 1566.
We're not even reaching Post-Setup to run .NET install...



WMF install requires a reboot to finish, and the conflict with monthly rollup doing its thing is why it reverted.
Some servicing steps are scheduled for the next reboot, and this order counts. So it's not the order of patch integration, but order of cleanup.

I don't know if it's still possible to come up with a winning combination. We do know the normal rule of running WMF (MSU or CAB) thru a post-setup command always works.

 

[LoneCrusader]

Interesting. Looks like I may want to hold off on adding the WMF package to a later "pass" - but even then I'm not sure when to add it, before/after this or that.. lol

Did you use the CAB version in the screenshot? I don't remember seeing a proper description for KB3191566, only for KB2809215 on my attempts.


I did find a possible source of confusion; I had used WHDownloader from MDL to quickly collect updates and it provides some documentation and explanation along with the collected files. There's a bit of conflicting information regarding WMF in it (emphasis mine):

- If you intend to install any of the following feature packages, install them *first* (before KB3125574)
so the rollup can install their updated components afterwards:
RDP, WMF, DCA2.0, AD LDS, RSAT, VirtualPC, WorkFolders, Server Essentials Connector

WMF
Windows Management Framework 5.1 - requires:
- .NET 4.5.2 Framework or higher
- Convenience Rollup KB3125574 or Security Monthly Quality Rollup

My original plan was based on getting all these things added prior to using the KB3125574 Rollup; it looks like WMF (at least 5.1 anyway) may not fall into this category after all, given the discrepancy in the documentation and the fact that I don't see a folder with HotFixes for WMF in the "WithoutKB3125574" section of the WHDownloader files.

What other packages do not support direct integration and must be handled as a post-setup command and/or require a specific cleanup order? I can reserve those for adding last, hopefully avoiding issues until everything else is working as intended...

So far, everything except WMF seems to be integrating properly. 27 packages covering all the things I listed above, plus 3 I went ahead and pulled from NTLite's list. Next I suppose I will try adding what remains on NTLite's list, holding out anything that requires special handling.

 

[garlin]

Yes, I used the CAB version of 1566 to override NTLite's rules. According to 2017's changelog, NTLite has specific understanding of WMF 5.1.

The question about installing WMF before 5574 is which versions?

WMF 3.0 - Dec 2012
WMF 4.0 - ?? 2013
5574 - May 2016
WMF 5.1 - Jan 2017

Fortunately, WMF 5.1 was the only strange glitch. If you installed it normally in post-setup, it reverts some of the versioning metadata and leads WU to suggest re-installing existing patches. It doesn't impact functionality, just WU thinks part of an update is downrev.

The only way to make this disappear is reinstall selected updates to redo the versioning. We refer to it as "WU satisfy".
Hence the carefully handcrafted update lists to avoid versioning hell. Once you're past 2018 in release dates, it's all gravy.

 

[LoneCrusader]

*changed thread title to expand the scope

Well, after more trial and error I'm now two "passes" in with most of the updates integrated.

Had to redo things from the beginning again using "Custom" clean update backup mode; tried to use "DISM Compatible" first as I thought this was the "correct" way but found that the .WIM size grows exponentially and found in the Documentation that "DISM modes do not support Windows 7." The "DISM ResetBase" option is grayed out but the other is selectable... if it isn't supported, why?

In the "first pass" I added these Updates:

Spoiler: Pass 1

KB917607 - Windows Help 32-bit Compatibility Update
KB943790 - File Management API Extensions For BitLocker
KB949104 - (WindowsUpdateAgent-7.6-x64.exe)
KB3138612 - Windows Update Agent
KB958559 - Windows Virtual PC
KB958830 - Remote Server Administration Tools
KB969168 - Microsoft Agent
KB970985 - Remote Administration Tools For Windows Media Services
KB974150 - Windows NTBackup Utility
KB974674 - Windows NTBackup Restore Utility
KB974405 - Windows Identity Foundation
KB975541 - AD LDS Feature
KB2462137 - AD MMC & ADAC Country Update
KB2539513 - Repadmin Indefinate Query
KB2589154 - AD MMC RODC Update
KB2647644 - AD Certificate Use Issuer Update
KB2790338 - AD FS Update Rollup 3
KB2898997 - Adamsync fails when you synchronize tombstoned objects *(one source found later says this one is unnecessary)
KB3012660 - Unable to install Security Update KB2853587
KB981390 - Windows Server Update Services Best Practices Analyzer
KB981392 - Application Server Best Practices Analyzer
KB2386667 - Application Server Best Practices Analyzer Rules Revision
KB2666914 - DirectAccess Connectivity Assistant 2.0
KB2790621 - Windows Server Essentials Connector
KB2891638 - Work Folders For Windows
KB2959936 - Embedded Lockdown Manager Feature Set Update
KB2574819 - Support for Datagram Transport Layer Security (DTLS)
KB2592687 - Remote Desktop Protocol (RDP) 8.0
KB2830477 - Remote Desktop Connection (RDC) 8.1 client
KB2984972 - Remote Desktop Protocol (RDP) 7.1 update
KB3075220 - Security Update for RDP 7.1

In the "second pass" I added these Updates:

Spoiler: Pass 2

KB2545698 (IE core fonts reliability)
KB2547666 (IE clear history reliability)
KB2667402 (Terminal server security)
KB2670838 (Platform Update)
KB2676562 (Kernel-mode drivers security)
KB2685811 (KMDF 1.11)
KB2685813 (UMDF 1.11)
KB2698365 (MDAC security)
KB2706045 (Jscript and VBscript security)
KB2729094 (Segoe UI font)
KB2732059 (XPS doc format)
KB2750841 (IPv6 readiness)
KB2761217 (Calibri fonts update)
KB2773072 (Game rating systems)
KB2834140 (Hybrid vid cards config reliability)
KB2841134 (Internet Explorer 11)
KB2862330 (USB drivers security)
KB2900986 (AcitveX killbits security)
KB2919469 (Canada country code)
KB2970228 (Russian currency symbol)
KB3000483 (Group Policy security)
KB3004375 (Audit Process creation policy)
KB3006137 (Lithuanian currency symbol)
KB3031432 (Elevated priveleges security)
KB3046269 (Task Scheduler security)
KB3059317 (Common controls security)
KB3102429 (Crystal Reports update)
KB3118401 (Universal C runtime)
KB3123479 (Deprecate SHA-1)
KB3125574 (Update Rollup)
KB3150220 (Media Center security)
KB3156016 (Graphics component security)
KB3156019 (Graphics component security)
KB3159398 (Group Policy security)
KB3161949 (WPAD protocol security)
KB3172605 (Update Rollup 7-21-16)
KB3179573 (Update Rollup)
KB4019990 (.NET 4.7 installation reliability)
KB4474419 (SHA-2)
KB4490628 (Servicing Stack Update)
KB4532945 (.NET 3.5.1 rollup, last Non-ESU)
KB4534251 (IE11 Cum. Sec. Upd, last Non-ESU)
KB4534310 (Monthly Rollup, last Non-ESU)
KB4539602 (Stretch wallpaper bug)

Is there a way to remove the "Uninstall" option from showing for integrated items on the Installed Updates page? I'm showing KB976902 which came pre-integrated on the ISO I use, and it has no Uninstall option.

Between the two passes, most of the things that are on NTLite's current list have been added. I haven't gone back to add WMF 5.1 yet, or anything else that requires special handling.

I assume because of the oddities revolving around Windows Update I'm seeing a few odd updates that aren't on the list. Just thought I would see if there's any input on these...
In the "Important" category:
KB4041083 & KB2894844 - Security updates for .NET; I assumed that since I had not added .NET 4.8 yet that it would satisfy these; it doesn't.
KB3185319 - appears to be an old superseded IE cumulative update; some info I found indicates the newer rollups fully supersede it but don't have the correct "supersedence metadata."
KB3155178 - appears to be a security update for Windows Journal; I assume I'm seeing this since I haven't used KB3161102.
KB976932 - SP1 shows up, even though my reference ISO already has it integrated. Weird, lol.
In the "Optional" category:
KB4049016 - more .NET, same as above
KB4493132 - haven't investigated yet
KB4539601- haven't investigated yet
KB4503548 - .NET 4.8
KB4567409 - Microsoft Edge (does this one support integration or is it another that needs special handling?)
-a few more here but most of them are "Telemetry" updates if I recognize the KB numbers correctly.


Once decisions are made pertaining to these it's time for a third update pass.. then on to other customization.

I've looked around through the various options in NTLite and didn't see anything seemingly related to these; is there a way to:
- force the Windows Classic theme?
- modify other Taskbar/Start Menu settings other than what I see listed?
- restore the Quick Launch bar?
- enable the hidden Administrator account?

 

[garlin]

- KB976902 is baked into SP1, you can't uninstall it.
- Windows Update Agent patches are superseded by the monthly rollup (skip all of them).
- IE11 requires KB3185319 + KB5005036 to satisfy WU metadata.
- KB4539601 (stretch wallpaper bug) supersedes KB4534310 (Dec 19), and can be integrated

Telemetry/W7 upgrade/EOL patches to skip:
- KB4493132
- KB3021917
- KB3068708
- KB3080149
- KB3150513
- KB971033

WU will nag you to install them, mark them as Hidden Updates.

Don't bother installing Edge in the update form. Edge pushes releases too quickly.
Download the x64 installer from Download and deploy Microsoft Edge for business

Some of the optional packages, no one really used because they sucked compared to contemporary alternatives. I call them "abandonware" since they didn't survive the test of time.
ie. Work Folders, DirectAccess, Virtual PC (go install VirtualBox or VMware)

Most people like throwing in NVME support for good measure:
KB2990941, KB3087873 [dig around the web for archived copies]

Here's my pure EOL list:

Pass 1:
KB2574819
KB2592687
KB2830477

Pass 2:
KB2533552
KB4490628
KB4536952
KB2670838
KB2984972
KB3075220
KB3031432
KB3125574-v4
KB2547666
KB2545698
KB2676562
KB2667402-v2
KB2698365
KB2706045
KB2685811
KB2685813
KB2732059-v5
KB2729094-v2
KB2761217
KB2750841
KB2773072
KB2834140-v2
KB2894844
KB2900986
KB2862330-v2
KB2919469
KB2970228
KB2990941-v3
KB3020388
KB3000483
KB3006137
KB3004375-v3
KB3046269
KB3059317
KB3075226
KB3087873-v2
KB3123479
KB3118401
KB3102429-v2
KB3138612
KB3156019
KB3156016
KB3150220
KB3161949
KB3159398
KB3179573
KB3161102
KB3184143
ie11-KB3185319
KB3172605
KB4019990
KB4040980
KB4532945
ie11-KB4534251
KB4538483
KB4539601

 

[Clanger]

Most people like throwing in NVME support for good measure:
KB2990941, KB3087873 [dig around the web for archived copies]

Both are in my w7 driver pack(link on profile page) for members convinience. Can also be found at win-raid.
Must be added to boot.wim - microsoft windows setup aswell as install.wim.

 

[LoneCrusader]

For some reason this seems to be a lot more difficult than what it should be... lol.

- KB976902 is baked into SP1, you can't uninstall it.

I know that; I don't want to uninstall it, I want to know if I can make the others I integrated "not uninstallable" as well. ("remove the "Uninstall" option")

- Windows Update Agent patches are superseded by the monthly rollup (skip all of them).

OK, that sounds good. Less updates to deal with. But why are the older ones included in the

...carefully handcrafted update lists to avoid versioning hell.

then?

- IE11 requires KB3185319 + KB5005036 to satisfy WU metadata.

I assume replace KB5005036 here with KB4534251 if not using ESU?

- KB4539601 (stretch wallpaper bug) supersedes KB4534310 (Dec 19), and can be integrated

I assume this renders KB4539602 unnecessary/obsolete as well?

Telemetry/W7 upgrade/EOL patches to skip:
- KB4493132
- KB3021917
- KB3068708
- KB3080149
- KB3150513
- KB971033

Good to know about KB4493132; the rest I had listed and I also have KB2952664 listed in this category as well.

If not using any of those, is KB3184143 actually good for anything?

Some of the optional packages, no one really used because they sucked compared to contemporary alternatives. I call them "abandonware" since they didn't survive the test of time.
ie. Work Folders, DirectAccess, Virtual PC (go install VirtualBox or VMware)

For the most part I agree with you here; most of these are useless to the average user, and I prefer VMware to Virtual PC (although I've heard Virtual PC is more "old Windows" friendly). I just like to add everything optional in before I start removing things (and especially in this case since apparently they need to be in place prior to the Update Rollup). Then it's there if I want it for some reason; I can always delete it later if not.

Most people like throwing in NVME support for good measure:
KB2990941, KB3087873 [dig around the web for archived copies]

Both are in my w7 driver pack(link on profile page) for members convinience. Can also be found at win-raid.
Must be added to boot.wim - microsoft windows setup aswell as install.wim.

A good idea; but I saw a comment here in another thread that these were integrated in the Update Rollup. If that's true then do they need to be used separately as well? (or just separately on boot.wim?)

Here's my pure EOL list:

Thanks; I'll try running a build with these along with the optionals and see how it compares with what I'd already done... I see a handful in here that aren't on NTLite's list (KB4536952, KB2894844, KB3020388, KB3075226, KB3150220, KB3185319, KB4040980, KB4539601). Collected those, all look like good additions.

KB2533552 - if this is superseded, is there a reason to keep using it?
KB2894844 - assume this is another case like KB3185319 where it's superseded but WU doesn't recognize that?
KB4040980 - read that it's supposed to be part of KB4049016 that I was offered on WU; but KB4049016 was pulled (Update Catalog now has 4 individual packages instead). Assuming neither of these is superseded by KB4532945 for WU?

And I assume the answer to my other questions in the last post is "no" since no one commented on them.

 

[Clanger]

A good idea; but I saw a comment here in another thread that these were integrated in the Update Rollup. If that's true then do they need to be used separately as well? (or just separately on boot.wim?)

MS NVMe driver and hotfix Windows6.1-KB2990941-v3-x64.msu and Windows6.1-KB3087873-v2-x64.msu will be needed by boot.wim - microsoft windows setup. They will not be needed for install.wim as kb3125574 will contain later nvme drivers.

You might want to have a look at this post, it may or may not be helpfull.

 

[garlin]

Bleh, you can't post a reply to a reply...

For some reason this seems to be a lot more difficult than what it should be... lol.

MS learned from W7 patch mistakes and went straight to all-in monthly CU's in W10/11. Outside of the separate SSU, .NET updates -- everything is automatically superseded by the next month's. Period.

Too late for W7. Good news is W7 is mostly static, and will be dead next January (2023).

I know that; I don't want to uninstall it, I want to know if I can make the others I integrated "not uninstallable" as well. ("remove the "Uninstall" option")

That's a NTLite quirk, it recognizes those updates came with SP1. All other updates are fair game for uninstalls.

OK, that sounds good. Less updates to deal with. But why are the older ones included

Simple, there's too much to research. I used to assume WU Agent was separate until I found an obscure site where someone tracked the build version of every later update that included WU Agent. Including older versions are harmless, they'll get superseded by CU.

I assume replace KB5005036 here with KB4534251 if not using ESU?

Correct. Jan 2020 is the cutoff date for pre-ESU.

I assume this renders KB4539602 unnecessary/obsolete as well?

KB4539601 is the preview version of 9602. MS felt terrible about the wallpaper bug, but didn't want to look stupid re-releasing the "FINAL UPDATE" for W7. They changed the rules and allowed 9601 to be its "replacement". Never admit failure.

If not using any of those, is KB3184143 actually good for anything?

I hear W10 is a great OS! 4143 is nagware.

For the most part I agree with you here; most of these are useless to the average user, and I prefer VMware to Virtual PC (although I've heard Virtual PC is more "old Windows" friendly). I just like to add everything optional in before I start removing things (and especially in this case since apparently they need to be in place prior to the Update Rollup). Then it's there if I want it for some reason; I can always delete it later if not.

Virtual PC is so primitive. The fact you can't host anything other than XP, Vista, W7 makes it pointless.
For the rest, so many promising product ideas... so little consumer adoption...

KB2533552 - if this is superseded, is there a reason to keep using it?
KB2894844 - assume this is another case like KB3185319 where it's superseded but WU doesn't recognize that?

Keep both for metadata.

KB4040980 - read that it's supposed to be part of KB4049016 that I was offered on WU; but KB4049016 was pulled (Update Catalog now has 4 individual packages instead). Assuming neither of these is superseded by KB4532945 for WU?

.NET 3.5 rollup is kinda weird. While it's listed as a single KB, in reality it's a bundle of individual fixes. Some of them you need, some you don't depending on other updates. If you roll over to Microsoft Update Catalog, find the download page it's actually 5 files.

Don't feel bad. I wasted three months from Dec '19 to Feb '20 trying to figure out the "perfect" update list that made WU happy, and didn't have any superseded updates. When you're caught up, we can hit our heads on wall on integrating WMF 5.1

 

[garlin]

MS NVMe driver and hotfix Windows6.1-KB2990941-v3-x64.msu and Windows6.1-KB3087873-v2-x64.msu will be needed by boot.wim - microsoft windows setup. They will not be needed for install.wim as kb3125574 will contain later nvme drivers.

I've heard that story before (5574 replaces the NVME drivers), but couldn't find independent confirmation.
Looking at my W7 system, the current stornvme.sys driver matches WinSxS build 6.1.7601.23403 (which is 5574).

DISM cleanup seems to have removed 7873 for me. Good to know.

 

[Clanger]

garlin My system, w7 64bit, updated to EOL only.
stornvme.sys - DriverVer=06/21/2006,6.1.7601.23403.

Windows6.1-KB2990941-v3-x64.msu does contain an earlier driver but its good enough to get setup going on a Crucial P2 M.2 250gb nvme drive. Its why i didnt include Windows6.1-KB2990941-v3-x64.msu and Windows6.1-KB3087873-v2-x64.msu in the INSTALLWIM folder in my driver pack.
If i am correct the driver is still up on Windows Update Catalog but the hot fix isnt.

Edit, i wonder if the ESU's have any newer drivers over and above those in 3125574+EOL updates,,,,

 

[Clanger]

garlin
KB2990941-v3 - v6.1.7601.18615
KB3125574 ----- v6.1.7601.23403
.23403 must be the latest because SDI has never offered me a newer driver.

 

[garlin]

Edit, i wonder if the ESU's have any newer drivers over and above those in 3125574+EOL updates,,,,

Not for NVME.
For a list of the files that are provided in this update, download the file information for update 5010404

 

[Clanger]

If i am still using w7 when ESU ends i might do a new capture with the esu's installed.

 

[LoneCrusader]

Good to see you all got to the bottom of the NVME drivers question.

MS learned from W7 patch mistakes and went straight to all-in monthly CU's in W10/11. Outside of the separate SSU, .NET updates -- everything is automatically superseded by the next month's. Period.

Too late for W7. Good news is W7 is mostly static, and will be dead next January (2023).

It does appear to be very messy. Every time I deal with "newer" versions of Windows I'm reminded why I don't use them.
(An old Win 9x diehard here.. and XP is still my daily driver. And I thought building slipstreamed versions of Windows 9x by hand was difficult...)

But unfortunately one sometimes encounters a newer piece of software that requires these newer monstrosities, or has to learn to manage them to help friends and family who want things to "just work." Both apply here.

Since as you point out 7 is mostly "static" now, I'm trying to build an image that I can "tolerate" working with. All the updates and optionals is of course important to reduce setup time, but the main issues for me are UI customization and user control. If I have to spend more than 5 minutes working on a Windows 7 or higher machine that doesn't have ClassicShell (and now also 7+ Taskbar Tweaker) installed, and doesn't have UAC and the other "automatic" nanny junk disabled I just end up wanting to bash the machine to bits with whatever I can lay hands on.. lol But I digress.

I used to assume WU Agent was separate until I found an obscure site where someone tracked the build version of every later update that included WU Agent. Including older versions are harmless, they'll get superseded by CU.

In this case, before I run yet another build culling superseded updates, is KB3138612 then also superseded by the final rollup?

I assume this renders KB4539602 unnecessary/obsolete as well?

KB4539601 is the preview version of 9602. MS felt terrible about the wallpaper bug, but didn't want to look stupid re-releasing the "FINAL UPDATE" for W7. They changed the rules and allowed 9601 to be its "replacement". Never admit failure.

"Preview version?" I saw that terminology used and wondered what that was supposed to mean, especially since 9602 is much smaller in size and I thought "there's no way everything that's in the larger package is in the smaller one..."

So, if I understand correctly: KB4539601 supersedes both KB4534310 and KB4539602 and neither of the latter will show up on WU if the former is used?

If not using any of those, is KB3184143 actually good for anything?

I hear W10 is a great OS! 4143 is nagware.

KB2533552 - if this is superseded, is there a reason to keep using it?
KB2894844 - assume this is another case like KB3185319 where it's superseded but WU doesn't recognize that?

Keep both for metadata.
...
Don't feel bad. I wasted three months from Dec '19 to Feb '20 trying to figure out the "perfect" update list that made WU happy, and didn't have any superseded updates. When you're caught up, we can hit our heads on wall on integrating WMF 5.1

So essentially these (nagware/telemetry + superseded updates) are only good for satisfying what Windows Update says..?

I've been sending my builds to WU to check for updates mainly just for investigative purposes. While it's nice to show everything "satisfied," I never allow any of my machines to "auto update" and probably would never even send them to WU, preferring to hand pick, download, and install such things manually.

Given that all that remains now for 7 is ESU, and from what I read those cannot be "integrated" anyway, I'm inclined to be more concerned with avoiding redundancy rather than satisfying WU...

(And I've not even attempted yet to examine all of the files WSUS Offline Update downloaded for Windows 7 when I ran it, or how they fit (or don't fit) into the context of what I've already done...)