I'm running Windows 7 Ultimate x86 (which possesses the WMC/MCE) with April 2023's SECURITY ONLY updates installed, and no issues thus far. Since February 2023 the security updates have mostly been about "improvements". I've mentioned beforehand that with Windows Embedded 7 Standard x86 updates I've yet to install a Security Monthly Quality Rollup, so I'm waiting for a month where there's visibly a load of important-to-critical listed patch-ups of multiple OS components.
Not meant to be harsh. Simply pointing out the lack of details needed to properly help them. If the wording seemed harsh I apologize. I now humbly bow out of this particular conversation & voice my appreciation for all the help available here for everyone. Thank you.
No luck for me this month! Bypass: BypassESU-v12_u.7z Rollup: windows6.1-kb5025279-x86_2a2e4d2cf10d42586099f5ad68543412e24f20e3.msu (Yes x86!) At first it seems to install, but then after the reboot it says "Failure configuring Windows updates. Reverting changes.". It was working fine last month (KB5023769). Any suggestions?
Updates can fail for other reasons than ESU, check logs in C:\Windows\Logs\CBS "Root Certificate Updates" has nothing to do with it
Anyone else has an nVidia GPU driver problem after using the latest bypass? Every time I try to install the 474.30-desktop-win8-win7-64bit-international-whql.exe update, the GPU breaks, shows as not installed, the system turns to using the mobo graphics. Have to revert to 474.11-desktop-win8-win7-64bit-international-whql.exe, then the GPU works fine as before.
win7-64bit Yes. Installed with glitches 474.30: - Missing Aero effect - Missing nVidia control panel. - In the Device Manager of the Video Adapter - it says that the driver does not have the required signature. It seems to me that bypassing the ESU has nothing to do with it, the cant is on the side of nVidia. I rolled back to 747.11 - everything is fine.
Ok, now the thread is actually getting off-topic. We already have a thread that covers the nvidia issue.
So no need to take care of them separately? Good! Done... KB5025279 is installed. Had entries for the driver "bthpan.inf" in the setupapi.dev.log "Failed to find driver update". I then installed it from WinSxS using "pnputil -a". After this KB5025279 installed successfully. It's funny, especially since the problem according to the log file has existed for years. But whatever - thank you Ready_Slavik and abbodi1406!
Or use a malware spy certificate driver from unknown peoples from the internet without an summonable address.
Then probably do not use anything downloaded from internet. My certificate is generated following official MS documentation, it's up to you to decide which solution is best. Just stick your comments about trustworth into related topic. As we already drive to offtopic - it's much better to use resigned driver with custom certificate instead enabling TEST mode if you talking about privacy.
I've ran the ESU bypass, was up to date with 2023-01 final 7 patches, and ran the POSReady patches via the WSUS proxy. I am using a VM with snapshots (QEMU) and noticed IE11 broke with an ieframe.dll error after the 7 Embedded updates. Would crash upon starting. Not complaining about anything, but warning others something can go wrong. I ran CHECKSUR and sfc /scannow before and after the updates were installed. Good thing I don't need IE11 so not a deal breaker for me. Maybe an option to use Server 2008 R2 ESUs would have more desirable behavior even though we would get 10 months less of updates? I used the Server 2008 updates with ESU bypass on an updated Vista VM and IE9 never crashed. So maybe Server 2008 R2 patches would fare better? Not sure. EDIT: I got IE11 to run again by disabling and re-enabling under Turn Windows Features on or off, then restarting Explorer, then disabling the IE to Edge redirect in Edge. Maybe the BHO messes with the security updated IE11?