If the update installed, then the subject of this thread, the ESU updates installer, worked, the working, including the problems it causes, of the installed update is not part of the subject of this thread, Just be glad that the ESU Bypass tool offered us almost 3 years of extra updates for free.
Ok, so please help me if you can, I'm standing now in front of 2024-11 updates after successful installation of Abodi's recent hacks: KB5046543 KB5046687 Should I go or should I stay with 2024-10 updates and wait for 2024-12 patches? I'm afraid of installing these after all your reports of destroyed Chrome and Firefox functions I still use both of them...
It is kind of that simple. Updates that don't work can't be used. The update process is working. I am waiting using only the Oct 2024 updates & the updates that did work. At some point we will be forced to accept what we have or to move on (Linux/Win11). Forever does not apply to Win7. There are other forums here that deal directly with Win7 problems. Click on "FORUMS" above & explore those. Hoping this is a little more gentle & helpful than the simple raw truth. Good hunting all. It has been a good run. ;>))
What do you expect to happen? That someone outside of MSFT fixes the braking of the use of browsers with unsupported updates for an EOS OS? ?
The world will not end with one month without updates, just wait until next month or fixed OOB update
Solution: 1. disable integrity-checks and driver-signing. in a console with admin-rights: BCDEDIT /set nointegritychecks ON BCDEDIT /set LoadOptions DISABLE_INTEGRITY_CHECKS BCDEDIT /set TESTSIGNING ON 2. Backup original \windows\system32\win32k.sys (before November Patches). 3. Install November Patch KB5046705 (security only) 4. Reboot to install this Update (Windows reboots automatically twice because of kernel-patch) 5. Boot into Windows 7 Recovery CD or WinPE or Linux-LIVE etc. Copy the original win32k.sys from Backup to c:\windows\system32 (overwrite the patched win32k.sys). 6. Reboot normal No BSOD because of 1. Test Firefox 115.17.0 ESR: OK Test Supermium 126.0.6478.256 R5: OK Browsers are working.
Installed BypassESU-v13 and ran WU search for updates before and after applying the Nov. Server 2008 R2 updates to an updated October Win7. Should the listed updates be installed or hidden? edit: Missed this post. So iI guess it's ignore or hide. Note: November updates not detected other than MRT IIRC there was a similar situation with W8.1 showing old updates with BypassESU-Blue, but they all disappeared after installing the current LCU back then which is not the case here.
So eloquent in its simplicity. Ask & it shall be given. (@Enthousiast) Help from beyond M$... (@GfaRm) Thank you. (@abbodi1406 @Paradroid666) I think I will create a restore point first & a Oct 2024 backup ISO before doing anything. Can't be too careful. I think I will retain a text copy of @Paradroid666's comment & a backup of Oct 2024 win32k.sys in case a future rollup repeats this problem. You have got to love it when a plan comes together for the greater good. ;>))
What's wrong with you people? Why do you listen to perverts and follow their recommendations? Compromising the integrity of the system and inserting an old file with a vulnerability is the worst solution you can come up with. Just skip this update and wait for the next one.
[Paradroid666, post: 1860547, member: 1170069 - "Solution 1. disable integrity-checks and driver-signing in a console with admin-rights: BCDEDIT /set nointegritychecks ON BCDEDIT /set LoadOptions DISABLE_INTEGRITY_CHECKS BCDEDIT /set TESTSIGNING ON 2, 3, 4, .. 5. Boot into Windows 7 Recovery CD or WinPE or Linux-LIVE etc. Copy the original win32k.sys from Backup to c:\windows\system32 (overwrite the patched win32k.sys)."] Would reconstructing the November 2024 .CAB file that possesses the new win32k.sys file work (simply to delete the new win32k.sys file and copy the October 2024 win32k.sys file [ie., the backup file], and then to recompile the .CAB file as per the original .CAB file to then use W7ESUI to install the update package)? It would require to unpack the KB5046705 .MSU package with 7-Zip, to locate the win32k.sys file in the correct .CAB file [unpack THAT one also, but rename the original .CAB file with a "0" in front of the original filename after unpacking its contents] and make the switchover for the win32k.sys file from October 2024's security update. Then, to recompile that .CAB file and place it into the W7ESUI folder along with its other 3 original files. If it works out, this would have to be the unofficial November 2024 Security Only Quality Update for Windows Server 2008 R2 for future setups (for now until a better monthly update patch is official). Just an idea that might cut out needing to use settings changing with BCDEdit or the Recovery CD/WinPE/Linux-LIVE methods at all. P.S.: Were the previous (no) integrity checks, load options and test signing settings reverted back to their original state settings? Or they are left as were performed to avoid a BSOD?
Good morning /or/ evening to everyone Long story short I've been a lurker at this thread for 4-5 years now ever since Windows 7 was condemned to EOS, and even saw the thread went it wasn't yet members-only censored. (plus monthly visits to Ghacks & later on Ask Woody) And it's only now that I was forced to create a MDL account because of my current problem Basically, because of work I only had the free time now (since yesterday) to install the October 2024 updates (KB5044356 & KB5044095 for me), but Windows Update always fails the downloaded updates: -if I try both updates, it keeps giving me the "Windows update encountered an unknown error" (forgot the exact code number but probably a 8024200) -if I try either 1 of the updates, it gives me the error code containg a 7 & e at the end I had to download individually from the Update Catalog because what else can I do... -successful with KB5044356 -for KB5044095 (.NET 4.8 Windows Embedded 7 x64) I downloaded all 4 files (2 MSU's & 2 EXE's) because I'm basically a noob regarding the more technical aspects, and only managed to successfully install Windows 6.1 KB4019990 x64 MSU & the ndp48 KB5044027 x64 EXE, while I couldn't proceed with the Windows 6.1 KB5044011 x64 MSU & the ndp48 KB5044019 x64 EXE for some reason I have downloaded the latest BypassESU (v13) and even triggered the Win7_WU_ESU_Patcher, but nothing happened, at least in a manner where I can say "Everything's fine" If anything the situation actually worsened -"View update history" got wiped out and only lists KB5044356 manual installation (it got similarly wiped out previously when I missed the February or March 2024 updates and I tried installing the previous month despite the then-current month updates) -"Most recent check for updates" & "Updates were installed" indicate "Never" -Windows Update is still stuck on "Checking for updates...", and I don't have any free time to either check in or even leave my laptop on as I have work the following day This post doesn't begin to start regarding potential November 2024 updates Can anyone tell me where & which stage I proverbially £ụćкęđ up??? Edited for a typo & additional information
I agree 100%. Each of us has to make that decision. I now have all of the info, research (so far) & the instructions saved without making any changes this month. I will be updating IE11 & .NET framework as these do not negatively affect my system & software. It is the Security Rollout that I am waiting on. What to do, what to do. lol
I have this message since January 2023, because Microsoft refused to sign the Nvidia-Drivers for Windows 7 (no WHQL). The bcdedit-commands for disabled driver-signature-check are included in the official Nvidia-Manual to allow the installation of the Nvidia-Drivers without signature. Windows shows just a watermark at the bottom right but works as good as ever. This has nothing to do with activation or something. The security is lowered because of this missing signature-checks, so you should be careful, what you install, as allways. Windows 7 Ultimate with Applocker ON can block all unknown programs because they have no execution rights and can't do anything malicious. On Win7-Home and Win7-Pro there is no Applocker available, but you can use Software Restriction Policies (SRP) to block unknown programs as good as Applocker. The solution obove with the replacing of win32k.sys is just step #1 with the intention to prove that it is just this one file which makes those problems. Step #2 will be information transfer to Microsoft and to the programmers of Firefox and Supermium, so they can make a better fix that avoids the incompatibility with the new win32k.sys. By the way: Windows Server 2008 R2 had various similar internet-problems since the year 2011 and curious workarounds had been found for those bugs.