Another successful installation (June 2023): kb5027140 - Net 3.5.1 kb5027129 - Net 4.8 kb5027275 - quality update
Just curious, are you using Bypass-v9 or Bypass-v12? I couldn't get kb5027129 to install at first but after switching from v9 to v12 it did. Interestingly, kb5027140 did install with v9 since I had went with that before kb5027129. So try them both and see if that makes a difference.
This is old news. Refer to Feb 14th and March 9th: When (good) people update their (good) software, it is usually for a good reason. Note the emphasis on "good". Yes, this in direct contrast to 99.9% of the modern software world, but everyone who comes to this thread should already be redpilled enough to know where to draw the line between "updates" for artificial job security (e.g. Chrome) and real updates that fix real problems. abbodi and the other people in this thread are the good guys. You should be taking the updates for the software they make. You should not be averse to updating the bypass tools. That makes zero sense because of the cat and mouse game we are stuck in with Microsoft. Updates to the bypass tools will likely continue to be necessary as M$ adds more obstacles. You really truly should try to use the latest version at least once before giving up and posting here. abbodi didn't create v12 just because he likes the number 12 more than 11. There are manhours of real labor with real effects behind the change from v11 to v12, and even more so from v9 to v12. Less of these redundant posts would help mitigate the vicious cycle of this thread getting way too bloated and dissuading people from actually reading it to get up-to-date before they ask a question that was answered months ago.
As alway, my most sincere thanks to the developers of the Bypass effort. Last night (13 June) I was able to manually install KB5027275 just fine. However, I was unable to install the .NET Framework update (KB5027129). Although I had successfully install all the preceding NET Framework updates since this thing started, in this case, I always got "Installation failed with error code: (0x80070643), " 'Fatal error during installation'." Then this morning, I went back to p. 1 of this Forum and found the info about the dotNetFx4 ESU Installer v3. I used it and was able to instal KB5027110, which I had downloaded after KB5027129 didn't work. And now - just for the heck of it - I retried KB5027129, and lo and behold, it worked, too! I then went back and uninstalled KB5027110, and now everything seems to be the way I want it. Again, my most sincere and profound thanks to the people who have so generously devoted their time, effort, and talent to making the Bypass happen.
This was a well thought out post but the point of mine was since the OP was having trouble installing kb5027140 then it might be worth trying v9 since it installed for me using that version. But please carry on...
Moin @ All! My June 2023 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 KB5027129 (Security and Quality Rollup for .NET Framework 4.8) -> succesfully installed KB5027140 (Security and Quality Rollup for .NET Framework 3.5.1) -> succesfully installed KB5027256 (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: KB5027797 (.NET 6.0.15 Security Update for x64 Client) & Security Intelligence-Update for Microsoft Security Essentials. @ abbodi1406: Thx for your support! Great job!
Thanks for your post. I had the same problem with trying to manually install KB5027129. I obtained and made use of that installer script and was able to successfully install that NET Framework 4.8 update.
I have a PC running Win7 x86 and one running X64. I didn't realize that the rollups had stopped installing with v11. Installed v12 and then the standalone patcher. Both PCs had the standalone open a command window and then it closed with nothing happening. On the x86 I uninstalled v12, rebooted, reinstalled, rebooted and then the standalone ran perfectly and I was able to have things running fine. I tried the same thing on the x64 PC and I just cannot get the standalone patcher to run. Any suggestions? Edit: While Windows update wasn't showing any updates available, I was manually able to install updates for .NET framework 4.8 and the 2023-06 Security quality monthly rollup. I wouldn't have thought that would work. (I'm also kind of surprised I didn't need to also manually install rollups for 2023-02 through 2023-05 first.)
A little ambiguity: What the .NET Framework 4.8 update kb5027110 is all about? Is this an additional update to kb5027129? I have only .NET Framework 4.8 installed. Is it enough to install only kb5027110, if that is possible, or must it be both? I see vonmir wrote in #7461 he had problems with the larger kb5027129 update for Framework and later he uninstalled the smaller kb5027110 update. Why? I'm a little unsure this time. I always install manually and so far everything went smoothly with it. Thanks! edit: KB numbers corrected, sorry...
KB5027129 is rollup, you only need that with base .NET 4.8 KB5027110 is security only update, you need all or most previous .NET 4.8 security only updates use either routes, not both
Ok, thanks! Is it the same with the last February .NET 4.8 updates kb5022509 (43.2MB) and kb5023823 (9.9MB)? I had both installed at the time. Then I would probably have made a mistake, but one could learn from that...
Clarification for dumb me, please:: I have been installing rollups both for .NET updates and Security Monthly Rollups for Windows, need I continue installing the rollups or can I use the Security Only updates? Thanks
Great work, I installed the 6 recommended updates, I tried 12u and I did get updates up to 2022-10 installed. Thank You! I'm getting very high sppsvc.exe CPU usage, resource manager shows 24.64% average CPU usage constantly. Killing sppsvc.exe only makes it auto-restart and it keeps hogging up CPU endlessly. There are no more updates for me and sppsvc keeps using 25% CPU even after being left for a few hours. Win 7 Professional 64 bit Is that a known bug? Can I remove WU ESU Patcher and .NET 4 ESU Bypass with the tool at this point?