Well Server 2008 R2 updates are first and foremost meant to be used on Server 2008 R2, as in mainly Server specific tasks and usage. Microsoft clearly doesn't care about compatibility with W7 Client or Embedded versions anymore. Those versions are officially not supported anymore. Worst case scenario, as time goes on it's possible that those versions become more and more unusable to be used for regular tasks and more and more fixes and workaround will have to be put in place. The upcoming 2024-12 Updates will definitely gives us more information on where this will be going and if the problems introduced with the 2024-11 Updates will even be fixed to begin with.
It worked! I can see the November update is available to download (which I am skipping for now). Looks like we need a BypassESU-v13u or v14 so there is no confusion.
The main issue we have with the Nov LCU also appears on a real Server 2008 R2. It's not because we repurposed it for Windows 7 client SKUs.
Some so amanzing did no read attentive the treads and still ask same same......all question about autodetect updates and fix browsers are to found in tread here..... try side 417
Currently BypassESU-v13.7z is not fixed. To fix it yourself, go to: Or wait until @abbodi1406 fixes it.
Agreed. But Microsoft won't care either way. Windows Server 2008 R2 supposedly "is not for browsing" and therefore we are on our own if we insist on using it (or the now unsupported Windows 7) for that purpose.
Personally I only patch my various Windows installations only once every 4-6 months unless there is an urgent security issue that I consider it necessary to patch as soon as I can. The patching issues I faced with Meltdown / Spectre back in 2018 and the subsequent experiences have convinced me there is no need to keep patching Windows every month, and I shall wait and see, for weeks and even months if necessary, whether there are any issues with these patches (not just for Windows but for other software like video card drivers). The last time I patched my Windows installations was in late August 2024 and I don't plan to patch them again before the end of 2024 at least.
I'm going to play it safe for now and wait until abbodi1406 fixes the issue with BypassESU-v13. If some changes in the coding need to be made in bin\PatchWU.cmd, I prefer he do it before I use it again.
You need dotNetFx4_ESU_Installer_v4 to install this month .NET 4.x updates (which has no issues, but they are non-security updates)
# Updated - BypassESU v13f - Fixed the bug with PatchWU.cmd (thanks to @Matrix360) - LiveOS-Setup.cmd and Wim-Integration.cmd are also updated to ignore installed "WU ESU Patcher" if above file is old, and offer install option
abbodi1406: I already have Windows 7 Professional SP1 64-bit configured as Windows Server 2008 R2 64-bit with BypassESU_v13. I used the gitlab.com and box.com links to download BypassESU_v13f. I noticed the file size for the old v13 and the new v13f are both 366 KB. When I deployed v13f, the window showed it as v13. This is the first window that appeared: When I selected option #3, this is the window that appeared: Am I doing something wrong?
After switching from BypassESU-v13 to BypassESU-v13f and rebooting, I re-installed the KB5046687 SMQR update for Windows Server 2008 R2 64-bit to see what would happen. After installing it and rebooting, I quickly discovered that my Mozilla Firefox ESR 115.17.0 browser was broken again. Uninstalling KB5046687 and rebooting again resolved the issue.