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.
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.
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...
hello, Sorry if this has been asked many times before, but I figured it^s easier to make a new post. I also had to re-register to the forums cause the decades old email address I had registered with died. anyway, I installed the original Bypass ESU tool in early 2022. The last updates I received were in late 2022. Since then I don't receive anymore updates.I thought that patch had died so I gave up and didn't check again. I now found out about WU ESU Patcher from march 2023 : https://forums.mydigitallife.net/th...dates-eligibility.80606/page-358#post-1779528 I suppose that was the reason why I didnt get any more updates. Question : now in Jan 2025, can I just install it and get all the updates I missed? From what I understand from the post mentioned above: I have all KBs above installed except the last tone - KB5016892. Can I simply install this and then run the tool with option 3? Is there anything else I should pay attention to? re: prerequisites, ""ESU Suppressor" and ".NET 4 ESU Bypass" are still required to successfully install ESU updates" <-- since I suppose I installed them but don't remember, is there a way to check if they are currently installed? thanks a lot for your help
Oh alright so using latest BypassESU-v13f is the best way, no need for the standalone WU ESU Patcher ? I was misled reading some reddit topics I think. Thanks for rectifying. Believe me, I take absolutely no offense in your message. I completely agree with it even. I probably am a slacker on the side because I stopped checking for a solution after a while back then (and didn't need one after the print nightmare was patched), but I do tremendously appreciate the work done to get this tool working and the help given in those forums. I don't think I'm a complete idiot though but I like to be on the safe side and make sure of what I'm about to do first. As I already said : thank you for all your work on these amazing scripts.
Yes but if you already used the standalone WU ESU Patcher to set category as Server 2008 R2, then no need to change you still need BypassESU-v13f to install newest .NET 4.x Bypass