Simplix updatepacks are not the subject of this thread, it is actually made for people who do not want to use Windows Update but the UpdatePacks themselves. If there will be new working updates than you can install the ESU bypass or the manual updates installation tool, or simply use the updatepacks when simplix releases a new one.
Enthousiast: The only time I use Simplix UpdatePack7R2 is when the new version and the new add-ons are released each month after "patch Tuesday". I integrate them into my Windows 7 Pro 64-bit DVD which is already integrated with USB3 and other drivers. I then create a new up-to-date install DVD and add it to my collection after I have tested it. Since there was no new update pack this month because of the broken browser issues, I had to use the install DVD that I created last month. I was just curious if those 3 script tools are usable for now until the broken browser issues get fixed.
108% sure that this was done intentionally, so people stopped using Win7, they surely know how good it is even in 2024. OS is 100% compatible with modern web.
It's possible. It's highly suspicious that this issue came into existence on the very first NT 6.1 monthly rollup that is meant for Server 2008 R2 only. As soon as the last client 6.1 SKU (embedded) is abandoned - boom, the serious breakage happens. I think Microsoft has been aware of that NTLM shortcoming for years, they knew how to fix it, and they simply chose not to fix it as long as a client 6.1 SKU was in support (7 and Embedded). After all, doing nothing is much easier and cheaper than fixing it properly, "security" be damned, particularly when considering their engineered revenue timelines based on the paying enterprise clients. They probably waited to pull the trigger on including this patch, and they did not wait a single day longer than they wanted to.
I've look into my Linux Firefox ESR setup, security.sandbox.content.level is at 4 as default value, so I think no risk for W7.
Thank you for your information. On Windows 7 x64 running on my main system the default of this setting appears to be 6, not the same as your Linux system. So changing the setting to 4 might result in a reduction in the security of Firefox.
Quoting FuzzleSnuz in the Bypass thread : All my own wild speculation below. Take it with a grain of salt. Here is a more serious question : Is it possible this is going to be the norm going forward? Will there be more serious problems caused by future Server 2008 R2 updates (up to January 2026) if you install them on Windows 7?
Moin Matrix360 & abbodi1406! The bugfix for codeline 22 in PatchWU.cmd works for me. KB5046687 is now offered for download and installation via WUS. Thx & Good Job!
Thanks to @Angilas and @abbodi1406 and @Matrix360 Everything works now. All the latest updates and browsers are working, too.
For at least a year now I update via simplix first my to VMs then start with some old laptops that sit on the shelf and around 10 days (minimum) after patch Tuesday I start updating any laptops that I rely one for real. Ironically in October I thought I will skip this month the main laptop and I will start once every two months Lets face it though the updates don't matter at this point. Windows 7 is as solid and bugfree as it gets. For security and the likes I rely on other means which are offtopic not on the updates.
It did not work for me. Internet Explorer 11.0.350 seems to be okay, but Mozilla Firefox ESR 115.17.0 is still broken.
Can one give me(us all) a clear answer, please: Is the BypassESU-v13 not fixed i have dowloaded the version on 12:32 14.11.2024. And can i(we all) install the 2024-11 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5046687) update without any problems with the firefox esr browser?! Thank you so much
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