abbodi1406

express cab contains only the update manifest files + xml file.. those are used by WU to identify the original package contents and to determine what components of it are needed for the system so it download them only
 
i.e.
if the update are multilingual, it will download only lang resources matching your system
 
only WU knows how to handle this mechanism
so, express cab are useless and cannot be used for integration

Read the entire thread.  Yes he was trying to use all possible updates, but he did quite a bit of analysis to determine which lists are the most complete and up to date and without duplicates.
 
What is your intention?  Just to satisfy Windows Update or get all available updates?  And are you building an install source just for your personal home use or are you making an install source for business use or what?
 
 
1. Yes there are that many updates available if you include the request only updates.
1a.  I haven't checked all of the various lists, but reasons can include:
 
* some lists might, or might not, include updates that are obsolete
* some lists might not be up to date
* some lists might, or might not, include request only updates
* some lists might, or might not, include updates that cannot be applied on an offline image
* some lists might, or might not, include updates that only apply to optional features

2&3. Windows Update does not, and cannot, download request only updates, even though the request only updates ARE "real" updates, they just might, or might not, officially apply to you at this time.
 
Request only updates are updates, or hotfixes, that have been developed by MS to deal with specific problems and generally they have not been tested quite as extensively on as wide a variety of systems as the "regular" updates that are pushed out by Windows Update, so there is a very small possibility that they might cause an issue on your system.  But that risk is extremely small and I know of no one personally that has ever had an issue if they installed those request only updates.  But even regular updates have caused issues in the past so it is possible.  Back when MS used to put out Service Packs, such as SP1, ALL updates issued prior to that time would be included in the SP, both regular and request only, so many folks, including me, just figured they might as well go ahead and install the request only updates when they became available, even if they did not apply to them at that time, "just in case".  Others just wanted Windows Update to say they were up to date, and they thought "unnecessary" updates just added bloat and applied to issues that they were unlikely to have, so decided not to install them.  It's up to you to decide what you want.  If you decide that you do not want any of the request only updates, then you might find this thread useful - http://www.wincert.net/forum/topic/10811-15-mars-2014-updates-packs-gdr-windows-7-sp1/ - but I have not checked lately to see if all links are still valid or if it is up to date.  You'll probably need to at least read the first page and the last couple of pages in the thread using a translation program such as Google Translate to know for sure what is going on.
 
As a general rule, you will be better off if you decide whether you want Request only updates or not, pick ONE list that seems to be kept up the best and meets your needs, and just use that one list.  Then pick up the few, if any missing updates after you have installed your system using Windows Update.
 
Good luck!
 
Cheers and Regards

On Winows 7 C: is always the OS partition, this never changes

@abbodi1406 - No problem, I value your .NEt pack and gladly wait :thumbsup_anim:

From Additional, integrate these:
PlatformPlatform UpdatesIE11 CABsIE11 UpdatesWindowsMediaCenterWinHelpWUClientonly IE11 is enough and needed to be integrated
 
from Extra, generally you don't need any unless you know what they are for

And keep in mind, that the OEM key from the sticker may be a "one-time only" key - as in using it, the activation will be bound to the hardware it is used on (I am mostly using SystemBuilder Variants(*1) for my system (as I build 'em myself or buy 'em without OS) and there thats not a problem (in short: I simply lack the Win7 OEM experience)), but as far as my knowledge has grown on the subject a vital change in hardware may or may not be activatable via phone or strictly license termin speaking may simply be rejected - so I see a reason to the "why someone will stick to autoactivation as long as possible", because then the OEM key could def. be used on changed hardware (if it is the first time this key is used - so why waste it on the OEM Hardware where its not needed) with just using the online activation. I am really not sure on this one, the MS specific sides (technet, etc.) are AFAIK strict on this one-time bound between key and hardware, other sides claim that an activation via phone is still possible.
 
P.S.: with Win8 this whole OEM/Preactivation Discussion is Void - the new scheme where the "to be activated" key for OEM Systems is kept in the BIOS is a total different matter
 
