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
Meh.. somewhere here I found some registry fix cmd command by @abbodi1406 I think it was about to hide obsolete updates (anything about right ordering) but It seems the created .cmd got lost in already deleted test-VM. Wanted to ask if I understood correct that is the purpose of it. Because I applied to that live, but WU still showing me very old updates, while latest ESU and stuff is installed. (pre-integrated) Maybe there is some other way? Would love to hide all the old stuff somehow... (without doing manually I mean)
WU will show old updates if you installed latest ESU Monthly Rollup, and did not install WU ESU Patcher (or WSUS Proxy)
Thanks a lot, will try out as soon my system let me. (RAM issues, other VM opened doing stuff, install crashes) EDIT: Mh still not worked. Not sure what went wrong. Will start from the scratch I guess. What I did: 1. Taking normal ultimate sp2 refresh en-us-ISOs (x86, x64) 1. Setup Win7 x64 VM installed from old Simplix AIO ISO (Win10 1607 boot.wim) 2. Installed Win8.1 and Win10 1607 ADK Deployment Tools into it 3. Download WHDownloader + NTLite Updates (included ESO ones)+ Komm Updates (for installed System) 4. Uses WHDownloader function to remove official supersed ones 5. Used ESO_Bypass on the wims from extraced ISO folders 6. Used W7MUI (with DISM from Win8.1) to integrate all LP stuff 7. Used WHD-W7UI to integrate all the Updates + Extras etc. (DISM detected Win10 DISM +Cleanup) 8. Used MDL Tool (Simplix Stuff without Simplix UP.exe, but all the rest) Even with WU-ESU-Patcher, (Server) restart, still shows me like 20 new updates. 9. Read the readme from WU-ESU-Patcher integrated the missing updates + latest ESU LCU again (Some like the kb4575903 it said were already detected as installed) 10. WU-ESU-Patcher again (Server), restart. Still shows like 20 new server updates i+ any 20 optional ones (no LPs)
Will set me up new VM, Will not remove supersed ones and use MDL Script at the end. Wish me luck it works this time. Ohyeah I also found back the reg one (was in some subfolder of older created ISOs "finished1") Windows7-QualityCompat.cmd
I think I'm bit late to start with Bypass ESU, but better late than never, and I just tried v12 on a fresh install. After live installing all provided updates but Edge, I installed the previously downloaded list of listed prerequisites (only 2 since the others were already installed). For bypass ESU I used option 1, and according to the feedback, everything went fine. However, after checking for new updates, I only got 3 rollup packages -- two for .Net framework and one for Win 7. Is this expected? I'm not sure how many updates I supposed to receive, but this is a bit less than expected, even with the three rollups in there. Any idea on what's happening?
Yes, ESU only provide 3 updates: Monthly Rollup, .NET Rollup, Servicing stack update which updates you got? you need the standalone WU ESU Patcher to receive latest updates