All of them are content-replaced but it's still prerequisite for Windows Update ESU detection, per category unless Update Cleanup remove it?
It is 6.1.7601.24558 vs. Rollup 6.1.7601.24559 actual files may still the same version, but it's CBS-superseded
You're right and this is a reason to remove KB4575903. If you know of other CBS-superseded updates, please indicate.
These are replaced by KB3125574-v4 (but most of them are needed to silence Windows Update): Code: KB2547666 KB2667402-v2 KB2698365 KB2732059-v5 KB2773072 KB2834140-v2 KB2862330-v2 KB2894844 KB2919469 KB2970228 KB2984972 KB3004375-v3 KB3006137
Thanks, I'll remove them from the updatepack. Previously, I satisfied the requirements of Windows Update (which is why I did not create a tool to find such updates), but now this no longer makes sense, especially since online updates may be removed over time.
My humble post triggered a ping pong between titans... I am honored Abbodi1406 you are correct in your assumption that I was using the ws2008r2 category. I should have thought of it. Maybe the feb cumulative was just re-triggered after I installed manually KB5016892. Simplix I don't know if this is helpful but in my script for vista I had to remove the equivalent of KB4575903 (kb4575904) because I would get datastore error with it present.Which meant that I would have to include abbodi1406's datastore fix at the time. The only 'downside' that I got by removing it was the 2020-01 SMQR being offered again regardless of being superseded. On seven might be a good idea to keep in the pack KB4575903 and KB5016892 for the purpose of more sane metadata at the cost of ~8MB added size. I wouldn't like to install manually a cumulative update for example due to telemetry etc and just hiding it would only trigger the previous update to show up while this wouldn't be a problem with a minor update. Of course I could disable WU all together but I find it handy due to defender definitions and satisfactory to bit the system by still getting updates in 2024 even if I don't install them through WU. Thank you both for your answers!!
I am using WU for only two reasons. One being the defender definitions and second being that I love the faces of my friends every time that I have updates on my "old unsupported" system. I never install anything other than definitions directly from WU though. WU serves only as a reminder that that I need to go and check simplix's pack I don't expect anything good coming from M$ anyway nowdays. Also I do have windows 10 as dual boot but I can't use it as main OS due to constant distractions. Normally it takes me an insane amount of time to customize my OS the way I want and I would like it to stay that way once I am done with it
I suggest adding an option to hide the superseded (an unwanted) windows updates after running simplix update pack, to keep windows update happy and still allow to use it for drivers and other MS stuff. Something like /hideunwanted
A suggestion to update Edge for Windows 7 via update it updates Internet Explorer for Edge, just a suggestion. @abbodi1406 @Enthousiast
@Enthousiast why wmf 5.1 aka powershell 5.1 are not integrated ? @abbodi1406 possible to create addon ?
It's already an update package but if you integrate it without .NET 4.5+, setup will fail you can try to integrate manually after .NET 4.8 addon
In this case, it is enough to simply add an update through UpdatePack7R2Wim.cmd using Dism. UpdatePack7R2Wim.cmd executed after updates are integrated and before the index is unmounted.