User Patch Unlocks Windows 7 and 8.1 Updates for Core "Kaby Lake" and Ryzen

[btarunr]

Microsoft, in a bid to ensure users of 7th generation Intel Core "Kaby Lake," AMD A-series "Bristol Ridge," and AMD Ryzen "Summit Ridge" processors stick to Windows 10, ensured that the three platforms don't receive software updates when running older Windows 8.1 or Windows 7 operating systems. A new user-made patch removes this draconian restriction, letting you install Windows 7 or Windows 8.1 on your new-generation CPU powered machine, and receive regular software updates through Windows Update.

The patch is open-source, so you can inspect its code, and available on GitHub. The author of the patch, Zeffy, discovered two new functions to system file wuaueng.dll after the March 2017 update for Windows 7 and Windows 8.1, labeled "IsCPUSupported(void)" and "IsDeviceServiceable(void)." This library is patched to toggle those two functions "1," telling Windows Update that the CPU is "supported" and that the platform is "serviceable," making it eligible to receive updates.

DOWNLOAD: New-gen CPU Windows Update Unlocking Patch for Windows 7 and Windows 8.1 by Zeffy

View at TechPowerUp Main Site

 

[Nuckles56]

That didn't take long, though I'm sure that Microsoft knew this was going to happen and will push out a modified version to lock the processors out from 7 and 8.1

 

[Melvis]

Good! Having your older OS blocked for having a CPU that still works under older OS's but isnt "officially" supported is BS (Even more so on W8.1), suck an egg MS.

 

[Octopuss]

I'm afraid this will be short lived, because Microsoft has tons of options how to lock this down again.

 

[Aenra]

I'm afraid this will be short lived, because Microsoft has tons of options how to lock this down again.

Such as?

 

[Octopuss]

Such as?

How the hell would I know? I'm not a programmer, but there are most definitely numerous ways to do that.

 

[meran]

LOL I've been using all patched cracked windows since I was born unless I got it oem all updated without microsoft knowing also upgraded cracked win7 to original win 10 I am sure there will always be a way to run around this.

 

[Parn]

I believe Win8.1 is still under mainstream support, isn't it? Blocking updates on an OS that is still under mainstream support is a complete BS.

For this reason alone, I'll not be upgrading anytime soon.

 

[Frick]

I believe Win8.1 is still under mainstream support, isn't it? Blocking updates on an OS that is still under mainstream support is a complete BS.

Yep. For Windows 7 I'd sorta understand if the new CPU's had some features it would not support (better power management and suchlike), but blocking even security updates is BS. MS has done a lot of good the past few years, but this is just daft.

 

[Darmok N Jalad]

Seems like this could end up being a cat and mouse game. MS will block the patch, then a new work around will be discovered. Honestly, I wonder if MS will actually block it. They have an official policy of not supporting those systems, so anyone attempting to use the Win7/8 on those CPUs will be disqualified from any official support. This fight will require them investing more resources onto their older OSes, which was something I think they were trying to avoid with this policy in the first place.

 

[Dave65]

GREAT!!

 

[Gundem]

Cool

 

[R-T-B]

Such as?

How the hell would I know? I'm not a programmer, but there are most definitely numerous ways to do that.

He's right. There are a million other dlls. Windows Update has ways to even add more if they want. It's a convoluted mess and they can hide that code anywhere. It depends on how much of an ass they want to be.

Seems like this could end up being a cat and mouse game. MS will block the patch, then a new work around will be discovered. Honestly, I wonder if MS will actually block it. They have an official policy of not supporting those systems, so anyone attempting to use the Win7/8 on those CPUs will be disqualified from any official support. This fight will require them investing more resources onto their older OSes, which was something I think they were trying to avoid with this policy in the first place.

My thoughts exactly.

 

[Ubersonic]

Yep. For Windows 7 I'd sorta understand if the new CPU's had some features it would not support (better power management and suchlike), but blocking even security updates is BS. MS has done a lot of good the past few years, but this is just daft.

There are two sides to the coin.

On one hand if people have paid for a retail copy of Windows they should be able to install it on a new system and have it work, and they can.

But on the other hand 7/8 are legacy O/S's, support patches are created and then provided (at Microsoft's expense) for the benefit of existing users who are unwilling or unable to upgrade to 10. It's not designed for people doing new system installations long after the end of sales, and I can sort of understand their point there.

If I installed my copies of Windows 98SE, XP or Vista on my Ryzen system I wouldn't get any updates either.

 

[Aenra]

When you reach a point where you're after custom-made patches, it goes wihout saying that your OS does not auto-update; not anymore. It will happen manually, it will be initiated by you and done after some thorough Google-ing.
As such, no, i don't see any scenario where 'naughty' .dlls will magically transport themselves to your OS and make you buy Win10.

 

[Static~Charge]

Such as?

1. Pushing a fresh copy of the DLL to your machine.
2. Invaliding the patched DLL via System File Checker.
3. Putting the CPU check into multiple files.

Those are just the obvious ideas.

 

[Ahhzz]

Seems like this could end up being a cat and mouse game. MS will block the patch, then a new work around will be discovered. Honestly, I wonder if MS will actually block it. They have an official policy of not supporting those systems, so anyone attempting to use the Win7/8 on those CPUs will be disqualified from any official support. This fight will require them investing more resources onto their older OSes, which was something I think they were trying to avoid with this policy in the first place.

"Official Support"? who cares? I haven't run Win Update on my 7.1 for years.... Still running strong, and without any issues. Screw em.

 

[Aenra]

1. Pushing a fresh copy of the DLL to your machine.
2. Invaliding the patched DLL via System File Checker.
3. Putting the CPU check into multiple files.

Those are just the obvious ideas.

1. Did you read my post before replying?
2. Who runs sfc without reason? And if reason, who stops you from creating an image when your system is healthy, just updated, and then patched with this?
3. What files? How? More dark magic?

Anyway
You don't wanna use it, don't. Bit of care and everyone else is fine i'd think.

"Official Support"? who cares? I haven't run Win Update on my 7.1 for years.... Still running strong, and without any issues. Screw em.

This.

I don't understand why people have this double obsession.. on one hand, they fear the updating process (with good reason, i sure as hell do too, reverts half my hacks), on the other they appear to want it anyway. Why? And considering the level of expertise of some these people.. honestly, just.. why?

If it works, don't fix it. Software 101.

 

[syrup]

If I installed my copies of Windows 98SE, XP or Vista on my Ryzen system I wouldn't get any updates either.

Provided the driver support was there, you could install service packs and updates that were issued through to the end of the extended support period.

Blocking updates in the manner they're now doing is different. The extended support periods for Windows 7 and 8.1 run until 2020 and 2023 respectively. Hardware manufacturers are still supporting 7 and 8.1 on current products (e.g. Z270 boards).

So it appears to be another dirty tactic to push reluctant users to Windows 10, in this case by artificially and prematurely limiting the hardware options for Windows 7 and 8.1.