*1: Ok, from a German Point of view and an old Sentence about the resale of OEM licenses, MS SB variants where (AFAIK) the result of that verdict (as a different model to pure OEM license (like from Dell or such);  SB (OEM) license is nowadays what is nearly 100% of the time sold to the customer here in germany (and I know only a few (real minority) shops who are actually offering the real retail)... And I am not sure what that means for reactivation on different hardware or such, but according to magazines like the C't (not talking Win8+ here) SB licenses under our law should be reactivatable under new hardware (but that may well be just an urban legend).

In addition, and as a final remark on my behalf (it is time to get back to my real studies, though it was fun and reminded me to the time of 2005 where I was one of the minorities who bought xp x64 and where often forced to get used to modify .msi's with Orca) - I tried it again with the (official technet) sysprep way... the reason why WinToolkit recognized my first preped image as being corrupt was that I have chosen a custom name for the image.... still now, and after I've named it right, and though simply building a .iso via WT from the syspreped .wim worked like a charm (the get-package information afterwards was the same as for a real sp1 install-media), it failed when I tried to integrate IE11 and its prerequisites. That doesn't worked out well - WT integrated fine, the install resulted in failures which may well be searched in this forum for the early times of IE11 and its integration. So i am not sure if I missed some KB or if it ain't be possible to use WT on a syspreped .wim (which makes no sense IMHO, so my guess would still be a fault in my procedures - and that one may include that I where using a WinPE.iso handed over to the VM that where build with the current ADK release for Win8+; I used that because it is much easier to apply the dism commands (/capture-image) to build the .wim then using the old variant with imageX). 
 
As said, I still think that it is possible (else all technet sysprep how to build an oem/multilingual media, how to deploy sp1, etc. descriptions wouldn't make sense; At least for the sysprep way).  In the meantime where the vm(s) where occupied with their install I checked the MD5 sums of the KB976902 files with their corresponding parts of KB976932 (SP1) and there where no differences to be found (haven't checked all of the files), so it should - in theory be possible - to get along that way to a working (and future proof) image... But as the OPs question (OEM based Win 7) and my curiosity about Dreamsparks PreSP1 Server 2008 R2 .img are just a minority in cases that may be neglected in the development of WT (or the Foolproof assignments/modules therein (which in my experiences make up 3/4 the time in the development of a GUI based project)) I just give up with trying any further (and will continue with my real work/study again    ). 

Most of the hotfixes are downloaded in sfx zip files and then extracted (this include 5 of the general updates)
 
maybe this is the cause of the inconsistent dating pattern, the timestamp is set for the zip file not the extracted msu file?

Integrating SP1 require manual method and some steps
 
if you can handle those steps, then i can provide you with tutorial

Bad news is that I have a lot of work to do for the next year and half (at least) because the good news is that Win Toolkit got approved to be my final year project. I will write an article so you guys know what to expect from this apart from a much better program.   :albert:  :graduated:
 
You think Win Toolkit is great now? It's only just begun! I have to prepare to rewrite everything with efficiency, concurrency and simplicity in mind. Oh god the paperwork is going to be fun (sarcasm)

General and Security Updates are either GDR only or GDR+LDR
you can easily install those normally (without LDR mode) to get GDR branch
and you may include/count Platform & Platform Updates & IE11/10 into this
 
Hotfixes however, some are LDR only, and the rest are GDR+LDR
managing those will be tricky for you
 
anyway, if you want to only have GDR updates, it's better you stick to what Windows Update offers 
or you may install "General, Security, Platform, Platform Updates, IE11 Cabs, IE11 Updates, WUClient" in normal mode, then go to Windows Update and see what else it offers and download them

Do not integrate these categories:
 
Additional\Not Integratable
Additional\SUR Tool
Additional\WinRE
Additional\Without Platform
Additional\WMF4.0
Additional\WUClient EXE
Extra\BrowserChoice
Extra\DCA2.0 Updates
Extra\French.Enterprise
Extra\NT.Backup.Utility
Extra\pl-pl
Extra\VirtualPC
Extra\VirtualPC Updates
Extra\WMF3.0
Extra\WMF3.0 Updates

Description:

The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.

Info: The .NET package will be slipstreamed as pre-installed
OS: Windows 7 SP1
Notes:
- The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
- Add main addon first before LangPack addon, to get ASP.NET service localization properly.
- To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
Windows6.1-KB4019990-x64.msu
Windows6.1-KB4019990-x86.msu
.NET 4.8:
Spoiler
Version: 4.8.4795.2 (KB5062065)
Date: 2025.07.08
Download:
https://github.com/abbodi1406/dotNetFx4xW7A/releases/latest
Language Packs:
https://github.com/abbodi1406/dotNetFx4xW7A/releases/tag/19.04.13
.NET 4.7.2:
Spoiler
Version: 4.7.3394.3 (KB4488666)
Date: 2019-03-19
dotNetFx472_20190319_x86.WA
   Size: 34.33 MB
SHA-256: 4af1f964868bfa70cec4ddf5f0be2a7beef7c0f51de781b3b26aa0967c412fff
https://rebrand.ly/dotNetWA86
dotNetFx472_20190319_x64.WA
   Size: 45.78 MB
SHA-256: ea59ed76d47b5fbad7885580e07be70a05587282c628c9de6be69b4f72f6a82b
https://rebrand.ly/dotNetWA64
Language Packs:
https://drive.google.com/open?id=1r8NJ6k8a1XTX3cbi1Kyv8BQpTE-6A-d0
Languages Codes Reference:
Spoiler
ARA | Arabic - العربية CHS | Chinese Simplified - 中文 简体 CHT | Chinese Traditional - 中文 繁體 CSY | Czech - čeština DAN | Danish - dansk DEU | German - Deutsch ELL | Greek - Ελληνικά ESN | Spanish - español FIN | Finnish - suomi FRA | French - français HEB | Hebrew - עברית HUN | Hungarian - magyar ITA | Italian - italiano JPN | Japanese - 日本語 KOR | Korean - 한국어 NLD | Dutch - Nederlands NOR | Norwegian - norsk PLK | Polish - polski PTB | Portuguese (Brazil) - Português (Brasil) PTG | Portuguese (Portugal) - Português (Portugal) RUS | Russian - Русский SVE | Swedish - svenska TRK | Turkish - Türkçe 
 

Hi Lego,
 
I just tested the installer (VM):
it's OK, but people should know, they should install it in user-modus (NOT express) and de-select the installation of the awesome-bar and search-engine,
otherwise they get some not wanted-software.
 
Silent-Switches are: /S /NCRC.
With this switches no other software has been installed.
 
And a small bug have I already found:
uninstalling the program the folder WinToolkit on C: and WinToolkit-RunOnce (.log, .exe, .cfg) have not been deleted.
 
Regards, Thiersee

new release: fixed a bug in extract update*.cab (for WinNT6.x Vista/Seven/8.*/Next. As always in Windows XP "msdelta.dll" file - WindowsXP-MSCompPackV1 - KB927374 - must be present in system)

General - Security - Hotfix.. are the main updates that are safe to use for all systems

regarding the difference between Additional & Extra Categories, the reason for having those two categories is for better organizing and to ease the download process for the average user

Additional Updates Category aims to include the "Special" updates that are common or most useful
this includes:

Updates for Specific Features that does not exists in All Windows Editions:
 




Updates or Packages that adds more features or have special functionality:





Extra Updates Category will contain the rest of additional updates
this includes:

Packages that adds more features or have special functionality but not needed for most users:





Updates or Packages that has newer releases:

1) deintergrate is not possible because the addon set and modifies registry settings in the image
but you could try to integrate newer version in image contains older addon version, let me know if it's working 
 
2) as bphlpt explained, .NET 3.5 Family is a completely separate package software than .NET 4.x Family

