Correctly. Аs a matter of principle, Install ESU bypass is needed to install only two updates (via WU) - the latest Monthly Rollup and Security and Quality Rollup for .NET Framework. Other updates from 2011 to 2020 do not require it.
Can verify the steps worked. Fresh install on Win 7, install prereq's (first three, then reoot, then last 2, then reboot), then install ESU Bypass, then WU over and over again until it finished. It took proba around 2 hours all together And I can also confirm that this method DID eliminate whatever update Simplix installs that triggers my disability. So Simplix is not installing the bare minimum updates but must have some optional ones too.
Simplix is not the subject of this thread, here you can find all updates it integrates offline: https://forums.mydigitallife.net/th...l-wim-esd-creation.79421/page-90#post-1730339 the middle part of the three.
Is kb5011649 safe to install? I did and everything has been quiet since. EDIT: sorry I saw the earlier message saying it was safe. Disregard.
Yes, another painless monthly update process. Thanks once again all who are involved. My understanding is that the wmc/mce issues caused by last month's updates were fixed in this month's. So, if you are using wmc/mce and did not implement the fix last month, you should be able to safely install this month's updates. Should clarify, this month's update is safe for wmc/mce users whether the fix (registry edit) was applied last month or not.
04-2022 (KB5012626, KB5012329) worked flawlessly - thanks! A question regarding the .NET ESU Bypass: Every month I use the "BypassESU-v11" to install the .NET 4 ESU Bypass, check and install updates via WU and then I uninstall the .NET 4 ESU Bypass again. Because on the first page here is written: Is there a alternative solution that can always be activated without having to worry about any problems or is the ON/OFF method still the recommended one? Thank you, Martin
Just successfully installed KB5012626 and saw that wuaueng3.dll was updated, hope BypassESU will still work fine next month.
This is the current version of Windows Update Agent. BypassESU-v11 has worked fine for me each "patch Tuesday" with obtaining SMQR and MNF updates.
Unfortunately, no v9 and v11 contain different types of .NET 4 ESU Bypass, but both cause issues (differently) for other programs if the bypass kept installed
Why not install the .net bypass and only use the standalone .net updates installer for when there is a new .net update?
Server 2008R2 SP1 I'm getting timestamp signature and or certificate could be verified error on all patches from Mar 2022 forward. I have various other serves with Bypass installed no issues at all. All requirements installed . Have tried with V9 and V11. - ServiceName = Windows Update Standalone Installer 2022-04-16 18:35:39:884 1292 464 COMAPI - ScanFileLocation = C:\e1e018b65143ca2f2f73\wsusscan.cab 2022-04-16 18:35:39:891 796 c88 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\18b4d576-7334-4d2c-9939-74d658788bbf\Source.cab with dwProvFlags 0x00000080: 2022-04-16 18:35:40:085 796 c88 Misc FATAL: Error: 0x80096005 when verifying trust for C:\Windows\SoftwareDistribution\ScanFile\18b4d576-7334-4d2c-9939-74d658788bbf\Source.cab 2022-04-16 18:35:40:085 796 c88 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\ScanFile\18b4d576-7334-4d2c-9939-74d658788bbf\Source.cab are not trusted: Error 0x80096005 2022-04-16 18:35:40:085 796 c88 OfflSnc WARNING: failed to verify signature for offline cab. hr = 0x80096005 2022-04-16 18:35:40:086 796 c88 PT WARNING: PTError: 0x80096005 2022-04-16 18:35:40:086 796 c88 Agent WARNING: WU client fails CClientCallRecorder::OpenOfflineSyncSource with error 0x80096005 2022-04-16 18:35:40:086 1292 464 COMAPI WARNING: ISusInternal::OpenOfflineSyncSource failed, hr=80096005 2022-04-16 18:35:40:087 1292 464 COMAPI - Exit code = 0x80096005
When is it appropriate to uninstall the ESU bypass? Can I just leave it installed, or do we have to uninstall and re-install when we want to do WU?
I have installed it prior to using WU. Following that I only uninstall the .NET Bypass part of the ESU Bypass until the next WU cycle... this has been flawless since v9 (incl. v11). Leaving the .NET Bypass in place following the WU cycle, it has caused issues with some apps (Adobe) and has hampered certain app installations along the way. The easiest thing to do rather than guess... uninstall the .NET portion of the ESU Bypass until needed during the next update.
So if I don't have issues with any other software, I can leave it installed and it's safe? Just wondering, thanks.
That's what I found. All issues associated with it (when they occurred) had to do with new installations only of certain software and some Adobe products. When I would see those anomalies, I would uninstall the .NET Bypass and all would be just fine.
Hi all, did the april update still break win7 media center? WMC is the only reason I still use win7 and after reading this^ thread just skipped March. Work around not worth the time suck and brain damage of keeping security update + resetting wmc settings/ channels/ cable card, imo [insert 'Nope' gif here]