Bypass Windows 7 Extended Security Updates Eligibility

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?

 

My understanding is that (for now) Bypass ESU v12 is only needed to install the extended .Net Updates ( .Net 4.8 etc.).

 

Last weekend I dove in & used Proxy to make sure I had everything available into Feb2023 updated. Everything went smoothly except .NET 4 updates. Framework updates have been hit & miss for over a year. When MU can't/won't install I download manually & install myself. 4.8 still refused to update. I hid it.

This weekend I went through the process of installing v12 after carefully checking the recommended installs first. And then the bypass package with the new bypass ESU validation for .NET 4 updates. Before installing I followed the instructions to remove the proxy. Bit of a long slow process due to being careful & restarting a lot. Once installed, I reactivated WU & set it to notify me. Then I manually ran it. Provided 3 R2 2008 updates & the .NET 4.8 update. WU was successful with the R2 2008 updates but failed with .NET 4.8 again. This version was for R2 2008 so I downloaded this version from catalog & manually updated. To my surprise it worked smoothly.

With it installed I restarted & then removed bypass ESU validation for .NET 4 updates due to conflict warnings. Ran WU one more time & received one more R2 2008 update that worked smoothly. Restarted. My Win7 Home Premium laptop is now updated fully with WU actively waiting for any & all future updates.

Somewhere in all of this the power to my USB ports was turned off. After a quick trip to my search engine I went into 4 hub files & unchecked the boxes that allowed the system to turn them off to save power. Bingo. USB ports work again. Ended this by de-fragmenting my edb file & making a backup on my Seagate external drive.

Smooth sailing. Thank you everyone for the amount of careful work & effort you have put into this project.

 

Hello everyone

I am with the BypassESU v9

I just installed the BypassESU v12 with option (2) Install USU Supressor then option (7) Install .Net 4 ESU Bypass

done over BypassESU v9

Then I installed KB5016892 And I installed the Win7_WU_ESU_Patcher with option (1) Patch as Windows Embedded 7 Category

I restarted the PC each time.

What should I do now

 

just a heads up – unzipping the standalone WU ESU Patcher caused my Norton to quaratntine some of the dlls. I had to tell Norton they were OK, and restore

 

Whitelisting before using is a good idea.

There is a reason we are told to temporarily turn our security software off during these procedures. I use PeaZip for extraction. A lot of code & scripts are ID'ed as evil by security programs because they are often used in good & bad software. Security companies have long lists of software that is whitelisted so they don't produce false positives during scans.

White Hats & Black Hats often use the same code/scripts. For most of us this project is legit because it saves a piece of software we care about & still want to use safely. MS has abandoned it & stopped support of the home versions. BUT they charge ridiculous sums for others who want the extended updates. All about greed.

M$ would label this project as Black Hat considering themselves White Hats. Most of us have a love/hate relationship with M$. Terrible support & customer service even to paying customers. Yet, we really like Win7. Remove the spyware telemetry & modify for continued updates & we are happy as clams. Win10/11 has proven to be spyware with sketchy update processes as usual. M$ are Black Hats to us here. Like politicians who only serve themselves.

So, use a standard unzip software (most are free & work great) & turn off the security software when working with this project. Don't forget to turn it back on when you are updated. And thank our "White Hats" here for their fantastic efforts on our behalves.