Bypass Windows 7 Extended Security Updates Eligibility

Yesterday at 17:22
Only manual download and install from now on, WU itself won't show anything @enesalpa

I have Windows 7 Ultimate with all ESU updates as of January 2023. Installed BypassESU-v12 (was ver. 11) After installation - Monthly Security Quality Rollup for x64-based Windows Embedded Standard 7 Systems (KB5022872), 02 2023 in manual mode and reboot, WU automatically found: Windows x64 Malicious Software Removal Tool v5.110 (KB890830) and installed successfully.
Next, in manual mode was installed:
1. Update without. and correct. for .NET Framework 3.5.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 on Windows Embedded Standard 7 for x64 (KB5022731), 2023-02
From this package, I have successfully installed:
- Rev. without. and correct. for .NET Framework 3.5.1 on Windows Embedded Standard 7 for x64 (KB5022523), 2023-02
- Microsoft .NET Framework 4.8. Update: KB5022509.
Not installed:
- windows6.1-kb4019990-x64
- ndp47-kb5022515-x64.

Also manually installed successfully - Cumulative Security Update for Internet Explorer 11 Systems for Windows Embedded Standard 7 x64-based Systems (KB5022835), 2023-02

Huge thanks to abbodi1406 and the team for a job well done.

 

Yes. I understand it.

 

Unfortunately .Net 4 ESU Bypass -v12 didn't work for me when trying to install the .Net 4.8 Feb Rollup kb5022509-x64 Window Embedded Standard to my live Windows 7 Pro x64, constantly showing error messages that the installation had stopped, followed by "The application was unable to start correctly (0x80000003). Click OK to close the application."



The Feb Security Rollup and update for .Net 3.5.1 installed fine using the Simplix Pack.

 

You need to login to view this posts content.

 

The BypassESU-v12 tool worked fine for me with getting the KB5022509 NET Framework 4.8 update installed in 3 Windows 7 Professional SP1 64-bit desktops which were up-to-date to January 2023.
Deploy the tool, then select option #7, then restart, then install the update.

 

Which is exactly what I did, twice. I also tried enabling all of the options in the package and rebooting still no go. Each try was on a restored image of the original system.

Edit: This is on a system updated with February's Rollups, not just to Jan 2023 which may account for the difference.

 

You need to login to view this posts content.

 

I was wondering if it's possible to write a script that can search the update catalog and download new updates to an update folder to kinda automate the manual look up process. Thought it would be cool to run every update tuesday.

 

https://forums.mydigitallife.net/th...dates-eligibility.80606/page-348#post-1777053

 

2023.02
KB5022874 (Security
KB5022835 (IE11 Security)
KB5022731 (.Net 4.8 Security) (KB5022523 + KB5022509)
+ Rollup (It include IE Update)

 

Thanks

 

You need to login to view this posts content.

 

Thanks @abbodi1406

 

Agree!
It would be even cooler if this script could be made into applets in the control panel.
Does anyone know how to do this?

 

I tried the WSUS proxy, but searching for updates did not find any Win7 embedded Kbs. Don't know what the problem could be.

 

I've used the Monthly Rollups for my Win7 Pro for the last three years and had no problems.
Can I continue like this, or is it now better to switch to security-only updates for compatibility reasons (given a Win Pro is not 100% a Win Embedded/Server...)?

Thank you for your work!

 

Having the regular (non-embedded) Win7 x86 now, and in the past doing the manual updates successfully, is the "Windows Embedded Standard 7 for x86" one actually OK to do going forward? I'm not sure what you mean by "different" above. Different as in incompatible with non-embedded?

 

You need to login to view this posts content.