Read first post....after bypass installed Use wu patcher , for windows 7 x64 choose patch as server 2008 r2 to have update up to 2026 Nb enable tls 1.2 and strong crypto tls for net frameworks are recommanded
Dou you have stoped the wuauserv service and do you have cleaned the C:\Windows\SoftwareDistribution folder?! and do you have installed the .NET 4 ESU Bypass?! if not do so.
bypass is installed, wuauserv is stopped. I deleted SoftwareDistribution folder now but still gets this error.
I had a couple of failures and a BSOD when WU was downloading the latest Tuesday patch rollup. I suspect that ESET was attempting to auto-update at the same time. In the end, I left it to do what it had to do, rebooted and finally got it to download and install the patch without further mishap. How I dislike auto-updaters!
Moin @ All! Somewhat belatedly, my September 2024 ESUpdate experience for Windows 7 Pro / Enterprise SP1 x64 systems: "Licensing method": KB4528069 & "new" BypassESU-v12 "Installing method": Manual download and installation via Microsoft®Update-Catalog KB5043049 (Cumulative Security Update for IE 11 for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed KB5043092 (Security Only Quality Update for Windows Embedded 7 Standard / Windows Server 2008 R2 SP1) -> succesfully installed The following additional update was offered by the Microsoft servers via the Windows Update Search and was also successfully installed: Security Intelligence-Update for Microsoft Security Essentials. @ abbodi1406: Thx for your support! Great job!
Hi all, I have BypassECU v9, can I install the latest patches available for Win 2008 R2 or do I need to install a later version of this ESU tool ? If so, can I run the v12 installer ?TIA!
Yes, v9 still work for installing Windows updates (and .NET 3.5 family updates) however, you need v12 to install .NET 4.x family updates in November or December, a new version will be probably required for ".NET 4 ESU Bypass" too
I just installed the final updates on my X64 W7 virtual machines and noticed something I haven't seen before -> a double re-boot ? Normally the update restart runs up to 30%, than actually reboots and when finishing it goes from 30 up to 100% and after that I can sign in. However now it runs up to 30% , than does a reboot, starts at the 30% but after a while, it reboots again and after this 2nd reboot the process is finished and the update is installed. When checking Update history the update has been succesfully installed. The VM's are both different and 1 is running on a Linux Mint host Vmware , the other on a Lubuntu host Virtualbox. Anyone else noticed this behaviour or is this the surprise Abbodi mentioned above ?
I've seen this on my machines (all real, no vms). I first noticed it about a year ago during the Year 4 ESU updates. I recall experiencing the double reboot just as you described on about 3 or 4 (memory isn't perfect here) of the last 15 monthly NT 6.1 rollups I've installed. All these rollups were successful. And the rollups that caused double reboots always did so on all of my machines. I'm pretty sure I never saw this behavior before ESU. Someone more knowledgeable can probably explain why the double reboot happens, but I can at least confirm it happens to other users. Maybe it's normal for ESU Year 4+ in general, with or without the bypass. Maybe it only happens when using the ESU bypass. I don't know.
This can happen if there are updates to some critical components like boot files, kernel or servicing stack which have to be completed first and exclusively before the rest. Even in old Win9x times, there were such exclusive updates which could only be selected alone. 0% - 30% Staging of updates. On 1st reboot 30% Installation of exclusive updates. On 2nd reboot 30%-100% Installation of the rest. Doesn't always happen.
Many thanks to all for this positive feedback and nothing to worry about Now I wonder for which period of time MSE will still do it's updates. Otherwise I can use W7 the rest of my life as VM but not connected to the internet.... Many many thanks for Abbodi1406 and the rest of the team who made it possible to enjoy W7 for an extended time because of their fantastic job