# PAE patch updated for Windows 10

This patch allows you to use more than 3/4GB of RAM on an x86 Windows system. Works on Windows Vista SP2, Windows 7 SP0, Windows 7 SP1, Windows 8, Windows 8.1 and Windows 10 (build 10586). Instructions and source code included.

Source code: https://github.com/wj32/PatchPae2

Before using this patch, make sure you have fully removed any other “RAM patches” you may have used. This patch does NOT enable test signing mode and does NOT add any watermarks.

Note: I do not offer any support for this. If this did not work for you, either:

• You cannot follow instructions correctly, or

## 368 responses

1. eu says:

not working with win10 1511 and NVidia driver 🙁 error in video driver

• pied-piper says:

Unfortunately not working…

• Aether says:

Windows 10 1151 known as windows 10 threshold 2, although this windows same built 10586

2. Don Williams says:

Unsupported kernel, was the message that I got.

3. Aether says:

Unsupported kernel version: 10240

• jcguzman says:

I have the same problem. Any solution??

4. Concerned says:

• wj32 says:

There is no virus.

• viktor says:

HI wj32 Whether they will be made to the newer version of the Patch for Windows 10 kernel versions?

5. ravikwow says:

Don’t work with intel graphics driver
http://i67.tinypic.com/2cxur8w.jpg
If intel driver remove and install standart vga driver then system work fine but resolution screen low.

6. Terry says:

Intel HD and Nvidia graphics are known issues. If you have either of these in a PC and you want to use the patch, then it is best to use another video card with different chipsets, eg ATI Radeon.

• Dr. Michael König says:

See my posts of Feb.2017: You can try old drivers. I had success with the NVidia- Win7-driver of 12-9-2013.

7. chris says:

I cannot get the loader to update, states Failed every time in windows 7. I tried the patchpae and patchpae2 and both fail patching the loader, kernel seems ok.

• Saied says:

I have same issue

8. kitt says:

I’ve tried to install this patch numerous times and using the latest 3 updates. I have nvidia card, and with the patch booted in screen froze with ‘windows shutting down’, yet when I start the parch in safe mode, it boots fine, and shows all my 8 gb ram. in task manager. It appears to be a video card issue as I know it works with the default vga driver in safe mode.

Is there going to be any more work on this? Thank you.

• Terry says:

The only way you will get the patch to work is to replace your video card with one having other than Nvidia chipsets, eg ATI Radeon , as already mentioned.

• Dr. Michael König says:

Or testing old NVidia-drivers, see my posts of Feb.2017

9. kitt says:

Still trying. I’ll try the very newest patch today or tomorrow. On the patch boot, after the normal animated windows loading screen I get half a correct windows ‘welcome’ screen and jagged half white image with little diamonds and weird patterns and no movement. Must hit reset button. Again, in safe mode, I see all 8 gigs and runs fine. Misconfig has memory unchecked as well. Maybe I could try going back 2 years in nvidia graphics drivers… they only have been adding support for 3d and physics, both of which I don’t use…Worth a try maybe.
Any thoughts?

10. VeganChocolate says:

WARNING!!

There’s fair chance this site has been compromised to some extent.

This new Windows 10 version of the patch is seen as heavily infected by anti-malware scanners.

If you use the Internet Archive Wayback Machine you can download the older versions of the patch (before someone replaced the link URL’s to direct people to the new infected patch).

Those older versions scan completely clean.

The original author of the patch spoke perfect English but the guy claiming to the be author and defending the infected patch in the comment section (using the name evgeny) speaks English poorly.

I looks like he may have the ability to upload infected files but not the ability to disable or remove negative/revealing comments.

It’s also possible that, in the process of making the patch work with Windows 10, legitimate changes needed to be made that trigger heuristics flags in anti-malware scanners. It’s also possible that the older versions also used to trigger those flags but have since been cleared as producers of false positives in the anti-malware databases.

In conclusion, if this new patch it legitimate and not actually infected, I apologize, but there are too many red flags here and I don’t have the C knowledge to check the source code, or the tools to recompile it for comparison. So, I’ll be sticking with the older versions accessible via the Wayback Machine.

• Terry says:

VeganChocolate

You are getting confused. The (unofficial) Win 10 pae patch by evgeny who AFAIK is Russian, has nothing to do whatsoever with this site owner’s (wj32) patch. The patches are completely separate and independent of one another. The evgeny patch for Win 10 was posted before the latest wj32 Win 10 patch became available.

However I have used both with no problems and with no virus’s showing up in either.

The file link posted by escape75 back in November is an executable program that uses the evegeny patch for win 10 and installs it automatically, no manual input is required except to run the program.

• wj32 says:

evgeny (who I do not have any affiliation with) does not have the ability to upload files to my website. I have not deleted negative comments such as yours because doing so serves no purpose to me.

Once again, there is no virus in the file. AV heuristics naturally come up with false positives. This is one of them.

11. Silver says:

Unfortunately it crushes into BSOD “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” on start, so Windows can’t even dumb anything.

If you are having the same issue, uninstall physical RAM — then you will be able to boot and disable this modification.

12. Kitt says:

Okay, First, this wj32 and patch has been around quite some time and appears to be the most dependable, robust and actively updated one.
There are no viruses in any of this code, but due to how it’s accessing kernals (with your permission) a decent virus/malware should detect something. This is normal, but it’s actually good people pay attention to this sort of thing.
From all my reading and experimenting, I will submit there’s a nvidia and other graphic driver problems.
I’m going to try loading some legacy win XP graphic drivers and test if there’s a different screen upon booting the pae boot option.

I am going this route before screwing around with microsoft updates and such. I believe it’s entirely possible that microsoft has put in code to distrupt this patch from working as they want people to buy another OS like the 64 bit. It’s all marketing as far as I’m concerned. Why else would larger memory work on win 2000 and some other older win OS’s natively and not the newer ones. I feel just reloading graphic drivers has much less potential for problems.

I will report when I’ve got something concrete to say.

13. kitt says:

I had to use a restore point after messing with too many graphic drivers and created another unrelated issue to the patch.. after fixing my created problem, I read to check for any ram type 3rd party or memory managers running at the same time as pae. I forgot I had a ram drive program resident from before. I disabled that and when I did second paepatch boot option I saw a lower res windows screen and it comes up ‘windows doing repair’ and it attempts to repair. I cancel and reboot with same thing in loop.
This is different than when the ram program was running so maybe I’m getting somewhere.
I will try the nvidia drivers from 2012 or so for win 7, this time with a restore point…
will update results. Always ALWAYS make sure to install this as a second boot option.

wj32 clearly designed an excellent almost fool proof program by giving you the dual boot option…USE IT!!!

14. Eric says:

hi? does the zip really contains virus? when i downloaded it, my antivirus always blocking it due to malware. Can someone give me an assurance that this has no virus included at all??

TIA..

• Saied says:

I have same issue

15. Works very fine on 2 PC with W10 build 10586.
Both PC are with AMD/ATI graphics.
According to Bitdefender, no virus inside.
Thank you very much!
BR
akapuma

16. KJT says:

Working fine for me. Winload patch doesn’t work: But signing the patched kernel as explained at unawave.de & bootmenu as explained there fixed all. Remove watermark with watermark-remover.

BTW: For my Nvidia Grafic card I use driver version 332.21. The newer ones don’t know about PAE.

All is running fine like a charm now. 8 Gbyte used by W7/32

KJT

• Hello, I tried wj32 patch early and could not get it to work, tried it again today and it failed to patch winload.exe, so i gave up.
i saw your comment and tried your tool, worked flawless, gj.(win 7 sp1, AMD vga)
I’m thankfully to both wj32 and you for the nice work.

• Sir, your patch saved the day. It works flawlessly (so far) for Windows 7 SP1 Professional in a vmware box.

• jackd says:

I tried this twice on my windows home 10.. and it just does not work. I get the “something broken” result each time. I followed the instructions for Pae2, but used the pae3 exe to execute them. The files were created, I checked that after running the commands. But upon restart, it won’t boot into this. My windows is 14393. is there some kind of log or something I can check to figure out what the problem might be?

• jackd says:

Sorry, it’s windows 10 pro 32 bit version and specifically 14393.693

17. asdfr says:

hello
patch no work win v1511 Build 10586 auto reboot

18. Dean says:

Works 100% perfect! Many, many, but many thanks. No problems at all, patch installation perfect, no virus (I have Bitdefender), no nothing. Less than 5 minutes. Fantastic! Thanks again! PS: I also use EmptyStandbyList (works perfectly) in a batch file. Please, I would like to ask if besides EmptyStandbyList, I need other cmd command or program in order to clean my RAM. Thanks!

