The unofficial patch from a developer calling him or herself ‘Zeffy’ on GitHub targets those running very new CPUs on older versions of Windows. Windows 7 and 8 are still supported with updates, but Microsoft has started blocking non-security updates for systems that run Intel 7th-Generation Kaby Lake processors, AMD “Bristol Ridge” Rizen chips, or the Qualcomm 8996 (Snapdragon 820 and 821) SoC.
If you try to install the new April patches for Windows 7 or 8.1 on these systems, it will fail with error code 8024003. The only solution Microsoft offers for that error is to upgrade to Windows 10. To be clear, there does not seem to be any legitimate reason to block these updates. Microsoft just really, really wants you to use Windows 10.
The Zeffy patch goes after a change Microsoft introduced in March that identifies the system’s CPU. As the changelog explained at the time, the patch “Enabled detection of processor generation and hardware support when PC tries to scan or download updates through Windows Update.” Zeffy is very clear on his dislike for Windows 10 when he calls this “essentially a giant middle finger to anyone who dare not ‘upgrade’ to the steaming pile of garbage known as Windows 10.”
Should you install Zeffy’s fix, two functions found in wuaueng.dll update code will be disabled. It is these functions, IsCPUSupported(void) and IsDeviceServiceable(void), that are responsible for blocking the update. This patch reportedly does the job, allowing you to install the previously blocked non-security updates on Windows 7 and 8.1 on affected systems. However, the Zeffy patch will need to be reapplied every time wuaueng.dll is updated by Microsoft. It’s also possible a future update will try to prevent this workaround. Then, maybe someone will release another custom patch, Microsoft will block that one, and then the whole thing starts all over.
The patch download is less than a megabyte and installs in a single step. The source code is available, so it’s unlikely Zeffy is up to anything shady. That said, using a third-party tool to modify Windows system files is not without risk.
Just wanted to give this a bump (should be a STICKY), and say that Zeffy has modified the patch so that it no longer modifies the system files as before, but it requires a permanent folder.
- At system boot the
wufucscheduled task runs as the
wufucdetermines what service host group process the Windows Update service runs in (typically
netsvcs), and injects itself into it.
- Once injected, it applies a hook to
LoadLibraryExthat automatically patches
wuaueng.dllwhen it is loaded.
- Any previously loaded
wuaueng.dllis also patched.
And I also think that he missed a massive opportunity to name it "wufucu"...
I may give this a go.. i basically did not install march and aprils microslop, and then went in and removed some micro diagnostic and hardware detection schedulers. then disabled updates but, hmmm .
usually microslop finds the work around like you said and then you need to reinstall.. so i am curious if i install this patch and then simply copy the good updateeng.dll file and replace it every month instead of reinstalling entire patch if that would work. its just a thought i had.. but that may not fix the registry.
thanks for the patch ..
i am not happy with AMD and microcrap shaking hands to allow this too happen to start with. and with microlimp still owing me 3 years of support as legally bound too. i feel they owe me some cash$ .. owell microdump is getting more and more lawsuites all the time over win10 so i am happy.!
I caught wind microdollars may consider making a new windows again since they have nothing to sell.. microlimp expected the windows store to bring the money in, and noone is buying lol.. so lets hope or by then i am sure either redhat or linux mint will be on top since they are developing so fast, with people in droves going that route and not windows.