PAE patch updated for Windows 8

Note: An updated version for Windows 8.1 is available.

This patch allows you to use more than 3/4GB of RAM on an x86 Windows system. Works on Vista, 7, 8, has been tested on Windows Vista SP2, Windows 7 SP0, Windows 7 SP1 and Windows 8 SP0. Instructions and source code included.

Download: (1733110 downloads)

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.


  1. As always awesome work, bit I don’t get the point why someone would use this hack to use more than 4gig ran instant of just installing the x64 version of windows?

    1. There is often older software that simply won’t run on 64 bit versions. Not only software but hardware as well for specific business related applications. Not every PC is for browsing and gaming.

    2. this is because 32 bit windows uses less memory. if you don’t believe, try installing x64 OS 1st and then afterwards an x86 of the same OS, but with all RAM unlocked, and just after formatting, just check the % of memory usage in task manager.
      and that is the reason you will find x64 versions of softwares(like office 2013, or 2010, CATIA, ANSYS) are larger in size tha their x86 versions

          1. Yo do not know anything about hardware architecture not?
            It is faster except on optimized task like compression and multimedia.

        1. AMD64/EM64T/x64/whatever-the-hell-you-want-to-call-it is a hell of a lot faster for 64-bit operations than x86 (*AND* more widely used). The cost, however, is that *everything* is 64-bit. Your pointers, your integers, your booleans, all regardless of whether or not you actually needed it.

          If your application never needs the extended instruction length and memory space, then yes, you’re just wasting memory, but the moment you need something above 32-bit, 32-bit execution will suffer a severe performance hit. If you have ever used software that uses RSA encryption, or other stuff requiring bigints (Heard of SSL/TLS?) or just 64-bit ints (e.g. Rabbit/Badger, any browser whatsoever, …), then you will benefit from 64-bit.

          x32 tries to remedy this – Can’t remember the details of it, though. I think it uses 32-bit pointers.

    1. Probably because you use a desktop/note/netbook with integrated intel video, and all video drivers for intel video have limmitations when using it on Windows Vista/7/8.
      See this blog posts to locate and read instruction to how download a xp driver that don’t have this limitation and install it on Windows Vista/7/8.

  2. Hi folks, I have been using this patch successfully on Win7 and lately on Win8. I have however discovered that whereas on Win7 there was no issue, on Win8 the system fails to recover from Hibernate state when in PAE Patched kernel (hibernation recovery works fine when booted into the unpatched kernel). If anyone has any ideas to resolve this please share. Tks, Colin

  3. Could it be that \Windows\system32\winresume.exe also needs to be patched in Win8? If so can anyone provide the instructions?

    I have checked using Visual BCD editor and ensured that the GUID of the hibernate resumer for the PAE patched kernel corresponds to the GUID of the “AssociatedResumeObject” entry in the PAE Patched Loader. The issue persists – resume from hibernate works if booted into the un-patched kernel, but does not work when booted into the patched kernel. The same machine (a DELL E6420) does not have the issue with a Win7 Patched kernel.

  4. OK – I have reproduced the issue on another model – a DELL D630. I will do another fresh installation on this machine in coming days to confirm and report back here. For info I am using Win8 Pro installed via Windows Deployment Services.

  5. Oh yay! I have been looking for a RAM patch for Windows 8 32Bit. I have Windows 7 x86 patched on my other HDD and it has NEVER given me any issues. I unfortunately had to upgrade to 8 to fix my Windows 7 after I screwed it up messing around with things. But having 8 in for a while I started to use it more often. And one thing that I noticed was that the system was once again stealing my RAM from me. So I called myself smart and ran the RAM patcher for windows 7 (in windows 7 mode) it completed but would not boot up again. So I stepped back in time and uninstalled it. Are you guys having any luck with this Windows 8 patch?

    Also Im using a Dell Precision T5400 – 8 cores 4GB RAM (overclocked 2.00GHz~2.44GHz)
    Do you think Dells have it rough for customizing like this? Or should it be smooth sailing?

  6. This patch works fine in Win 8. I have tested it on DELL D630 and DELL E6420 so far. The only issue I have is failure to resume from hibernate (on both platforms). The developer of the patch has not confirmed this to be an issue with the patch as he has not been able to reproduce on his hardware. I am still working on trying to understand why the resume from hibernate does not work on my machines, but in the meanwhile I am simply not using hibernate – the rest works fine! 🙂

      1. Sounds very promising. Kind of makes me wish that I had a test machine to try this out on. The only build I have at the moment is this one that Im on now. Im sure you guys know how it is having PC hot-rod’n as your hobby. Parts for days, software for days, but not too many test subjects. LOL I will download a sample and figure out a safe method of recovery just in case. And post here the results.
        Thanks a million.

      2. Hi all,

        @WJ32, I have just run some tests and it appears that there is something strange happening since the April / May updates from MS. On a test VM running vanilla Win8 I can patch and unpatch at will. After running Windows Update the kernel patch returns a failed message whereas the loader patch continues to succeed. However, after reboot everything works as expected and on examination the new ntoskernx is present with a datestamp of 10/04/2013. The only anomaly I have seen is the failed message on the kernel patch operation, but it looks like the operation is in fact successful. Can you please look into this and comment?

        1. Hi all, I tested today on a DELL E5400 with 4G of RAM (more than I had in the VM I used before). The command to patch the kernel does in fact fail, though a copy is still made. This means that the system boots using ntoskrnx, but since ntoskrnx is unchanged it is still subject to the 3.2G RAM limit…

          @WJ32, any chance of an updated version please?

    1. Colin I have a Dell E5420 also, with the i Core 5 cpu, though Im running Windows 7 x86. Have you any experience with this patch and Windows 7? I ran the other RAM patcher that I would always use to do so. And wouldn’t you know, for some reason, on my E6420 it wouldnt do it properly. It would run, say its complete. Then upon a restart, would boot up like normal, but at the screen where it should show your login info, its stays black. With no HDD activity. Im going to check right now on one thing. I DID change my login method to NOT show the last user to log in. So I want to verify that, that is not the reason. I’m interested in trying this patch, but I have to learn how to uninstall my current failed patch first.

        1. Hey buddy I dont have the E6420 with a GPU. Its got the Intel HD 3000 bull-crap integrated crap. but this little crapper eats 750MB of RAM doing nothing. Leaving me with a virtually useless platform to try to run a 64bit OS. Thus me trying to get my x86 patched. I recently installed a different HDD and installed Windows 7 x86, I have patched Windows 7 so many times before, but nooooooooooo! This Dell is a nightmare. -.-
          I dont care about this iCore crap generation of processors, OC’n is damn near impossible. I would much rather have my Xeon’s in a workstation or my QX9560’s in my skulltrail. Way more headroom. But if you can spare any time I would appreciate the help buddy. Thanks

          1. Hi M8. I’m afraid I was unsuccessful in getting a previously patched Win 7 OS from a 6420 to work on the 5420 – same symptom you experienced despite numerous BIOS tweaks (which were pretty much random shots in the dark even if performed with method…). The system works fine on the standard kernel in both the 6420 and the 5420 chassis… I did not test from vanilla up as I don’t intend using Seven much any more and really don’t want to spend more time on this – sorry…

  7. Please let us know how you found the instruction sequence where the memory limit checked and why you didn’t override the stored value, but instead alter the returned result.

    Out of curiosity – have you explored the same patch for WinXP SP3?

    Thanks and keep up the great work.
    – R

  8. Thanks for this I can use full 4GB ram on x86..this patch is great tool for all those who want to stick to x86 to run legacy apps n have a lightweight x86 system (x64 windows = larger drivers, larger files, 32-bit emulation layer, no 16 bit support) still with full 4GB or more ram

  9. Not so good ,
    crashing graphics card memory. All 3D game won’t work. System Become unstable .Can you fix these issues?
    Win8 32bit , GeForce GTX 580

    1. they dont offer assistance, so my best guess would be to use one of your file history states. or a system restore point. best of luck bro

  10. Sadly, the patch does not work for me. I was greeted with automatic repair.

    Luckily I could return to normal WIN 8 by choosing “Advanced Options” > “Use Another OS”.

    I think I just have to get the real 64 bit Windows. Free lunch is nowhere to be found.

  11. I’ve write a fully-automated batch scripts to do every copy-paste step for you!

    1.) Copy and paste text between lines in notepad and save as two different documents ‘Patch_WVi-7.bat’ and ‘Patch_W8.bat’.
    2.) Put batch files and ‘PatchPae2.exe’ in same folder.
    3.) Run appropriate batch script for your OS as Administrator.
    4.) System will be restarted automatically.

    ~Batch script for Vista, Windows 7 and Windows 7 SP1~
    @echo off
    TITLE …::: WinVi-7 32-bit Unlocker Script :::… by: Wiwi-maX
    color 30
    echo Script use PatchPae v2.
    cd %Windir%\system32

    .\PatchPae2.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe
    .\PatchPae2.exe -type loader -o winloadp.exe winload.exe
    bcdedit /copy {current} /d “Windows 7 (Unlocked)”
    bcdedit /set {current} kernel ntkrnlpx.exe
    bcdedit /set {current} path \Windows\system32\winloadp.exe
    bcdedit /set {current} nointegritychecks 1
    bcdedit /set {bootmgr} default {current}
    bcdedit /set {bootmgr} timeout 2

    shutdown.exe -r -f -t 5 -c “RAM 2GB’s Limit Removed.”

    ~Batch script for Windows 8~
    @echo off
    TITLE …::: Win8 32-bit Unlocker Script :::… by: Wiwi-maX
    color 30
    echo Script use PatchPae v2.
    cd %Windir%\system32

    .\PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe
    .\PatchPae2.exe -type loader -o winloadp.exe winload.exe
    bcdedit /copy {current} /d “Windows 8 (Unlocked)”
    bcdedit /set {current} kernel ntoskrnx.exe
    bcdedit /set {current} path \Windows\system32\winloadp.exe
    bcdedit /set {current} nointegritychecks 1
    bcdedit /default {current}
    bcdedit /set {bootmgr} timeout 2

    shutdown.exe -r -f -t 5 -c “RAM 2GB’s Limit Removed.”

    Everything else you need to do is to set (check) your new boot entry as default via msconfig.

  12. Thanks for your hard work! Needs to be updated though. April windows 8 updates have rendered it non-functional. Step 3 = response of “failed” both when trying to reapply the kernel as well as after deleting the patch and starting from scratch.

    1. Dude you should hit me up. I couldnt get it working on my X86 W8 system. -.- But as for your situation, it should be fairly enough easy. Why dont you uninstall the updates , and run bleachbit and remove installer files and clean the reg , basically the deep clean feature, and reboot. Then you should be refreshed and able to re-install. I never let MS tech tuesday auto install. I would always come home to a blue screen. LOL
      let me know if that works out for you. And once I get my system flowing steady again maybe you could give me a pointer or two to get it patched and moving. 😀


  13. when i try to enter this line C:\WherePatchPaeIs\PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe its say “failed”, anybody help….

    1. tell me you didnt enter it like that right? You actually entered the location of the files right? Like if it was saved to your desktop, you entered
      C:\Users\”whatever your profile name is on your PC”\Desktop\ “the name you saved the file under” (example)


  14. for me in step 3 it also says failed! having Windows 8 Pro en-Us May 2013 by Murphy78. Previously, it worked for me like a charm. Now it doesnt want to patch.

    Do you want to make an upadate, so we can use this patch for newer Versions of Windows 8?

  15. Windows 8 pro(with last updates) dont work:
    C:\Windows\System32>E:\pae\PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe

    1. also, before run windows update everything worked fine, but after updating flew off, new kernel is not available patch

  16. Hi, everyone!! Maybe i talk a “little shit” but, if i can make a backup of kernel patched, and after windows updates, i restore that? You try make this? I waiting a response. See later.

    1. I have tested this on a physical machine (DELL D630). If you save your old kernel (ntoskrnx.exe) you can still use it after a failed patch operation against the newer version as long as you follow all the proper steps as outlined by the developer. In my case I simply made a copy of ntoskrnx.exe, re-patched to double-check – patch failed, the OS still booted to the new ntoskrnx, but naturally providing access to only 3.5G of RAM and not the 5G installed on this machine. I renamed the new kernel, renamed the old patched one back to ntoskrnx, rebooted and the OS can once again address all 5G. As mentioned in another of my posts, this scenario is not ideal since the older kernel does not benefit from the latest MS fixes and enhancements, but at least you can access all your memory, and nothing gets broken…

      1. Nice buddy,
        Thats what I do no matter the procedure. Ever since Windows introduced the concept of restore points, and my smarter than me friends always recommending to me to make redundant back ups of ALL my data. That concept of making a snapshot of what ever Im not sure of will break my system or not, before I modify it, is a standard practice. Plus learning about modding and bypassing and “cracking”, lets your mind grow and become more resourceful and creative.
        Glad to see others doing the same. ☻

  17. Folks, please do not perform the patch on systems updated since March 2013 (using windows Update for example), since the patch will not work (if you do it correctly following the readme it wont break your system but you will be downgraded to 3.2 GB of RAM after the reboot). Previously patched systems will continue to function as before (addressing all of your RAM) even if you apply the Windows updates, as long as you do not re-patch your kernel (such systems will of course retain any vulnerabilities / issues that have been addressed in subsequent MS updates).

    @WJ32, it seems MS did not like what you did for us and they have tried to close the door on us – could you please let us know if you have found / believe you can find another way in?

    1. @Colin and all, i wonder does it work for me ??

      i’m running HP Pavilion g4 2216TU, core 13-3110M 2,4Ghz,
      2 GB RAM (932 MB usable),
      Windows 8 Pro 32-bit OS, x-64 based processor,
      Update were installed 5/5/2013 12:11 AM.

      I wonder how can I reduce / remapping hardware-reserved memory usage for the machine, so i can get more usable-memory ? does the patch can do such stuffs ?

      any suggestions will be appreciate.
      thanks, regards.

      1. Im guessing that your laptop does not have a seperate GPU (grafix processing unit). So that alone CAN, but not always take anywhere from 64Mb up to 1Gb+ of RAM just to “function” normally. This I know from experience and research on my own, and from school. I just corrected my teacher on this subject in front of the class. 😀 If you can, change the amount of memory your hardware uses, you can do it in 2 places. One is a setting in the registry that addresses virtual memory allocated. It will NOT give you more RAM, but it increases the systems total virtual memory. Think of that as RAM combined with unseen Phantom RAM. It uses the page area on your HDD.
        The other and Direct method is in your system BIOS. At power on, enter your BIOS, and look in your system config to see if there is a entry for video memory. Just remember the lower you go, the less you can do, because there will be less that you can see, literally. Certain games will not play with less than the desired amount of RAM. Certain formats of video will not decompress. Certain Windows programs will not be able to function with lower resources. Or they will just slow to a grinding slow speed similar to that of a 1GHz or so, processor.

        If you want to utilize your little amount of RAM, I would use

        those are the smallest OS’s that I know of and have used. The last one for example is only 30Mb (the entire OS) and takes only 80Mb for a complete install. All three of those OS’s can be ran live. Meaning off of a Disc, with no install.

        I hope that helps.
        Peeeeeeeeaaaaaceeeee out!

  18. Hi Irfan, I am not a developer so do not have an intimate understanding of the mechanics of this patch (nor for that matter do I have the skill to comprehend the code even if I had the source). However, I do not think this is what you are looking for if you machine has less than 4 G of RAM. The purpose of this patch is to permit use of more memory than Win8 32-bit is officially designed to manage (i.e. typically 3 to 3.5 G depending on hardware reservation requirements). This patch is really useful if you need to run more than 4G of RAM (I am running 8) and you cannot or do not wish to use an X64 version of Win8. As for your OS declaring only 932 MB usable out of the 2G it can see this might need further investigation.

  19. I note that the version of the kernel version is not a patch with the message failed, the loader kernel lends itself to unlock

    1. I note that patching the kernel version ru_windows_8_enterprise_x86_dvd_917687 does not work with the version of the message failed, the loader kernel lends itself to unlock

  20. @wj32, any progress on an updated version capable of patching the newer kernels MS has been imposing for the past couple of months via Windows Update?

    1. I’m quite busy right now, but if I don’t get it done in the next few weeks feel free to send me an email to remind me 🙂

      1. Windows_8_enterprise_x86 kernel version 6.2.9200.16604
        Microsoft Windows [Version 6.2.9200]

        C:\Windows\System32>PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe


      2. You asked me to remind you – so here it is 🙂

        I see there has been work done here by others who I am sure are quite competent, but I am not completely comfortable with any fully automated option that in addition appears to remove the original BCD entry. I would much prefer your step by step version and / or your validation of the other work presented here before proceeding further 🙂

          1. Much appreciated 🙂 … Lots on my plate here too right now 🙁 …Expect to update next week 🙂 … Thanks again! 🙂

  21. Hello wj32,

    Mine also same problem, can you provide us latest PAE patch for kernel version 6.2 (build 9200)

    c:\Windows\System32>takeown /f ntoskrnl.exe

    SUCCESS: The file (or folder): “c:\Windows\System32\ntoskrnl.exe” now owned by u
    ser “xxx\Administrator”.

    c:\Windows\System32>C:\PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe


    Microsoft Windows [Version 6.2.9200]


  22. Im looking through the code, I think the first 4 values are unneeded (I ran comparison with this vs another patcher that works and looked at before & after kernel image differences) thats the only sense I can make, gonna try recompiling and testing it.

    1. Well, only if I knew where to get the dependencies & what software to compile it with lol… ugh, I try to compile in visual studio express 2012 and it cant find ph.h file & gets lots of wincrypt.h errors…. help!

  23. Ok, think Ive got it figured out, recompiled a new version and testing it atm. The byte comparisons look good on stock kernel vs the patched one. So, will test my installer script shortly w/ the patched version of the pae2 patcher.

  24. Ok, Ive successfully rewritten some of the code to work w/ both the older & newer kernel. Basically in the loop that compares the target & original code in the kernel, I have it skip 1 byte because I notice that one byte is different between the older kernel & the newer one. This does not mean, of course, that MS wont change some other byte again in the area … this patch looks for ‘pattern matching’ … heres the updated archive which has the new binary in root folder & modified source file

    Ive also created a patcher which does all of the steps needed. I was using an older method for win7 & vista, before I found this script, which meant patching the MUI files as well. The script has an uninstall option when you run it with argument ‘uninstall’ (w/o quotes)

    The above file automates the entire process for you.

  25. found a way out of a situation where the involved PAE kernel does not support the original remains in the cache through a search draw appropriate kernel patching treatable:



    1. is to copy and rename

      Microsoft Windows [Version 6.2.9200]
      C:\Windows\System32>PatchPae2.exe -type kernel -o “C:\Windows\System32\20522.exe
      ” “C:\Windows\System32\20521.exe”


      [[ For Windows 8: ]]
      6. bcdedit /set {e041b0af-ddd5-11e2-aeb5-8ef23a4a1248} kernel 20522.exe
      This will set our boot entry to load our patched kernel.

  26. that works as well, but ur still using an older kernel version. If you use my modified script(1st link if u dont want the autopatcher) it will work on newer kernel builds.

  27. best script for all windows (vista, 7, 8). this will install only if you have 32bit os and if you have more than 3gb ram.
    it is not add another boot entry. it replacing existing one so you can safely install
    write following text to a note pad and save as “install.cmd” and placed on save folder contains “PatchPae2.exe”
    note that script will shows error if you don’t run as administrator mode

    @echo off

    NET SESSION >nul 2>&1
    IF NOT %ERRORLEVEL%==0 (ECHO.& ECHO failed….
    ECHO. && ECHO Run as administrator by right clicking this cmd
    ECHO. && TIMEOUT /T 6 >NUL && EXIT)

    ::check windows is 32bit
    if exist “%Windir%\SysWOW64\cmd.exe” exit

    ::check ram is more than 4gb {patch only above 3gb ram}
    for /f “tokens=2 delims==” %%A in (‘wmic memorychip get Capacity /VALUE’) DO CALL :slotot %%A

    SET/A MEMSLOMB=%MEMSLO:~0,-1%/104857
    GOTO :eof

    SET RQR1=REG QUERY “HKLM\SOFTWARE\Microsoft\WinDOws NT\CurrentVersion” /V “ProductName”

    IF EXIST “%windir%\system32\ntoskrnx.exe” DEL /F /Q “%windir%\system32\ntoskrnx.exe” >NUL
    “%~dp0PatchPae2.exe” -type kernel -o ntoskrnx.exe ntoskrnl.exe
    IF EXIST “%windir%\system32\ntoskrnx.exe” bcdedit /set {current} kernel ntoskrnx.exe >NUL

    IF EXIST “%windir%\system32\ntkrnlpx.exe” DEL /F /Q “%windir%\system32\ntkrnlpx.exe” >NUL
    “%~dp0PatchPae2.exe” -type kernel -o ntkrnlpx.exe ntkrnlpa.exe
    IF EXIST “%windir%\system32\ntkrnlpx.exe” bcdedit /set {current} kernel ntkrnlpx.exe >NUL

    IF EXIST “%windir%\system32\winloadp.exe” DEL /F /Q “%windir%\system32\winloadp.exe” >NUL
    “%~dp0PatchPae2.exe” -type loader -o winloadp.exe winload.exe
    IF EXIST “%windir%\system32\winloadp.exe” bcdedit /set {current} path \Windows\system32\winloadp.exe >NUL
    bcdedit /set {current} nointegritychecks 1 >NUL
    bcdedit /set {current} bootstatuspolicy ignoreallfailures >NUL
    bcdedit /set {bootmgr} timeout 5 >NUL
    bcdedit /set {current} increaseuserva 2500 >NUL

    1. do not rush things, there is always a good alternative, as is 64-bit version of Windows 8.1 Preview, which only began to be tested on the client computers, although it can be said of a certain stability and speed kernel Smaller volume of occupied space on the system partition as compared to the previous uncle Bill’s development office …

      1. Saferbytes x86 memory bootkit – the only credible alternative that does not replace the original kernel and bootloader, and only the right boot information in the MBR

        1. despite the fact that in the Windows 8.1 build 9431 with a version of the 6 .3 .6431.0, which initially incorporated support for PAE mode (ntkrpamp.exe – multiprocessor kernel Windows with more than 3 GB of RAM)

          1. with that at the moment the only version of the kernel is included in the assembly of Windows 8.1 Preview build9431 ntoskrnl.ehe the original file name NTKRPAMP.EXE, multi-processor with PAE, and in which it is possible to unlock inaccessible memory

  28. when i type PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe

    it just shows:
    unsupported kernel version .

    i can’t continue to next step

    how can i fix it ?

    1. If it goes on Windows 8.1 build 9431, the patch bezsilen with a specific version of the kernel at the moment there is a good alternative to this patch, such as Saferbytes x86 memory bootkit

      1. If it goes on Windows 8.1 build 9431, the patch is powerless with the specific version of the kernel at the moment there is a good alternative to this patch, such as Saferbytes x86 memory bootkit

  29. that, under what other new updated if the patch on the same link gives a similar warning:

    Microsoft Windows [Version 6.3.9431]
    (c) Корпорация Майкрософт (Microsoft Corporation), 2013. Все права защищены.

    C:\Windows\system32>PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe
    Unsupported kernel version.


  30. Thanks! I followed the instructions in the included text file. I have tested and the system can indeed allocate more than 4GB in RAM. Windows reports 20GB RAM useable. Games (Grid 2) work fine too.

    Windows 7 SP1 32 bit
    2xXeon E5540, Quadro K5000, 24GB RAM

  31. I think you’re a master. A genius or something similar. Thank you so much. Could you please tell me if I can run this patch in Windows 7 Pro 32bit native installation on a MacPro machine?


  32. I don’t understand what people with Integrated intel graphics should do. I have 8 GB of RAM on my laptop and just 3.3 is usable… :/

  33. Hi, installed beautifully on my machine, Windows 7 w/Sp1 but then I ran a ‘tweaker’ program that I believe turned my ‘patched’ loader to “forcedisablePae”, is that supposed to be so in our ‘patched’ loader? or is it ok to have it like that?Thanks in advance for your response and your fine work on this limitation in Windows 32 bit.

  34. is there any troubleshooting link or part in where I can see why the hell am I the only one that can patch my CP, thanks !!!!

  35. Hi wj32, I used this patch for my tablet but got problem. It’s a win8.1 pad, which is using Intel Atom z3770 cpu. According to the official description, seems it can only support 4GB memory. I guess maybe this patch is trying to patch to use 128GB, so failed on my pad. Can you help? Thanks in advance!

  36. Trying this on Win7 32 bit SP1 on an older T2500 Core Duo system and it does not boot, getting Windows Loading Files which fails, then Repair menu. Patchpae2 says that both files patch correctly. System has ATI graphics and I thought that their drivers are ok. Any suggestions? Is the patch still valid with all the windows updates since last tested? Should I try a basic VGA driver rather than the ATI driver?

    1. Sorry tried it again and it booted this time, I was able to see that everything is set up correctly with bcdedit /enum yet I see 4GB installed 3.5 GB usable. The 3.5 usable should be gone after the patch as I understand it. Any suggestions to determine if the patch is working?

  37. WIN 8.1 PRO = doesn’t work at bootup!! pls fix/help!! at after windows loading screen it tries to go to login screen but instead I get a terrible graphics problem, some have gotten BSOD, I get a bunch of random pink spots and fuzziness…. PAE patch for win8.1 isn’t working!

    1. Go back through the procedure and make sure your using “-type kernel -o ntoskrnx.exe ntoskrnl.exe” and not “-type kernel -o ntkrnlpx.exe ntkrnlpa.exe” which is for Win 7,probably the most common mistake.Also make sure your in c:/windows/system32 at the command prompt or it will not work correctly,take your time,follow the steps correctly,make sure you do them all correctly and you should be fine

  38. Can anyone help me ? I recently installed win7 32 professional and wanted to use this hack , I upgraded my system thought windows update so my winloadp is 6.1.7601.17514 and my ntkrnl is 6.1.7601.18409 I booted into pae patched kernel but there were 2 BSOD’s my laptop is acer v3 771G and here are .dmp files:
    caused by ntfs.sys and ntkrnlpx.exe
    Thank you very much 🙂

    1. Clear all aspects of this patch out, and go to here; ,scroll down to “download” and download and unzip..then install using the GUI interface. Have gone to this and I’m no longer getting any of the BSOD I was frequently getting w/the patch.Do install all of the updates for your operating system 1st,and it will install and run fine,even tells you in the ‘log’ file that they’ve to a non-standard’ loader and it takes care of that too.

  39. i have BSOD using your patch and every single patch i’ve found in the internet. it’s always complaining about direct x and nvidia files. but works fine in safe mode. please help, can i fix that? 64 bit is not an option for me

  40. Colin, Joshua, go to the page for Win 8.1

    and scroll down to the postings by evgeny November 23 2015 where you can download the latest patch for Win 10.

    There is also a post further down by Escape75 on November 23 giving a link to an executable script file he wrote incorporating evgeny’s patch.
    This works well, it installs the patch and does all the hard work for you.

    It would pay you to read the various comments on this site concerning Nvidia video drivers which prevent the patch from working

    1. This worked for me (Win10 Version 1511 – OS Build 10586.63) – I ran the patch commands manually using the instructions in the PatchPae2 readme against the updated patch (PatchPAE3). Many thanks for the guidance.

  41. Windows 7 SP1

    Not work with PAE ! ! !


  42. Windows 7 SP1

    Not work with PAE ! ! !


Leave a Reply to uncle Bance Cancel reply