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

You need to login to view this posts content.

 

Kaspersky Anti-Virus 2013 and Malwarebytes Anti-Malware Pro say this file(s) are clean- but do not take my/their word for it.

Anyways, if this doesn't

then why bother patching if its only going to lead to problems? Seems like a hassle.

 

There are quite a number of people on old CPUs, they may wish to try out win8/win8.1 to see if they like it(then buy a new PC); this would help them to test-run and decide. Many people have said and @Jan1 has emphasized: don't use it as your main OS.

 

You need to login to view this posts content.

 

This is an interesting project, but can you tell me what problem it actually solves?
What cpu is unable to load win8?
Someone using an old cyrix chip trying to load win8?

 

That would interest me sometimes, how do you exactly the patching?


Since one can make a small Tut?

 

Older P4's as an example!!

 

Its so sad, the older higher end P4's are still up to par with todays CPU's for moderate work!!

 

Thanks for the great tool. i am having trouble finding a graphics driver for intel 915 (the hacks i found work for Windows 7 but fail for Win8) anyobe know a workaround? since i don't have a graphics driver there's no sleep or hibernate.

Thanks!

 

lol ... only workaround for intel crap is to wait until them wake up. it is a mess since a while

 

My good old IBM T42 is going to run Windows 8 in a while. ^^

 

Na problem is it never sleeps, so no waking involved

 

It isn't so simple:
For example, if you will patch only NX (majority of iP4 compatibility problems), Windows 8 will find out by other mechanisms correctly, that NX isn't available and the settings of DEP in \Control panels\System will be grayed out and inactive. IMHO in this case, there is no reason for BSOD (patching NX is 100% safe).

View attachment 22958

If the CPU hasn't PAE and SSE2, it means, that it is VERY old and Windows 8 will run so slowly, that they can't be used anyway. (BTW: patching SSE2 is VERY safe (99%), while IMHO patching PAE isn't safe).

Patching CMPXCHG16B is feature for testing only since it is true, that it isn't safe.

Key is, if Jan will be able to support future versions of DLLs (for example W8-1 RTM).

On older notebooks, you will also face missing XPDM graphic driver model in W8, so you have to try to find WDDM v1-x drivers from vendor or use "Standard VGA WDDM v1-2" driver (BTW: I have hibernation and wake up support with it on my ancient nb).

 

Just why disabling some extremly important feature such as PatchGuard sounds crazy...

 

Awesome, thanks!

So this should let me run 8 on my Athlon XP 2500+ ? (it was able to run the developer preview fine, but the final version chokes because of no nx bit)

 

KB2859537 (W8-0 x32 Only) updates NTOSKRNL.EXE to version v6-2-9200-16659.
Patch v1-4 will handle that.

 

I've just tested this.
Someone here said that P4 Prescott runs Windows 8, but please take into account that not all Prescott will run W8.
NX-bit was implemented in later P4 Prescott CPU's, not in the "A" Prescott's.

So it was an old rig, P4 Prescott 2.4Ghz, 1MB L2 and 533Mhz FSB. 2GB RAM DDR.
Board Intel D865PERL, videocard Geforce FX5200.
Applied the W8 pro image from within some Win7 PE, patched both Winload and Ntoskrn files.
Modified the bootstore so no signature nags, and off it went.

I must say, it runs faster than anything I had on that rig before. It's just like getting a new PC, although this one has almost passed the 10 year mark.
Definitely very happy with the result, not going back to W7.

Cheers.

 

Hopefully when win8.1 RTM is out, some guys would test and see if patch works for it too.

 

You need to login to view this posts content.

 

Yup, and after that , "remove winload win8.1 X64 check", and then apply the BCDedit command to disable integrity check.