I got one that showed up from 2017. Update for Windows 7 for x64-based Systems (KB3125574). You should be good since you uninstalled the .net 4.x part of the Bypass. It tends to interfere with MSInstaller.
I have Windows 7 Ultimate with all ESU updates as of January 2023, installed with previous BypassESU. Checked all of the Recommended Updates for Live OS installation. The only ones that I don't have are: KB4575903: ESU Licensing Preparation Package / to receive updates up to 2023-01 KB5016892: ESU Licensing Preparation Package / to receive updates after 2023-01 for Server 2008 R2 only Installed BypassESU-v12. Ran LiveOS-Setup.cmd as administrator. Everything loaded with no errors. Choose option 1. Ran Windows Update. The only updates I am offered at this time are: KB4567409 a Microsoft Edge Update for Windows 7 x64 KB3118401 an Update for Windows 7 X64 What did I do wrong not to get the 02-2023 updates? Thanks for any and all help in advance
Let me try to rephrase: From now on WU will not offer you any new updates anymore, when you are running regular win 7. From now on you need to download the updates from catalog and install them manually (or use simplix update packs sorry @abbodi1406 )
I'm confused by everyone saying to install both Dot NET 3.5.1 and 4.7 or 4.8 updates. In my case I have had 4.7.2 installed for a loong time. And each time I ran Windows Update it has installed an update called: "Security and Quality Rollup for .NET Framework 3.5.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 SP1 and Windows Server 2008 R2 SP1" Was this then actually two updates being installed on my system? (Both 3.5.1 and 4.7.2 as separate updates?)
Yes, it's expected when you manually install 2023-02 Monthly Rollup KB5022872, last official 2023-01 Monthly Rollup KB5022338 becomes superseded however, WU has metadata only for 2023-01 Rollup, when it see it become superseded, it offer old updates that were replaced by it solution: none workaround: hide or ignore or install the old updates, they do not have any effect
Thank you! I see it in "Installed Updates" under "Programs and Features": Update for Microsoft Windows (KB5020861)
All working here with BypassESU-v12. The question is if it is worth going through all this trouble for keeping alive a largely obsolete OS. For me this is only for testing and hobby, but I really don't see a purpose for any serious use of Windows 7 in year 2023.
@abbodi1406 It seems the ESU Suppressor doesn't work when activated Off-line (with Wim-Integration.cmd) with updates newer than 2023-01-10 (KB5010798, KB5022872, KB5022523). I use the last version (BypassESU-v12_r). When these updates are integrated, there is an error 0x00003712 = "The component store has been corrupted". When the ISO image (in which the ESU Suppressor has been off-line activated) is installed, to get a live OS, the ESU Suppressor doesn't work either. The same error occurs when the updates are installed on-line (msu). Then If the ESU Suppressor is removed and reinstalled (on-line), the ESU Suppressor works again. The updates can be installed successfully.
What's obsolete about it though? Nearly every major program still runs on it, except for a few like Chrome/Edge, which I rarely use anyway but even then there's a Kernelex project to keep those browsers going. Firefox is up to date so with full Microsoft support Win 7 is quite usable for the foreseeable future.
OK, Problem Solved! I decided to see if I could figure out once and for all what was causing the recursive error messages and failures on my system when trying to install the February .Net 4.8 rollup with ESU Bypass v12. To that end, I made an image of my C Drive, and proceeded to uninstall each of my programs one by one while testing the .Net installation after each. Finally, after eliminating to most obvious candidates, I found that PC Tools Firewall Plus 7 was the culprit. By uninstalling it, making use of ESU Bypass to install the .Net rollup, and then reinstalling the program everything worked properly. The same procedure was then used on my restored C Drive image, resulting in a properly updated/ working system.
what about buying new hardware because your already perfectly working hardware is not compatible with newer OS ?
I wonder, why does a .NET Framework 4.8 also need the updates for .NET 3.5.1? Backward compatibility reasons? So far, the "Rollup for .NET Framework 3.5.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8" has always been downloaded to me via WU and the updates for 4.8 and 3.5.1 have been installed. Updates for .net 4.7 were not installed, only one older one (KB4019990...which file is included with every rollup!?) is installed since 2017 - but at that time maybe an older version was (also) installed. I will now continue to manually install the updates for 3.5.1 - but as I said, I would be interested in why the latter is required.