@abbodi1406 There is a bug in the BypassESU-v13. The EditionID key value in the registry is not changed by the task "Patch WU ESU" when "LiveOS-Setup.cmd" is used to install the "WU ESU Patcher" (server 2008 R2). The task ends with an error with code 2. To fix the bug, in bin\PatchWU.cmd, line 22, replace Code: for /f %%# in ('type SKU.tag') do set "_sku=%%#" by Code: for /f %%# in ('type "%~dp0SKU.tag"') do set "_sku=%%#" Then run "LiveOS-Setup.cmd" of the "BypassESU-v13" and remove the "WU ESU Patcher", then reinstall it. (The old "standalone WU ESU Patcher" is no longer needed.)
Saying that, I have had problems with adobe acrobat when I load a pdf it shows error 0xc0000142 but it was fine before installing the nov update 6687. I'm going to uninstall 6687 for now and wait till dec
Just uninstalled it now and taking forever on the preparing to configure windows screen Anyone else having issues pls?
It failed to uninstall the update So stuck with it so i have removed adobe and use firefox to open pdf docs as editing i can do in word Not installing this on the 2 laptops i will wait till dec
abbodi1406: I just did a clean install of Windows 7 Pro 64-bit with an install DVD which is integrated with the October 2024 simplex update pack and the appropriate add-ons and drivers. Because of the issues the November 2024 updates have caused, do I need to deploy any of these script tools at this time?
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?