Bypass Windows 7 Extended Security Updates Eligibility

Can someone perhaps help me.
I had to reset my PC complete new. Format all and installed windows.
Installed thy Bypass and know i get error to update the November 2019 Security update KB4525235.
Some Servicing Stack Updates before failed too.
Did i miss something ?

 

You should just use this: https://forums.mydigitallife.net/threads/45005/

 

There are two lines in `LiveOS-Setup.cmd` that test if the user is administrator.
They don't work right if user elevated to admin rights because it tests the users ID. I propose to change the test to check if the current user has the right privilege, for example something like:

whoami /PRIV | find /i "SeImpersonatePrivilege"​

 

You saved my week. Thank you. All worked perfektly for me.
Now Windows update running too.

 

Hi All! This is my first post on My Digital Life. I joined because I am a long time Windows 7 user and I wanted to be able to access the ESU Bypass. While the bypass worked flawlessly, I am experiencing a strange problem with x64 version Adobe Photoshop CS5.

All of the other programs in CS5 work without issue, including the x86 version of Photoshop, but each time I try to run the x64 version I get a popup that says "Could not find the file specified." After which the program does not run.

I have attempted to run chkdsk on the C:\ drive and sfc /scannow in the directory where I have CS5 installed, but these troubleshooting methods have not helped.

I revered the PC to a restore point I created before attempting the ESU Bypass and now the x64 version of Photoshop CS5 runs properly, but I still want access to the extended security updates. Any and all help would be much appreciated!

 

After updating using the ByPass, remove the .NET portion of t he bypass... see if that helps. Many users have applicatioon issues when the .NET ByPass is in place. What many of them do is remove the .NET portion once the update is complete and reinstall prior to the next update cycle.

 

I open a cmd prompt with my domain user, right-clicking and selecting "Run as Administrator".

In the output of `whomi /groups` there is no S-1-5-19 SID.
There are other groups like BUILTIN\Administrators. I guess the SID could be changed as well. Or maybe there is some reason why exactly that SID is being currently checked.

The current test does not work for me anyways, running the .cdm file just exits without any output (I guess the superadmin fails due to some restriction active in the domain). After I changed the test to either test some privilege, or simply the BUILTIN\Administrators SID, running the .cmd file seems to work fine.

Maybe I am missing something important about how the .cmd is supposed to work...

 

Ah, we are talking about different commands. Actually I did not have issue with the HKU check, the problem was with the "whoami /USER" check (where it checks if user is SYSTEM). It seems I have some problem elevating to SYSTEM with TrustedInstaller. Sorry for the confusion, I need to look more deeply why it fails at those points with zero output (no error at location "E_TI" is printed).

Edit: Aaah, OK, looking at what is SuperUser64 it is clear what is my problem. The SeDebug privilege has been removed from any user (even administrator) in my domain. And it does not handle that gracefully, no error is printed. Sorry for the noise, I should have checked this first before opening my mouth!
I guess it could check the exit value of SuperUser64 if it is non-zero, or even print "Couldn't acquire SeDebugPrivilege" if the exit value is 2.

 

One small issue removing WU ESU Patcher in line 320:
if exist "%SysPath%\sle.dll" (removing "%SystemRoot%\System32\sle.dll"&del /f /q "%SysPath%\sle.dll")

It is missing "echo" before the "removing"...

 

Thank you for the response! Please forgive my ignorance, but what are the steps that I must take the remove the .NET portion of the bypass?

 

open BypassESU-v9 or v11 and enter the number corresponding with Remove .net bypass (6). It will show you when done. When done close the bypass window by using the corresponding number (9)

 

Thank you for you help! This did the trick and I can now run Photoshop x64

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You are false; you need it to unlock the updates for the new processor generations.

Here you see the .exe info :

Enables Windows Update on PCs with unsupported processors.

 

Simplix does disable cpu check too.

 

If you do not install some updates then there is no CPU check...