• Dean says:

PS2: I installed PAE patch on Windows 10 version 1511 build 10586.164 with 4GB RAM.

19. asdfr says:

patch no work win v1511 Build 10586 boot menu and press f8 auto reboot

windows isnot boot

20. Igor says:

Failed.

• Saied says:

I have same problem

21. asdfr says:

hello
bypass PAE/NX/SSE2 check

22. asdfr says:

load windows 10 from old pc pentium 3 and 4

23. asdfr says:

help me
boot Windows 10 Pro Insider Preview 14295 from old pc pentium 4

24. Matheus says:

After some unsuccessful attempts, I downgrade the intel chipset g45 drivers from windows 7 to windows xp, Then I reinstalled PatchPae2 and now works. Thank you!

25. Installed okay, but doesnt seem to work on Win7 Home on old HP 6715s (AMD Turion X2 processor). I believe the install went okay, here’s bcdedit /enum output

——————-
identifier {current}
device partition=C:
description Windows (PAE Patched)
locale en-US
recoverysequence {d7f21e6c-f69c-11e5-82e3-8f7716722112}
truncatememory 0x100000000
recoveryenabled Yes
nointegritychecks Yes
testsigning No
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
kernel ntoskrnx.exe
resumeobject {68de8738-f69c-11e5-82e3-8f7716722112}
nx OptIn
numproc 2
usefirmwarepcisettings No
sos Yes

26. Pablo says:

I followed instructions and it failed to patch the Windows Loader on Windows 7 Professional 32 bit with SP1 (4GB RAM). I just get the Failed message after trying to patch the loader but patching the kernel is fine. I looked in the source code and I guess some hex codes weren’t lining up which is why it didn’t patch properly? Any way we can resolve this issue?

• Saied says:

I have same issue

27. Please don’t use this patch. It is very hard to get rid of it & to boot to the original Windows 10 profile. (After Installing.)

• christian says:

why should you get rid of it…I’ve been using it for ages and worked wonderfully

28. safdf says:

patch oder version win 10 pro and enterprize all builld

• christian says:

you better off a clean install mate….

29. Hi. Thanks for everything. I have a problem in executing the instructions: you said “make sure the directory is in fact system 32”. Then C:\WherePatchPaeis etc.. , Do you mean I have to change directory from System32 back to C:? Also and since I am not a computer wiz, do I copy the whole command line “PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe ” as is after changing to the patch directory?
I have Windows 10 pro, and the message I am getting is: “unable to copy file: The system cannot find the file specified.” Can you please help? I need specific instructions step by step please. Thanks a million

• christian says:

No, check and make sure it is c:/system32 means that inside command prompt window you will actually read the line displaying: “C:/system32>” at this point you indeed copy/paste the whole line exactly as you wrote and press “Enter”.
Remember the command prompt must be with admin rights (right-click the cmd icon and choose “execute as admin”) and remember to substitute the path where you actually have your patchpae2 folder.
Hope it helped…sorry for bad english 😉

30. Darkscepter says:

windows 10 cant find the file path hellp

31. Escape75 says:

Just a quick update to my PatchPAE, now using fix128 0.43
PureBasic used to encapsulate the .cmd (source included)

Should work on Windows 7, 8, 8.1 and 10 (x86 & ATI card required)

https://filescdn.com/mkic9tcyrfsp

• Al says:

Your patch works only for ATI card? I’ve a Intel chipset and nVidia card.

• Escape75 says:

Well it works with anything, but on nvidia and intel you need old drivers 🙂

• Al says:

Thanks, just as I thought 🙁 will be there any patch for new or recent drivers?

• Max999 says:

Escape75, the file is no more available!

Thank you!

• Max999 says:

32. Christian says:

can anyone help me.
i’ve succesfully patched my windows 7, but it only works when i boot with safe mode (it reads 8 GB RAM)
if i boot windows on regular basis, it always stuck on black screen after windows logo (i supposed it’s because of the VGA drivers)

I’m using NVIDIA GeForce GTX 650 and processor Core i5 – 3330

• Al says:

I think that the problem is always the same. nvidia driver.

33. Liam says:

You should uninstall the following patch on Windows7: KB3153171, KB3146706, KB3147071
@wj32, is it possible to update the patch so it works with the new patches?

34. Lucas says:

This patch did not work for me, seems to be just a skin, space engineers for example need 8GB of RAM to run, I can not even load a world, the game closes before for lack of memory, when I have 8GB on my pc and not can not install 64-bit due to driver incompatibility (gives BSOD) so I’m using this patch, but appears to be a skin as it did no good to me, it is the same thing as being with 4GB of RAM.

35. Avg says:

I have the current build 14366. On reboot it takes windows into auto restore and fails in doing so. Is there a new patch coming ? Would be great help

• Liam says:

This means that any of the following patches: KB3153171, KB3146706, KB3147071 or any other new patches that adjust the kernel in such a way that it won’t boot.

36. You can try Long Path Took, it helped me with the same issues.

• Liam says:

Can you explain how to use this and what it is?

37. Boogie says:

Can we get a new update for the latest windows 10 release? Official build 14393, anniversary update

• MtnCowboy says:

I second this motion. Works fabulous with win 7 -win 10 1511…. But I haven’t been able to get it to work with the new 1607 build…..

38. Janik says:

Updated Windows 10 yesterday.
The Patch is gone and I get “unsupported kernel version 14393” error when I try to patch again…

39. Nur says:

it’s not work in windows 10.0.14393 Build 14393

40. ichbins says:

Windows 10 Build 14393:
By patching I get the “unsupported kernel version 14393” error too.

41. antscmat says:

Windows 10 Build 14393:
By patching I get the “unsupported kernel version 14393” error

42. anana says:

will you support win10 14393 please? thank you

43. evgeny says:

– added support for Vista SP0, 7 SP1 with KB3033929+,
– Windows XP SP2/SP3,
– Windows 10 (10240/10586/14393)
– Server 2003 SP1/SP2/SP2R2, Server 2008 SP1
– Server/Windows 2000 SP4 and 2000 SP4 with KernelEx by blackwingcat
– Windows Longhorn (4093 stable), Visual C++ 2010 Redistributable required

• after applying this patch. When started Win 10 it says error in starting windows and tries to repair itself. Which it is not able to do. It then gives various boot options . So started in safe mode, carried out system restore and deleted the patch install leftovers.

• Applied patch. Started Win 10 X86 version. Start-up says error in starting up and goes into repair mode.
Unable to repair it gives various start up options like re booting , system restore etc.
Carried out system restore and deleted residual patch files.
Additional information my OS build is WIN 10 X86 Build 14393.51

• Applied patch. Started Win 10 X86 version. Start-up says error in starting up and goes into repair mode.
Unable to repair it gives various start up options like re booting , system restore etc.
Carried out system restore and deleted residual patch files.
Additional information my OS build is WIN 10 X86 Build 14393.51

• zaza says:

ive the same problem

• Re applied patch.
Now win 10 working with 6.5 GB Total Physical Memory.
Many Thanks.

• Brian says:

Are there any step by syep instructions please, or are they the same as PatchPae2?
Thanks

• j212 says:

can you check the latest windows 10 build14393.693 …It’s not working for me on this particular build.

• Evgeny, your PatchPae3 doesn’t support patching Windows 10 Creators Update (fiel ver. 15063) winload.exe. Could you either update your patchpae or publish source to experienced programmers?

44. Terry says:

Many thanks evgeny. Works well with Windows 10 14393, no problems.

45. ichbins says:

Windows 10 Build 14393:
Everything is working fine.
Thanks.

46. Al says:

no hope for nvidia cards?

47. Very Happy work fine in Windows 10 Build 14393, tank you evgeny, step by step.

48. Escorpiom says:

I just found out that this doesn’t work for Windows 10 LTSB build 14393. The kernel and winload are different in size, as compared to CB kernels. So in fact the patch only copies the two files without any changes being made to the files itself.
I guess the patch checks the checksum, if it doesn’t match no patching is done.
The patcher however says “patched”, incorrectly so.
Evgeny, can you add support for LTSB builds?

Cheers.

• evgeny says:

Patch prints “Fail” and exitcode != 0 in this case exactly as wj32.
Checksum never checked.

• evgeny says:

I just install LTSB 14393 and patch works fine.

• Zzzz says:

What i did wrong? I follow strictly the list and in the end of process i get the repair mode when try to load patched boot, and attempts to fix the boot doesnt help. I running win 10 14393.82

