Thanks for pointing this out, I had been installing them manually this year. But now that I installed "standalone WU ESU Patcher" I am getting them thru WU again. Your are right it isn't easy to keep up with the diff versions of the patcher. I think the newest version of the patcher should be posted above the old patcher, so that it is top prominent and easy to find.
Moin @ All! My April 2024 ESUpdate experience for Windows 7 Pro SP1 x64 systems: "Licensing method": KB4528069 & "new" BypassESU-v12 "Installing method": Manual download and installation via Microsoft®Update-Catalog KB5036632 (Security Only Update for .NET Framework 4.8) -> succesfully installed KB5036634 (Security Only Update for .NET Framework 3.5.1) -> succesfully installed KB5036922 (Security Only Quality Update for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed The following additional updates were offered by the Microsoft servers via the Windows Update Search and were also successfully installed: Security Intelligence-Update for Microsoft Security Essentials and .NET 6.0.29 Security Update for x64 Client (KB5037336). @ abbodi1406: Thx for your support! Great job!
I have been using this tool to keep my two Win7 machines updated for several years without a hitch. I haven't updated one machine since December and went to do the updates today. In addition to the 4-24 quality rollup KB5036967, and .Net update KB5037038, I am also being offered KB4041083 (2017-09 .Net update) and KB4049016 (2017-11 .Net update). These are basically ancient. I searched the thread and no one else has mentioned getting these updates recently. How would you recommend handling these two? Install them like other .Net updates? Hide them? Sacrifice a pigeon to the update gods? Thanks
Do you have this registry value? it's still required for WU metadata Code: reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat /v cadca5fe-87d3-4b96-b7fb-a231484277cc /t REG_DWORD /d 0 /f
Thanks for the reply. Yes, that value is still present. Would you agree about hiding the 2 old updates? Thanks
I have 4049016 installed but not 4041083. The 4049016 would be the most recent of the two & probably replaced the older. I don't think it would hurt to install them now (oldest first or let WU do it) or even skip them using only the most recent update; 5037038. If you are successful with the rollup & the most recent .NET update then older should not matter. Following @abbodi1406 's advice will always be wise.
Win 7 Home Premium on an Acer Laptop x86 & x64; SUCCESS once again. Used WU for Security rollup & manual download/install for .NET Framework 3.5.1 & 4.8 ================================================================= 2024/04/09: My #4 Bypass is always "ON"; no issues... Installed Security rollup w/WU Installed .NET Framework w/Win Catalog; manually; successful 3.5.1 & 4.8 Added: Security Monthly Quality Rollup 4 Windows Server 2008 R2 4 x64-based Systems (KB5036967) 5036967 Rollup; downloaded; Installed w/WU successfully Security & Quality Rollup 4.NET Framework 3.5.1, 4.8 Windows Server 2008 R2 4 x64-based Systems (KB5037038) 5036626 / NET35; downloaded; Installed manually successfully 5036615 / NET48; downloaded; Installed manually successfully Removed/Superseded automatically: 5035888 5033899 5034615 Superseded automatically: WithoutKB3125574: 2719857 2905407
I know it is quite early for this question, but @ abbodi1406, are there any plans for a project about Windows 10 ESU in the future?
Spoiler Hello, I have been able to successfully install all updates since October 2023. But there are problems with the April 2024 update. Do you have any suggestions for solutions for this? I always get error code 80004005 I've already tried a few suggested solutions for this error code, but I kept getting this error. Thanks I found a solution: Grub as a problem in dual boot environments: There is a note in an external forum thread that the access error occurred on a DualBoot system with Linux and Grub Loader. After Grub was shut down, the update could be installed. In this MS Answers forum post, the user posted an excerpt from Event Viewer. Package KB3185330 failed to be changed to the Installed state. Status: 0x80004005. Something is blocking the installer's ability to set the update's status to "installed" status. There, too, a multiboot environment with a Grub boot loader turned out to be the cause. I removed all hard drives and only booted WIN7 without GRUB on the Ubuntu partition. The update installed without any problems.
Run Disk Cleanup and select "Windows Update Cleanup" yes it's safe, as long you installed ESU suppressor