I continue to receive MSE updates through the WU client on all of my machines. Latest ones were about 3 hours ago (version 1.393.39.0 circa 2023-07-11). I've patched the WU client with Server 2008 R2 Only mode using the "WU ESU Patcher" tool. Make sure your computer is enrolled in the "Microsoft Update" extension of the Windows Update service. If the option is missing in the WU client settings, use something like the Silverlight installer to enable Microsoft Update.
I get all the other Windows 7 updates just fine using @abbodi1406 's WSUS proxy script. I just can't download MSE updates now. But I was able to last month (June 2023).
Maybe try the new(er) WU ESU Patcher instead of the WSUS Proxy. Perhaps M$ no longer publishes MSE defs through WSUS for WES7, thus the WSUS proxy script wont get them. abbodi would know better than I do. Year 4 of ESU with its Azure headlines ensures that WU client on Server 2008 R2 skus will continue to receive MSE defs. Years 5 and 6 maybe as well, I hope.
This can happen if the TrustedInstaller service is disabled. Open a command prompt as administrator: Code: sc qc TrustedInstaller See if the "START_TYPE" value is "DISABLED". If so, enable it by setting the start type to "demand". Code: sc config TrustedInstaller start= demand
Is it safe to install the latest embedded servicing stack update (KB5028264) on windows 7 pro with BypassESU-v12 installed?
Just to make sure, I have the .NET ESU installed, after the monthly .NET updates are installed, is it necessary to remove the .NET bypass?
Moin @ All! My July 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 KB5028167 (Cumulative Security Update for IE 11 for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed KB5028224 (Security Only Quality Update for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed KB5028264 (New Extendet Servicing Stack Update for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed KB5028860 (Security and Quality Rollup for .NET Framework 4.8) -> succesfully installed KB5028917 (Security and Quality Rollup for .NET Framework 3.5.1) -> 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. @ abbodi1406: Thx for your support! Great job!
Hi people, for the ones that used ESU for windows 7 till 2023 like me. Which is the correct way to continue receiving updates, should I do it with windows server or windows embed, thanks. Edit, all of my questions were previously answered.
Not necessarily. Previous versions of the .net esu bypass (like v9 and v11) had significant side effects, so it was recommended to only enable the .NET bypass when installing updates then disable it afterwards. The current version (v12) is a lot better. On all my machines with quite a wide variety of software installed, I have left the v12 .net bypass installed for the last 3 months and have experienced zero side effects. Unlike v11, it does not break prevent any of my applications from starting (like 64-bit Photoshop), so it much more convenient to leave the v12 .net bypass installed, instead of having to remember to turn it on and then off again when installing updates. No more "failed to install the .net rollup'" messages from forgetting to turn it on and then having to manually download and run the msus. abbodi is the ultimate authority of how good the bypass is and whether or not he recommends leaving the v12 .net bypass installed for convenience's sake. But in my experience, I have not observed any side effects from leaving v12 permanently installed on any of machines. I'd suggest leaving the v12 bypass installed for a while and seeing if you have the same experience.
Hmmmm. For the first time since this thread began, this months two updates are failing on me (KB5028240 and 5028939) with error code 80070426. I'm running Win7Pro, BESU v12u and WSUS Proxy, have tried with or without .NET Bypass, uninstalling and reinstalling BESU altogether. Sadface.
Anyone else seeing weird behaviour with Windows Defender definition updates lately? WU is suddenly popping-up the same update "Security Intelligence Update for Windows Defender Antivirus - KB915597 (Version 1.393.418.0)" over and over. I install, then it re-appears few mins later!