Last time i tested a 24H2 release on my i3 M380 8GB ram it started to be a bit slow, could also be related to the new pny 512GB SSD i put in the old laptop to test on. But i will stop cluttering this thread with non windows 7 info now, if the user wants to start with 7 now it already stopped being (unofficially) supported for how many times i wish him luck with that
Hello, I have here a Win7 Pro x64 which was last patched in March 2023. Rollup: KB5023769 (2023-03-14) SSU: KB5017397 (2022-09-13) Bypass: BypassESU-v12_u I have now removed ESU-v12_u and installed ESU-v13f. But no matter which Windows category setting I use, I cannot install the current SSU (KB5039339). Error message: The update is not applicable to your computer. I also tried an older Rollup (KB5027275 from 2023-06-13) and also SSU (KB5028264 = 2023-07-11) as a test - no chance. Does anyone have any idea what could be wrong? Or...since it's only a test VM anyway, I could do a new install. Are these steps still valid or is there a newer/better tutorial? Thanks and regards, Martin
Make sure you downloaded the update for the correct architecture. I have two snapshotted virtual machines (x86 and x64) with pre-ESU status and KB5039339 installs fine on both.
Use KB947821-v34 (System Update Readiness Tool for Windows 7 October 2014) to repair broken Windows Update components, then check on Windows Update for any missing updates. Reinstall the latest Cumulative update. After reinstalling the Cumulative update, restart your computer and then check for updates again in Windows Update to ensure everything is up to date. PS: https://forums.mydigitallife.net/goto/post?id=1860736#post-1860736 My two cents.
Hi everyone! I hadn't checked the thread since around February, so I don't have the latest overview. The last official update for win7 (embedded) was in January 2024. I used to install manually each month's security update only + IE11 update. I avoided rollup updates to reduce telemetry. Is there anything else we can use for security updates after January 2024? I have one laptop with w7 64bit and an old mini network with 32bit, if this info helps.
Comments #8465 & #8466 above could help. Most of us with a Win7 x64 system will continue updating thru Jan 2026 with WinServer2008R2x64 updates. IE11 & .NET updates continue as well. You have been lazy. I suggest going back in the forum to the date that corresponds with the second Tuesday each month & read everything that applies. I, for one, am not doing it for you. :>((
Server 2008 R2 is still getting Security-Only updates and IE11 Cumulative Updates for x64. So you can continue doing that. Make sure to update to the latest version of the Bypass first though. You can also look at this post, it has all the necessary links : https://forums.mydigitallife.net/th...dates-eligibility.80606/page-413#post-1860363
Wrong, security only updates are not cumulative, you need to install the november update first, restart and then install the december update.
I have 2 PCs under W7, one is up to date with patch 13f, got december updates thanks for it. Second pc have error because I had stopped updates for some months: It got updates to november 2023, it is patched with version from 02 march 2023, when launching update i get error 80072EFD . What are the steps to update it including december 2024 Kbs?
Interesting. Why bypass esu 13f don't let's update IE 11 on automatic in Windows 7 ? But manually working install that update?
This forum is for updating Win7. IE is a separate program. It is way beyond EOL & not required to run Win7. WU does not alert to IE updates but you can still find them manually via legacy software that still uses it in the catalog. Pretty much you have SSU, .NET framework & security updates via WinServer2008R2x64 updates. To be honest, almost no-one uses IE any longer (for years). I only update it because I have it & I can. I keep everything on my system updated because it is on my system.
This isn't true. Microsoft's user-facing literature doesn't mention it much, so it's an understandable misconception (that M$ intentionally spreads too...), but IE is a critical part of the Windows shell and even the underlying OS. This is why Internet Explorer is still in service and receiving updates until at least January 2029. It's not meant to be removed. If you rip out IE from Windows, many things break. Components of IE are used in explorer (the file browser), the stock Microsoft applications (wmp, wmc, sidebar, etc), the help system, the management console, web controls for Microsoft application frameworks (winforms, wpf, etc), and more et cetera. Fun fact: if you install a toolbar for Internet Explorer, you can also try enabling it in explorer. You can also use explorer to access ftp urls and other network locations without starting a web browser - this because of how closely explorer is coupled with IE. So even if you never actually open the "Internet Explorer" application, it is still required for Windows to function as intended, and it's in your interest to take IE updates just the same as the main rollup if you like staying updated. This is in part why Microsoft started bundling the IE rollups into the main rollup since a year or so ago. tl;dr Treat IE like the .NET Framework when it comes to updates and dependencies. It is the backbone of a lot of things.