Полигон-2

[q]

Зачем вообще ставить эту гадость?

[/q]

[q]

Windows 8 CPU Feature Patch (Bypass Windows 8 CPU feature checks)



W8CPUFeaturePatch can be used to bypass the checks for the availability of the following CPU features in Windows 8: PAE, NX, SSE2, CMPXCHG16B.

Which patches do I need?

Click Remove PAE check if your CPU doesn't support PAE
If your CPU doesn't support SSE2, NX or both (missing PAE support implies missing NX support) click Remove SSE2 and NX check
To enable support for more than one logical CPU core after patching NX, click Fix hyper-threading in hal.dll and Fix hyper-threading in halmacpi.dll
If you want to get rid of the digital signature warning on boot after applying one of the patches above, click Remove winload patchguard x86
Click Remove various CPU feature checks in Windows 8.1 x64 if you want to skip some CPU feature checks (like CMPXCHG16B support) in Windows 8.1 x64
Click Remove winload patchguard of Windows 8.1 x64 to skip the digital signature warning that appears on boot after applying the Windows 8.1 x64 check.



How to apply the patches?
Create an ISO image by following FaiKee's guide or apply the patches from Windows PE.
W8CPUFeaturePatch.exe and W8CPUFeaturePatch x64.exe do the same things. The only difference is that W8CPUFeaturePatch x64.exe is compiled for x64. Use it if you want to patch from Windows PE x64 since you can't run 32 bit applications on Windows PE x64.

Notes:

The patch does not make Windows 8 compatible to your CPU since it only bypasses the compatibility checks. This means that if Windows 8 tries to use one of the features, your computer will probably crash. For example, if you applied the CMPXCHG16B patch, a 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED) BSOD with error code 0xFFFFFFFFC000001D (STATUS_ILLEGAL_INSTRUCTION) could occur if a CMPXCHG16B instruction is attempted to be executed. The only relatively safe patches are the NX and the hal/halmacpi patch.
The tool cannot predict how the feature checks will be implemented in future file versions of the files to be patched, which means that there is a risk that future file versions cannot be patched
For the reasons above, don't use these patches on your main OS!
If Windows is stuck at the spinning dots on boot, you have to disable hyper-threading or to patch hal.dll and halmacpi.dll
You have to run bcdedit /set {default} NoIntegrityChecks Yes if you patched winload.exe

[/q]