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.
I always have done that for years, is more reliable. @abbodi1406 Do you know if M$ will soon invent a blocking method, or will give some years more for Win7? Thank you for your great work.
If I am correct, here is what I know: .Net frameworks updated independently, i.e. if you update 3.5.1 it doesn't mean that 4.7.1 for example would get updated too, they are independent entities More over you don't have to have every .net framework installed on your machine You only install whatever .net framework needed by you to run a certain program There are tools available online that tells you which .net frameworks are installed in your system But there is one last point , windows 7 comes with .net frameworks : 1.0, 1.1, 2.0, 3.0 and 3.5 preloaded out of box, that is when you finish installing windows 7 you don't have to install these .net frameworks So your mentioned rollup for .net framework tries to update "whatever" .net framework it finds on your PC, if it finds only one of them it will update it, if it finds 2 it will update both .. & so on
On 15.02., I used BypassESU-v8-AIO to manually update KB5022872 without any problems. And for .NET Framework KB5022731, I followed the dotNetFx4_ESU_Installer_u instructions, loaded the ndpKB5022509.exe file and installed. But it doesn't show up in the update history , only in installed updates! Now I don't know if it installed correctly. I looked at the 2022-12 .NET Framework update KB5021091, in the update history it shows as KB5021091, but in the installed updates it shows as KB5020879.
What does this line in the wsus proxy readme mean? ============ if you are using external tool, make sure to select "Windows Server Update Services" for Update service ============ I feel like I followed the instructions - Win7 Home premium 64 - updated via v11 thru last month - V12 is installed and running including .net bypass (should this be running along w/proxy?) Ran WU first and installed the malicious ... Ran db reset Ran wsus proxy and unblock php Ran WU (no important updates) Obviously I'm doing something wrong, but not sure what Thanks