Ah. I thought that this only had to be completed upon initial installation, and not every time you reapply the patch. I'm definitely trying this as soon as I get home - I'll let you know if this works or not! Thanks a lot! EDIT: That worked like a charm. What an awesome community - you guys are the best. Thanks again!
On your place I would plug that system hdd via USB to another computer as a 2nd (3rd... - non-system) drive. Then you should check for example via Total Commander file compare, if all (four) files were really patched successfully. You will need original files for the comparison.
can't patch with the new GUI patcher! I had already patched and installed win8 with your old patcher. Now that you have updated it with new patcher which resolves hyper threading, I tried it and it gives me an error "CreateFile failed" !!! I copied the file to E:\ which is my system partition. Then I ran the W8CPUFeaturePatch.exe. When I click [Remove SSE2 and NX check] OR [Fix hyper-threading in hal.dll] OR [Fix hyper-threading in halmacpi.dll] which are the ones I need, it opens up a file explorer and asks me to direct to ntoskrnl.exe, hal.dll, halmacpi.dll respectively. Was the file explorer supposed to open up like that ???? Or did it happened because my system partition is E:\ and not C:\ ???? Pls help me I want to get rid of the driver signature check and enable hyperthreading!
You need to boot to that system to patch it. If you boot to that system, it should change it to C:, not E:.
Ok, I have just did.The files are corectly patched. In windows--> system 32, I have 1 winload.exe, 1 winload.exe.bak and 1 winload.exe.bak2, all same size, 1.01 mb but all diferent hashes. One is DC2C9EB6900CC46AF62D5B0D27885903, the other 9275893085FD1574F80E8E3C2096CFEE and the third is AAF6D9985C1CB8FAE640B4B3DF08DE5B. These are the MD5. Same way, hal.dll and halmacpi.dll have different hashes with backups... I know that I am doing something wrong, since everyone else has managed it. WHAT????
I wonder if steps up to 10 can be performed being loged on a Windows 8 x64. I know that on the Windows instalation CD there is an ”boot wim” file. If this is the one that blocks the boot of the instalation CD, maybe this file could be edited to edit the official iso itself, to make it bootable, and also add the patches to it, and also have it as a recovery medium, if necesary. By the way, if you disable recovery, in case I need to enter Safe Mode, will I still be able to do it?
why don't we make a batch file (very hard to put in exactly the commands if you cant copy and paste): %~dp0imagex.exe /apply %~dp0install.wim 2 W:\ pause copy %~dp0W8CPUFeaturePatch.exe W:\ pause W:\W8CPUFeaturePatch.exe pause bcdboot W:\Windows /s W: pause bootsect /nt60 W: /force /mbr bcdedit /set {default} NoIntegrityChecks Yes bcdedit /set {default} RecoveryEnabled No rem bcdedit /store W:\Boot\BCD /set {default} NoIntegrityChecks Yes rem bcdedit /store W:\Boot\BCD /set {default} RecoveryEnabled No pause wpeutil reboot
Tested on VMWare Player, tring to install Windows Server 2012 r2 (Windows 8.1 x64 kernel), using a Windows Server 2008 r2 (Windows 7 x64 kernel) instalation dvd. To be able to load the W8CPUFeaturePatch x64, I have deleted the blank space and changed the file name into W8CPUFeaturePatchx64 (This is the right file, right?). All seemed to have worked according to plan. On first boot, Windows crashed with error code 0x0000001E . Parameters 0xFFFFFFFFC000001D, 0xFFFFF800E2174A76, 0xFFFFF800E2369A80, 0xFFFFFA800619BBO . What could this mean? Has anybody else tried this patch for Windows 8.1 x64?
It seems a CMPXCHG16B instruction was about to be executed. This could also happen in Windows 8.1 x64.
hi for all i need help .. i try install .. i have patched for pae and nx but get started say HAL_INITIALIZATION_FAILED ... how fix this _ plz is a laptop toshiba portege m200 greetings for all sorry for my english
all ready succesfull install.. the last error is but i try install win 8.1 prevew .. now have installed win8 pro..work fine with screen wacon with pen XD WTF ... loadin windows effect ..with nvidia fx go 5200 32 mb ram ddr1 at screen resolution 1400x1050 O.O
Tested again, with Windows 8.1 x64 this time. Same error code, this time with parameters 0xFFFFFFFFC000001D, 0xFFFFF800CA971A76, 0xFFFFF800CAB66A80, 0xFFFFFA800619BBE0 . I did not used the patches destined to Windows 8 x86 and the ones regarding hal.dll and halmacpi.dll, of course.