49. korg says:

Working fine on my Windows 10 Build 14393. Thank you evegeny !

• viktor says:

Hi korg for me not work on Windows 10 Build 14393 32 bit where is my fault ? Thanks Advance.
the screenshot is here:
imgur.com/a/eoUkx

• Terry says:

Viktor, you are using patchpae2.exe, this does not work with build 14393.

Cheers

50. pls tutorial how to install pae patch windows 10

• Execute the exe-file from evgeny in a window. It will print a long and good help.
br
akapuma

51. Applied patch. Started Win 10 X86 version. Start-up says error in starting up and goes into repair mode.
Unable to repair it gives various start up options like re booting , system restore etc.
Carried out system restore and deleted residual patch files.
Additional information my OS build is WIN 10 X86 Build 14393.51

52. Applied patch. Started Win 10 X86 version. Start-up says error in starting up and goes into repair mode.
Unable to repair it gives various start up options like re booting , system restore etc.
Carried out system restore and deleted residual patch files.
Additional information my OS build is WIN 10 X86 Build 14393.51

MY PC is Dell Vostro 3560- Processor Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 2101 Mhz, 4 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 2.39 GB
Available Physical Memory 418 MB
Total Virtual Memory 6.01 GB
Available Virtual Memory 2.48 GB
Page File Space 3.63 GB

53. Re applied patch.
Now win 10 working with 6.5 GB Total Physical Memory.
Many Thanks.

• Zzzz says:

How did you deal with it? What you do? I follow the list but in the end i get into repair mode as you

• Zzzz says:

In my case the problem was in missing winloadp.exe file, i just copied winload file and add p to the name. After that i done the list steps, and got it working.

54. Janik says:

wj32 are you working on a 14393-patch?
I am still waiting for your version 🙂

• akapuma says:

Why you are not using patch from evgeny? Works fine with 14393.

• Janik says:

Because I do not like what evgeny is doing here…
This ist wj32.org so why does evgeny publish his version here at all???

• Brian Brackley says:

• Brian says:

I am running Windows 10 Pro version 14393 with the evgeny patch V3. All i am asking for is a step by step guide please to insatll it should it be different than the set up for V2 as it is not working and I must have done something wrong.

55. daniel says:

windows10 10586， bootloader ， error， can not continue to boot

56. Terry says:

With the latest batch of Windows 10 updates, people may find they have to run “step 3” again to ensure the latest version of the kernel is installed. You will probably have to run unpatched windows in order to get Windows to load.

57. I started the last windows update. The kernel was updated from 14393.103 to 14393.187. After this, I got a reboot loop. I solved the problem as follows:
– Boot without PAE patch.
– Patch the new kernel 14393.187
– Reboot with PAE patch.
After this, everything works fine.
Best regards
akapuma

58. Yuri says:

After updating Windows 10 Pro to Version 10.0.14393 Build 14393 (anniversary update), PAE patch can no longer be applied: Access denied and invitattion for new version is displayed: http://i.imgur.com/itmp7Pq.png

I have to remove the patch when Win was updating or else experiencing never ending cycle of rebooting and/or recovering previous OS version.

Kind regards

• Yuri says:

When moving PatchPae exe to c: drive: Unsupported kernel version: 14393

59. For 14393, use PatchPae3, not PatchPae2.

BR

akapuma

• Yuri says:

• See post from evgeny, August 16, 2016 at 8:56 am, in this thread.

BR akapuma

• Yuri says:

You are very kind, thank you!
I have tried it. No success.
Unable to copy file: Access is denied.
Here is my screenshot: http://i.imgur.com/HmawomF.png

I’ve ran my command prompt as administrator.

Any hint how to resolve please?

• evgeny says:

the patch tells You “i can’t copy new patced kernel, becouse file already exist”
delete previous copy of “ntoskrnx.exe” and try again.

60. Yuri says:

Thank you evgeny.. This was true. I have deleted it, double check where my 3 is, tried again like this:

C:\Windows\System32>C:\PatchPae2\PatchPAE3.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

… and get this below:

PatchPAE by wj32:
– support for Windows Vista SP1/SP2, 7, 7 SP1, 8, 8.1
– Server 2008 SP2
evgen_b MOD:
– added support for Vista SP0, 7 SP1 with KB3033929+,
– Windows XP SP2/SP3,
– Windows 10 (10240/10586/14393)
– Server 2003 SP1/SP2/SP2R2, Server 2008 SP1
– Server/Windows 2000 SP4 and 2000 SP4 with KernelEx by blackwingcat
– Windows Longhorn (4093 stable), Visual C++ 2010 Redistributable required
Version: 0.0.0.45

Unable to copy file: The system cannot find the file specified.

• evgeny says:

in Windows 8…10 kernel file name is “ntoskrnl.exe” instead “ntkrnlpa.exe”
run patchpae3.exe without arguments and You will see step-3 from help

61. Have run V3 on W10 14393. Everything gives the correct responses in bdcedit etc, but it doesn’t appear to work, I still have less that 3G usable of the 8G installed. It worked fine on the previous build.

62. Fixed it! Had to run “bcdedit /set {id} kernel ntknew.exe”. That put a specific kernel entry in the Boot Loader and that appears to have done the trick.

63. B-Lex says:

Tested it today with Build 14393.222, works fine.

64. Donald Novak says:

I installed this patch after upgrading to Win 10. At the “Anniversary Update” (1607) the computer crashed and I reinstalled everything. With today’s update I again got the BSOD, but this time (after enduring all of MS’s attempts to recover the PC) I chose the non-patched Win 10 and it booted up (without full use of 8 GB of RAM). The update knocked out ntoskrnx.exe, but left winloadapp and the boot option. I followed directions to remove the patch leftovers and now will reinstall it (with thanks to B-Lex for assurance that this version of the patch works with the new update). SO: apparently any update that modifies the kernel will require (1)booting to Win 10 plain, and (2) reinstalling the PAE3 patch. The BSOD will let you know.

65. Don N. says:

…However, it didn’t work. Got an error message on the last entry, tried berrycommsIan Berry’s suggestion above, and it brought an error message too. Is that {id} the boot id?

66. Don N. says:

–And this time it did work!–I had entered “[boot id}” instead of the boot id NUMBER in brackets in the last step. Also, I did not need berrcommIan Berry’s additional entry. Some do, some don’t …. Thanks to all!

• Peterd51 says:

Hi Don, where would I find this boot id number please? I tried to set this up yesterday but it failed. I’m on Win 10 build 14393.0. If it’s possible to ‘read’ the bootloader in something like notepad could you tell me how to do it please?

67. Terry says:

After Win10 build 222 I had to restart without the patch using Windows Automatic Repair-Advanced options-Choose another operating system. Msconfig was used to remove the patch.

After re-patching the computer booted ok using the patched OS.

68. If somebody have problems (reboot loop) after the last update, here is the solution:
– Boot without PAE patch.
– Patch the new kernel (step 3 of help)
– Patch winload (step 4 of help)!!!
– Reboot with PAE patch.
After this, everything works fine.
Best regards
akapuma

69. forbidden 404 says:

My PC was bootloop,, don’t try this programs :'(

70. boogie says:

I applied the patch and booted in with 4gb of Ram, it sees 4 gb, it recognizes 4 gb, but it won’t go past 3.2gb when I try to fill up the ram on Windows 10 14393. Can anybody else confirm this? Can you use more than 3.2gb of ram even if it shows you have Xamount-3.2gb ?

71. Terry says:

boogie,
You need to check whether the patch has actually been applied.
Either right click ‘This PC’ icon on desktop and then Properties, or Settings-System-about and check installed RAM. It should say 4GB.

If it says some something like 4GB installed, 3.2GB useable, then the patch has not been correctly applied.

You can’t actually use all of the 4GB of RAM installed because Windows requires some for overheads, and if you have onboard video, then some more of that 4GB will be used for video memory.

The other thing to realise is that only 4GB of ram will be used by any one program, even though there may be say, 8 or more GB installed

72. Terry says:

….boogie,
I should have said only a maximum of 4GB is able to be used by any one program

73. boogie says:

Nah it’s my bad. It’s just that windows 32bit actually doesn’t let me use over 2.2gb actually which is very weird for me and it leaves 1 gb available and after applying the patch it uses that extra 800 mb to get 3.2 but once again 900 mb available. So the patch works but Windows is acting weird because on my 64bit version I can fill up the ram until I have 200mb left

74. Tsoe says:

