A of duplicate entries for a number of staged Win7 Updates.

Rikomenar

New Member
Hello

I freshly installed NTLite v2.3.2.8526 64-bit and renewed the license. I opened an earlier WIM image made with NTLite ~2.1.x.xxxxx (~June 2021)

Stage 1: The ISO is Win7 Ultimate EN-US 64-bit 7601.24214.180801-1700 - with older NTLite.
  • I have removed a number of updates that include those which would mess up running older games, exported as a WIM package.
  • I am aware that removing pre-integrated default updates is risky and could create buggy behavior or conflicts.
  • I have removed updates with a rule from newest to oldest in an effort to avoid conflicts, NTLITE/DISM/CBS has no problems in this process.
  • However the final success of this will only be seen in practice once the OS is installed and put into normal use. We shall see.
  • Once I removed them, I exported the session as a WIM package (the stuff inside an ISO)

Stage 2: Using the above WIM package as a source for a new fresh NTLite session.
  • Then I manually added/integrated several updates. The list of updates:
  • ie11-windows6.1-kb4534251-x64_91ee2d40871aba94d4c13eaaa623c7f4b6577e46.msu
    • windows6.1-kb2574819-v2-x64_a0b7ffff5c8fc9b2f16b323e582bcda3bbe972d5.msu
    • windows6.1-kb2592687-x64_f5cd9f3dab8cdbbf287fee84148e8ea69042bcc3.msu
    • windows6.1-kb2676562-x64_446b9165a9a52540896cefb69f6de1d193416056.msu
    • windows6.1-kb2706045-x64_ffc82084794531c27bd4a670408d2c4a4d038ad8.msu
    • windows6.1-kb2830477-x64_21cae4796ac834f66eec9a190815e1e1b8195908.msu
    • windows6.1-kb3000483-x64_67cdef488e5dc049ecae5c2fd041092fd959b187.msu
    • windows6.1-kb3102429-v2-x64_fbf07105ff35e936f413663e0f4900cb7055368a.msu
    • windows6.1-kb3118401-x64_99153d75ee4d103a429464cdd9c63ef4e4957140.msu
    • windows6.1-kb3123479-x64_f8d8752d60da493c119b5b03c6b54ffc5dbff69d.msu
    • windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu
    • windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu
    • windows6.1-kb4490628-x64_d3de52d6987f7c8bdc2c015dca69eac96047c76e.msu
    • windows6.1-kb4532945-x64_d070fb06c4c56f70e4d2e891181028fa7c35694d.msu
    • windows6.1-kb4534310-x64_4dc78a6eeb14e2eac1ede7381f4a93658c8e2cdc.msu
    • windows6.1-kb4539602-x64_977d8a5421d03ba7ddd992ddf79175dddcfb90d4.msu
    • windows6.1-kb4592510-x64_2798f0d248e08c292076980d2b954e6e1f2c8f99.msu
  • And exported the session as a new WIM package again.

Stage 3: Using new NTLite version, I loaded a copy of the above WIM package(folder) in a fresh new session.

In the Updates section, there are lists of installed, integrated, uninstalled ones, but some appear so many times.

KB3125574 - staged - appears over 100 times.
KB4534310 - staged - also
KB4539602 - staged - also but lesser times.

Now I think this is perhaps due to these packages including more updates inside ...

Proposition for enhancements:

If so, Add an indication that an update includes other updates.
Or, provide a tree-vew feature to the Update section so that all of the instances can be selected by selecting the parent.
Otherwise just show one item in the list per package, if this is a bug.

Add right-click option to copy update label/name ("KB???????")
Add multi-select feature so that multiple different updates could be removed/changed with a single click.
 

Rikomenar

New Member
Actually, I forgot where I was left off and just started over, infact, I think I it would have been more conflict-friendly if I made my edits after removing updates, exporting that as WIM package and then adding the updates as I later found out in my notes.
That's because many of these updates are staged to install afterward, I guess after the base installation, seems like you can't install them fully like MS does or I haven't found a way.

It may not be an issue with the ordering in such a case if these updates will always be staged for later no matter when you add them with NTLite, but it's worth some experimentation to see the result.
 

garlin

Moderator
Staff member
Don't use 7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_ULTIMATE_x64FRE_en-us.iso

While it's an official release, post-RTM images have many updates already integrated. Removing them and adding more will destroy the image integrity. Start over with a clean SP1 image, and apply your updates list.

W7 is especially picky about removing and re-applying updates, due to known component versioning issues. Most of which are avoided by using an unmodified SP to start.
 

Rikomenar

New Member
Don't use 7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_ULTIMATE_x64FRE_en-us.iso

While it's an official release, post-RTM images have many updates already integrated. Removing them and adding more will destroy the image integrity. Start over with a clean SP1 image, and apply your updates list.

W7 is especially picky about removing and re-applying updates, due to known component versioning issues. Most of which are avoided by using an unmodified SP to start.

Thanks for your warning, indeed this was one of the 2 attempts I thought I could see if it'll work, it was optimistic.

Eventually, I still have to remove those updates somehow later for a number of games to work. I assume the commuinty has most likely figured out a way to do that already?
 

garlin

Moderator
Staff member
No, because it's not practical. Start over with SP1 RTM and add your updates list.

MS restricted W7 ISO downloads to only users with retail license keys (not OEM), which is why everyone uses win7sp1_ldr_escrow_CLIENT_ULTIMATE_x64FRE.

What if Google searched for "GSP1RMCPRXFRER_EN_DVD archive.org"? Maybe that ISO won't have "bad" updates...
 

Rikomenar

New Member
Sure I was going to redo it ofcourse, I believe some of the updates that break older games were added from 2015-2020, but I forgot exactly. Need to check my notes.
 
Last edited:

Rikomenar

New Member
SP1 RTM (7601.17514) -> Nov 2010
SP1 LDR_ESCROW (7601.24214) -> Aug 2018

There you go.

So I guess to do it the best way, you said I need to use RTM way back in 2010 and build it up, that does indeed seem familiar.

I had a plan worked out and pretty much understood most of it, I unfortunately went busy for 6 months and now I forgot a lot, I apologize for this thread going off the topic into support. Now I remember reading something about the newer version being too-new and bloated with stuff that kills legacy compatability, and you said I'm not suppose to use it at all, so these LDR ESCROW are actually useless?

Honestly, sometimes I'm royally confused with all of the different designations and ISOs and combinations even tho I deal with a lot more complex stuff on a daily basis, just one of those annoying thorns, never got to dig into it yet.
So many different identifiers for the same thing, Build Number, Build Name, DVD number, DVD Label, probably DISM the mount title, and more, and more combinations for OEM, VL and Client, but that's fine, not something that I can't get over eventually.

I already had the RTM prepared to start customizing, I only picked LDR_ESCROW to see if it'll work. I did seem to work tho I had no games installed yet. Thanks for saving me the trouble in the future, I'll stay away from 24214 then.
 
Last edited:

garlin

Moderator
Staff member
The confusion is from using non-RTM editions. W7 only had two RTM's: original and SP1.

For MSDN and OEM partners, they released later W7 images for installation. They're not intended for building ISO's, since updates are already pre-installed for convenience. You can apply later updates to any of those images.

When an image has a build number [7601.24214.180801], the last digits are the date 2018-08-01
Don't use any image past 2010-11 for building ISO's.

The rest of the crazy naming is targeted editions for international markets (languages, no Media Player edition), or eval copies.
 
Top