The problem is the sandbox of the browsers. If you start Supermium with parameter --no-sandbox then it works even with the updated win32k.sys. Without this parameter it results in error STATUS_NO_MEMORY. Some older ungoogled chromium browsers (v109) work also, because they use other sandboxing-method.
Confirmed, thx Paradroid666 for this tip ! Checked with Win7 and november patch / Win2008R2 (same) : Edge : adding "--no-sandbox" to the start link or argument, start browser and run ok Firefox esr 115.17.x (and other mozilla like) : change link with : C:\Windows\System32\cmd.exe /c "set MOZ_DISABLE_CONTENT_SANDBOX=1 && start firefox" but also same with Discord : \pathtoyourbin\Discord.exe --no-sandbox etc. That temporarily fixes the problem; let's say it's less bad. ;-)
Alternative: In the Firefox profile folder, open the prefs.js file and add a line at the end of it user_pref("security.sandbox.content.level", 1);
Installed requirements updates KB4575903 and KB5016892? Installed latest SSU? Rebooted after? Resetted DataStore.edb ? Code: net stop wuauserv 2>nul net stop TrustedInstaller 2>nul del /f /q %SystemRoot%\SoftwareDistribution\DataStore\DataStore.edb 1>nul 2>nul net start wuauserv 2>nul
Does BypassESU v12 support WEPOSReady 7/WS2K8R2 (after January 2023) updates on Windows 7 client counterpart (aka professional, ultimate, enterprise,...)? P/S: Sorry for my bad English
Moin Paradroid666! Just played around a bit with this Firefox workarount after installing KB5046705: The browser issue with the tabs crashing only appears from security sandbox content level 5 onwards... Postscript: After the installation of KB504670 the workaround does not work 100% correctly on my Windows 7 test system. If I call up a website with an embedded video, I can start the loading process, but it gets lost in an endless loop and the video is not played. So there seem to be more mismatches between Firefox 115.17.0esr (64-Bit) and KB5046705 / KB5046687. Therefore, I will not install KB5046705 / KB5046687 on my work systems and will wait and see what updates Microsoft will offer us on this topic in December. The other November updates have worked without any problems so far.
How it's resolved exactly? v12 can't show embedded or server updates, and can't install 2024-11 .NET 4.x updates
Tried to install .NET 4.x November update using dotNetFx4_ESU_Installer but it failed this time. Every other including October installed fine. Is there something else that I'm missing?
hello, I think I'm a little confused about the new options in ByPassESU-v13. I had installed BypassESU-v12-u. Then I installed Win7_WU_ESU_Patcher with the "Windows 7 embedded" option so that updates could be installed until October. Then I installed BypassESU-v13 with the "Server 2008 R2" option. No November updates are displayed. Now I've installed Win7_WU_ESU_Patcher with the "Server 2008 R2" option. Now it shows me November updates. That means that BypassESU patches the system so that the updates can be installed manually and Win7_WU_ESU_Patcher patches so that the updates are also displayed in Windows Update. So I still need both tools to install the updates via Windows Update. Is that right?
I would also like to know the answer to this question. I uninstalled all bypass's and installed only v13 and got no updates shown in windows update, but when I changed the registry key for the EditionID to ServerEnterprise the updates showed up in windows update.
Yes, this is correct, afaik. It's confusing, because there are multiple required tools with similar names between their various components that do similar yet different things. I tried to explain some of this in an earlier post. See here: Regarding "BypassESU-v13": At first, I thought abbodi integrated "standalone WU ESU Patcher" into "BypassESU-v13", since "BypassESU-v13" has a new menu (since v12) for selecting the Embedded vs Server 2008 SKU change option (to get 2024-02 and later updates) - which looks very similar to the menu that does the same thing in "standalone WU ESU Patcher". However, based on reports in this thread, it seems that maybe(?) this is not true, and you still need both "standalone WU ESU Patcher" and "BypassESU-v13" in order to install the newest updates. As opposed to being able to remove "standalone WU ESU Patcher" and just use "BypassESU-v13" (a simpler setup). - "BypassESU" enables the discovery of older ESU updates (Years 1-3) and enables the installation of ESU updates in general, among other things. - Version 13 of "BypassESU" is required to install the Nov 2024+ .NET Framework updates. Version 12 includes a .NET bypass which only works up to Oct 2024. - "Standalone WU ESU Patcher" enables the discovery and installation of Years 4-6 ESU updates for Embedded and Server 2008 R2. And 2008 R2 is the only 6.1 SKU Microsoft which is still publishing updates for since Nov 2024. tl;dr, you must use both 1) "BypassESU-v13" and 2) "standalone WU ESU Patcher" in Server 2008 R2 mode to get the newest updates (Nov 2024 and later). I think this is all correct. Please correct if not.