This tool (which is really a simple DLL library) is given "AS IS" without any warranty for testing/academical purposes only. It is designed to allow updates to be installed using Windows Update on Windows 7 and Windows 8.1 systems running Intel Kaby Lake and AMD Ryzen processors or the later ones.
Microsoft recently disallowed any updates to be installed on such systems saying, that the company no longer supports older operating systems on the newest processors. This tool circumvents that limitation.
As mentioned above – this tool comes with no warranty from the author. I do not recommend to use it on any production environment or any device which is used for normal/regular work or any device having any valuable data stored on it.
Because any patches starting from April 2017 for Windows 7 and Windows 8.1 are likely not to be tested by Microsoft for working properly with the newest processors, this tool can potentially render such systems unusable or cause loss of data. Why? Because it will allow such potentially non-tested and non-compatible updates to be installed on such systems.
As a result of the above you use this tool completely at your own risk!!!
64 bit Windows 7 or Windows 8.1 systems. 32 bit operating systems are currently not supported.
To install or update just download the "Deployment" folder and run "install.bat" with administrator rights (right click on the file and choose "Run As Administrator"). Follow the on screen instructions.
To uninstall just run "uninstall.bat" with administrator rights (right click on the file and choose "Run As Administrator") from the folder where you have previously downloaded the "Deployment" folder. Follow the on-screen instructions.
-
Download or build WuaCpuFix64.dll file and place it in %systemroot%\system32\ folder.
-
Open registry editor and navigate to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wuauserv\Parameters
-
Double-click the "ServiceDLL" registry key and set its value to "%systemroot%\system32\wuacpufix64.dll" path.
-
Reboot computer.
-
Stop Windows Update service.
-
Download or build WuaCpuFix64.dll file and place it in %systemroot%\system32\ folder.
-
Start Windows Update service.
-
If you still see a "hardware not supported" error message in Windows Update then reboot computer.
This tool is being licensed under GNU GPL License version 3.
I was inspired to create this tool based on findings made by Zeffy in his project called kb4012218-19 (https://github.com/zeffy/kb4012218-19). He did a great job finding the heart of the mechanism Microsoft had introduced for limiting the CPU support in Windows Update. However, in his solution, one thing was dirty for me - direct modification of system files, which I simply do not want to do. I tried to do the same thing as he but trying to not modify a single byte on any of the system files. I think I managed to do so here.
My tool is simply a dll file which acts as a proxy to the original dll file called "wuaueng.dll" used by Windows Update service. Thanks to the registry setting mentioned in the "manual installation" section it is being loaded by the svchost.exe process directly to its memory instead of the original "wuaueng.dll" file.
When that dll is loaded and launched by svchost.exe process it then loads the original library and patches it in memory (by making a FAR JUMP from the original IsCpuSupported function to my function which always returns 1) before allowing its code to execute. Thanks to that no system files are being modified on disk by this tool. Such behavior preserves all integrity checks made by the system and potentially does not violate the EULA of Windows. However I am not a lawyer, so I am not sure about that.
Any feedback is welcome. Feel free to issue bug reports, feature or improvement suggestions.
To build the project you have to install either Visual Studio 2013 Community or Visual Studio 2015 Community editions together with MFC C++ Libraries.
Then just open the WuaCpuFix.sln file and build the solution. When building in Release mode the compiled dll will automatically be copied into the Deployment folder ready for installation.
