Thanks to Nirsoft's WinUpdatesView v1.17, I was able to lookup what SSU I have. Turns out you're right. I'm currently using SSU March 2022 (KB5011649).
I wonder if there is a log file somewhere in all those logs Windows keeps that might give me more information on why the May monthly rollup always fails.
I had a look, but nothing really stands out to me. Even searching for the word "failed" didn't help me much. I just don't have enough knowledge to piece together the meanings of all those statements. I've attached the log file in case someone knows what it means. The last 2 things I tried were installing KB5008244 and KB3108664, and both said they weren't applicable to my computer.
There are a lot of reasons for the renewal error (from stupid: antivirus, UAC, OS "tweaks", “curve” activator and etc., to RAM errors, damaged HDD (chkdsk), virus and random events) and even more corrective options. Very lucky if simple actions help: Removing the SoftwareDistribution folder Turning off antivirus and removal of a "hung" package (dism /online /get-packages), all updates in waiting (not installed) DISM.exe /Online /Remove-Package /PackageName:*** /quiet /norestart Cleanmgr sfc /scannow DISM /Online /Cleanup-Image /ScanHealth Install the update manually For example, in the posted log (CBS.log) there are a lot of errors (from "Windows could not search for new updates" to fatal errors), except for CBS, there are logs: Checksur.log, Dism.log, Windowsupdate.log and etc .. There are sites that describe the analysis of the logs and "treatment" options, in the same place (if you are lucky to find a specialist) they can give direct advice (what files to delete, replace, reinstall). You must have a “donor” (may be required) to take files from WinSXS, Servicing \ Packages and the registry bushes. All this is very long and tedious to study. For not a specialist, the simplest is to return to the point when everything worked or ... reinstall the OS. … Analysis of logs and "treatment" is not the subject of this thread.
Code: Microsoft-Windows-BootEnvironment-Core-BootManager-EFI "C:\Windows\bfsvc.exe" C:\Windows\boot /nofonts Process exit code 123 (0x0000007b) resulted in success? FALSE before 2022-05 Rollup, last time this component updated was in 2019-09 are you using any "workarounds" to run Win7 UEFI? do you know how to boot into WinPE using standard or recovery ISO? you could try to add the failed update manually offline using dism.exe tool, then update boot files manually offline too example: Code: dism /image:C: /add-package /packagepath:Windows6.1-KB5014012-x64.msu bcdboot C:\Windows /s C:
I'm running a dual boot system. Linux Mint and Windows 7. I've got Windows on a SSD, Linux on a second SSD, and my data on an NTFS partition on a 3rd spinning drive. I installed the 2nd SSD and put Linux on it much later than the original system was setup. I suspect the problem may have something to do with the activator I used on Windows because of the error code in the History program WoodWoff2PAEA suggested. The activator I used was v2.2.1 of Windows 7 Loader that I believe I got from this forum. I do not have a UEFI system. It is a BIOS system with no "workarounds" other than the activator. I used all defaults on the activator. It's been running for years without any changes being required. I've used the same activator on several VM's and they take the May update fine. I know how to boot into WinPE using a recovery or install image, but I would be copying and pasting the dism command, and guessing at manually configuring the boot files.
I am going to comment as an anecdote what happens to me on a laptop where I have Windows 7 Pro with ESU installed. Since I started using ESU to get the monthly updates, I have never had to manually activate the corresponding option with Administrator permission to get the .NET Framework updates. This option has ALWAYS been disabled in each and every one of the versions of ESU that have been published on this website. However, and this is the most curious thing, Windows Update offers me all the updates monthly, including the .NET ones, without me ever having to turn the ESU option on or off and install them without problems. As a curiosity, it is an old laptop that uses the 32-bit version of Windows 7 Pro, with a very slow processor and only 2 GB of RAM that I use for the same purpose as a Rasperry PI, but with a screen. Not that I care at all, but I'm curious because on the other computers I have, if I don't manually turn on the ESU option to get updates for the .NET Framework, I can't install them. I don't know if anyone else has experienced this same situation as me, but I'm sure @abbodi1406 or @Enthousiast could offer some explanation.
@JaimeSH "[3] WU ESU Patcher" allow to recieve all ESU updates including .NET updates "[2] ESU Suppressor" allow to install .NET 3.5 updates, in addition to Monthly Rollup "[7] .NET 4 ESU Bypass" allow to install .NET 4.x updates if you did not install any .NET 4.x Framework, then option 7 is not needed or have effect
Well, that is the most striking curiosity: I'm precisely receiving the .NET 4.8 updates on the mentioned laptop without activating the corresponding option in ESU. The option has always been disabled and, despite everything, not only I receive notifications that there are .NET 4.8 updates, but they are updated through Windows Update without ever having the option 7 "Install .NET 4 ESU Bypass" activated. I guess it's an unsolved computer science mystery.
can anyone help? I run Win7 Ultimate. Hadn't applied BypassESU until today. I followed readme before installing, installed all required KBs, then installed BypassESU, ran windows update. Some updates were offered, and I updated everything that was possible. Among those were installed "2021-10 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB5006743)" ; "2022-05 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 for x64 (KB5013870)" Are there any newer updates that should be offered? I was able install individual ESU KBs (such as network print nightmare fix), this worked. Am I up to date or do I have an issue?
The latest updates that should appear with Windows Update are the following: 2022-05 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB5014012) 2022-05 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 for x64 (KB5013870) If KB5014012 do not appear, it is that some update of the most recent Servicing Stack has yet to be installed. Regards.
Is it just me or can you just download all these security updates from the update catalog and install them manually? Is there anything I would be missing by installing updates from there instead of using ESU?