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.

Download: PatchPae2.zip (567299 downloads)
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
  • You cannot use more than 4GB of physical memory on 32-bit Windows due to hardware/software conflicts. See the comments on this page for more information.

172 responses

  1. Download PatchPae2.zip contains a Trojan.Gen.2 virus. Download size with virus is 69.5 Kb. Download size without should be 51 Kb.

  2. 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.

  3. 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.

  4. 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.

    • 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.

  5. 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?

  6. 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.

    • 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.

    • 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.

  7. 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.

  8. 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.

  9. 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!!!

  10. 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..

  11. 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.

  12. 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!

  13. 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!

  14. 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

    Windows Boot Loader
    ——————-
    identifier {current}
    device partition=C:
    path \Windows\System32\winloadp.exe
    description Windows (PAE Patched)
    locale en-US
    inherit {bootloadersettings}
    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
    bootmenupolicy Standard
    usefirmwarepcisettings No
    sos Yes

  15. 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?

  16. 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

    • 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 😉

  17. 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

    please help me…

  18. 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?

  19. 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.

  20. 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

    • 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.

    • 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…..

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

    • 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

  22. 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.

    • Patch prints “Fail” and exitcode != 0 in this case exactly as wj32.
      Checksum never checked.
      Can you upload your winload and ntoskrnl?

        • 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

    • 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

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

        Use patchpae3.exe downloadable from the evgeny post dated 16 August,
        Cheers

  23. 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

  24. 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

    Yvgeny can you please help.

    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

      • 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.

  25. 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.

  26. 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

  27. 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

    Any help from developer please?

    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

  28. 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.

    Any more hints available please?

    • 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

  29. 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.

  30. 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.

  31. …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?

  32. –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!

    • 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?

  33. 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.

  34. 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

  35. 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 ?

  36. 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

  37. 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

  38. 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.

    • 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).
      Please, can you help me?
      Thanks!

    • 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).
      Please, can you help me?
      Thanks!

  39. 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.

  40. 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?

    • 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

  41. PLEASE, HELP:

    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).
    Please, help me.
    Thanks!

  42. 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

    • 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)

  43. @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

  44. 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?

    • 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 !

  45. 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

  46. 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.

  47. 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!

  48. 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.

  49. 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

    • 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?

Leave a Reply