I have updated to Windows 10.0.14393. The current patch is for Windows 10.0.10586. Is there a way to update the current PAEpatch2 for Windows 10. Thank you. I’m getting an unsupported kernel when I try to Patch my current Windows version.

• No, there is no way to update PatchPae2. Please use PatchPae3. See post August 16, 2016 at 8:56 am from evgeny in this thread.

BR

akapuma

75. Dario Romagnoli says:

Nave windows 10 kernel 14393.321 patchpae3 got blue screen band lock system. Anybody could help?

• Here, 14393.321 works fine.
Have you used the patch first time?
If not, have you re-patched kernel and winload?

BR

akapuma

• I just updated Windows. New kernel is 14393.351. Works fine, too.

BR

akapuma

• Duy Khánh says:

How did u do it? Mine it said kernel not supported :~

• Decopi says:

Hi!
I used PAEPATCH for a long time, in several Windows versions, without problem.
Today I updated to Windows 10 1607 (kernel 14393.447). However couldn’t install PAEPATCH again (Error message: Unsupported kernel version: 14393).
Thanks!

• Decopi says:

Solved by using PaePatch3… works perfectly on 14393.447!

76. B-Lex says:

Update: works fine with kernel 14393.447. Happy updating!

• Decopi says:

Hi!
I used PAEPATCH for a long time, in several Windows versions, without problem.
Today I updated to Windows 10 1607 (kernel 14393.447). However couldn’t install PAEPATCH again (Error message: Unsupported kernel version: 14393).
Thanks!

• Decopi says:

Solved by using PaePatch3… works perfectly on 14393.447!

77. Duy Khánh says:

Working great on my device running win 10 build 10586. At first i forgot to turn on DEP and got error but it work when i turn DEP on again. So for some1 get error at first check ur win ver if it s supported, and DEP must be on.

78. Yuri says:

Hey community,
what is your experience when you use USB devices on PAE patched OS?

I found out, that for me connecting USB devices fails every time I boot PC with PAE.
PC note that device is attached, but init of driver fails. In settings, under devices, I found note: Driver error.

When I boot PC without PAE, USB devices works.
My kernel 14393.351.

Dear developer(s), it is possible to resolve this issue?

• Terry says:

Yuri, Re your posting on 30 November, Indeed you are correct, I hadn’t noticed before since I use mainly Win 8.1, but USB memory sticks do not install correctly and do not show up in ‘This PC’.
Trying to update driver is not successful as it is already the most up to date.

I am using Evengy’s patchpae3 downloaded from his posting of 16 August

• Q says:

Also having this problem. Help please!

79. Decopi says:

Hi!
I used PAEPATCH for a long time, in several Windows versions, without problem.
Today I updated to Windows 10 1607 (kernel 14393.447). However couldn’t install PAEPATCH again (Error message: Unsupported kernel version: 14393).
Thanks!

• Decopi says:

Solved by using PaePatch3… works perfectly on 14393.447!

80. @Gstone:.

Yo can find PaePatch3 at post from evgeny, August 16, 2016 at 8:56 am, in this thread.

BR

akapuma

81. ROBOCOP says:

I ask for help.. After performing all the steps using paeparch3 I still have no available 4gb I only have 3gb available, is this the latest version for my specification? :

Windows 10 HOME
VERSION 1607
COMPILACION DE SISTEMA OPERATIVO -14393.479

• ROBOCOP says:

My problem continues. I ask for help.. After performing all the steps using paeparch3 I still have no available 4gb I only have 3gb available, is this the latest version for my specification? :

Windows 10 HOME
VERSION 1607
COMPILACION DE SISTEMA OPERATIVO -14393.576
SISTEMA OPERATIVO de 32 bits

At the windows boot menu, i have 2 choices:
– “Windows”
– “Windows (PAE Patched)”

In both environments the system shows 4.00 gb (3.00 gb usable)

82. @Robocop:

At the windows boot menu, you should have 2 choices:
– “Windows”
– “Windows (PAE Patched)”

Try both and compare the available RAM. Is there a difference?

BR

akapuma

83. ROBOCOP says:

In both environments the system shows 4.00 gb (3.00 gb usable)

84. I’m running kind of a complex setup. A little background, my motivation stems from ACT! 2008 not being installable on 64-bit OSs. So, I loaded it on a Windows 10 Enterprise x86 Hyper-V VM along with RDP Wrap, RemoteApp Tool, and PatchPAE3. All successful. I published the app with RemoteApp, the system shows that it has 8GB of RAM and I have 6 users using it simultaneously from their PCs.

The problem is, once the system hits between 3.0 and 3.2 GB of RAM used (the system, as a whole, has never gone past 3.2 GB used), new connections start bombing out with an RDP protocol error of 0x112f. Looking it up seems to point to memory restrictions on the host PC. So, I don’t know if PatchPAE3 isn’t working or if a Windows behavior regarding memory allocation to a single exe even if there are multiple instances of it (so, like a shared pool per exe even if there are six of them running, they all pull from a fixed amount…maybe?). Does anyone know or can point me in the right direction?

• Terry says:

Just a guess, but the problem may well be a limitation of PAE in a 32 bit system. Even though more than 4GB RAM is recognised as installed, only up to 4GB per program can be used.

So if you have multiple instances of the same program running, then problems may arise if more than 4GB
is tried to be accessed. I guess multiple instances of a program is not the same as running different programs.

Hopefully someone more knowledgeable will be able to comment better than me !

85. grml4d says:

can you do a patch like that for win7 x64 home ? because it allows only 8 or 16 Go of ram
may be you can it to x86 release ?
have a good xmas day

86. Pixelboy says:

Good day all 🙂
Please you can write at which hardware of the patch works!.
Much users then do not need to have a try at all first .
Thanks you.

87. unclem says:

Hi!
unclem@hotmail.com

• unclem says:

@Pixelboy
Hi !

88. Hi Wen Jia,
Thank you very much for your work. I didn’t use my laptop for some time and therefore the Win10 Anniversary update hadn’t been installed until now. After updating it, the patch doesn’t work no more. I get the error “Unsupported kernel version: 14393”
It would be very kind if you could create an updated version of your patch. Thank you very much!

• dwaltz says:

same here, I also would appreciate an update

89. @ urs, @dwalzz:

For 14393, use paepatch3, not paepatch2.

BR

akapuma

90. j212 says:

Can I do this on a windows 10-PE(x86) image .wim file, like the gandalf (win32) 11-07-2016 redstone

91. Michael says:

Just tested with HP p6029de, 6GB RAM, BIOS 5.43 and Win10Pro 1511 build 10586.545 – and it works. SYSTEm shows full 6GB RAM.

92. Michael says:

Ahh – sorry, I forgot: I have used patchpae2. What is the difference to the later patchpae3 in regard of Win10?

93. Michael says:

Because Win10 only installed the driver for MS Basic Display Adapter for the pre-installed old NVidia GeForce GT120 I tried the latest NVIDIA-Win10-driver 21.21.13.4201 of 11-14-2016: Win10 w/o 4GB-patch booted but Win10 with 4GB-patch did not boot to the end.
The same effect was with 4GB-patched Win7 and the latest NVIDIA-Win7-driver (same version). I tested all available old Win7-driver from newest to oldest and at last 4GB-patched-Win7 started with the older NVIDIA-Win7-driver 9.18.13.3221 of 12-19-2013.
Because the oldest Win10-driver is of 07-29-15 (and so not old enough) I tried this Win7-version-9.18.13.3221 also with the 4GB-patched Win10 – and it worked. Surprise, surprise.

94. Hello Michael,

you asked for the difference between patchpae2 and 3.

Patchpae2 does not work on current win10. For current win10, patchpae3 is required.

If you can use patchpae2 without error message, your win10 is old.

Best regards

akapuma

• Michael says:

Yes, it is Win10Pro 1511 build 10586.545.
But what is the substantial difference between the both programs? I know that patchpae2 modifies some byte in the kernel-file, changes the memory-limit. Does patchpae3 does the same, only at other places due to a updated and so different kernel-file?

95. It works! I used Evengy’s PatchPae3.
My setup:
– Windows 10 Pro (32bit) 10240 Build
– Intel HD Graphics 530
– Gigabyte mobo (GA-H170-HD3)

I able to use all my 8GB DDR4 RAM, don’t need change display adapter driver, no issue about USB devices, no BSOD, thanks!.

96. Valt says:

Hi
@evgeny
I’m trying to run your PatchPAE3 on Windows 10 Pro \ Version 1607 \ OS Build 14393.693, but get nothing, no even an error notification.

