Maybe they are doing the same as with win 10, ssu inside cu: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-524#post-1617220
Got it, finally. I just wasn't being patient enough, it took about 10 minutes to get to the second stage but kb4577051 installed successfully. Thanks again to all those working on this project and helping us to keep using Windows 7.
I'm on SecOnly (Group B), and also got no SSU. It might come at a later time, or, if integrated, it has to be in the SecOnly update, too.
I would like to add my thanks to the people who have been working so hard to make the Bypass work and provide support to others (like me) who need help to make things work right. You people are GREAT!
Moin @ All! My September 2020 ESUpdate experience for Windows 7 Pro SP1 x64 systems: KB4576490 (Security Only Update for .NET Framework 4.8) -> succesfully installed with the help of the .NET 4 ESU Bypass solution from BypassESU-v7-AIO KB4577010 (Cumulative Security Update for IE 11 for Windows 7 x64) -> succesfully installed with the help of the standalone installer script W7ESUI_0.2 KB4577053 (Security Only Quality Update for Windows 7 x64) -> succesfully installed with the help of the standalone installer script W7ESUI_0.2 (Original "Licensing method": KB4528069 & BypassESU-v4.7z) @ abbodi1406, Enthousiast, Pawulon & Co: Thx for your support! Great job! Edit: Tested the new ByassESU-v8-AIO with a Windows 7 Home Premium SP1 x64 system: KB4576490 (Security Only Update for .NET Framework 4.8) -> succesfully installed with the help of the .NET 4 ESU Bypass solution from BypassESU-v7-AIO KB4577010 (Cumulative Security Update for IE 11 for Windows 7 x64) -> succesfully installed KB4577053 (Security Only Quality Update for Windows 7 x64) -> succesfully installed "Licensing method": KB4528069 & BypassESU-v8-AIO.7z @ abbodi1406: Thx for your magnificent timely support! Great job!
ESU component version is now higher than the suppressor KB4528069 W7ESUI manipulate registry values to make the OS think that ESU component contained within is already installed they probably gave up the new SSU each month method, since it did not stop BypassESU Latest mandatory SSU was KB4555449 (May 2020) it can be used to install all updates from May to September
Uninstall the DotNET part of ESU Bypass v7 before removing it. v8 does not contain it, so, no way to uninstall here.
The .net part of v7 takes care of the .net cu, the esu part of v8 takes care of the other cu or separate updates.
And this is exactly why I kept the old V5 of ESU bypass. It works the exact same way, and can actually be REMOVED! After years of hearing strange stories, I'm beginning to realize the reasons to dread updates; newer stuff is more difficult to deal with. I keep the few versions that do work.
So does that mean that the separate .NET ESU patch can still work side-by-side with the new ESU bypass v8? More importantly, will it be necessary to use the separate .NET patch since ESU v8 "does not contain it?"