Bypass Windows 7 Extended Security Updates Eligibility

@abbodi1406 OMG your magic continues to work perfectly. Thank you!

 

Two different tools with two different tasks. So I suggest to keep them separate.

 

POST for the MDL Forum on Sunday 12-03-2023


I have been running Windows 7 Home Premium Edition SP1 x64 since 2011.

To continue to receive updates via Windows Update, since January 2020 I have always followed the recommendations of the MDL Forum, and in particular I have installed and used the different BypassESU, first v4, v9-AIO, v10 and v11. I have recently installed BypassESU-v12 which has allowed me to install the ESU Suppressor option.

BypassESU-v12 now gives me 2 options:

[ 4 ] Remove ESU Patcher

[ 6 ] Remove .NET 4 ESU Bypass

I don't change anything and leave it as is.

I then installed the Win7 WU-ESU Patcher, which gives me 3 options or choices:

[ 1 ] Patch as Windows Embedded 7 category

[ 2 ] Patch as Windows Server 2008 R2 category

[ 3 ] Patch as Windows Server 2008 R2 category + Windows 7 category.

According to you, in my situation, which option or choice would be the most judicious or the most necessary to continue to receive the ESU updates by Windows Update, at least until October 2023, knowing in advance that I will probably not apply the option or choice N° 3 ?

Thank you in advance for your possible future answer.

 

I just want to say a big thank you to the author of these tools. Yesterday I've read a lot of pages and then I've applied the tools. Everything was perfect
Thanks as well to all the people who wrote advices and info.

A guy from Italy

 

abbodi1406

Hi, I do not understand what the problem is. I installed ByPassESU-v12 and then Patcher with point "1" on your recommendation, but updates for 2023 and still not find it through the Windows Update Center.

 

abbodi1406

Yes, both updates are installed in the system and after applying the patch I naturally rebooted the computer. This is what I have installed:

2023-01 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB5022338) Installation date: ‎11.‎01.‎2023 6:52

 

that is a +1 here too

 

Is LiveOS-Setup.cmd (v12) supposed to work in a VM (Win7 + Updates from 01)?
I ran it as admin, but it just flashed the cmd prompt, so I changed it to /k to try and get some info. I don't see any output.
I was expecting a window wirh Choose a menu option:

Code:

X:\$W7\$0_KUC\ESU_All\BypassESU-v12\bin>whoami /USER   | find /i "S-1-5-18"   1>nul  && (goto :Begin )  || (
if defined _elv goto :E_TI
 net start TrustedInstaller  1>nul 2>nul
 superUser32.exe /c cmd.exe /k ""!_bat!" -su"  1>nul 2>nul  & exit /b
)
.
.
.

'"X:\$W7\$0_KUC\ESU_All\BypassESU-v12\LiveOS-Setup.cmd"' is not recognized as an internal or external command, operable program or batch file.

X:\$W7\$0_KUC\ESU_All\BypassESU-v12\bin>

 

If you open up a COMMAND PROMPT window as an Administrator then execute the CMD file, it should be fine.

 

Did that too trying various methods. Same problem

 

@adric your path contains a dollar sign, that is not even a possibility in Windows because it is a special character for MFT metadata files.
Extract the files to a simple folder like C:\BypassESU like the readme says and try again

 

Works fine with a $w7\... on native system.

 

running superUser32.exe only adding /v option gives:

Not sure if that's an additional problem not related to LiveOS-Setup.cmd not running

 

Did they only release a security update this month, I can't see any .net updates?

 

You need to login to view this posts content.

 

an internal tool from where I used to work that I've used for ages on DOS/Windows. 32-bit only. No
problems running with it on a native W7 64-bit system.