Same here. Last Tuesday's emergency OOB patch went smoothly, and this week's Monthly Rollup, .NET Quality Rollup, and Servicing Stack Update all installed without issue. Thanks guys! We all appreciate your efforts to keep Win7 alive.
Windows 7 Professional SP1 64-bit is up-to-date for July 2021 "patch Tuesday". Internet Explorer updated to 11.0.245. After several months without one, a new servicing stack update was finally released.
Anyone tried to install Rollup KB5004289 after SSU KB5004378? just to be sure they didn't change ESU validation mechanism
In my first Windows 7 PC, the KB5004289 SMQR update was detected and installed first. After the PC restarted, the KB5004378 SSU update was detected and installed second. No second restart was needed. Update: My second Windows 7 PC detected and installed those 2 updates in the same order.
SSU is exclusive update, it will be offered or installed only if no other updates are pending (i.e. always after all updates)
I've been updating Win7 since it came out in 2009, but I've never seen this before. I've also been using the wonderful Bypass since the beginning, and I'm sure it's not involved here. The Bypass worked perfectly for yesterday's (i.e. July's) updates on all six of my machines, but when I checked my HP EliteBook laptop, I saw something strange. (please see the image). 1. The top entry says Update KB5004378 (SSU update) failed. 2. The middle one says it's already installed (though it doesn't specify whether the install is OK or not). As a result, I can't reinstall it manually. 3. The bottom one also indicates it's installed, again without an indication of whether it's functioning or not. Right-clicking doesn't do anything, so I can't uninstall it. What should I believe? How can I solve this problem? Thank you.
Moin @ All! My July 2021 ESUpdate experience for Windows 7 Pro SP1 x64 systems: "Licensing method": KB4528069 & BypassESU-v11 KB5004951 (Security Only Quality Update for Windows 7 SP1 from 2021/07/06) -> succesfully installed KB5004116 (Security and Quality Rollup for .NET Framework 4.8 for Windows 7 SP1) -> succesfully installed KB5004233 (Cumulative Security Update for IE 11 for Windows 7 SP1) -> succesfully installed KB5004307 (Security Only Quality Update for Windows 7 SP1) -> succesfully installed KB5004378 (Servicing Stack Update for Windows 7 SP1) -> succesfully installed @ abbodi1406: Thx for your support! Great job!
I'd hypothesise that MS are well aware of how quickly ESU tweaks are getting fixed by you and have either given up or will make a significant change that should theoretically be much harder to circumvent... probably for a matter of weeks...
That's normal, SSU cannot be uninstalled (which means it's correctly installed) Update History failure is not really relevant
I did it in the usual order: first 2021-07 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB5004289) 2021-07 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 for x64 (KB5004229) then reboot and then 2021-07 Servicing Stack Update for Windows 7 for x64-based Systems (KB5004378) Everything ok as always. Thanks! PS: Interestingly, minutes after the las one was installed, two very old (year 2014) updates appeared: KB2631813 and KB2640148 More interestingly, I had installed them back in the day, so I haven't installed them again.
Yes. I did this, first (manually) installed SSU KB5004378, then Rollup KB5004289 (via WU) > installed (with two reboots).
someone had problems with boot win7 after installing kb5004289? Mine installs fine, wants reboot so i am doing it and win7 boots only in repair menu(for fix that i need revertpendingactions via dism)... Using bypass esu v11 and any sfc or surt saying no errors in sys files, I guess ms broke something with gpt/uefi boot in that update but this is mine guess
Curious, I guess I'm the only one having problems with KB5004229 (2021-07 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 for x64)..? It's behaving the same as before the .NET Bypass was implemented (just fails to install)... EDIT : Un/reinstall Bypass seemed to work