Bypass Windows 7 Extended Security Updates Eligibility

Should be:

Code:

5049628 (.NET 4.8)
5050681 (SSU)
5050049 (LCU)

 

Hi, the updates for Windows 7 as for Embedded POSReady 7 were until 10-2024. For Windows 7 as Server 2008 R2 they are from 11-2024. BypassESU-v13f ReadMe.txt says it clearly! For Windows 7 x64: [1] Windows Server 2008 R2 category. I don't know if you need to uninstall KB5050681 before .NET. Framework (01-2025). After .NET (01-2025), manual install the SSU KB5050681 so you can look up and install the updates (01-2025).

 

Same.

Currently looking at the list in Ghacks and having difficulty choosing the correct .NET package to manually download...

Edit:
Serious question to proceed, what to manually install first: the Servicing Stack (KB5050681) or the .NET one??? #IAmConfusion
I am seeing two factions wherein one claims the other to be installed first for other updates to be automatically seen by WU...

 

Are you serious? It's been mentioned a few times here. Up also Carlos Detweiller showed you the sequence. 1.(.NET 4.8), 2.(SSU), 3.(LCU)

 

SSU must be installed before the LCU this time, as it is a prerequisite. Bypass v13f needed.
When to install .NET 4.8 doesn't matter, but you need to have Bypass v13f .NET4.8 option activated. Deactivating the .NET4 option again after successful .NET installation is recommended, as it sometimes conflicts with MSI.

WU might not always show all updates, for me it doesn't show .NET4.8 after October '24. I'm just installing manually from the catalog.



Alternative: SiMPLiX pack with .NET 4.8 WA add-on. No Bypass needed.

 

I just realized it did not show .net for me after Oct. 24 as well. I wonder if that has happened to a lot of people.

 

It won't let me uninstall KB5050681 now, either through the Uninstall feature in the Installed Updates list or through using a Restore Point I created before installing this update but which now cannot be found (the restore point). (( In fact, the latest available restore point is from 4,5 years ago.

 

My advice is to remove the .NET 4 ESU Bypass and instead use the standalone installer:
forums.mydigitallife.net/threads/bypass-windows-7-extended-security-updates-eligibility.80606/page-157#post-1596676

I did each individually by moving the exe file into the folder where I extracted the tool and then running the batch with admin rights:

• ndp48-kb5049628-x64_4a50cb44d81ed701ec2f5419afc7c1b618a7c54e.exe from catalog.update.microsoft.com/Search.aspx?q=KB5049628
• ndp48-kb5049619-x64_87b626aee9010734b2e9da131b3ec71cfbec144e.exe from catalog.update.microsoft.com/Search.aspx?q=KB5050183 (or KB5049619)

My two cents.

PS: I installed the non-net 2025-01 updates before, so I confirmed this works.

 

So wait, I wrote I don't know ... If you had read the posts of other parties as well (page 427), you would have learned more. I am install .NET, ... manually and I've never had any problems. I was responding to your post (page 428): I have downloaded and installed KB5050681 ... So, my last Security Monthly Quality Roll Up for Windows 7 and Quality Roll Up for .NET Framework were installed on 22 October 2024. That means you didn't even have BypassESU-v13f for 11-2024 to 2026 setup correctly. And .NET, above NewEraCracker explained it to you.

 

For what it's worth and to give a big thanks to abbodi1406:
On my Win7 systems when I first searched for updates it gave me only the .NET KB5050183 and monthly "Windows Malicious Software Removal Tool"
After those where installed Windows Update then offered the KB5050681 Servicing Stack update.
And finally once that was installed Windows Update offered the KB5050049 Security Monthly Quality Rollup for Windows Server 2008 R2 update.
All where installed in this order on multiple systems with no issues using BypassESU-v13f.
Again a big thanks to abbodi1406!!! (And maybe this helps to ease those above that wondered about the installation order).

 

Correct.
I use dotNetFx4_ESU_Installer_v4 because BypassESU-v13f doesn't show any .NET update, even if .NET4.8 option is activated.
For me is good, anyway.

 

So i have a Windows Server 2008 Service Pack 2 Computer, not Windows 7 Server, Vista Server, i installed the 2008 Patch. Problem is, it is now only giving me "Update not Applicable" errors. And only those

 

This is a Win7 forum. BypassESU-v13f ONLY applies to Win7 updates via WinServer2008R2 updates.
The Server forum is here: https://forums.mydigitallife.net/forums/windows-server.15/

Now; using my own logic, we are using your updates for our OS. Seems to reason you should be able to get those numbers here & use the M$ catalog to download the same updates that apply to your server. It is working for me here for my Win7.

The DIFFERENCE is the changes provided by BypassESU-v13f software that allows us to use your updates for our OS. We have been EOS for years just like you.

abbodi1406 is the one to direct your questions to & if he can't fix it maybe he can direct you to the right spot to find your answers. Sounds like the 2008 patch reset your EOS triggers so the current updates are not recognized even if you download them. Check out the server link I gave you above.

You can start a conversation with abbodi1406 here: https://forums.mydigitallife.net/conversations/add?to=abbodi1406

 

I know you just mentioned it is "only for Windows 7" when abbodi has provided a 2008 SP2 Version in this Post. And here is something i found out, it seems the January 2025 SSU causes a Memory Leak on 2008 SP2 Servers. It runs full, then i get a 8007000E. Clearing SoftwareDistrubutions appears to fix it, but does nothing. When you then try to Check again, it starts just filling the RAM, then crash the Update Service. Only on 32 Bit though.

 

I experienced two memory fault related BSODs on my main Win 7 PC yesterday, after installing the three January updates. I wonder if it's related to the updates. The last BSOD of that type was months prior. This is on x64.

 

These are the first problems I have heard about that might be related back to Jan 2025 updates. Tons of crap for Win10 & 11. Nothing but M$ night & day mares for those folks.

Nice of @Maximilian Schäfer to elaborate further. And, yes, this is a forum about using 2008 R2 server updates for Win7. His are the FIRST I have read here about the server updates being used for servers that went bad. I agree with you. This is as good a place to start as any.

I have not heard of anyone else reporting problems they thought were update related. I do know many common M$ screwups cause BSODs. And some malware infections. x86 & x64 machines. I think we are all curious now.

My final suggestion stands:

abbodi1406 is the one to direct your questions to & if he can't fix it maybe he can direct you to the right spot to find your answers. You can start a conversation with abbodi1406 here: https://forums.mydigitallife.net/conversations/add?to=abbodi1406

 

I know it's only anecdotal evidence, but I've had absolutely no problems with January's update (KB5050049) since its installation on the 16th.

 

You need to login to view this posts content.

 

You need to login to view this posts content.