(2) Unlike in XP, earlier ".NET's" are now part of the OS, and are not designed to be removed, though I think they can be.  And like XP, while .NET 4.5.1 completely replaces 4.5 and 4.0, it does not totally replace 3.5.1 and earlier in the sense that if you did remove 3.5.1 and earlier from your Win7 install, and a poorly written app looked specifically to see if 2.0 or 3.0 or 3.5 was installed, that app would fail even if you had 4.5.1 installed.  At least that's the way I understand how things work.
 
For (1), I'll let abodi1406 or someone else that knows more than I do about this particular addon answer that definitively, but my opinion is that when you do a new build each month or whatever, and you have new hotfixes, addons, tweaks, etc., you are better off starting from scratch, rather than trying to remove the outdated ones and add the new ones in their place.
 
Cheers and Regards

Something simple then. I could add that tonight

This was made using Rick's hep and guidance.  AFAIK, the essential difference is this is an addon while Rick's is a silent installer.  Once installed, the results should be the same.
 
Cheers and Regards

Note:
 
Not to mention its enormous size, KB947821 should not be used offline at all (integrated or silent install), it's ment only for verifying Online system Updates and Packages

@Lego: If you move IE and all the related updates/addons to the end of the integration process, you should not worry about prerequisites.
That's the smartest and simplest way , because months after months, more and more updates will be superseded and because of this the list of prerequisites will be constantly changing.
 
Win Toolkit 1.4.1.27 does not recognize IE11 cabs and let me integrate them at the end: that works beautifully !
 
 
Because an image worth thousand words:
 

KB2726535 is superseded by KB2768486 & KB2905454
 
The IE11 prerequisites components of KB2726535 is superseded by KB2768486, and KB2905454 completes the supersedence
 
so, KB2768486 becomes the new prerequisite instead of KB2533623 & KB2731771
 
BTW, those KB article are not accurate, if you want to see the actual or complete list of prerequisites check SETUPDOWNLOADLIST.txt that is included with IE11.exe package (after you extract it)

KB2726535 is superseded by KB2768486 & KB2905454
 
The IE11 prerequisites components of KB2726535 is superseded by KB2768486, and KB2905454 completes the supersedence
 
so, KB2768486 becomes the new prerequisite instead of KB2533623 & KB2731771
 
BTW, those KB article are not accurate, if you want to see the actual or complete list of prerequisites check SETUPDOWNLOADLIST.txt that is included with IE11.exe package (after you extract it)