Bypass Windows 7 Extended Security Updates Eligibility

Thank you very much abbodi1 406

 

in a vm installation, first install BypassESU-v12_u then, Win7_WU_ESU_Patcher choose the 2 install , then connect to the internet and get this, why

 

Hi @abbodi1406,
Thanks for your relentless efforts that allow us to still use Windows 7 in a safe way. Your latest WU ESU Patcher works great for me, both for x86 and x64 VM.

One question :
. Under "Important notes" from the abovementioned link : * Windows Server 2008 R2 category is recommended for Windows 7 x64. Hence Option 2.
. In your latest messages, you recommend Option 1, hence Windows Embedded 7 category.

From previous messages, I understand that option 2 will offer updates after October 2023, hence longer than option 1.
On the other hand, using option 1 offers the strict necessary updates for Windows 7, while option 2 offers a longer list with some updates that seem specific to Windows Server.
Therefore, I tend to prefer option 1 for the time being, to avoid headaches on what has to be installed or not from the longer list of Windows Server updates.
Any recommendation or comment on this reasoning ?

Thanks in advance and have a good week, Bill.

 

i mean that it didn't prompted the February updates ,i choose the option 2.

 

No offense, but we are hardly trying to keep track .. as a general rule of thumb you first search, read, then ask .. most of the time your question would be already answered !
As @FuzzleSnuz stated in a previous post in this thread it's a mouse & cat play .. guys @ M$oft just making things harder & harder just for money & greed !

 

You need to login to view this posts content.

 

I have an install of Windows Server 2008 R2 for Itanium, however, whenever I run the bypass esu LiveOS Setup, I get the following error:

"The image file C:\Users\Administrator\esu\bin\superUser64.exe is valid, but is for a machine type other than the current machine"

According to Microsoft's support website, 2008 R2 for Itanium should still be receiving ESU updates, is there a way to fix the esu bypasser so that it supports IA64?

 

Itanium is different processor architecture from x86 and amd64. Just like how you cannot run Itanium executables on an x86 or amd64 machine, you cannot run x86 or amd64 executables on an Itanium machine. For reasons™, the vast majority of the world has abandoned Itanium, and it is becoming exceedingly rare to find a third party company, let alone an individual, who builds an Itanium release of their software. The ESU bypass is like the other 99.99% of contemporary Windows software in existence and the PEs included are built for x86 or amd64. abbodi would have to change his release engineering to produce an Itanium release of the bypass. Depending on how many external dependencies he has (superUser64.exe looks like one), this will either be a slog to find them or flat out impossible if those projects do not provide Itanium binaries or source.

 

oh i forgot,thanks!!

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I did not imply there is any problem, as mentioned I could not see that this update had previously been installed on my system, but it is valid for all editions of Windows.

 

I never touched a Itanic machine myself, but I think it had a (sloooow) x86 compatibility layer. Not that different in principle of the one bundled nowadays in W10/W11 and MacOS for ARM.

If I remember correctly the first generation "Merced" had some level of HW based helper to speedup the emulation, making it closer to MacOS for ARM than Windows for ARM which is entirely SW based

 

@abbodi1406

Sorry for beyng lazy on reading this huge tread, but I have a simple question:

Recently I updated a 2008R2 VM using Bypass ESU v11 which was already installed there the last time I opened it.

Everything worked as expected, and that machine is now updated to Feb 2023.

So should I upgrade to v12? Any major advantage upgrading? Any special path needed to upgrade or launching the script is enough?