Yes, but should he? That DotNET Bypass is troublesome, and most people regard AIO as "Set it and forget it". Maybe it should be integrated to enable for 24h, and then being automatically reverted by a task. So, it cannot cause permanent trouble, while still providing enough time to conveniently install .NET CU or Seconly.
For the latest .net update v7 worked fine, so it could be very possible for him to put v7 and v8 together to have it AIO again.
I'm not sure as @Carlos Detweiller said, .NET Bypass can be problematic for some maybe it's best to keep it separated
Best strategy IMHO is to enable the bypasses just prior to the WU, and then disable afterwards to avoid problems with MSIEXEC - very easy for v7 because everything is nicely integrated, but a bit confusing now with v7 and v8
A few Qs: 1. Is ESU Bypass v8 backwards compatible and allows installing all ESUs, even the old ones? (I'm on SecOnly) 2. The Server 2008 one is still at v5. It isn't affected, right?
From WU I succeeded with the .net update and the KB4576628. Only for KB4577051 I am then asked to restart the computer because a service is already running and then it indicates "failed to configure windows updates" when the computer restarts. i download the v8 but it's the same. Someone can help me please ?
Try this: GiF + info: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-209#post-1617242
Dear @abbodi1406, @IMI Kurwica & @Enthousiast, thank You, thank you all who made this Win 7 ESU show (still) possible! Astonish and monumental work, especially with the fact, that so many users still did not migrate onto Microsoft Win 10 OS... I have also one humble question here... Till now, till the whole new "BypassESU-v8-AIO.7z" come in the game before just the couple of days ago here..., the older "BypassESU-v7-AIO.7z" has an ability for temporary installation of the "Install .NET 4 ESU Bypass", which was very important of its own features, that we all install just temporary (very important), only to be able to (+ only till we successfully), install the one specifically and individual Windows Update component all here: the "Security and Quality Rollup for .NET Framework xy for Windows 7 for x64", or its similar update name... However, the whole new "BypassESU-v8-AIO.7z" by its design now, for some reason and from now on, does not contain anymore the "Install .NET 4 ESU Bypass" integration option feature... So, to be able to still install, now or in the future, the "Security and Quality Rollup for .NET Framework xy for Windows 7 for x64", or its similar update name, we have still 2-3 options here for that, if I am correct: a) Hold also in our reserve, an older "BypassESU-v7-AIO.7z", and temporary from here, only install the "Install .NET 4 ESU Bypass" feature when we really need it it; or b) from now on, just disregard completely that the older "BypassESU-v7-AIO.7z" solution ever existed, and for the Microsoft .NET Framework updates only, just and also temporary install, the "dotNetFx4_ESU_Bypass", which is totally individual solution all here for that particular Microsoft .NET Framework updates purpose; or c) in the near future, the whole new "BypassESU-v9-AIO.7z" will also have again the big comeback integration, of its own "Install .NET 4 ESU Bypass" feature???!!! Thank you for clarifying all this in advance for people here and best regards to you, the astonish three guys here to make all this possible with Win 7 ESU project, and to all the rest of the folks here on this great forum!
v7 complimented by v8 contains all you desire (running v7 should offer to remove the .net ESU bypass). This will have the same options as v7 has but now should be working for both, .net 4 ESU updates + non dotnet ESU updates.
Thank you for your most kindest answer! Also, I apologize, I obvious did not notice in the meantime, that @abbodi1406 already said that he will add the "Install .NET 4 ESU Bypass" feature back again into the whole new "BypassESU-v8-AIO.7z".
Finally I uninstall the WU ESU patcher then reinstall with version V8 then I download the update manually and the update configuration after reboot worked. If I understood correctly another V8 version will come soon ?