Bypass Windows 7 Extended Security Updates Eligibility

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?

 

dotNetFx4_ESU_Installer_v4 and kb5046258, yes, it works.

 

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.

 

Didn't know there was a new version. Thanks.

 

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.

 

You need to login to view this posts content.

 

I think this is all correct.

 

I used both "BypassESU-v13" and "standalone WU ESU Patcher" in Server 2008 R2 mode.

 

You need to login to view this posts content.

 

@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

 

Thanks，the most important step is to remove the "WU ESU Patcher", then reinstall it.

 

Just uninstalled it now and taking forever on the preparing to configure windows screen

Anyone else having issues pls?

 

You need to login to view this posts content.

 

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

 

RdrCEF issue in adobe acrobat, need to uninstall KB5046705 and it's fine

 

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?