Microsoft has effectively killed off Win7 on older PCs

Self-built, one of many / Asus m4a77d
July 2, 2018 at 08:43:01
Specs: Windows 7 64-bit, Core i5 / 6GB
I just ran across this issue over the weekend & thought I'd share what I found. A friend recently gave me an old AMD system that had encountered issues with Windows Updates & MSE. This is a system I'd worked on before so I'm pretty familiar with it. Socket A Sempron 3000+, 1GB RAM, Radeon 9600, 160GB IDE HDD. It still ran decently up until a few months ago. He didn't want it fixed; he just asked me to wipe the HDD & then do whatever I please with it. So I wiped it & did a clean install of Win7 32-bit. All went well until one of the updates crashed the system. To make a long story short, it appears MS has quietly dropped support for systems with old CPUs that don't support SSE2 (pre-P4 & pre-Athlon64). I ran across these articles when researching the problem(s):

So I guess the only way to keep them going will be to stop running Windows Updates, or at least carefully pick & choose which updates to install. Browsers are another issue as most of them require SSE2 too. The choice there is to either run an older out of date browser that doesn't have the SSE2 requirement or try something like New Moon SSE.

Regardless, it seems like the days of running Windows on P3, AthlonXP, & older systems are numbered.

See More: Microsoft has effectively killed off Win7 on older PCs

Report •

July 2, 2018 at 11:25:34

i5-6600K[delid]@4.8GHz/4.4GHz@1.39v LLC=6 | 2x4GB Crucial-DDR4-2133CL15@14-14-14-30 1T 2800MHz@1.37v
MSI Armor RX 570 4GB@1395Mhz core@1.168v/1920MHz BiosModded

Report •

July 2, 2018 at 12:16:06
They'll go to any lengths to force people onto win-10...

XP and win-7 were good systems once the bugs were ironed out; unlike win-10 which is constantly plagued by screw ups galore with each "update or improvement", if one reads many of the win-10 related posts here, and elsewhere.

Report •

July 3, 2018 at 01:54:09
NOOOOO! Even the upcoming processors will no longer support Windows 7, this is bad news. I don't like Windows 10, I feel like it is still in beta mode.

Report •

Related Solutions

July 3, 2018 at 05:56:26
I've read the same comments after Windows XP expired or even earlier after windows 2000 was "replaced" with windows XP ... Get over it and move on!

Report •

July 3, 2018 at 08:42:08
In a general way I agree with sluc but Win 10 is different as the mess ups which come along with upgrading the operating system (features updates) happen every six months. This results in never ending "bedding in time" awaiting bug fixes. which doesn't make for a reliable OS. In the old days it was often suggested never to upgrade but to do a clean install instead. Not so sure I really want to do this every 6 months though.

There's another little angle with Win 10 too. You cannot refuse updates. If they fail Windows Update forces them on you again and again, rather like a virus. In extreme cases the only way around it is to either dump the machine or install Linux instead. Not everyone appreciates that choice.

This "service" approach works with Apple because major software upgrades are delivered to known hardware.

Having said all that "mostly" Win 10 works surprisingly well these days but for the reasons given it is never going to be as reliable as XP or Win 7. It's not just the same old bleating this time.

Always pop back and let us know the outcome - thanks

Report •

July 3, 2018 at 13:58:10
OK, I get that we're talking about old hardware, but the system I listed had absolutely no problem running Win7 until just recently. It wasn't "fast" but it was certainly good enough for email & web surfing.

I would think that MS should be able to create updates that can 1st check the processor type or for the presence of SSE2, & then either accept or deny the installation of the update(s) that require it. Unfortunately, the update installs & then the system becomes unusable after the required restart. The screen is blank & there is no HDD activity, therefore no way to access the F8 menu or Safe Mode. The only way to get it running again was to boot off a Win7 disc, click Repair, & then run System Restore. I tried it multiple times to confirm. I even re-wiped the HDD & started from scratch again. I installed ALL the updates but avoided the one that I determined to be the problem. The system was running fine. I made sure to create a Restore Point, then installed the final update & rebooted - DEAD! I booted off the disc again, ran System Restore again, & I was back in business. The problem was caused by the June Rollup KB4284826.

If a simple program like CPUZ can quickly identify a CPU & its supported instruction sets, I don't see why some sort of "identifier" couldn't be included in the Windows Update packages.

Report •

July 3, 2018 at 14:19:38
As earlier - it’s all about M$ making money by forcing people onto win-10 one way or t’other win-7 is supposed to be supported until 2020 at least is not?

Report •

July 3, 2018 at 14:44:04
"win-7 is supposed to be supported until 2020 at least is not?"

That's the point. MS changed the rules of the game while the game was still being played. Approx 40% of the desktop world is still using Win7. Of that 40%, there are still people running it on old hardware. IMO, they should be able to continue running it until support runs out in 2020. But if they install these new updates, they will brick their machines.

Report •

July 3, 2018 at 16:01:58
Is it any wonder many are switching to Linux and/or Mac OS...

True Apple do gradually delist earlier spec’d kit as OSX evolves; but they don’t deliberately, in effect, cripple older systems via an alleged “update”...

Report •

July 3, 2018 at 18:06:33
"IMO, they should be able to continue running it until support runs out in 2020. But if they install these new updates, they will brick their machines."

But is that really that surprising? Seems like they're doing well enough at bricking Win8/8.1/10 systems as well. They just send out patches to "fix" those---until the next update comes along and does it again.

Remember what you agreed to in that EULA?:

Installed WinXP on my old Compaq Evo E-PC back in '09. Never updated. Nary a problem....

"Channeling the spirit of jboy..."

message edited by T-R-A

Report •

July 3, 2018 at 21:28:38
If updates cause problems on your Win10 machine, this tool can hide it:

One of the latest monthly roll-ups caused a problem with this win10; stuck while booting up.
Going in to safe mode it will uninstall the failed update. Turn off auto update because the update will reappear in the "new updates available" list. With the tool above mark it as hidden.
This does not mean that MS can force some updates to be installed....

WIn10 upgraded from Win7 (or earlier versions) are more prone to update-problems. So far this WIN10 is far more stable than my previous WIN7 which became more unstable after every update.

Report •

July 4, 2018 at 12:14:35
The trouble I had wasn't with monthly roll-ups but with those massive features updates. In truth I regard them as Upgrades rather than updates because they virtually install a new operating system (every six months). Not sure whether the tool would help but I managed to stop updates for month (in Services and elsewhere) then eventually MS just over-rode my settings and forced the issue.

The machine in question was too slow for Win 10 and any features update that managed to install just slowed it down even more. I tried all the tricks under the sun to no avail. It is now a door stop.

Always pop back and let us know the outcome - thanks

Report •

Ask Question