Bypass Windows 7 Extended Security Updates Eligibility

Thanks for the tip! I definitely didn't know that.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Interesting, it's never been on my machine, and according to the article it hasn't been on a number of other user's computers either.

 

Thanks, I should have googled it first, but I'm one of those people who thinks anything Microsoft does anymore has some nefarious purpose.

 

It's added by this .manifest file.

 

You need to login to view this posts content.

 

The folder should not be deleted. (So it can, but should not). Microsoft itself describes it like this: “An authenticated attacker who successfully exploits this vulnerability gains the ability to execute and/or manipulate file management operations on the victim machine in the context of the NT account AUTHORITY\SYSTEM. After installing the updates listed in the overview of security updates for your operating system, a new folder %systemdrive%\inetpub will be created on your device. This folder should not be deleted, regardless of whether Internet Information Services (IIS) is active on the target device. This behavior is part of the changes that increase protection and does not require any action from IT administrators and end users." So, if the folder is there, just leave it there.

 

You need to login to view this posts content.

 

Hi, I removed .NET 4 ESU Bypass and from BypassESU-v13f's LiveOS-Setup.cmd settings and, then, rebooted and then re-enabled .NET 4 ESU Bypass from settings again and then rebooted again. For 3-4 times. I was not able to install KB5055171 because, very simply, .NET 4 ESU Bypass doesn't work on my 3 Windows 7 Pro.
I had to install KB5055171 manually as it has always been happening for several months with the .NET 4 updates.
At the contrary, no problem with KB5055561 and KB5056456.
I don't understand...

 

Kirklang:
You need to place the new NET Framework 4.8 update inside the same folder as the dotNetFx4_ESU_Installer_v4 tool, then run its command(.cmd) script as Administrator.
After the 2 - 3 minute install process is over, press any key to exit the tool.

 

Thanks a lot for your answer.
In the previous months, I used dotNetFx4_ESU_Installer, but I did a test and I realized that I could install KB5055171 as a matter of fact without dotNetFx4_ESU_Installer, too.
But always and only manually, because BypassESU-v13f can't "see" the .Net update via Windows Update.

 

Thank you, but I already know that.
I can install NET Framework 4.8 update (only manually...) with dotNetFx4_ESU_Installer_v4 tool and also without that, indifferently...

 

Hello. Just a reminder, until when updates for Windows Server 2008 R2 will be released and when all other options for using Windows 7 will be gone. Thanks.

 

For windows 7 patch as server 2008 r2 to have update up to 2026

For 64 bits only


For 32bits patch as posready to have update up to october 2024

 

Nothing is everything & there are very few absolutes. None with this Win7 update process. WU still alerts me to the monthly security rollouts, the .NET framework monthlies when available & that another SSU is available. Just this last month as a matter of fact. I like to download & do the installs myself but I do use WU as an alarm clock. A process with years of success & no need to change this late in the game. ;>))

 

Ony if processor is SSE2 compatible, and if not it's march 2018.