Bypass Windows 7 Extended Security Updates Eligibility

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.

 

Looks like the SSU might be at fault on NT6.0 x86 then. Time to roll back to a previous backup and stay away from 2025-01 Updates
and hopefully it will be fixed with the next SSU Update then. NT6.0 is the only version who still gets x86 updates in the NT6.x line so not possible to compare with other versions anymore.

 

You need to login to view this posts content.

 

I remember seeing a thread about Windows Update memory leaks on Windows Vista and a patch was provided to make it behave more like Windows 7. Maybe the latest update undid said patch:
https://forums.mydigitallife.net/threads/restore-windows-update-for-vista.82336/page-14#post-1775211

Hi, I think it might be a good idea for a moderator to move these messages to a separate thread in the Windows Vista forum, as they seem to be discussing a specific issue related to Windows Vista.

Thanks!

 

It's possible that the issues are hardware-specific, rather than related to the update itself. I've seen cases where certain hardware configurations or components can cause compatibility issues with Windows updates. Additionally, you could try running a memory stress test or other diagnostic tools to see if there are any hardware-related issues that could be contributing to the problems.

I've also had no issues with January's updates since installing them. However, I'm running Windows 7 on a virtual machine, which might be a different scenario from a physical installation. It's worth noting that virtualized installations might behave differently from physical ones.

 

The "spike" in memory usage is not strange considering your system only has 1GB RAM, that is not enough to do anything useful in a fully patched Server 2008 machine.

 

I just used this stand alone installer to get the Jan 2025 .Net 4 update for my Win 7 VM. I was aware that I had not gotten .Net 4 updates for quite a while and I went and viewed Installed Updates and saw that the last prior .Net 4 up date I had received on my Win 7 VM was from Jan 9, 2024. Would I need to go back and get any prior .Net 4 updates also, because I don't know how far back they are cumulative. Perhaps @Enthousiast could comment on this.

 

Not only the RAM the CPU(2 Cores) aslo.^^

 

It is strange to keep a machine like that running, there are many used computer shops around, that will sell you a computer many generations younger for way below $100... No one can be that poor...

 

Unfortunately, yes.

 

You need to login to view this posts content.