Jump to content

[14 janvier 2020] Update list GDR pour Windows 7 SP1 x86/x64 (Fr-En-De-Es-It)


Recommended Posts

No, I mean the three .CAB-files

Spoiler

<!-- WUClient self-update composants -->

<update id="WUClient-SelfUpdate-ActiveX-x64" category="1" publishdate="2014-07-09" article="">
    <title>WUClient-SelfUpdate-ActiveX-x64</title>
    <description></description>
    <filename>WUClient-SelfUpdate-ActiveX-x64.cab</filename>
    <url>http://ds.download.windowsupdate.com/v11/3/windowsupdate/selfupdate/WSUS3/x64/Win7SP1/WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320.cab</url>
  </update>
  <update id="WUClient-SelfUpdate-Aux-TopLevel-x64" category="1" publishdate="2014-07-09" article="">
    <title>WUClient-SelfUpdate-Aux-TopLevel-x64</title>
    <description></description>
    <filename>WUClient-SelfUpdate-Aux-TopLevel-x64.cab</filename>
    <url>http://ds.download.windowsupdate.com/v11/3/windowsupdate/selfupdate/WSUS3/x64/Win7SP1/WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320.cab</url>
  </update>
  <update id="WUClient-SelfUpdate-Core-TopLevel-x64" category="1" publishdate="2014-07-09" article="">
    <title>WUClient-SelfUpdate-Core-TopLevel-x64</title>
    <description></description>
    <filename>WUClient-SelfUpdate-Core-TopLevel-x64.cab</filename>
    <url>http://ds.download.windowsupdate.com/v11/3/windowsupdate/selfupdate/WSUS3/x64/Win7SP1/WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320.cab</url>
  </update>

 

From abbodi140's explanation (post #10467) of the Convenience Rollup

Spoiler

WUClient cabs (superseded, but still checked by WU on each search session as fail-safe)

 

Edited by Thiersee
Link to comment
Share on other sites

On ‎3‎/‎22‎/‎2014 at 10:02 AM, rhahgleuhargh said:

Hello,

Voici des Update Lists (UL) x86 et x64 à utiliser avec la dernière version de Windows Update Downloader (WUD), en partant d’un ISO de Windows 7 SP1.

Elles reprennent le principe des mises à jour proposées par mooms dans son Update pack, à savoir qu'elles contiennent uniquement le minimum de MAJ requises pour n'avoir aucune demande de Windows Update après intégration et installation. Si vous ajoutez le .Net Framework 4.61, ainsi que MRT, aucune mise à jour prioritaire ne sera demandée par WU.

