I have just installed BypassESU-v13 and selected Windows Server 2008 R2 (before I have used Windows Embedded 7 with ESU-v12) After long searching with Windows update I get 8 results (6 seem to be older updates for Windows Server 2008 from the years 2012 - 2016) What updates should I install? Only KB5046687 and KB890830 and skip all the other 6 old ones?
No it will override them Yes you can hide or install the others, they will not cause effect or just ignore
Yes, Win 7 Pro here and this new update breaks Opera and Firefox for me too, both just crashing when opened. Rolled back using the Windows system restore point it made just before installing this update and all well again.
The same thing happened to my Firefox 115.17 ESR, so I also rolled back using the last system restore point.
Firefox Portable 132.0 x 64 Supermium and Pale Moon 33.4.0.1 x 64 both still work after KB5046687. Firefox 115.17.0 does not.
I have rolled back updates to follow situation with FF115 & others. A month, for me, will not hurt one way or another. Could be hidden problems with other programs as well yet unseen. Now... To many here with questions. I have long a held gratitude for abbodi1406 in particular & for all who have helped keep this Win7 update project successfully running for many years now. We are in the final stretch run. 2026. The Nov2024 update would seem to be for x64 systems only. That has been my current experience. I used WU to check for updates & was alerted to the .NET & monthly rollup for WinServer2008R2 x64 ONLY! RIP x86. To those with these systems you have a choice to make. Back up your hard drive NOW! Then... Upgrade to x64 based Win7 OS. Upgrade to a different current OS like ZORIN. Upgrade to M$ Win11 OS which might require a new computer. I will choose ZORIN when the time comes as my system/computer still does everything I want & need. I still have support from browsers & my banks, medical, etc. My system is an Acer Aspire laptop running x64 Win7 Home Premium. 1T SSD & 8gig of ram. So far so good & I can see making it past 2026. WAITING due to conflicts with browsers... I copied the KB numbers of the updates from WU & found both in the MS catalog. I downloaded both from the catalog. I killed all of my security programs & any running programs not needed. I killed WU. I created a System Restore point. I updated the Monthly Rollup first. Then restarted my system. I again killed programs & created a restore point. I updated the .NET framework programs next & restarted the system & WU. ANOTHER successful month of updates. I DID NOT require the updates to ESU that were so quickly & kindly provided here. My MSE continues to be updated automatically. It is strongly possible that I will upgrade my ESU programs before the Dec updates. Maybe not. ;>)) My successful downloads today (11/12/2024): 11/12/2024 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5046687) 410.6 MB 11/12/2024 Security and Quality Rollup for .NET Framework 3.5.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2008 R2 for x64 (KB5046543) 121.1 MB Good hunting all...
The common programs that I use every day all seemed to work properly, and SFC didn't find any issues, but I'm rolling back to a stored image as well to wait and see if any other problems with this update crop up or if there is a fix for the browsers that don't work properly.
The security-only update KB5046705 also breaks all legacy browsers (Chrome 109, Edge 109, Firefox ESR 115, Opera 95). I have tested this at my own risk on Virtual Machines with snapshots to revert. I think Microsoft released a broken Patch Tuesday, and soon we'll be reading news articles about it. On my Windows 10 computer, as it is a production PC, to workaround this, I made sure all my networks were set as metered on Windows and paused automatic updates a few days ago. Thank you everyone for bringing the issue to attention and avoiding unnecessary pain. If someone has an actual contract with Microsoft, it is worth to let them know. Browsers are probably only one of the symptoms. Edit - Here's a post about this: github.com/win32ss/supermium/issues/1012
Either this is done intentionally by M$ or we could see a OOB fix in a few days. If it isn't fixed by the time the December Updates come out it probably is the first. But Firefox ESR 115 is still officially supported, so hopefully the Mozilla team will release a statement soon if this is a M$ problem or something that they can fix.
I agree 100% & this may be a problem MS will not "fix" because of it. As far as they are concerned theses updates are targeted towards the servers; not out of date OSes. Could require some programming magic from outside of M$. Wait & see for now. Solutions will present themselves I am sure. ;>))
So the November 2024 security updates for Windows Server 2008 R2 KB5046687 and KB5046705 apparently break the "legacy" browsers including Firefox ESR 115. I have one computer setup with Windows Server 2008 R2, with patches up to August 2024. I have no plans to patch it (or in fact any of my Windows installations) before the end of 2024. So I will watch closely to see if this is "intentional" from Microsoft and that it really considers 2008 R2 machines "are not for browsing". There may be other problems with these security updates as well. By the way, for the new Bypass ESU 13 : I am aware that we can't remove the Bypass once ESU updates are installed. Do I just extract the package and run it on Windows 7 x64 or Windows Server 2008 R2 and then it will override and replace previous bypasses? I am also wondering whether the corresponding update for Windows Server 2012 R2 KB5046682 will cause similar problems for Windows 8.1 x64 and Windows Server 2012 R2. I think I should find time to do some tests myself.
I can add my experience to the list of data points. All programs using CEF (I only have <= M109) were broken by KB5046687 on all the Windows 7 machines I manage. KB5046687 also broke Supermium 124 and Firefox 115. However, ungoogled chromium 109 is still working fine under KB5046687. I find that interesting. Perhaps the google trust coordinated and planned this to affect all browsers under their control that they decided were "too old".
better to skip this update. It looks like R3dFox is not affected. Another thing i am thinking about: is there any ability to backport windows server 2012 r2 updates which will be available till 2029 to Windows 7 platform? If it is possible it will be tremendous!
Don't forget that KB5046687 and future rollup updates are cumulative. Later rollup updates will contain the "fixes" for KB5046687. If Microsoft does not "fix" this problem you will be forced to skip ALL subsequent rollup updates if you don't want to be affected. Unless you are already using (or switch to) the security-only updates and then you can just skip this month's security-only update KB5046705. The hope is that Microsoft will come around and fix the underlying code that causes this problem, but as mentioned above, from Microsoft's perspective starting from November 2024 these updates are only targeted at 2008 R2 and not at 7, so Microsoft may not care that the updates cause significant problems for Windows 7 if they achieve their primary objective of fixing the specified vulnerabilities of Server 2008 R2.