• j212 says:

same here…does not work on OS Build 14393.693

97. Michael says:

Now I have updated to Win10-32 v.1607, built 14393.693, and done the modification again with patchpae3 (the same hardware, HP p6029de, 6GB RAM, BIOS 5.43) and it works as with patchpae2 and v.1511.W/o the patch system reports 6GB RAM and useable 3,35GB RAM, with the patch it reports 6GB RAM.
I am not very surprised because patchpae3 modifies the same byte-sequences in the kernel-file as patchpae2 and in the same way and so the result should be the same.

But of course the problem with the NVidia-driver for GT 120 is the same – I have to use the old Win7-driver 332.21 (9.18.13.3221 of 12-19-2013). This is an origin problem of the driver, not an origin problem of the 4GB-kernel-patch, although this “bug” of the driver only appears with the 4GB-kernel-patch.

I have also tested it in an old Medion-PC with a MCI-7204-Motherboard, which can take 4GB RAM only. Surprisingly with and w/o the patch system reports only 3,35GB RAM. Seems as if some some-devices makes Windows to see only 3,35GB and not the actual 4GB. Strange. I hoped getting usage of the full 4GB RAM.

• Thank you very much for this your comment, it was really crucial. Any other driver (327, 341 and 384) did not work.

98. Valt says:

Hello @Michael
Could you write down steps that you performed when patching you Windows 10 built 14393.693?
I really appreciate it.

• Dr. Michael König says:

I have done the modifications exactly as described in the patchpae2-“manual”, with both PC (of course path and filename changed to patchpae3-location and -name) by copy&paste the commands to the elevated-command-window.
Additional I have also checked that the modifications of the kernel- and winload-file were done by comparing the original and modified files (I have used the “universal”-tool Total Commander for this).
When all the step are performed and the answers of the programs/Windows to each command are correct then Windows boots with the modified files.
I would suggest also compare the files and if the files are different (and so modifications are done) checking the new boot-entry with bcdedit or with EasyBCD (which is also helpful in many other cases).

99. For me, 14393.693 works fine with patchpae3. Installed RAM is 4GB.
With patch; 3,46GB usable.
Without patch: 2,47GB usable.

Using AMD A10-5700 with integrated ATI graphics.

Best regards

akapuma

• Dr. Michael König says:

Absolutely strange that
– you have this large difference between with and w/o patch AND even with patch not the complete 4GB RAM
– my old MCI-7204-MB shows 3,35GB with AND w/o patch.

• Terry says:

You will never get 4GB of usable RAM with a 32 bit Windows OS even with PAE. Firstly an integrated graphics video adapter will take up whatever has been allocated in the BIOS, and then there is the RAM used for overheads.
With a separate graphics card up to around 3.5GB will be usable, maybe a little less depending on motherboard and the hardware you have. PAE may only give an extra 200+MB or less depending on hardware.

So, it is a moot point as to whether the PAE is worthwhile if only 4GB is installed.

Interestingly with 8GB installed on a patched win 10 machine and also on a patched win 8.1 machine, both with separate AMD Radeon (ATI) graphics cards, both report in ‘Properties’ that 8GB is installed, there is no statement of ‘usable ‘ memory.

100. Michael says:

This is not so easy, sorry.

With the MSI-7204-Motherboard and 4GB RAM System reports only 3.35GB RAM w/o message about availabe or useable RAM and doesn´t matter whether w/ or w/o the patch. And this although the MSI-7204 does NOT has Video onboard.

With the above reported HP p6029de (Motherboard Pegatron Benicia) and 4GB RAM (I have removed one 2GB-module) System reports w/o patch 4GB and useable 3.25GB RAM (Benicia has Video onboard, but disabled due to the used GeForce GT120). And with patch System reports the complete 4GB w/o any limitation to a smaller available/useable RAM.
It is the same bevaiour as with 6GB RAM: W/o patch System reports 6GB RAM existing and 3.25GB RAM useable, w/ patch 6GB existing.

So with the HP p6029de (Motherboard Pegatron Benicia) the patch really gives access to the “missing” 0.75GB RAM and so to the complete 4GB (if “only” 4 GB is installed).

I have another PC available for tests, a HP dc7900. I will test it this evening.

101. j212 says:

I’ve tested it on another 32 bit system by installing 14393.693 and it just does not work with PatchPAE3_2016_08_15.zip…absolutely nothing changes if i boot from the original vs. the modded boot option.There’s not even a byte changed in the executables if you compare it with windiff.
can someone upload some files…I would love to see the diff…ntknew.exe,winldnew.exe

• j212 says:

Actually there is a change..I used a different tool…

• Oytun says:

Can you share which tool you used?

• Oytun says:

would you reply me my friend?

• j212 says:

even thought there is a 2 byte change on the executable, I still can only use 3gb…..I have a discrete gpu and ram is not shared.

• Oytun says:

I didn’t understand what this programme is for. But I thank you for sharing anyway. 🙂

102. Terry says:

Hello Michael, well OK you are quite right, I had forgotten or got mixed up, a problem with 80 year old memory! With 4GB and system patched, 4.00GB is reported as installed with no mention of usable memory.

As regards the MSI motherboard, that is odd. Maybe run a memory test program like Memtest to see if it is all working OK ?

• Michael says:

The BIOS-test shows complete 4GB w/o problems. But “missing” 0.65 GB is not really disadvantegous. The PC/MB is old, is not really fast using Win7 or Win10 (when bought with WinXP nearly 13 years ago it was the highlight in our house, even with 512kB – tempus fugit), it´s o.k for emailing, writing and a little bit surfing, looking some vids on youtube etc., so far even the 3.35GB are not needed and used complete.

• Michael says:

In the manual of the MSI-7204-MB I found the explanation, that due to the limitiations of the chipset not more than 3GB could be used. The truth seems to be that this chipset does not has the feature of “switching” the adresses of the RAM-area used by other devices (videocard etc.) into the area above the physical memory resp. the regular 4GB-adress-area. So is is a matter of the MB and it´s chipset how much of the 4GB can be used.

103. Frank Shashaty says:

104. Rui says:

How to roll back from this?
Tried on Windows 10 32bit, pc restarted and never start again. Now corrupted the HDD (which is a flash MLC 32GB). Show 12.5GB free space, can´t format it, can´t delete partition… tried as external hdd on other pc, tried with aomei partition assistant, tried with easeus partition master, tried on the original pc starting with usb Windows 10 install, can´t repair, can´t reinstall, with CMD can´t format it, even with diskpart can´t do anything. How to solve this?
Thank you

• Pixelboy says:

Hi Rui 🙂

MLC 32GB >> SSD ?
Format the SSD-Partion new with the original SSD software and install WIN 10 new, Please !

Good luck !

Pixelboy

• Rui says:

Yes, MLC 32GB SSD, unfortunetly this came without original software… Tried many softwares, and until now, nothing solved it. 🙁

• pixelboy says:

Sorry Rui,

ANOTHER USER IN THIS FORUM PERHAPS !?

H E L P him !!

Pixelboy

105. Pixelboy says:

@ all other userer !!! PLEASE CONFIRMING !!

I THINK >

This patch from wj32 works together in all probability only with AMD Graphic Cards and original INTEL internal graphic cards. NOT with Nvidia – GrCa. and Driver from
year 2013 – up today.

Pixelboy

106. Lewdsnow says:

@pixelboy

It’s true.
All AMD Graphic Cards works with this patch (for me).
Intel Graphic Cards might work with new version driver (My HD4600 PCs work with 20.19.15.4404 driver now).
Nvidia Graphic Cards only works with 331.82 and earlier version driver.

107. DuyK says:

Working on my pc Intel 7700HQ, card HD Graphic 630 and GTX 1050Ti

• evgeny says:

DuyK
What nvidia driver version you are using?

108. I have NVidia Geforce 8400M GT (in laptop) (and latest Win 10 Build 14393) and got the “VIDEO TDR” blue screen using Patchpae3. Based on others having same NVidia issues with patch as well – I installed the oldest one I could find for Win 7 (as post suggested) – which was 8400M GT driver (10/23/2013 – 9.18.13.3165)
Win 10 will update that driver to the latest that doesnt work with patch. You have reboot without patched kernel then “roll back” via device managler.
This works most of the time about 90% – but still occasionally crashes and luckily reboots instead of those couple different blue screens.

109. gb says:

Does this patch work with the new AMD Ryzen platform ( especially the drivers )? Using Windows 7 SP1.

Will gladly switch to AMD if it does.