Les mises à jour des programmes supplémentaires (Silverlight, etc...) ne sont pas incluses, utilisez plutôt les sfx du site (l'avantage est que vous aurez la dernière version à jour).

Pour ceux qui ne veulent pas migrer sous Windows 10 et ne veulent pas les mises à jour de télémétrie, lancez en dernier le script HideW10KBs. Vous pouvez aussi installer GWX Control Panel (mais ce programme ne concerne pas les mises à jour de télémétrie) ou Never10 (même inconvénient mais moins invasif que GWX Control Panel).

Certains ont reporté des erreurs SFC avec Wintoolkit (ça dépend des tweaks et des programmes ajoutés). Vous pouvez ajouter le script SFC.exe après HideW10KB dans la liste des programmes à intégrer pour lancer automatiquement la vérification après installation.

Ces listes ont été testées au préalable en MV avec Windows 7 SP1 Professionnel avant publication. Attention : il est possible que certaines KB soient obsolètes si vous utilisez une autre édition de Windows 7 (ex. : KB2973351 est inutile sous Windows 7 Home Premium). Dans ce cas, faites un nettoyage de disque après installation, et signalez-moi les KB inutiles (je ne teste que la version professionnelle, je n'ai pas le temps pour les autres).

Les instructions pour WUD sont dans le fichier Read-me.txt.

Pour intégrer le Convenience Rollup Pack sous Wintoolkit, il faut faire passer KB3020369 et KB2670838 dans la section "Prerequisites" de Wintoolkit.

Credits : mooms pour l'idée du pack et les scripts pour créer les installateurs silencieux, abbodi1406 pour ses infos sur les mises à jour, gillesg pour l'utilisation de WUD, icare pour les SFX, Thiersee, Pink_Freud, Dareckibmw et les autres pour les différents retours et coups de main.

 

@non-french users :

Here are x86 and x64 Update lists for WUD based on mooms Update packs and configured to be used with Win Toolkit. The purpose of these ULs is to integrate the minimum updates required, so you won't have any update asked by Windows Update after integration and installation. These ULs don't include Silverlight and .net Framework 4.x, but you can DL their updated version in the Installer Repack section of this forum and integrate them via "Silent install + SFX" section of Win Toolkit. With .net framework and MRT integrated, your Win7 installation will be up-to-date. Some updates can't be integrated offline, they are renamed zWindowsXXX.msu so you can find them easily and integrate them via "Silent installer + SFX" section of Wintoolkit or via Setupcomplete.cmd. For those who don't want migrate to Windows 10 and install telemetry related updates, just run HideW10KB script at the end of installation. You can also install GWX Control Panel or Never10 to definitively block W10 migration (no action on telemetry related updates). Some people have reported SFC /scannow errors after integration ; to check it, add the SFC.exe script after HideW10KB in the list of programs.

These ULs have been tested in a VM with Professional edition of Windows 7 before publication. But if you use an other edition, some KBs may be useless (ex. : KB2973351 for Home Premium) ; in this case please perform a deep clean after installation, and report obsolete KBs in this topic (I only test Professional edition, I have no time for the others). Please have a look on Read-me file in the archive for more information. If you don't write french no problem, most of us understand English !

 

2016-05-10-HideW10_KBs_Silent_SFX.7z

2016-06-08-Read me.txt

2016-06-08-Win7-Post-SP1 GDR-x86-MULTI.ulz

2016-06-08-Rollup-HideW10_KBs_Silent_SFX.7z

2016-06-08-Win7-Post-SP1 GDR-x64-MULTI.ulz

for some reason the June 8, 2016 files (ulz) for x86 and x64 are giving errors in WUD "illegal characters in path". I never had an issue before..

regards...

Link to comment
Share on other sites

Win7 Pro X86 Test result (not roll-up)

KB3162835        replace  KB3153731 (Timezone update)
KB3159398         
KB3161561        replace  KB3156417 & deepclean KB2536275
KB3161664        replace  KB3153199
KB3161949        deepclean KB2888049
KB3161958        
KB3164033        replace KB3140735
KB3164035        replace KB3156013


IE11
KB3160005        replace    KB3154070

Windows 10 Spyware Updates
KB2952664   /
08.06.2016 v18

Edited by X-Force
Link to comment
Share on other sites

@X-Force

Thanks. In my case, WU sucks, I only succeeded to obtain updates from Rollup test machine : IE 11 KB3160005, KB3159398, KB3161561, KB3161664, KB3161949, KB3161958, KB3164033, KB3164035, KB3162835 ; Optional KB3139923 and  KB3140245 are  now marked as "important".

Links are ready. I just wait the results of "classic" VM to begin the tests.

Edited by rhahgleuhargh
Link to comment
Share on other sites

1 hour ago, Thiersee said:

At the moment my VM (installed with Conv-Rollup) searches since 1 hour....

I know this might be difficult to answer but I'm at my wits end. I am using an april 2016 win 7_64 updated ISO made by LEGO. I have incorporated the May 2016 updates from this thread. On some machines I cannot get windows update to find any new updates. It just keeps searching for hours. However on other machines it works fine. It worked on my VM (on my main computer) because I always test the new ISO I create. The latest machine I used it on yesterday still cannot get past finding any new updates. Initially this machine also failed sfc after I used all my silent installs, including mbam, ccleaner, cryptoprevent, GWX, adobe FP, reader dc, googletoolbar. However, sfc corrected the files. I ran sfc again and then it PASSED. I thought that was the reason  for winupdate to not work but winupdate still searching. I then took another HD in this machine, did a new install with same ISO and immediately did an sfc (passed) and then checked for updates. It's still searching....grrrr

When this iso works this is the scenario: 5 minutes after the installation if you manually go to win update there will be in my case about 12 or so updates ready to get installed. If after 5 minutes you manually go to win update and it wants you to search for new updates I know its futile. In addition I have tried literally a dozen fixes via google searches for a repair and nothing works. spent hours and am totally frustrated. I cant seem to get a working ISO. I wrote to lego and even he is stumped. using wtk 1.5.4.4....

regards....

Link to comment
Share on other sites

20 hours ago, rhahgleuhargh said:

@pennsylvaniaron

Yes it's due to the fact I putted " " in the name of the fisrt category, it causes a crash if you have checked "category as subfolder" option. Uncheck it or wait for the next UL release, I've corrected that.

yes I unchecked subfolder and now it works. thanks. Now that I can see the files what are the first 2 "convenience" updates as compared to the "classic". From recollection these are new to me. Am I supposed to COMBINE both categories? In other words should I incorporate BOTH into my ISO?

regards...

Link to comment
Share on other sites

6 minutes ago, rhahgleuhargh said:

since 2 monthes, M$ servers are busy and saturated the 3 days following Patch Tuesday. Even on my Windows 10 installation it was very long to obtain the updates. My opinion : WU needs a fix or M$ should revise the manner to obtain updates.

yes that theory at this point makes the most sense. It was even suggested in some of the blogs I visited when trying to repair. I'll check it out later.

regards...

Link to comment
Share on other sites

1 minute ago, pennsylvaniaron said:

yes I unchecked subfolder and now it works. thanks. Now that I can see the files what are the first 2 "convenience" updates as compared to the "classic". From recollection these are new to me. Am I supposed to COMBINE both categories? In other words should I incorporate BOTH into my ISO?

regards...

Just be patient, this bug will be solved for next release. The 2 integration methods can coexist. In next release, all updates related to Convenience Rollup will be numeroted.

Link to comment
Share on other sites

Half an hour ago I terminated the search in my VM, I didn't want to wait longer.

Ten minutes ago I started the VM and the search again: I got immediately the list of requests!

I started the installation and I wait and wait....

Edit:

Just now finished....

 

@pennsylvaniaron

The first category contains only the Convenience -Rollup

the second contains the common patches for method 1 (with rollup) and method 2 (classic, like up to may)

the third contains all the patches only for method 2 (classic).

It means:

if you are using the rollup-methode you need category 1 & 2

if you are using the classic-methode you need category 2 & 3

All other categories are related to both ways.

 

BTW, I tested the Rollup-methode (Professional x64) with WTK 1.5.4.4 with this .INI and it works very good: rollup-pack (KB3125574) just before the patches for may

Spoiler

*AIO|v1.5.4.4|2016-06-13_21-20-PM
#Silent Installs
KB2533552::N/A (Not Needed);NO;9,23 MB;E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2533552-x64.msu;Always Installed
#Updates
E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3064209-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3020369-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2670838-x64.msu
E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3102429-v2-x64.msu
E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3139923-v2-x64.msu
E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3140245-x64.msu
E:\WUD_Convenience_Rollup\x64\ADD-Windows6.1-KB3156417-x64.msu
E:\WUD_Convenience_Rollup\x64\RDP-Windows6.1-KB2574819-v2-x64.msu
E:\WUD_Convenience_Rollup\x64\RDP-Windows6.1-KB2592687-x64.msu
E:\WUD_Convenience_Rollup\x64\RDP-Windows6.1-KB2813347-x64.msu
E:\WUD_Convenience_Rollup\x64\RDP-Windows6.1-KB2830477-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB971033-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2545698-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2547666-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2667402-v2-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2676562-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2698365-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2729094-v2-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2732059-v5-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2750841-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2761217-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2773072-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2834140-v2-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2862330-v2-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2894844-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2900986-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2919469-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2970228-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB2984972-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3004375-v3-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3006137-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3059317-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3118401-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3123479-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3138378-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3138612-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3142024-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3145739-x64.msu
E:\WUD_Convenience_Rollup\x64\WUClient-SelfUpdate-ActiveX-x64.cab
E:\WUD_Convenience_Rollup\x64\WUClient-SelfUpdate-Aux-TopLevel-x64.cab
E:\WUD_Convenience_Rollup\x64\WUClient-SelfUpdate-Core-TopLevel-x64.cab
E:\WUD_Convenience_Rollup\x64\Windows6.1-kb3125574-v4-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3150220-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3153171-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3153199-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3153731-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3155178-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3156013-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3156016-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3156017-x64.msu
E:\WUD_Convenience_Rollup\x64\Windows6.1-KB3156019-x64.msu
E:\WUD_Convenience_Rollup\x64\IE11\IE11-Windows6.1-x64-de-de.exe
E:\WUD_Convenience_Rollup\x64\IE11\IE11-Windows6.1-KB3154070-x64.msu
#Options
Compatibility Check
Enable CMD
Force Unsigned
Log Registry Changes
Prepare Drivers
Prompt Addons
Prompt Drivers
Prompt Gadgets
Prompt Silent
Prompt Themes
Prompt Updates
Prompt Wallpapers
Rebuild Image
Retry Updates
Show Duplicates

 

Edited by Thiersee
Link to comment
Share on other sites

Thiersee plz excuse my newbieness on this subject but what is the "convenience rollups?". In addition are you saying when using WUD I should download EITHER the classics or the CONVENIENCE or download BOTH and incorporate them into my last months win 7_64 ISO?

regards...

Link to comment
Share on other sites

3 hours ago, rhahgleuhargh said:

since 2 monthes, M$ servers are busy and saturated the 3 days following Patch Tuesday. Even on my Windows 10 installation it was very long to obtain the updates. My opinion : WU needs a fix or M$ should revise the manner to obtain updates.

I have to say I now disagree with this theory. I just tried updating again. my working computers are getting new updates for defender regularly. On a working computer if you do a manual check for updates and there aren't any win update informs you. on the non working one it just keeps CHECKING. It never ends. Win update is corrupted somehow on my ISO and I can't figure it out. This is no way to create an updated slipstreamed ISO. I am giving people a corrupted win 7 setup from the get go. somehow when all these updates get integrated something is amiss....very frustrating..

regards...

Edited by pennsylvaniaron
Link to comment
Share on other sites

37 minutes ago, pennsylvaniaron said:

Thiersee plz excuse my newbieness on this subject but what is the "convenience rollups?". In addition are you saying when using WUD I should download EITHER the classics or the CONVENIENCE or download BOTH and incorporate them into my last months win 7_64 ISO?

regards...

@pennsylvaniaron

No, no, you misunderstood me (oder, better, I explained it to simply ;))

Convenience-Rollup is a package (KB3125574) released by MS on May 2016, containing almost all patches (but not all!) since release of SP1 though April 2016.

This package has some prerequisite to observe.

You can build an actual ISO in the way used up to May 2016 (WUD, Classic): you need category 2 (Common) & 3 (Classic)

OR

you can build it with this new package (Convenience Rollup): you need category 1 (Convenience Rollup Pack Update) & 2 (Common).

This is the "basis"; if you need some other features (RDP 8.0 or 8.1, additional patches, IE11 and so on) it's up to you: for this purpose you can use the other categories of WUD.

BTW, I don't know how do you build your ISO, but I don't think WUD-ULs are the right choice to implement some patches in your last month ISO.

Regards, Thiersee

Edited by Thiersee
Link to comment
Share on other sites

@Thiersee

EDIT : same observation for me. The only ones I had after deep-clean of my Convenience Rollup VM are usual KB2685811/13 and KB253411 (present in ISO).

@pennsylvaniaron

All my VM are OK with WU this evening. I don't understand why. I'm not sure WU is corrupted, but it seems regarding to abbodi1406 comments that the 3 old WUclient cabs are needed even if they are superseeded by KB3138612 (classic integration) and Convenience Rollup (newest WU Client, but KB3138612 still requested !). I putted them back in next UL release.

Concerning Convenience Rollup, it's like a SP containing most important updates since SP1. Integrating it instead of classic method saves time, saves spaces in your final installation (1.5 Go). But some updates are still required, that's why I create the common Updates category. I'll update first post when I'll upload the new ULs.

Edited by rhahgleuhargh
Link to comment
Share on other sites

thiersee you have been very helpful. I didn't know anything about this convenience rollup. now I understand much more. so it does seem like its almost a sp2 for win 7? what I am doing as I write is using lego's april iso which I ASSume has the convenience rollup. not sure how he made it. I am not introducing anything update wise from may or june. its almost finished. it has my silent installs and some minor component removals, net 4.6, and some files I use placed on the desktop for convenience. I will do an sfc and winupdate and report back in a few minutes.

regards...

Link to comment
Share on other sites

@rhahgleuhargh

Quote

EDIT : same observation for me. The only ones I had after deep-clean of my Convenience Rollup VM are usual KB2685811/13 and KB253411 (present in ISO).

I had KB2685811/813 on a try a couple of days ago: normally I install them later, but I forgot them in the list during integration, so I installed them twice....

KB2534111 was the only difference between W7SP1 RTM and W7SP1_u (Media Refresh); so if somebody uses the old ISO without media-refresh should not get it uninstalled.

And indeed, deep clean depends on, how the system has been originally installed, classic- or rollup-way.

Link to comment
Share on other sites

I just ran sfc on this april iso and it passes. I also ran win update on my main computer (using it to write this) and it took a little longer than usual but found 12 new updates which have to be the newest just released. The april iso using manual winupdate has the red X saying it has never been checked or run. Its still checking some 20 minutes or so...

if my computer found 12 new updates then it cant be Microsoft servers. I believe lego is making a new iso. maybe that will solve the problem....

regards...

Link to comment
Share on other sites

@pennsylvaniaron,

The problems with WU/MU, especially with "older" OS such as Windows 7, have been going on for quite awhile and have been getting worse. My Windows 7 Ultimate x64 system was completely up to date with WU/MU on Monday, and would pass SFC with no errors.  Running WU/MU today took well over an hour to "scan" before it came up with the list of available updates. Then it took well over another hour to install those same updates.  In both cases it was just sitting there doing nothing most of the time. After restarting I double checked and it still passes SFC.  I then let WU/MU rescan and this time it only took about 5 minutes to come back with info that there was a Security Essentials update and it took less than 5 min to install it, and less than 5 min for another rescan to confirm that WU/MU was now happy and completely up to date again. The situation of WU/MU taking an extremely long time for the initial scan and for the initial install at both the time of the initial Windows 7 OS install and then again after every patch Tuesday is now expected behavior for many people. Which updates that need to be installed first to "fix" this situation  seem to vary and don't consistently work for everyone.  After the first successful update session each month succeeding runs are better, but the first time is a real bear.

If anyone can come up with a reliable solution that works for everyone it would really be appreciated.

Cheers and Regards

Link to comment
Share on other sites

KB3145739 was installed on my system 10 days ago, when I last reinstalled my OS, and is still in place.  Having it didn't help my initial scan and install today after patch Tuesday.  Unless you're saying that I should have uninstalled it and reinstalled it before today's updates?  Or maybe that I should be happy with my experiences today because they would have been even worse if I didn't have KB 3145739 installed? LOL

Glad to see you around Liam!

[OT]  @Liam, if I could please ask a favor.  At this point anyone that installs Windows 7 probably wants to keep Windows 7 and doesn't want to upgrade downgrade to Windows 10.  So the next time you make your updated ISO could you please NOT include the following KB's: KB971033, KB2952664, KB3021917, KB3035583, KB3068708, KB3080149, and KB3123862.  Assuming that an install of your ISO passes SFC and can still be updated by the user with those updates or any other updates that come up in the future, then I think that your ISO would appeal to the widest audience possible. Thanks for considering my request. [/OT]

Cheers and Regards

Link to comment
Share on other sites

  • mooms pinned this topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...