I’m a little confused. I just updated a Windows 7 pro installation with UpdatePack7R2-21.3.10. Prior to the update Windows had been patched through 11-9-2019 with all security updates with the exception of those containing telemetry, and GWX. The update completed, installing the following: KB917607----------[Windows help patch 2016] KB2592687--------[Remote Desktop Protocol 2012] KB2818604--------[Microcode Update 2013] KB2834140-v2---[Stop Error 2013] KB3102429-v2---[Azerbaijani currency Symbols 2016] KB3138612--------[Update support for Windows 10 updates 2016] KB3161102--------[Windows Journal component removal 2016] KB3179573--------[August update roll-up 2016] KB3184143--------[Remove Windows 10 free upgrade offer 2016] KB4474419-v3---[SHA-2 code signing support update 2019] KB4490628--------[Servicing stack update for Windows 7 2019] KB4592510--------[Servicing stack update for Windows 7 2020] KB3125574-v4---[Convenience roll-up 2016] KB4575903--------[Extended Security Updates (ESU) Licensing Preparation 2020] KB4578952--------[Security and Quality Roll-up for .NET Framework 3.5.1 2020] KB5000841--------[Monthly Roll-up 2021] What I don’t quite understand is why there are so many older (2012, 2016) updates versus those from 2020 and 2021. Are these prerequisites to get the newer Extended Service Updates, and if so were there really only three updates in that period or does the monthly roll-up (KB5000841) contain all the other 2020 patches? Thanks. (Also my apologies if this was covered in one of the other 190 some pages)
MS started CUs for Windows 7 at the end of 2016, IIRC. Original plan was to eventually include all older patches as well. To my knowledge, this never happened. So, there might still be some patches installed from that "before" era (aka the glory days of free update control).
Because Windows 7 was very different from Windows 10: Most updates/hotfixes were more or less individual, so the ones you see currently included in the updatepack are most likely not superseded. The convenience rollup was included in the updatepack much later than its release date because of numerous issues with the rollup itself, but now that most(if not all) of them are resolved, this rollup replaces a ton of updates inside the updatepack, so instead of integrating ~150 updates you only integrate ~55. The resulting iso size(assuming a single edition inside the install.wim) is still roughly the same as before the rollup, it's just the integration process that goes much faster(obviously, after every monthly update the images may or may not become bigger). At present, offline updating a windows 7 sp1 iso is a fairly streamlined process: 1. Download a clean win 7 sp1 iso(media refresh from 2011 highly recommended) 2. Download the latest updatepack, the directx, .net framework 4.8 and visual c++ addons 3. Put everything you downloaded in one folder 3. Drag&drop your win 7 sp1 iso onto the updatepack 4. Fix up a coffee or watch some youtubez while the updatepack does the job for you You could also forget about using Windows Updates, just download the latest updatepack and new addons(.net/visual c, if there are new versions released), put them in one folder, run the updatepack.
It is convenient, using @Enthousiast's tool, to update Windows 7, as long as you don't deviate from the standard images. Currently working on Windows 7 E and it's an adventure.
Thank you both for the information. I appreciate all the hard work that went in to making the 7R2 Update Pack and that the Windows telemetry has been removed, not to mention all the possible customizations. Now I have to decide whether the enhanced security provided by the latest updates outweighs the fact that (to my mind anyway) several other less than desirable updates come along for the ride.
@ryegrass I'm pretty sure the comrade has suppressed whatever update you're referring to in registry or other tweak.
Most of my hesitancy about the update pack stems from not wanting to mess-up my extremely stable existing system. After I updated, a couple of things caught my eye, first my fans were running somewhat faster and my temperatures were about 3˚ to 5˚ higher on the same tasks. The culprit turned out to be the 2013 microcode update KB2818604 which according to the associated Microsoft support article shouldn’t apply to my (then non- existent) Ryzen 3900x at all. Uninstalling the update fixed this. The other thing which concerned me are the 3 leftover GWX manifests in the SysWOW64 folder. Since I spent a fair amount of time and effort in the mid to late 2010’s preventing any traces of the Get Windows 10 program from infesting my system, I’m probably over reacting to what are more than likely ‘safe’ and dormant leftovers. For the time being, I’ve been switching back and forth between disk images of my original configuration and the patched version till I make a final decision as to which to keep going forward.
My fridge tends to warm up too when i update win7 using the updates pack. Just use /FixOFF and the spectre etctec... stuff won't even be enabled. and microcode updates for intel won't do anything on amd systems. The program finished 5 years ago (upgrades still give free hwid). Once the old updates are in, there will be only 2 updates a month. Afaik, simplix uses the same telemetry blocking method as @abbodi1406 does.
The KB2818604 update I referenced actually is for AMD CPU's but in theory should only affect Series C, E, G, and Z processors. The changes I noticed persisted over two days and disappeared after the update was uninstalled (weird I know). As to the GWX program being finished, I simply don't trust Microsoft anymore not to try and slip some other nefarious items into their updates, so I do appreciate the vigilance everyone involved in the Simplex Pack project has shown to try and prevent this.
When CEIP is off, Windows 7 will never ever send anything, even with all telemetry components active this does not include Edge Chromium, it has its own agenda
Updatepack 21.3.23 log: https://forums.mydigitallife.net/th...l-wim-esd-creation.79421/page-60#post-1651579