110. Terry says:

Apparently you can’t run Win7 on the Ryzen platform because there is no driver support.
https://www.pcgamesn.com/amd/ryzen-windows-7-drivers

I’d have thought if you go to a new PC build then you’d get Win 10 64 bit OS, and hence no need for this patch ?
I don’t think the patch is hardware dependent………..AFAIK………….

• evgeny says:

driver for CPU? marketing’s bullshit.
You are right. The patch is hardware independent.

111. gb says:

Intel drivers are not compatible with this patch. I just wanted to confirm that the same problem does not exist for AMD drivers.
afaik, only Windows 7 update may not work with Ryzen.

I use this patch to boot Win7 32-bit from memory (using firadisk driver + grub4dos). It works well with my old AMD system – poor man’s SSD 😉

112. zaza says:

Have any body tested paepatch3 with win10 build 15063?

• evgeny says:

later, with updated fix128, as usual.

113. Michael says:

The new one is a complete different file … whta´s the difference?

• Michael says:

Oops, sorry, mixed up with PatchPAE3_2017_03_28.zip. Please delete.

114. Michael says:

Win10-Defender says that there is a virus inside.Trojan Win32/Fuery.B!cl and other software also give a virus-alert.

• Escape75 says:

My is just fix128 encapsulated with autohotkey and a .cmd that executes it,
so unless fix128 contains something it will be the exact same thing …

On a side note fix128 is niw twice as big as previous versions,
but I think it just wasn’t packed with mpress or upx, however
when I encapsulated with purebasic it was also triggering a virus
warning so that’s why I switched to using autohotkey… strange!

• Michael says:

• Escape75 says:

Ok, I’ve checked it out myself as well, see below, nothing to worry about.

115. evgeny says:

PatchPAE3 is command-line utility. It’s PatchPae2 mod.
fix128 is GUI for PatchPAE3. It’s compilation of VBScript, 7zip, UPX and some Micro$oft utilities. PAE Patch 2.1 by Escape75 is very simple… (GUI without GUI?) wrapper for PatchPAE3 to easy use. PatchPae2.zip is not virus. It’s AV false positives heuristics, because any PatchPae modifies some windows critical kernel files just like virus. For example, when you run “PatchPae2.exe -type loader …”, you disable DRM, and Micro$oft and AVs worship DRM 🙂

116. Michael says:

Extracted PatchPAE3.EXE ist accepted by Defender. But extracted PATCHPAE.EXE is removed by Defender – reason: Virus (see abvove). I can only report what I see on the screen.

• Escape75 says:

Yeah I had another look and you’re right, these A/V engines are weird …

When I scan my PatchPAE.exe and PatchPAE.cmd separately they are clean (via virustotal.com)

When I scan PatchPAE 2.1 which encapsulates the 2 above using AutoHotkey I get detections (16!)
When I scan a test version of PatchPAE encapsulated with WinRAR SFX I get detections (8!)

The PatchPAE.exe in all of the above files is PatchPAE3.exe by evgeny.
So you get detections from all, but rest assured that PatchPAE 2.1 is clean.

AutoHotkey source code is also very simplistic:

#NoEnv
#SingleInstance force
#NoTrayIcon

Random, Rand, 100000, 999999

FileInstall, PatchPAE.cmd, %A_Temp%\PatchPAE.cmd, 1
FileInstall, PatchPAE.exe, %A_Temp%\PatchPAE.exe, 1

Gui, Color, 1E3C5A
Gui, Font, S9 cB4D2F0, Lucida Console
Gui, Margin, 10, 0
Gui -MaximizeBox -MinimizeBox +Owner
Gui, Add, Text, W640 H300 vVar
Gui, Show, Center W640 H300, PAE Patch 2.1

Run *runas %A_Temp%\PatchPAE.cmd > %A_Temp%\%Rand%.log,, Hide, PID

Process, Exist, %PID%

while (errorlevel)
{
Sleep, 250
GuiControl,, Var, %Output%
Process, Exist, %PID%
}

Sleep, 5000

GuiClose:
GuiEscape:

FileDelete, %A_Temp%\PatchPAE.cmd
FileDelete, %A_Temp%\PatchPAE.exe
FileDelete, %A_Temp%\%Rand%.log

ExitApp

117. When I type this command ‘C:\WherePatchPaeIs\PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe’
a message appears saying that system cannot find the patch specified

118. I am using Windows 10 32bit

When I type this command ‘C:\WherePatchPaeIs\PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe’
a message appears saying that system cannot find the patch specified

• derrick says:

i have 15063.138 @Escape75 when i run your patch the one with the funny logo it says “Error cannot detect Loader” any help please tried like most the patches u have put up none seem to work, others just CMD appear then dissapear nothing done thanks

• Frank Shashaty says:

The following error occurred: Error code 0x80070002. The system cannot find the file specified.

Category: Trojan Win32?Fuery.B!cl

Description: This program is dangerous and executes commands from an attacker.

Recommended action: Remove this software immediately.

Items:

• Escape75 says:

The Trojan warning is a false positive, you should white list the Patch program.
What AV software is giving you the warning anyways? Windows Defender is fine for me.

• Frank Shashaty says:

Hello .. I’m using Windows Defender …. tried again .. same result — reports a virus

• Frank Shashaty says:

How do we do the following?

’m guessing you’re running EFI boot and my patch needs to be corrected to work with that …

FOR /F %%a in (‘bcdedit /enum {current} ^| find “%systemroot:~2%\system32\winload.exe”‘) do set winload=1
FOR /F %%a in (‘bcdedit /enum {current} ^| find “%systemroot:~2%\system32\winloadx.exe”‘) do set winload=1
if %winload% equ 0 (echo -ERROR- Cannot Detect Loader!) & (goto end)

119. Frank Shashaty says:

The newest windows 10 creators edition doesn’t work with patchpae 3… Does anyone have a solution?

120. derrick says:

i have 15063.138 @Escape75 when i run your patch the one with the funny logo it says “Error cannot detect Loader” any help please tried like most the patches u have put up none seem to work, others just CMD appear then dissapear nothing done thanks

• Escape75 says:

I’m guessing you’re running EFI boot and my patch needs to be corrected to work with that …

FOR /F %%a in (‘bcdedit /enum {current} ^| find “%systemroot:~2%\system32\winload.exe”‘) do set winload=1
FOR /F %%a in (‘bcdedit /enum {current} ^| find “%systemroot:~2%\system32\winloadx.exe”‘) do set winload=1
if %winload% equ 0 (echo -ERROR- Cannot Detect Loader!) & (goto end)

• Frank Shashaty says:

How do we do this?

121. evgeny says:

And if you will patch winload.efi, first you need to disable secure boot.

• Escape75 says:

Try opening cmd, and type:

This will show what files you have, is your boot drive c: ?

122. Escape75 says:

You should also attach the output of (from elevated cmd)
Bcdedit /enum

• Escape75 says:

Ok I see a previous patch there, running as {current} …

Try rebooting your windows 10 and selecting “Windows 10” at the boot menu,
then after windows boots execute the patch again. Hopefully that will work.

• Derrick says:

cheers man deleted all the old ones worked treat thanks again and fast respone ty

• Triviño says:

I can’t decompress the file Pae-Mod.rar…

• It works but it is black/white screen instead blue screen at Boot selection.

123. I have tried all patches you posted, non of them worked unfortunately. The last one says ‘cannot detect loader’.
I have Windows 10 32 bit
15063

• Escape75 says:

Please post output of “bcdedit /enum” see above,
I’m guessing there’s a previous patch or weird bcd entries …

You could also try rebooting choosing another startup option.

• Derrick says:

Hi go to msconfig see how many windows you have at startup, if u already have a patched one that is default then delete it so u only have windows 10 then run that as defult, re-apply patch worked for me i had same issue.
thanks to Escape75

124. I was so happy that I forgot to thank you.

Thanks a lot man, you helped me a lot

125. Patch PatchPAE3 with Windows 15063.138 works fine for me. But I’m wondering:

“bootmenupolicy” is set to “Legacy” (checked with bcdedit /enum). The help of PatchPAE3 says:

But with new WIN10, boot menu is not the classic black/white text menu. It’s a blue (graphics?) menu. (Not always but usually.)

Is this normal?

Best regards

akapuma

• I found the difference:
During a “cold” start, the “classic text mode” (black/white) is used.
During a “hibernate” start, the blue mode is used.

Best regards

akapuma

126. gb says:

@Escape75, JFYI : v2.4 of PatchPAE3 working OK with Windows 7 SP1 fully updated
Thanks.
PS : you could include a readme to tell users it is full auto. At first I tried to use it according to the instructions for the original PatchPAE2.

127. Sanjeev says:

Patch pae 3 worked for my windows 10 version 1493.. but i am facing prblm while installing intel hd graphics its not installing nd screen goes while its installation ….processor is i3 2gen can anyone know how cn i install graphics driver

128. gildo says:

can you add version 15063.250 this goes to automatic repair

• Terry says:

Gildo, the patch works OK for me with 15063.250.

I’d suggest the problem may elsewhere.

• gildo says:

if i chose the pateched version goes to automatic reapair if i chose the normal the windows works fine do you know what could be the possible causes? i do have an Geforce 220 could that be the problem?

• gildo says:

i maybe somethig wrong las tme but now i get KERNEL_MODE_EXCEPTION_NOT_HANDLED as error as soon as i enter in my windows and see my desktop

129. van says:

Just tried the newest version on my Win 10 Pro installation and it worked like a charm. Many thanks!!

130. Pixelboy says:

Hi Guys !!

This is helpfully for everyone, to use this Patch want.

Thanks !!

Pixelboy

• Escape75 says:

It’s pretty simple, unless you want to use really old drivers,
the only requirement is an ATI Radeon card for this to work.

Other than that, it should work on anything.

131. The PAE patch worked for me Windows 10 Update version1607 (KB4015438)

132. stanhcorder6 says:

Does this patch work if Windows is booted in UEFI mode?

133. stanhcorder6 says:

Does this patch work when Windows is booted in UEFI mode?

134. tamangspace says:

Unsupported kernel version: 15063. Windows 10 creators update.

135. Fall Creators update is coming! Anyone is working on the patch?

136. steven says:

My computer has crached when using this tools on windows 7 sp1 update pack 06/2017

137. ANdrew says:

It worked on Win 7 32 bit. Sp1 Home premium running on Virtual box.
My lesson was Make sure I follow the readme intructions exactly! I suggest extract the patch zip to root of drive ie C:\ seemed to work better than extracting into system 32 folder.
You will note in the read me that the path given to the loader is \windows not c:\windows as I mistakenly used. I’m not sure why that is but just use what the read me has.
If anyone little thing is wrong the loader wont work and as soon as you hit enter on the os selection screen it will go into windows recovery – dont give up! If you wait for the windows recovery to restart – and then select the same boot option again let windows recovery keep running untill it gives an error message – that will help alot – my error was cant find boot loader which helped me notice I had not followed the readme with the path. Note if you get a blue screen error thats different a driver possibly needs rolling back or an older driver installed (from what ive real mainly intel on board graphics)

Yay Now in computer properties it shows 6gb ram.

• Pixelboy says:

Hello ANdrew 🙂

Pixelboy

138. MisterLeeD says:

Am I crazy or did the latest update really make a mess?

• Rich Reamer says:

maybe its the KB4025339 update thing I’m experiencing?

139. Rich Reamer says:

PaePatch 3 patched system fails to boot with a “pdc.sys” 0xc0000098 error after MS update KB4025339 installs. I have to remove KB4025339 and then system will start giving me full memory again. But then windows update starts downloading KB4025339 again. Ideas?

• Rich Reamer says:

Figured out how to fix/workaround:
1) boot into original win kernel (original non-paepatch you should still have in boot menu) – let windows update finish installing
2) might reboot again, boot back into original non-paepatch windows
3) go into “control panel” -> “updates & security” — click “update history” — click “uninstall updates”
4) find “Security Update … (KB4025339)” – select it and “uninstall” it
5) let system reboot once
6) when back up after update has been uninstalled
7) open cmd prompt – goto “windows\system32\drivers” directory
8) copy pdc.sys pdc.sys.org
9) go back to “control panel” -> “updates & security” – watch and wait for windows to install the KB4025339 update again – let system reboot. startup will fail again so go back into the non-paepatch windows to complete KB4025339 install
10) go into “control panel” -> “updates & security” — click “Recovery” – scroll down to “Advanced” and click “restart now”
11) when it comes up in maintenace mode version – select “Troubleshooting” — then select “Advanced Options” — then select “commmand prompt”
12) when it comes up do:
d:
cd \windows\system32\drivers
ren pdc.sys.org pdc.sys
exit
13) now you should be able to select you default paepatched windows

## NOTE: ## — I found with this workaround — that now at this point with the old “pdc.sys” file back – that booting into the non-paepatched windows throws a bluescreen. So use at your known risk. since you keeping the new “pdc.sys” file you can always revert back.

• Rich Reamer says:

ATTENTION: scratch all I said above !
Except you can still uninstall update KB4025339 if you wish but it will come back.

Ended up needing to redo the bcd edits – not just patch kernel and loader, the bcd got changed somehow.

140. MisterLeeD says:

Yeah they bombed me with multiple updates I should have paid attention to what they were doing.
Sure enough I look and the PAE OS has crashed.

141. MisterLeeD says:

Sooner or later I am sure Microsoft will try to force on to me but maybe some one will come up with another patch.
I also caught Norton security killing the patch so I was able to get around that.
For now I got my computer back.
Ryzen build I will have to give in and go 64 bit.

142. Hello,

the following worked for me:

– Set default boot mode to non-paepatch.
– Let Windows make all updates to 15063.483. If windows makes a reboot, paepatch is not active.
– If windows updates are completely finished, re-apply PAE-patch !!!
– Then, you can set default mode to paepatch and use it.

Enjoy!

Best regards

akapuma

• Rich Reamer says:

ah, interesting, my windows is kernel version 14393. I thought i re-patched the 2 files.. rechecked — the KB4025339 update provides new ntoskrnl.exe but no change to winload.exe. Didnt redo any bcdedit stuff.

• Rich Reamer says:

yeah, now its working — read, rechecked the steps, and redid the bcdedits – that appeared to have changed.
that was it — so no “pdc” workaround needed.

143. MisterLeeD says:

Problem is whatever they did on that update mentioned the kernel does not patch.
KB4025339

144. My workaround (see above) works. All exe-files (ntknew, ntoskrnl, winldnew and winload) are 15063.483.

I only patched both files. No bcdedit.

Best regards

akapuma

145. Without the workaround, i got the following:

– Windows update makes an update.
– PC restarts
– At boot time, there were messages like “PC is checked” or “PC is repaired”
– PC restarts
– After reboot, I got the message “Updates can’t be applied”
– Procedure begins again.

BR

akapuma

146. koolong says:

For those uninitiated who are experiencing crashes after the latest windows update try this method:

Run CMD as admin and type in ‘bcdedit /set removememory’, and then run your patch file.

It worked for me.

• koolong says:

correction
“bcdedit /set removememory 0” is the full sentence
sorry for the cause

• koolong says:

correction.
‘bcdedit /set removememory’ is the full sentence
Sorry for the late response

147. MisterLeeD says:

Hate to ask but what does the command do??
Sooner or later Mr. softy is going to push that update down on me.
I don’t even get an update loop.
The PAE OS crashes and none of the other entries can I patch.

148. MisterLeeD says:

Strange I let another update run and now it patches great.

149. 423 says:

So….
any solution for win10 (os:14393.1480) to use 8GB memory?

150. MisterLeeD says:

akapuma
July 14, 2017 at 8:08 am
Hello,
the following worked for me:
– Set default boot mode to non-paepatch.
– Let Windows make all updates to 15063.483. If windows makes a reboot, paepatch is not active.
– If windows updates are completely finished, re-apply PAE-patch !!!
– Then, you can set default mode to paepatch and use it.
Enjoy!
Seems to be the best answer.
Even if it does not move you up to latest version the last update I had was easy to patch.

151. @Bill:

Why? Patch works fine with 15063.540.

BR

akapuma

152. ****** Any way to get around this failing?

PatchPAE by wj32:
– support for Windows Vista SP1/SP2, 7, 7 SP1, 8, 8.1
– Server 2008 SP2
evgen_b MOD:
– added support for Vista SP0, 7 SP1 with KB3033929+,
– Windows XP SP2/SP3,
– Windows 10 (10240/10586/14393)
– Server 2003 SP1/SP2/SP2R2, Server 2008 SP1
– Server/Windows 2000 SP4 and 2000 SP4 with KernelEx by blackwingcat
– Windows Longhorn (4093 stable), Visual C++ 2010 Redistributable required
Version: 0.0.0.45

Input file version: 15063
Failed.

153. Nevermind! It’s working now. I had to make sure I used PatchPAE3_2017_03_28.zip.

154. Scyzor says:

I have done PatchPAE3 w/o any issues

Input file version: 15063
Patched.

but after the reboot I still have 8GB (3GB usable)

Any clue?

Thanks

• stanchcorder6 says:

Make sure you have enabled MMIO in BIOS

• Randy says:

I’ve searched and I can’t find anything about MMIO for my x60. How do i check this setting?

• evegeny says:

Make sure you have applied bcdedit.exe after PatchPAE3.

• Randy says:

What does this mean? I have to rerun all the bcdedit commands again? Does it matter what boot load I’m in? Thanks

155. zaza says:

will it work on Windows 10 Insider Preview 16299? May be anybody have already tried?

156. tester says:

Fails on 1709 16299.19 with nVidia driver. PAE boot entry just keeps in restarting loop cycle or ends up with the green screen of death informing bout failure of some nvxyz.sys thingy. Also it screwed up the WinBtrfs module somehow; clicking on a drive in File Explorer results in An internal error occurred message.

• stanchcorder6 says:

Please update this patch for 1709

157. Now the latest version of Windows 10 is 16299. Anyone is working on patching the new kernel and loader?

• zaza says:

Ill try to day later on my notebook with ati and post the results

158. zaza says:

Cheked – runing good!

159. Frank says:

Hello guys!
Do you know which Windows 10 32bit version will surely work with this patch?

My specs are:
Cpu Q6600
Ram 8Gb Corsair
Motherboard Asus P5K-E
VGA nVidia Gt-440 (but i can change it
with an ATI card)

I don’t care if is an older Win 10 version, i need the 32 bit for my old printers ’cause they don’t have 64 bit drivers

Thank you in advance if someone will help
Frank

160. Michael says:

It is (only) a matter of the video-drivers. You have to obtain and use old (maybe Win7-)driver. Please see my comments above.

• Frank says:

Even with the nvidia gt-440 card?

• Michael says:

I don´t know. The latest/youngest driver which worked with the patch and my (old) Nvidia-cards (see above my old comments) was NVIDIA-Win7-driver 9.18.13.3221 (332.21) of 12-19-2013. Due to my experiences that no younger/later driver worked with the patch I assume that you must use/test this driver. Maybe it works with your card.

• Frank says:

Thank you so much Michael. I really appreciate your help.
So, last question just ’cause i’m a lame, no problem if i use Win 10 1703 or even 1709?

• Michael says:

I do not use Win10 regularily. But due to my experiences with Win7 and Win10 in the past it is not a matter of the win10-version but a matter of the nvidia-driver-version. The same problem occurs with Win7. I also do not exspect that a newer Win10-version would not accept the old Win7-driver. But at last with all this patches and improvisations and workarounds: There is no guarantee, make a try.

161. For NVIDIA users try to install old drivers. Mine was in 2013

• Michael says:

Yes. See my comments of Feb.2017: NVIDIA-Win7-driver 9.18.13.3221 of 12-19-2013. Working “perfectly”.

• Frank says:

Didn’t work for me with Windows 10 1703 or 1709.

162. Faris says:

Uh why does it state that it “failed” when i did the command to patch the loader to disable signature verification? I need help thanks in advance

163. Michael says:

Upgrade to 1703 is done. This sh* MS-software again (unwanted and w/o giving notice) updated the NVidia-videocard-driver to the newest version. The result was that after patching the kernel the system does not boot. I went back to the previous driver
NVIDIA-Win7-driver 9.18.13.3221 of 12-19-2013 (see my post of February 18, 2017)
and now, as exspected, also the patched system is booting. 8GB from 8GB are in usage.
Testet on an EVGA force 780i SLI FTW motherboard (132-YW-E178) with E8400-CPUs.

• Pixelboy says:

Hi Michael, good day 🙂
Which graphic card are you using?

Pixelboy

• Michael says:

NVidia GeForce 8800GT

164. Michael says:

The differences between original and patched ntoskrnl.exe:

original patched
002E8 FD D0 59 65 54 5A
516179 8B 75 DC 85 F6 74 3F BE 00 00 02 00 90 90
5161A9 8B 4D FC 85 C9 74 06 B9 00 00 02 00 90 90

The replacements with “BE 00 00 02 00 90 90″/”B9 00 00 02 00 90 90” are well-know form the manually-done Win7-patch.
But what is the reason for replacing “FD D0 59” with “65 54 5A” ?

The differences between original and patched winload.exe:

original patched
00148 FE A3 4C AC
3AE06 8B F0 33 F6
3BE50 8B D8 31 DB

You may remember that when patching the Win7-kernel manually you must give the patched file ntkrlICE.exe a valid signature by using makecert.exe and signtool.exe and the commands:
makecert -r -ss my -n “CN=Microsoft Windows”
signtool sign -a -s my -n “Microsoft Windows” ntkrlICE.exe
I have done and testet this procedure with a manually patched ntoskrnl.exe and also with the patchpae3-patched ntoskrnl.exe. Although there was no error-message and so the signature should be o.k. the system does not boot but starts the repair-procedure (of course w/o success).
Any idea why this does not work with Win 10?

165. Michael says:

Also upgrade to 1709 (Build 16299) is done. Again the updater updated (unwanted and w/o giving notice) the NVidia-videocard-driver to the newest version. The result was again that after patching the kernel the system does not boot. Again I went back to the previous driver
NVIDIA-Win7-driver 9.18.13.3221 of 12-19-2013 (see my post of February 18, 2017)
and now, as exspected, also the patched 1709-system is booting. 8GB from 8GB are in usage.
Testet on an EVGA force 780i SLI FTW motherboard (132-YW-E178) with E8400-CPUs and NVidia GeForce 8800GT.

166. Michael says:

The differences between original and patched 1709-ntoskrnl.exe:

…………original …………………………… patched
002E8 . 87 FD 61 ………………………. F4 80 62
5991C1 8B 75 FC 85. F6 74 3F …… BE 00 00 02 00 90 90
5991F1 8B 4D FC 85 C9 74 06 ……. B9 00 00 02 00 90 90

The replacements with “BE 00 00 02 00 90 90″/”B9 00 00 02 00 90 90” are well-know form the manually-done Win7-patch.
But what is the reason for replacing “87 FD 61” with “F4 80 62” ?

The differences between original and patched winload.exe:

…………original …….. patched
00148 .AD 5F ……… 59 0A
3A5D7 8B F0 ……… 33 F6
3B55C 8B D8 ……… 31 DB

• Vox Humana says:

The file checksum is obviously different, even if the code of the function is basically the same.

167. mike says:

where is the pae patch for window 10 build 16299 ?

• SaschaK says:

I use the latest available patch für 16299. Works fine for me.

168. I just downloaded the patch today but it isn’t working for me on version 16299. I’m getting an “incompatible with kernel 16299” message. Any ideas?

• akapuma says:

BR

akapuma

169. Michael says:

I do not have any idea due to the fact that I do not know the sourcecode of the patcher.
But you can do the necessary patches manually using a hexeditor and the information of my previous posts. Of course offline.

Hi !
Friends, anyone can rebuild pae patch for Windows 10 core 1709?

• akapuma says:

No need for this. Patch works fine with Version 1709 = OS build 16299.192.

BR

akapuma

• Alex says:

Hi from Germany… I used the PAE Patch bfore but now it doesn’t work anymore. I always get the the message: “Unsupported kernel version: 16299”

My System: AMD FX-6300 six-cor @ 3,5 Ghz with 12 GB RAM Win 10 Pro 32bit Version 1709 Systembuild 16299.125

How may I fix this again??? Thx 4 help

• akapuma says:

I just re-applied the patch. Neuw Windows kernel is 16299.192. Works fine with this version, too.

• Alex says:

yes! It worked… thx for help. Maybe it was the last Update on systembuild 16299.192

171. Randy says:

How can I determine if this is truly working on my system? I’m positive I followed all steps correctly, and dialogues seem to confirm. Upon reboot however, according to sys-info/sys properties it is not able to allocate more than 2.99 MB. Should I try the ntknew.exe command? I’m on the latest Win10 build (16299.192) and have a Lenovo x60 laptop. Perhaps there is a hardware conflict? Thanks, Randy

• Vox Humana says:

I’m not quite clear about the amount of physical RAM your system is equipped with

• Yuri says:

To determine this is working you can check systeminfo or use systeminfo.exe as a cmd prompt.

172. Yuri says:

PAE3_2017_03_28 posted above works with Microsoft Windows [Version 10.0.16299.192]