PAE patch updated for Windows 7 SP1

Note: An updated version for Windows 8 is available.

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

Download: (4942876 downloads)

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.

To remove the patch:

  1. Run msconfig, click Boot, highlight the entry named “Windows 7 (PAE Patched)”, and click Delete.
  2. Delete the files ntkrnlpx.exe and winloadp.exe from C:\Windows\system32.


    1. You see, this is the reason why MS disabled more than 4GB on 32-bit systems. Because of fishy drivers that can’t handle memory above 4GB. The fault is Intel driver, not the PAE patch.

      Now, some versions of Windows Server do support more than 4GB on 32-bit. You may try Intel HD drivers for those versions of Windows. Note that I have NO IDEA if it will work or not! Basically you are at the mercy of the driver maker.

      1. Well, I have dug deeply the internet and from what we have found the following problems:
        Microsoft has put a restriction of 4 Gb memory on all 32-bit versions of their operating systems from Vista, except for the Server versions (2003, 2008 and 2012). The reason is not known and there are several assumptions and rumors.
        Intel is a partner of Microsoft in many things and not offended things decided it will not fix the bug in their driver (HD 2000/3000 and 2500/4000) which gives a beautiful crash every time you use a PAE kernel versions in a 32-bit no Server Windows O. S.
        And these crashes doesn’t happen with Nvidia and AMD/ATI drivers.
        This is very clear because Intel has partnered with and is a partner in developing drivers for GNU / Linux systems that have 32-bit PAE kernel and there is no limitation in the intel graphic driver nor crashes.
        I also read that a user who probably did an upgrade from Windows XP to Seven, did a rollback of a Intel HD Windows 7 driver to a XP driver version and has worked fine (Windows PAE kernel driver Intel HD XP).
        Unfortunately if you try to install the XP driver ain the Windows Vista/7/8 the system informs that “the computer does not meet the requirements”.
        Then the bullet hole is there. Based on the Intel driver for Windows XP, or modify it to be accepted by Windows Vista/7/8 or modify the Intel driver for Vista/7/8.
        I believe even in not a bug, but a deliberate restriction.
        And so is this link ( Forum Intel can sit and wait that Intel will fix this pseudo “bug”.
        The other options are:
        Use the Standard VGA Driver
        Buy a Graphic Card (not Intel) to user with Windows PAE kernel.
        Migrate to Windows 64 bit versions.
        Migrate to Linux.
        And f**k the consumer.

    2. I can’t believe it, but I got Win7 to work on a Intel HD 3000 graphics (i3 Sandy Bridge) with this PAE patch.

      The solution was using an XP 32bit driver, which seemingly can do PAE. The only downside (?) is that it will NOT do Win7 Aero. But at least that’s better than the standard VGA driver, since it can do the full resolution of attached gig screens.

      Here we go:

      1) Patch Win7 for PAE

      2) Boot Win7 in unpatched mode

      3) Download the HD3000 Windows XP driver, I used this one:

      4) Unpack

      5) Edit the INF file in folder \Graphics\igxp32.inf by copying the WinXP section to the Vista/Win7 section:

      5a) before:

      ; no install on Vista/Win7

      ; no install on Win8

      5b) after:

      ; no install on Vista/Win7
      %iSNBGM1% = iSNBM0, PCI\VEN_8086&DEV_0106
      %iSNBGD1% = iSNBD0, PCI\VEN_8086&DEV_0102
      %iSNBGM2% = iSNBM0, PCI\VEN_8086&DEV_0116
      %iSNBGD2% = iSNBD0, PCI\VEN_8086&DEV_0112
      %iSNBGM2P% = iSNBM0, PCI\VEN_8086&DEV_0126
      %iSNBGD2P% = iSNBD0, PCI\VEN_8086&DEV_0122
      %iSNBGD3% = iSNBD0, PCI\VEN_8086&DEV_010A
      %iIVBGD0% = iIVBD0, PCI\VEN_8086&DEV_0162
      %iIVBGM0% = iIVBM0, PCI\VEN_8086&DEV_0166
      %iIVBGD0SRV% = iIVBD0, PCI\VEN_8086&DEV_016A
      %iIVBGD0GT1% = iIVBD0, PCI\VEN_8086&DEV_0152
      %iIVBGM0GT1% = iIVBM0, PCI\VEN_8086&DEV_0156
      %iIVBGD0SRVGT1% = iIVBD0, PCI\VEN_8086&DEV_015A

      ; no install on Win8

      6) Install the patched driver by
      Device Manager
      -> Your Graphics Chip
      -> Update Driver
      -> Browse my computer…
      -> Let me pick…
      -> Have disk
      -> Point it to the folder with the INF file

      You might have to agree to install unsigned drivers

      7) Change the Windows 7 theme to Windows 7 Basic

      8) Restart and enjoy 4+ GB RAM with HD graphics 🙂

      1. I did this in Sunday and have testing it before publish to avoid headache with lots of questions.
        Really works but the Aero don’t work and the speed it’s no to great compared with the Microsoft VGA Generic driver.
        But I do this in other machine that I have with the G41 chipset and have the same issue.
        Well, I prepared to install the VGA after uninstalled the intel HD driver but Windows 7 have installed a Microsoft HD driver instead.
        Well, I just try it and works with this driver that’s present in the Windows update on the G41 vdriver.
        But it works in the HD2000 chipset too?
        I don’t tested this too.
        Maybe this weekend.
        But if you can try this Andy and later report we appreciate.

        1. Thank you, Andy, it works! ) To help other users I’ve uploaded to Mediafire file host ready-to-use package of WinXP 32bit / driver, modified to use with Windows 7 SP1 (and maybe 8, not tried)

          Supported GPU:
          Intel(R) HD Graphics
          Intel(R) HD Graphics 3000
          Intel(R) HD Graphics Pxxxx
          Intel Haswell HD Graphics

          Install clicking on Setup, or via Device Manager, or New Hardware wizard. Do not forget that driver is functional with some limitations. Only 1 point in Windows Experience Index, so Aero expectedly don’t work, then I’ve noticed glitches in Rome Total War video scenes, and not all graphics details in game – driver doesn’t like different OS. But it’s completely playable, and also no problem with HD movies. Try on your own risk of course

      2. Can you send a video fr wht u have said above …..i have patched windows 10 n its successful but whenever i try to install intel hd graphics my screen goes black simply saying m facing prblm …….Is there any way to use window 10 pae with intel hd graphic …..pls try to reply wid working video how you do it i shall be grateful to you

        Mail me at =

  1. The problem seems to be the driver of this Intel HD Graphics (Mobile Intel® 4 Series Express Chipset for me). Without it, I can go up to 1280×768 on my Dell Latitude E6400 using standard Windows VGA driver. As soon as the driver is installed, after Welcome Windows startup I have black screen and laptop freezes. But I can always enter within the Windows safe mode. Do you think that memory is shared differently with that kind of graphics adapters?

    1. It’s the driver’s problem. It probably uses 32-bit variables to store physical addresses which are actually 64-bit, truncating the addresses and reading/writing random memory.

    2. Same problem with Dell Inspiron 14R N4110 here. I only want to ask, if you have another graphic driver (mine is AMD Radeon HD 6630M), does disabling the Mobile Intel HD Graphics would solve the black screen problem?

      1. yes I was using pae hack with switchable card set to only radeon 6490m until my radeon chip died and it reverted back to intel only and then I got black screen. not sur eif I can fix radeon chip easily but I will try the driver hack next.. sucks intel havent paw support in their latest builds WTF.. i will prob end up installing windows 8 64bit since laptop can support it.. but much work reinstalling stuff which I wanted to avoid.

    3. I had this problem too with Mobile Intel® 4 Series Express Chipset.
      but I changed my graphics driver to XP driver, and now it’s working fine. except, I missed aero themes, but I’m using 4GB ram fine.

      1. ou god, it’s not just aero theme I miss, the graphic processing is so much lower now (let alone it was awful before…), can’t even play normal old games now.
        I’m switching back.

    1. Sorry, I was wrong. All work fine 🙂
      I was get BSOD 8e becouse had overclocked memory 2*270*(5/3)=900MHz (5-5-5-15) for DDR2 800. Then I grow up timings to 6-6-6-18 and tested with MemTest86+. Currently memory is stable and Windows 7 with PAE patch stable also.

      Thank you).

    1. Apologies for my inferior reading and Googling skills, I used the old patch. However after finishing all steps successfully and rebooting to the new patched Windows, the usable RAM size was still only 3,46 GB.

    2. how did you get that done coz im going through the same issue. there isnt any winload.exe file in the patch anyway. I followed step 4 exactly but i still got the error ‘ windows cannot find the path specified’

  2. My pc didn’t overclocked at all, and the configuration are on normal setting… , but still BSOD, windows 7 sp1..

  3. Dear Wj32,

    Thank you for this worderful patch. What I want to know is that, all the steps mentioned in the readme text I have to follow. If after patching the system with the patched pae and then I delete PAE folder will it still work.

  4. Hi Wj32,

    I can get into windows but not for a while BSOD. I’ve tried more than 5 times using the patch PAE (Win7SP1) but always BSOD with various kinds of error messages.

    Any suggestions?

  5. Hi everyone. Can someone explain me how to completely uninstall this patch? I have used instruction attached to patch, but it didn’t worked for me Now Win7 see only 2 GB of ram in my computer :/. I removed patched entry from boot tab in ms config but issue is still the same. Also in the bottom right corner of my desktop appeared info witch says: “Test mode, Windows 7 Compilation 7601″.

  6. work fine here, this is some picture without patched and patched PAE

    non-patched PAE
    patched PAE

    there is some problem, but that must be becouse, like wj32 said, software/hardware issue, in my case i start alot application which use user-mode or kernel-mode drivers but for now i saw just apllications which use capture drivers not work on my system, specifically AverMedia Hybrid TV card and Logitech WebCam

    1. actually my mistake, just AverMedia capture device driver will cause application crash or system hang, depending which application will use that device driver.
      WebCam works fine

  7. thank you very much wj32 for this patch! it works pretty fine on windows 7 pro 32 bit. my kernel-version is: ntkrnlpa.exe 6.1.7601.17592.
    till now no problems with drivers …

    1. And your mobo is?
      VGA driver?
      This issue affect’s only INtel HD (2000/3000 and 2500/4000).
      I tell you because I’m use this patch in a netbook with 945 chipset and has no problem with the Intel Graphic driver.

    1. Did you do all steps like shown in the readme.txt-file?

      I have exactly followed the instructions in the readme.txt, there is no water mark at all at me PC…

  8. I have tried the patch on another Notebook with an Mobile Intel X3100 Grafic-Adapter onboard. The patch does NOT work. It seems to be a problem with the Intel-driver, like people reportet above …

  9. nointegritychecks works only for the 1st boot, after that Windows Startup Repari will launch and complain about bad signature in either ntkrnlpx or winloadp.
    For the rest the patch works fine.

  10. Forget about last post, it works fine just now.
    I forgot my bcd entry has nx AlwaysOff and it seems that option also disables PAE.
    So if you want to have +4 Gb PAE kernel but dont want Microsoft DEP (Data Execution Prevention) on you you need to set:

    bcdedit /set {current} nx AlwaysOff
    bcdedit /set {current} pae ForceEnable

  11. Oh and another drivers that has problems with this memory seems to be MacDrive’s HFS driver, when the patched kernel is active the driver doesnt mount HFS partitions.

  12. Hi, thanks for the post, this helped me a lot, i tried with different patches, but without success. I follow your instructions over Windows 7 Ultimate “Sp1” and it worked just FINE. For all of the guys that didn’t get it working, i would suggest PowerCmd , so you will be able to copy and paste the commands instead of typing everything manually. THANKS again, it works like a charm.

  13. Those who are unable to run bcdedit for error “The boot configuration data store could not be opened”, this may be because your Boot files are on a recovery partition which is not attached by default to the windows. In that case you can press F8 at boot up and enter into repairmode. open a command prompt and do the procedure listed above. HTH

  14. For those who got into a brick wall thanks to intel igdkmd32.sys and the like, they can verify whether this patch works by entering the safe mode.

  15. Thanks for this great hack, my pc works fine with win7 sp1 and this patch and now I dont need move to an 64bit version anymore!

    1. Also that powercmd program makes ur life easier, as it has to do with the progress of this patch. Just copy-pastes and finished 🙂
      Thanks again!

  16. Still can’t work on Intel HD Graphics (Thinkpad x220)
    In safe mode it totally works. When starting normally, black screen just like R0man says.

    So sad… My 6GB RAM…

  17. I got the version before SP1 to work but this one does not.
    I get a Windows repair screen just like when you insert the repair CD.
    I used Powercmd as Administrator hoping that would be an elevated command prompt.
    Anyway.. How do I REMOVE this?

  18. Seems I myself made a mistake.
    I could see what I did wrong in the powercmd history log.

    Anyway it works now.
    I will give a short tutorial how I did it, perhaps someone who is also not very technical will benefit from it.

    Download the patch zip file from this website.
    Unpack the zip file with Winrar to a folder named tinytim on your desktop.
    Download and install Powercmd.
    Run Powercmd as Administrator.
    Type: cd C:Windowssystem32
    Then just follow the steps from the read me which is also in the patch zip file.
    Where it says:C:WherePatchPaeIs
    remove that and put in: C:UsersusernameDesktoptinytim
    Where username is YOUR username.

    So for example this:
    3. C:WherePatchPaeIsPatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

    Would have to be this:
    3. C:UsersusernameDesktoptinytimPatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

    It’s great having bought 4 GB and actually USING 4 GB!

  19. not really working on cores which have memory sharing on built-in gpu’s (arrandale, sandybridge, new gen cores, nvidia’s optimus, other switching techs) unlike when you setup it on a machine with dedicated gpu it will run without any problems.

  20. I get the message: winloadp.exe

    The selected entry could not be loaded because the application is missing or corrupt. Any idea?

  21. I also have tried to patch the Win7 32bit on a nvidia optimus system. I get the same problems as decribed above. Everything works fine with standard vga driver. After install the Intel HD Graphics driver the system hangs close before welcome screen.

    Does anyone with lots of knowledge about memory sharing have an idea how to solve this Intel driver problem?

    1. if its switchable just use catalyst to use the 2nd card always. then should work fine. I think you open power save and select max performance.. by memory since my 2nd chip in laptop died.. I think HP poor heat venting cooks the video chip or maybe its a bad solder point.

  22. Same problem also for me on HP EliteBook 8460p with Intel HD graphic driver.
    Installed this and other 4GB patch, but is always the same: BSOD after entered Seven password login account or the PC crash. If I execute the patched boot in safe mode than I don’t have problem.
    I investigate that the root cause is due to Intel HD graphics driver. In fact I’ll uninstall the driver and execute the patch it works correctly but I have the VGA mode.
    Any suggestion to fix this issue?

  23. Has anyone verified this patch against the latest release of ntkrnlpa.exe?

    File version: 6.1.7601.17713
    Date modified: 10/25/2011 11:47 p.m.
    MD5: F2368C2A4B126B2EAEF1985116B88A1D


    1. After some extensive experimentation, I will respond to my own post. The short answer is, “Yes … the patch will work with 32-bit Windows 7 Professional SP1, from the bare SP1 installation all the way through the latest available updates as of 14 Jan 2012.”

      Intel S1200BTL server motherboard (Intel & Micro$oft drivers)
      Intel Xeon E3-1230 CPU
      Video – ATI 5450 GPU (AMD/ATI driver)
      Sound – Creative Audigy PCI (Creative driver)
      Disks – (2) Seagate 1TB disks configured as a RAID 1 mirror array using standard Micro$oft software RAID

      Kernel revisions:
      The PAE kernel file (ntkrnlpa.exe) on the original SP1 install disc was version 6.1.7601.17514 (20 Nov 1010). The kernel file was updated per KB2633171 to revision 6.1.7601.17713 (25 Oct 2011). PatchPAE works correctly with either kernel file.

      To repeat myself … If you install the PAE patch exactly in accordance with the instructions provided in the package it will work correctly with any 32-bit Win 7 Professional revision level from the M$ distribution discs through the latest updates as of 14 Jan 2012. It is still possible that the patch will fail to work correctly in some environments due to non-standards-compliant third-party drivers.

      I hope this helps.

      1. Theres a new autoit installer and new patched pae that works with all kernels win 7 and 8 as of apr 2013, floating on the p2p channels if have problems.. you just click its exe to install its so simple no manual stuff needed

  24. Nothing to do. Installed last version 6.1.7601.17713 but hte problem is still present if I start Seven in Normal mode. In Safe mode or better removing the Graphic driver (Intel) the problem disappear and I have the 4Gb.
    The main problem is focused on the Intel Graphics drivers that probably are not compatible with PAE enabling 🙁

  25. Windows 7 runs well with Intel Graphics driver for XP. You won’t get the AERO effects but the basic design. Still better than default VGA or blue screen.

    1. I can confirm that the Intel HD XP driver works fine on my Dell N5110 i7 8GB with Windows7 32bit, and I can use the full 8 gigs with the patch. But… the nVidia Geforce 525M with Optimus technology doesn’t work with this driver, so I am not able to use the nVidia card, just the HD graphics. Any suggestions? As a “workaround” I don’t use the patch, but I installed Gavotte Ramdisk which is able to use the memory above 4GB, and I put the pagefile there.

  26. HI all,

    did exactly as the instruction everything went great but on boot it still shows ” 4.00gb 3.25gb usable”
    have win 7 ultimate lic. copy and laptop XPS M1210 DEll can sone one help.

    I tried again and again have more than three entries in boot but none works.

    can some one help me and guide.

  27. i did that and just before the welcome screen where i should write my password for windows it only shows black screen without anything else… 🙁 it seems its not working for me i have windows 7 32-bit with 4bg, but it says 2,36 usable.

  28. Exellent patch!

    Also, big thanks to PA for these 2 lines:

    bcdedit /set {current} nx AlwaysOff
    bcdedit /set {current} pae ForceEnable

    Did not work until after enetering them.

    Sidenote: if the patch did not work from first try, chances are, you booted using the other “Windows 7” boot entry. So to go into correct boot store, the lines above should look like this:

    bcdedit /set {default} nx AlwaysOff
    bcdedit /set {default} pae ForceEnable

    Using this on HP 8540p notebook.

    1. I tried the uniwave patch and it didn’t do anything. I have 4GB ram but still can only use 2.94GB even though it said patch was successful and I got the watermark and dual boot screen. typing in bcdedit proved it did nothing and ntkrlICE.exe file was unchanged. I didn’t try this patch from here and after reading these comments I won’t try this one either. I’ll just install 64bit 7 Ultimate.

  29. Fantastic! Just patched a Win7 SP1 32bit system (Intel i5 with Nvidia gfx) and it now shows the full 4GB that is installed. Mate you are a legend – put the donate button up now!

  30. hi
    I have a problem
    after the restart and start Windows 7 (PAE Patched). I have mesage “Your computer was unable to start” and starting startup repair.
    Startup repair is not corrected the problem.
    what am i doing wrong and what is the solution?

    1. I’ve been having the same problem. I’ve found that if you boot the normal windows first and do something for awhile and then restart and choose the PAE boot choice, the next few times or so you will be OK. Then it’ll do it again and you have repeat the process. It’s a little annoying, but not overly so. I’d still like a fix though.

  31. Qual, é…?
    Cade os mano BRASILEIRO…?
    Háa, tenho o Windows Srever 2008 64 bits…Como resolvo problemas de incompatibilidade com programas (32bits)?

  32. grat Stuff !
    …it works good under Win7.
    How about Vista x86 ? someone tried it there ?

    Hint for Win7:
    if youre PC wont start after “correct” Patching, reboot again and press F8 in Bootmenu !
    Now select the Menu “disable Signature veryfing” and VIOLA youre System will Run after this with FULL Ram !

    1. I ran this for over a year on vista 32, It was like magic. Every idiot out there says that the PAE patch, does not improve game performance. That’s horsesh** I got incredible performance increases from all my games.

  33. I got this to work as well using the intel HD 3000 windows XP driver on windows 7. I downloaded the window 7 SDK for makecert and signed the patched ntkrnlpa.exe based on the german website instructions. Like everybody else I could boot in to safe mode but was just getting a black screen on boot (no windows logo ever).

    We’ll see how we go but it looks like my dell vostro is kitted out with a new SSD and 8GB ram now. I like to run multiple virtual machines.

    1. Come’on! It’s frustrating when someone who doesn’t know anything about something demands everyone else educate them on the subject. Just google PAE and the name of your windows version, and read the results that talk about PAE by itself. Enabling PAE in the BCD does NOT allow the use of more than 4 gbs. This patch fixes that.

  34. Help! I had windows vista 32 and 6gbs ram with the PAE patch installed worked great.

    Then I upgraded to windows 7 32 installed the PAE patch and now I have only 4 of 6 gbs usable.

    I made no hardware changes. Why isn’t the patch giving me all 6 gbs????

  35. I had about a half a dozen blue screens over the last 4 months using this patch with 8 GB ram, the windows XP intel HD 3000 driver, and a OCZ vertex 3 ssd. I got a lenovo T430s and put 16gb ram in that and went back to 3GB on this Dell, which has been relegated to secondary duties.

    1. I also have Intel HD graphics. Managed to run PAE Patch, a new boot entry has been created but I get BSOD too. Some of you guys say that installing the XP driver solves the BSOD. So how did you manage to install XP driver on Windows7? I downloaded both the zip and exe files from Intel’s website but I can not run any setup application because it complains that the installer cannot run on Windows7. I tried running it on Compatibility mode but still having that error. How did you guys install the XP Driver??

  36. Hello
    i did apply the patch before when had 4 GB only of ram , was working great and i was able to use all the ammount of ram
    NOW i added extra 4 GB of ram , it was very strange to see only 3.94 gb usable !!!!!
    i applied a MS update to update kernel to new version which is reported compatible with the pacth KB2633171-x86
    i deleted bcd entries and created clean one > applied patch > but still 4029 usable reported in task manager
    any suggestions would be appreciated
    thanks for this work

  37. Hi,

    I applied the patch and i’m getting the 4GB working on win7 starter. However my graphics driver now isn’t working! (it’s a samsung nc110-intel atom n2600 – intel gma3600).

    When i boot from the normal kernel the driver works fine but only 2GB of the 4GB is useable. When i boot from the PAE patched kernel i got the 4GB set as useable but the intel gma3600 driver has stopped working.

    Any suggestions? Should i try reinstalling the driver or is their something I need to configure?


  38. I got win7 starter on an atom n2600 to recongise 3.25GB of ram – it wouldn’t work with the full 4GB as i think the 64bit instruction set is disabled on the atom n2600.

    As above when I tried the full 4GB the GMA3600 graphics driver wouldn’t load (as i think it needed the address space over the 3.25GB hard limit on 32 bit).

    I did this by going to MSCONFIG -> BOOT -> select the patched boot option and click Advanced Options then m,anually set the maximum memory field to 3328MB.

    I’m happy enough with the 3.25GB as win7 starter is only supposed to have 2GB!

  39. Hello!
    Can you please help? When I try to install the patch I get stuck at the third step:
    C:UsersVIODesktoptinytimPatchPae.exe’ is not recognized as an internal or external command,
    operable program or batch file.
    Any ideas ?
    Thank you!

    1. Alex,

      The 1st thing I would do is move the PAE folder to the C drive so it reads: C:PAE
      Of course, you should have 5 files in this folder:

      After this is done, your step 3 command should read:
      C:PAE\PatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

      Step 4 should read:
      C:PAEPatchPae.exe -type loader -o winloadp.exe winload.exe

      Hope this helps.

  40. Thank you, wj32. I have downloaded and installed the patch. I’ve tested just about everything I could before posting this message. All programs seem to be working appropriately. My only concern was the Adobe PageMaker program I have since it is THE most important application on the computer. But low and behold, it works too! Thanks for making the instructions so easy to follow.

  41. I need help to remove this patch, installed it succesfully but with the result that I cant connect with my internet and my geforce 8600 wont work. Tryed to restore the sytem to an earlier config but it doesn’t help, the patch is still there… :/

    1. Solved it…

      1. Open an elevated Command Prompt window.

      2. cd C:Windowssystem32.
      Make sure the current directory is in fact system32.

      3. bcdedit /enum

      4. Made sure that “Windows 7 (PAE Patched)” were listed as {deafault}

      5. bcdedit /delete {default}

      Done! Restart and my Windows 7 in original started. =)

  42. I got it working on my OptiPlex 380 at office. Both Resource Monitor and System Info show that I have 8GB installed and usable.

    Here are the screen dumps:

    I also had the Intel driver issue. As told by comments above, I have to install the XP version of driver (no Areo, no big deal for me). My situation is I then encountered BSOD after XP driver was installed. It was due to Windows was trying to install another driver for Win7. So with two drivers, I got BSOD. I simply disable the Win7 one, and viola!

    @wj32 thank you so much for your work. I have no option for 64bit, but I have to run VMs for work. You saved my life.

  43. Hi, wj32. I really need a patch for Windows 8 as my old laptop has just 4GB memory. A 64bit version do takes more memory while I usually open quite a lot of tabs in Firefox.
    Also, many Chinese bank and the offical sites are still sticked to WinXP 32bit, and 64 bit softwares are often missing or cannot be setup directly due to the different path.

    Would you please update this patch ?

  44. Also interested with windows 8 patch. Please make it, i’m going to install windows 8 only if patch is released, thank you.
    Or somebody can give instructions how to manually modify files using hex editors.
    Currently with windows 7 sp1 32bit, 6gb ram, never had any problems.

  45. OK, install and work good on “HD western Digital sata 320 gb AV series BUDT” with Windows 7 on “Samsung R580 notebook” . PAE Patched > 3956 mb RAM disponible > OK

    But, NO BOOT (error of ntkrnlpx.exe no found…) on “SSD Samsung 120 gb 840 series” , system and the same machine….!

    repeated 3 times…NO BOOT (PAE Patched) — BOOT OK > Win32 (no pae patched)


    Luca Zapparoli
    Gorgonzola (MI)

    thanks also.

    1. sorry, solved

      the system on SSD had received two commands before starting the patch.
      1) bcdedit / set {current} nx AlwaysOff
      2) bcdedit / set {current) landscape ForceDisable
      Blocking the kernel patch. (!!!)
      Removed all.
      launched two commands:
      1) bcdedit / set {current} nx AlwaysOn
      2) bcdedit / set {current} pae ForceEnable
      3) patch as instructed
      4) re-started

      ok updates
      nvidia more ‘available RAM
      photoshop also
      RamDisk also


  46. I was getting the crash with this in win 7 32-bit enterprise. I downgraded my video drivers to the win XP ones and now it’s working great!!!

    1. I spoke a little too soon. It appears to crash (BSOD) when watching video for more than a few minutes. If I don’t watch video it’s stable.

  47. I have successfully patched a current 32bit Windows 8 download upgrade. 8GB appear to be available. Unfortunately Adobe Creative Suite 6 programs don’t work. Does anyone has experienced this and maybe knows a solution?

    Thanks a lot


  48. HP ELiteBook 8470p With intel HD 4000 you have to install the latest XP drivers and change the .inf (copying from the Windows part of the INF to the part that says ;no install on Windows 7) and it works… If you try with the Windows 7 Drivers it boots and hangs.

    Just my 2 Cents…


  49. WJ32 I have another problem not yet mentioned hereabove:
    There is no winload.exe and no ntkrnl–.exe in my System32 folder, but in c:/Windows/Winsxs there are 4 winload.exe’s of even date and 4 ntkrnlpa.exe of even date.
    The full reference of one such ntkrnlpa = “C:\Windows\winsxs\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.17207_none_6c5f1f0a15341779”.
    No. 2 finishes as: 18044_none_6e173b82127da724, / no.3: 21417_none_6cddedcf2e59d05b and no.4 as: 22210_none_6ebd48cf2b868ae6
    They are dated all 5 Jan 2013 and have the following time: 07:02/07:00/06:53/06:49

    I executed the remainder of the bcdedits hoping (in vain) that the boot-loader would search for the actual ntkrnlpa.exe’s.

    So now I have a double boot option of which the PAEpatch selection runs into the same problems a number of people have too: i.e. startup repair with no final solution.

    I run Win 7 Ultimate + SP1 – 4GB available (2.96 usable) – (done earlier with bcdedit /set increaseuserva 3072)

    Any suggestion to get the PAEpatch selection utilize the WINSXS folder entries, even with 4 different register entries for the even-dated ntkrnlpa.exe’s ?

  50. After having a patched Win7 Ultimate 32 on an MSI notebook, I ust tried to patch my Windows 7 Ultimate on a Atom D2700 driven machine.
    When I select the patched winloaid version system stops caused by an inaccessable device.

    I still have no idea where this comes from.

    I also set up Win7 Ultimate in a virtual machine, giving 6 GB of RAM to it. Patch worked fine on that virtual machine, so I do not think that it’s the patch itself.

  51. Update: I was too stupid this time, sim´ply forgot to switch off integrity check.
    Patch works fine but this time it could not help, because the display driver (Intel Atom D2700) crashes when additional ram is enabled.
    I found a beta state driver for Win7 x64, even this driver on Win7 x64 crashes. So my new Atom driven mini-pc will remain 32 bit having 3.25MB addressable.

  52. Hi all, not working for Toshiba Satellite Pro A100. I went through all the steps but the system couldn’t start. Then I added also the “nx AlwaysOff, pae ForceEnable” to the bcd and the system starts correctly although still only 3.00 GB usable. Processor supports PAE (checked with sysinternals), Mobility Radeon x1600 graphics.

  53. it is working for me with some differences
    instead of patch signature checking i use the signtool suggestion from this resource ( )
    because my gigabyte z77n-wifi have intel hd4000 graphics i had to downgrade the drivers to modified inf file as suggested above.

    Finally there is 16GB – gfx memory available
    the only minus is that the performance in graphics goes from 6 to 1
    the only question is why there is “test mode windows 7 kompilation 7601” in the right-down corner.

    1. Can you explain how you do to generate the certificate etc, etc, etc, step by step?
      What softwares are used?
      I’m very interested on these!
      It’s better than the workaround trying to modificate the intel video driver.

  54. It worked for me. Thanks for this patch, buddy. Just one doubt. Is it better to use this patch with 32 bit windows version or install 64 bit? Nowadays processors are still 32 bit processing, just memory addresses got an update to 64 bit. I guess processing 64 bit is more expensive for the processor, once it will have to break 64 bit words in two 32 bit, processing and remount again. Or am I mistaken?

  55. I typed in the commands line by line. It appears to have partially worked for me. I built my PC via components, and the Motherboard/Processor supports 32 GB RAM.
    Upon using this, I now have 24 GB RAM available, but I still have 8 GB RAM that are not usable. How would I got about correcting this?

    1. i believe its not 64bit addresses is the reason.. but 36bit so I say thats why 8gb still not available.. I suspect if laptop can support win 7 or win 8 64bit go and install that.. as it will be better and still faster then patching win7 32 .. theres a new kernel patcher for pae on p2p netowrks if search for it.takes away manual steps mishaps.

  56. Hello!, it didn’t work for me, i tried with version 3000, 4000, P3000, P4000 and it only gives me a 1920×1280 resolution, and the optimal for me is 1920×1080 so, every time that i install the controller through the patch file, the system automatically updates it. I have 6Gb of Ram and my pc is a core 2 duo. The driver for my graphics card (the conflictive one) is INTEL (R) G41 express chipset and i need to use the 6 Gb of my RAM memory, what can i do now? i repeat: The configuration in the INF patch file is good, but i can’t have the optimal resolution and the system updates the driver automatically. Please help me.

  57. Hi, can you tell me which p2p channel that is? My kernel version is updated at mar 2013 so this patch doesn’t work for me. And I can’t find the new patched pae anywhere on torrent channels 🙁
    Thanks a lot.

    1. Hey, it works, but occasionally the screen flashes and the system send a recuperation message and than it looks normal again. Barton88 can you fix that? and also thank you for do this 😀

    2. Hello Barton88!
      How you patch this driver?
      Can you make the same for Intel® HD Graphics 2000/3000?
      Or can you explain howe to me and other make the same on Intel® HD Graphics 2000/3000?

      1. J. J. COB, it’s as simple as cut/paste in driver’ *.inf file )

        For HD 3000 driver (same as 2000, but more powerful) see my post at about 10% from the top of the page (or search the page for my nickname). But be ware that it isn’t flawless in 3D games – can be slower by 50%

    3. Is the patched intel HD graphics driver still available? Best would be the newest for a Thinkpad X200 released version ( Or instructions how to patch. Thanks!

  58. Hey, it works, but occasionally the screen flashes and the system send a recuperation message and than it looks normal again. Barton88 can you fix that? and also thank you for do this

  59. Hi Barton88,
    Thanks for your fantastic jobs!~
    But, I still have one question about this, I got 6GB RAM installed, but after patch, there is only 4GB available.
    It seems to be M$ had another patch to get this limitation back, do you have this problem also?


    1. Update, I can saw my 6GB RAM at first when I applied this patch, but after few days latter with Windows update, my RAM got back to 4GB left.
      If I removed the patch, there will 3.05 GB left.

    2. I’m sorry wj32, I missed recognized Barton88 as developer…
      Deeply sorry for my mistake!

      And, thanks millions of your fantastic job of this path.

  60. After some doupts about the behaviour of windows 7 32bit after patching, I run some tests analysing the memory usage with resmon and Sysinternals rammap :

    Sysinternals testlimit.exe -d 512 in multiple instances (administrator shell) : process usage increased not limited by 2/4 GB up to my 8 GB, then I stopped the test and closed the process instances (command shells).
    Result: memory usage per process limited to 32bit, multiple process memory usage not limited.

    Then with Totalcommander, I did a search for the text “hello” over a big disk partition.
    Result: Win7 file cache increased up to my 8 GB (standby means “memory in use but can be release upon other requests). Then I stopped the search.

    This means: Windows 7 32bit is using the full 8 GB RAM without any tweaks or registry hacks for process or file cache.

  61. tested with dell optiplex 780.. original oem win 7 SP1 the one that came with dell’s win 7 CD.. up to date (with all updates up to this date from microsoft)

    i had BSOD (windows did not even start after i restart).. but had to enter en safe mod..disabled integrated (intel) video installed drivers from device manager..actually it has Intel(R) Q45/Q43 Express Chipset i restart again then downloaded the driver for XP version(32bits) for same chipset..installed using original setup.. asked me to restart..restart it.. all iS OK and so far working.. i have 5.84 available ram of 6 GB.

    if someone interested, this is the original driver i downloaded and tested OK:

  62. Primo RamDisk is good way to use more then 3.25 GB RAM on x86 systems. It’s complaint with any Intel onboard graphics because no kernel patch requested. It is possible to put pagefile to invisible (IMM) for OS memory. I use SSD and to keep it from unnecessary write operations move TEMP/TMP variable to RAM by using Primo Ramdisk 5.6 Server Edition.
    Primo Ramdisk works together with kernel patch on Windows 7 x86 SP1 Right Now, Samsung 530U3C with 12 GB of RAM. I wants so much memory as possible and cann’t install more.
    Thanks for the Good Patch Job.

  63. I follow the instruction when I restart and choose Windows7 (PatchPea), the system always SHUTDOWN. Can you guy help me to find out the solution.

    1. Thankyouthankyouthankyouthankyou. Thank you. I spent at least 3 hours on trying to make this work and all I had to do was downgrade Nvidia drivers to 320.18.

      1. it works all fine incl. the driver from NVIDIA 332.21 … i ´ve installed newer … and my system crashed 🙁
        (WIN 7 32bit geforce nvidia 9600gt)
        have a nice day 😉

  64. Does this patch work only for ms windows, or along with practical apps like 3dsmax photoshop etc… I mean can other applications other than windows make the use of more than 4gb Like computer graphics apps for exemple?

  65. I have applied the patch on a Windows 7 Ultimate SP1, but I cannot find a “PAE compatible” nVidia driver (I have a Quadro FX 580). Lots of artifacts and after a while BSODs appear (when using modified kernel), related to graphics drivers. I have read some were lucky with older nVidia drivers…so I would like to know which driver versions are confirmed to work perfectly while in PAE-enabled kernel mode. Thank you very much in advance, GABRIEL.

  66. Hmm, so far it has been 2 days and I have not had any problems like BSOD or anything. I have Windows 7 Ultimate SP1 and the patch worked just fine. I am worried though about what I should do when a Windows Update occurs and the whole process is reseted. Do I use the patch again from the patched OS or I go back to the default OS and use from there again?

  67. I installed this two years ago in my windows starter system, and had only had driver issues (resolved at the time). But today August 15, 2014, provided several updates windows update; of which one is incompatible with PAE patch.
    After a few hours, I have the list of suspicious updates (all of them are windows security updates):


    Meanwhile, I will avoid installing security updates for windows on my system.
    In short, beware of windows security updates from KB2949927

    1. I had the same today after appling them… I have noticed that both ntkrnlpa.exe and winload.exe have been updated (mine are 6.1.7601.22736).
      The first was patched correctly but winload not; the PatchPae2 output is “Failed.”
      Me too I think the offending one is (Availability of SHA-2 hashing algorithm) because it updates both files! I’ll remove it asap…

  68. You too huh? I will try installing all the other updates except the security ones. Well, I also have some updates for Microsoft .NET Framework so I wonder if I should exclude them as well.

    1. Then again you can see which updates affect the PC negatively by checking the update history. I assume all those that Failed to be installed are the cause.

  69. This patch works great but be aware that it breaks the Intel USB 3.0 driver for Windows 7 32-bit that comes with the new X99 motherboards. You get an exclamation mark in Device Manager. However, if you de-install the Intel driver the USB ports do operate just fine with the generic Windows MS drivers, but only at USB 2.0 speeds. (NB: the Intel X99 chipset drivers do get on fine with PAE, the conflict is only with the Intel USB 3.0 driver). The driver I tested was downloaded from Gigabyte’s website – – “Intel(R) USB 3.0 eXtensible Host Controller”
    The package includes the equivalent driver for Windows Server 2008 R2 and Windows Small Business Server 2008 and perhaps this can be modified to install under Win 7, maybe it works better for PAE? If anyone succeeds with this please post the detailed procedure here.
    Also, has anyone gotten Intel USB 3.0 driver to work on other Intel 9 or 8 series chipset motherboards under PAE?

        1. Thanks for info, I downloaded this newer Intel USB 3.0 driver but decided not to install it for now. Since I acquired a Renesas uPD720201 PCIe USB 3.0 card from ebay and this gives me 4 native USB 3.0 ports (two via the back, two via internal 19-pin header) – this is the exact one:
          My Device Manager config now looks like this:-

          The Renesas USB 3.0 drivers are very stable and mature and work perfectly with PAE Patch. I find this to be the best workaround in this situation. 4 ports (plus an external USB 3.0 hub) give me sufficient USB 3.0 options. As for the integrated Intel USB 3.0 ports of the X99 motherboard, I don’t mind if they are stuck at USB 2.0 speeds using generic Win 7 driver, since the attached peripherals like keyboard, mouse, scanner, printer, etc. are all USB 1.0/2.0 devices anyhow. (I also have VMWare Player v.6.0.3-1895310 with a Win 8.1 x64 virtual machine and this does detect all Intel ports as USB 3.0 with standard MS drivers as you’d expect…)

      1. Yes, at least on my Seven!
        This morning I have installed all the pending ones, then I have removed only KB2949927 and here I am again with patched kernel!! 🙂

          1. Well, yea. You can start the default OS as well. It won’t have the updates though. Currently I have marked the latest updates as Hidden.

  70. MS has officially removed the KB2949927!!!
    •V1.0 (October 14, 2014): Advisory published.
    •V2.0 (October 17, 2014): Removed Download Center links for Microsoft security update 2949927. Microsoft recommends that customers experiencing issues uninstall this update. Microsoft is investigating behavior associated with this update, and will update the advisory when more information becomes available.

    1. Hmm, it seems the particular update is no longer in my hidden updates. Perhaps MS removed it automatically or something. I will try installing the rest of the updates to see if I get a problem again.

    1. It worked on both my laptop, but on one I had to search for a “not public” hotfix that put the pc on the LDR branch!! kb3023266 contains an LDR winloader that patchpae2 can’t process! 🙁
      The hotfix I had to remove is “An enterprise hotfix rollup is available for Windows 7 SP1”

      I was lucky to find it quite quickly 🙂

    2. KB3035131 and KB3033929 -> ntkrnlpa patched, winload failed.
      I don’t know which of the both brought the unpatchable winload.exe, maybe both because both renew ntkrnlpa.exe and winload.exe.
      So I uninstalled them and patching worked again.

      1. Really? In that case I will remove tham as well, I mean, who cares about only 2 updates. Its better than wasting time rebooting over and over again.

        1. Actually, it seems the culprit is KB3033929 so those who can’t load their patched Windows just need to load the Default OS, go to Windows Updates to find KB3033929 and right click on it to Uninstall it. After uninstalling it it will ask you to restart. Do so and then choose your patched OS this time, it will load. Well, mine did.

          1. Thanks, the missing step after the unisntall of KB3033929 is go to windows update, manually seach updates, and hide KB3033929 in windows update

          2. thanks!
            My list of ‘Microsoft Windows’ updates is mysteriously missing in the Installed Updates list. Then I had to use
            wusa /uninstall /kb:3033929
            from elevated cmd. I had to hard reset because it was 10 minutes stuck in a “Windows updating…” screen with no HD activity.
            Rebooted to not-patched OS, patched both files again, rebooted, and the trick works again in all its glory. 7,67Gb usable out of 8Gb installed.
            This issue served me to remember how slow was my W7 with only 2~3GB usable RAM!
            Thank you wj32!!

          3. I’ve been a PAE evangelist ever since finding out about it a couple years ago. I have experienced issues after previous updates but have just re-patched and every worked fine again. That was not the case after the big MS Update a couple days ago and I was starting to panic when I had to revert to the non-patched boot and realized how much slower my computer was without three times the useable memory. Luckily, I stumbled across this thread and specifically the updates by Achmed and Condor. Big big thanks for figuring out which patch caused the problem. Saved me loads of time and frustration, I’m sure.

          4. thanks so much ! removing KB3033929 (only) worked for me, too.
            how does one hide it from updates as suggested by Luk ?
            what should we pay attention to when installing future security updates ?

          5. To hide an update you click on the f.e. 1 Important Update or 1 Optional Update left of the Install Updates button. It will lead you to all the available updates to install. The re you can right-click on an update and choose to hide it preventing it from trying to install again.

        2. Patches can be mostly analyzed in advance by selecting patch details. It leads to the corresponding microsoft patch page or directly browsing

          If it shows a section “file information”, one can search for winload.exe or ntkrnlpa.exe – I didn’t, so I had to uninstall the mentioned patches.
          Anyway, as a wise man said: “To fall is not to fail, unless you fail to get your backup again”

          1. Hmm, I see. SO if I search there and find anywhere mentioning winload.exe or ntkrnlpa.exe I should skip that update, right?

  71. Hi all,

    I’ve gave it a try on my Windows 7 x86 and it worked as a charm. But…it lasts only until the next reboot. I can reapply the “fix” and again it works. I’ve deleted the original files (ntkrnlpa.exe, winload.exe) leaving only the patched ones. I’ve removed the original boot entry leaving only the PAE version as the only boot option. I ran out of ideas…
    Any suggestions will be appreciated.

    Thank you !

    1. Yea, I have a suggestion as to why this happens to you. Its because you delete those 2 files from “C:Windows/system32”. You must leave them be as soon as you install the patch. The only reaseon to delete those files is if you want remove the patch.

      1. It makes no difference like I said if the files are there or not. I’ve deleted the originals after I tried about 3-4 times without deleting anything. This is the problem, not me deleting the files.

        The steps were:
        1. New Windows 7 clean install
        2. Applied the patch
        3. Rebooted selecting PAE option – the patch works 4GB available
        4. Reboot – select PAE option – back to normal 3GB available
        5. Repeated 2 to 4 with the same result
        6. Deleted the original files and the boot entry to see if it makes any difference – 3GB available.

        I hope it’s more clear now.


        1. Hmm, just in case, have you checked in the boot options if perhaps the memory limit is set to 3 GB or something? Just saying it might be the case. Go to Start -> type “msconfig”(without quotes) click on the Boot tab and then click on the Advanced options. There if where it says Maximum Memory the box underneath it is checked and it has a value inputed just uncheck the box.

          1. Hmm, weird. What graphics do you use? AMD? Nvidia? If it was Intel HD you would have gotten a BSOD so it shouldnt be the case.

          2. I see. Even if you do not get a BSOD it is known that the PAE patch is a bad match for Intel Graphics which may be the reason why it only works temporarily. I also remember reading that the patch may not work on most laptops which might a reason as well.

  72. 4. C:\WherePatchPaeIs\PatchPae.exe -type loader -o winloadp.exe winload.exe
    This will patch the loader to disable signature verification.

    if bootleg enter when says failed just move on, bootleg windows already have hacked loaders but will still create winload files for u to use when going through instructions

    1. It also seems I did something wrong or due to using a bootleg windows and the loader not patching correctly, windows 7 under PAE patched will boot into windows repair. So if you on a bootleg windows I do not believe this will work for you (but also if your on a bootleg windows you might as well just use a flashdrive to reinstall windows to 64bit.)

  73. Hi
    In my window 7SP1 after 4. C:\WherePatchPaeIs\PatchPae.exe -type loader -o winloadp.exe winload.exe >>This will patch the loader to disable signature verification.
    Result Failed:

    So even if I move on , and follow the next instruction, after reboot Ive still kernel error unsigned.. error
    Any clue ?

    1. From other answer
      Here the reason


      Meanwhile, I will avoid installing security updates for windows on my system.
      In short, beware of windows security updates from KB2949927

      I can attest that uninstalling these updates, removing the current PAE patch, and re-patching works.

  74. Hi Yann,

    Can you please tell me the version of ntkrnlpa.exe and winload.exe you’re currently using?

    My versions are as follow:
    ntkrnlpa.exe – 6.1.7601.18741
    winload.exe – 6.1.7601.18649

    Thanks and regards,


  75. Yet another pack of updates were released today. I personally got 22 updates and as usual I was weary of them. And I was right. After installing them, when I tried entering the patched OS I always got a BSOD, so I started uninstalling security updates one by one till I find the one responsible. And I did find it (after an hour), its the security update KB3045999. So, those who have to install their updates should hide this update and those like me who suffered from it should just enter the default OS and remove it from there, then re-enter your patched OS.

    1. You don’t have to remove the update. Boot into the non-patched kernel and reapply the patch. Removing that update is not safe because it leaves you vulnerable to the security flaw that the update fixes. The reason the update breaks the patched Windows version is because it updates winload.exe (you can see “winload.exe” under the file information section at Update 3045999 probably changes the way winload.exe interacts with some other Windows components that are also updated by 3045999. However your patched Windows version uses a patched winload.exe (winloadp.exe) which isn’t updated by 3045999, so when the Windows components updated by 3045999 expect winload to behave like the winload.exe as updated by 3045999 they get to deal with a non-updated winloadp.exe and this causes the BSOD.So install the update, which updates winload.exe, then patch it again to make an updated + pae-patched winloadp.exe.

      1. That is fine, if the patch works with the new component installed by the update. The last time there was an update like this the patch would not work. Thus the uninstall solution.

  76. thanks Condor. keep posting these when you find an update that gives BSOD. you saved me a lot of time and frustration.

    1. This morning I have checked/installed all the fixes from January (I had time… 🙂 and tested this new patcher.
      It worked perfectly up to (SHA-2 code signing support) which contains ntkrnlpa 6.1.7601.18741 and winload 6.1.7601.18649 (winload is the one not supported by the original PatchPAE2!!)
      I’m still missing the latest one which contains ntkrnlpa 6.1.7601.18798, I’ll leave it for later…

    2. If you have failed error on winload patch, use maxdm’s file. I have all updates and it worked for me! Thanks mate, thank you all guys.

    3. Hi maxdm,
      could you please reupload the modified PAE patch that you created,…..cause the link that you originally pprovided does not work anymore!

      Thanks in advance!

  77. maxdm
    April 16, 2015 at 9:34 am

    I have modified original patcher for latest windows 7 SP1 updates support:

    Yes, I have tried it succesfully, maxdm kindly included the source also, not spam nor fishing
    File analysed

    This file was last analysed by VirusTotal on 2015-04-16 16:59:58 UTC (18 hodin, 42 minut ago) it was first analysed by VirusTotal on 2015-04-16 16:59:58 UTC.

    Detection ratio: 0/56

    SHA256: 79dd09b79817a4fb701a3d96cb8bd9670e3f73e773fc02fbd35226af52c456c1
    File name: PatchPae2.exe
    Detection ratio: 0 / 56
    Analysis date: 2015-04-16 16:59:58 UTC ( 18 hodin, 43 minut ago )

    1. Today I did Windows update, security fixes only, after that, patched ntkrnlpa.exe and winload.exe with your modified patcher – everything ok, 8GB usable.

    2. I must have been an idiot to try the modified patchpae2.exe from above poster. Norton is having a field day getting rid of the virus now.

  78. The patching process goes through but eventually it does not work for me. I get a BSOD following the display of the windows logo at startup with the following indications:

    STOP: 0x00000116 (0x8C629510, 0x97B38CB4, 0x00000000, 0x00000002)
    nvlddmkm.sys – Address 97B38CB4 base at 97A26000, DateStamp 54d160… [I missed the final figures]

    By the way, I have an NVIDIA graphic card running the recently aupdated GeForce 341.44 Driver.

    Thank you in advance for your kind help!

    1. FYI, the problem was indeed the NVIDIA GeForce 341.44 Driver.
      At the moment, the easiest solution seems to be downgrading to the GeForce 332.21 Driver.
      It worked well for me.

  79. sigh~ Another batch of updates were released again and there problems this time as well. So far whenever there was a problem with an update either the Windows Startup Repair would start or I would get a BSOD, but this time I got a forced restart lol. Anyway, again I figured which update is the cause and that is KB3022345 so if you have installed it uninstall it and if you are lucky and read my message right now you will just need to uncheck the update preventing it from being installed. I had my suspicion about this update from the beginning as when I read the update’s information it mentioned that it needs a previously bad update, KB3045999 which I/we hid but I thought of installing it anyway as it might have worked.

    1. No, those two updates are safe but there is no need to become paranoid about updates. When new updates are available you have the option if clicking on the More Information of each update and see if it might be bad to install it or not. If for example you read in the prerequisites that in order for the new update to work one of the already bad/hidden updates is/are needed then you should not install that update.

  80. Hello, thanks for the effort.

    Unfortunately, patching of my loader fails. Which also revealed a flaw in the patcher — such an error (detected deep in the Patch() code) is not propagated to the exit status of the tool thus making its checking a bit useless (I made a batch script to “harden” the process against my mistakes — commands are cut&paste-d :)).

    Freshly installed & fully patched Windows 7 Pro/CZ
    winload.exe: Version 6.1.7601.18649, Build date: 2014/10/31 23:22, Language: Angličtina (i.e. English/US 😮 even in my Czech Windows)

    Any idea? TIA,

    1. Oh, the angle backets and its text were striped off :-(… Please, read the Patch() function name something like

    2. I checked the suspicious KB list from this thread one more time and found KB3033929 still sitting among my installed updates; removing it has helped. Ie. the primary issue has been solved. I’m sorry, that’s my fault.

      Nevertheless the error information propagation issue (easy to fix) persists, as well as the incompatibility of winloader patch with updated Win7/SP1. The latter seems rather serious as the first question of a support personel is usually “Have you installed all updates from MS?”

      Dear Wj32, do you plan to update the PatchPae2 to resemble new environment(s)?


        1. Yippee! A few restarts including a forced one (re-applied updates locked in “Don’t turn your computer off” screen — what else one can expect from MS X-() and voilà, I’ve almost 8gigs and no pending updates 🙂

          Many thanks to you for pointing this hack and maxdm for the update (sounds like a neigbour according to the virusscan reports).

          It must be a nightmare to have to analyze disassembly/trace(/source?) of those modules and fit a patch…great job.


    1. I installed a bunch of updates yesterday, after my success with pathcing the loader. It seems none of them touched those key modules (loader and kernel). I decided to keep date-stamped copies for future reference…

      1. kb3057839 caused random bluescreens with 0xcf and 0x50 on Terminaservers.
        after removal anything is fine again.

  81. These were installed yesterday w/o issues (and no need to re-patch) at my side:
    # KB3059317, KB3063858, KB3033890, KB3058515, KB3057839, KB2952664
    # KB890830

    1. Thank you!
      I “left alone” that KB for deeper check because it doesn’t contain the file included list but it does reference kb 3045999 that DO contains a kernel update!
      After I’ve read the detail “The diagnostics tracking service collects diagnostics about functional issues on Windows systems that participate in the Customer Experience Improvement Program (CEIP)” I’ve simply hided it because I do not care about CEIP… 🙂

  82. hi there,

    I got a little problem. I tried to patch as it shown in the readme file, but I cant disable the integrity check. there is always an error, bad command bcdedit /set…
    if I reboot wirhout the integrity command I will get the repair center. any help?

    I also uninstalled all mentioned security updates and downgrade nvidia to 320.18

  83. Just follow Step-by-Step in the readme replacing the xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx with the actual entry created!!
    For me (i have saved the output at first run) was:

    readme (stripped to leave Win7 only!!)
    1. Open an elevated Command Prompt window.
    2. cd C:\Windows\system32.
    3. C:\WherePatchPaeIs\PatchPae2.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe
    4. C:\WherePatchPaeIs\PatchPae2.exe -type loader -o winloadp.exe winload.exe
    5. bcdedit /copy {current} /d “Windows (PAE Patched)”
    6. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} kernel ntkrnlpx.exe
    7. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} path \Windows\system32\winloadp.exe
    8. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} nointegritychecks 1
    9. bcdedit /set {bootmgr} default {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
    10. bcdedit /set {bootmgr} timeout 2
    11. Restart the computer and enjoy.

    I have copied the steps to a new text file and replaced all the “xxx” with the actual output from step 5 (i have just changed the timeout from 2 to 10):

    bcdedit /copy {current} /d “Windows (PAE Patched)”

    bcdedit /set {99e2cc75-08bd-11e0-8109-a1433afa9d1d} kernel ntkrnlpx.exe
    bcdedit /set {99e2cc75-08bd-11e0-8109-a1433afa9d1d} path \Windows\system32\winloadp.exe
    bcdedit /set {99e2cc75-08bd-11e0-8109-a1433afa9d1d} nointegritychecks 1
    bcdedit /set {99e2cc75-08bd-11e0-8109-a1433afa9d1d} pae ForceEnable
    bcdedit /set {bootmgr} default {99e2cc75-08bd-11e0-8109-a1433afa9d1d}
    bcdedit /set {bootmgr} timeout 10

    1. If my drive is not C instead of G, can I just replace all command from C : to G:? Does it workable? Please let me know, thank you very much.

  84. I had the same problem as ppl that come here, my kid has Windows 7-32 installed with 4GB RAM but only 3GB usable (Toshiba Satellite A300).

    I tried a few automated solutions, including this one from WJ32.

    It didn’t work for me because the step
    C:\WherePatchPaeIs\PatchPae2.exe -type loader -o winloadp.exe winload.exe
    kept giving me “Failed.” instead of “Sucess”.
    I’m sure it has something to do with some installed KB from M$, (Achmed above talks about KB3035131 and KB3033929).

    So, I went and did all the steps manually, patching my ntkrnlpa.exe, using an Hex editor, replacing the (8B 45 FC 85 C0 74 0A) and (8B 45 85 C0 74 FC 09) sequences for (B8 00 00 02 00 90 90), using the tools makecert.exe and signtool.exe from the Platform SDK and the same bcdedit commands as ppl stated here for the boot menu (+ Pae ForceEnable and the testsigning setting).

    Result = Success. 4GB usable in Windows.

    IMPORTANT tip: If you fiddled with the msconfig – Boot menu – Advanced Options, MAKE SURE the “Maximum Memory” is unchecked. My patched kernel changes wouldn’t make a difference until I unchecked it. I had it checked with 0/4096/other values, and the usable memory was always stuck at 3GB. The moment I unchecked it and rebooted, I finally got 4GB usable.

    Thanx for all the tips in these posts. Helped a bunch.

  85. More MS updates have broken the patch — any idea which ones? I last updated in May 2015, so something between then and now doesn’t agree with the kernel hack 🙁 Le Sigh. Our clinic is moving to x64 in January but until then we have to use this patch (or else lose 5-6GB of usable memory). Thanks everyone

  86. The Nvidia drivers are still from late 2012, so that wasn’t the issue (we have a GPO that stops auto update so this is on a test computer). After several hours of uninstalling patches one by one, I found that KB3067904 was the culprit. I’ll install the other ones I uninstalled during testing one at a time and ping back if anymore cause issues.

  87. What I have done today to check updates for PAE compatibility:

    After Windows Update showed new updates, I right-clicked on the KB… entries to check for modification of winload.exe or ntkrnlpa.exe

    Then, I downloaded these fixes that modify them.

    Then, I unpacked the kb…msu to a previous created unpack dir named “expdir” (expand kb…msu -F:* .\expdir).

    From expdir, I unpacked the unpacked kb…cab to a previous created unpack dir named “unpk” (cd expdir ; expand kb…cab -F:* .\unpk).

    Then, I searched in unpk any occurences of ntkrnlpa.exe and winload.exe and copied them to a third temporary directory – windows copy gave them a number with space and bracket, but I changed the name, so it has only the number, no space, no bracket.

    Then I run PatchPAE2 on any one of these winload…exe / ntkrnlpa…exe to see if it fails
    If it worked (“patched”), I installed the downloaded patch.

    May this description help somebody…

  88. I’m having a little trouble too. Some windows updates causes windows to fail startup and goes into startup repair. What updates should I avoid? (I have avoided the KB3033929 update as that gives your system an infinite startup loop.)

  89. Thank you so much for this patch.

    I’m now able to use all of the 6 GB of RAM my aging PC has got rather than just the little over 3 GB I was able to use previously.

  90. Can anyone help me with this? I have a ton of windows updates to install, but the problem is, that some windows updates just don’t work with paepatch. Any ideas which ones are not cooperating with the patch? Help!

  91. I have succesfully patched my x86 windows 7 professional.
    I use NVIDIA GeForce GTX650, however when my vga driver was loaded the windows can not startup (always black screen after windows logo).
    Otherwise, when i dissable my vga driver, it startup succesfully and read my 8GB RAM.

    Please help me, it’s just a little bit to complete.

  92. You can use PAE patch for 8.1 modified for windows xp/2003/vista/2008/7/8/8.1/10 since KB3033929+
    You find it in PAE patch updated for Windows 8.1 thread, see escape75 comments.

  93. I’ve been following this thread for some months and am grateful for information you have offered. Now it’s my turn. Recent WU KB I have found to be 32-bit W7 Greater-than-3GB-RAM-PAE-Patch-preventing culprits are: KB3097966 and KB3083992. Best wishes!

  94. Hi! What kind of text did i replace in the -type loader command line? where i can find my “loader”? for the kernel version i used “ver” command in cmd, but for this i don’t know what to do!

  95. Hi folks: I’m writing to report that finally with the newset driver (win32_153342.exe) I was able to have a native Windows 7 driver working with the kernel PAE patched with no blue screens!
    Kudos to Intel for fixing it.

    The driver is signed as version: date: 21/12/2015.
    My hardware is a Dell Laptop with an i5 3210M and an HD4000 Intel graphics card.

    1. WOW! That’s could be “the news of the year 2016”!!!!!!
      I’ll give it a try in a few days!
      Thank you for letting us know!!

    2. Unfortunately that is not true on my Seven SP1 with Intel HD 2500… 🙁 I get a BSOD 0xBE that means “An attempt was made to write to read-only memory”

      Current driver was release on 13 jan 2016
      Here you are the Intel report:

      Intel(R) HD Graphics 2500
      Report Date: Sunday, January 31, 2016
      Report Time [hh:mm:ss]: 4:49:39 PM
      Driver Version:
      Operating System: Windows* 7 Enterprise (6.1.7601)
      Default Language: Italian (Italy)
      Installed DirectX* Version: 11.0
      Supported DirectX* Version: 11.0
      Shader Version: 5.0
      OpenGL* Version: 4.0
      OpenCL* Version: 1.2
      Physical Memory: 3283 MB
      Processor: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
      Processor Speed: 3200 MHz
      Vendor ID: 8086
      Device ID: 0152
      Device Revision: 09

  96. I got some problem on shutting down.
    my laptop just stock on shutting down screen and not shutdown at all, except pressing power button.

    Please help.

  97. Hey guys,
    Everything works fine BUT the command “C:\PatchPae.exe -type loader -o winloadp.exe winload.exe”
    which says failed, and as a result (I am guessing) it does not work on my computer. Could this be related to having a SSD by any chance? I see that for most of you it has worked well actually. I have a Toshiba Satellite A205 running windows 7 SP1 with 4gb RAM Thanks!!!!!!!!

  98. Update…. I did a fresh install of windows 7 pre activated in my SSD and then, before applying the patch, I run what luca zapparoli (IT) suggested, it worked like a charm! Grazie mille Luca, bravo!

  99. Hello all. I started with a clean install of Windows 7 x86 SP1 and the patch appears to have worked with no changes, but I still only see 3GB usable instead of 4GB. If the patch had failed would I still be able to boot successfully into the modified kernel? Has anyone else seen this issue?

  100. Hi maxdm,
    could you please reupload the modified PAE patch that you created,…..cause the link that you originally pprovided does not work anymore!

    Thanks in advance!

  101. I used this and it worked and I could boot into windows but….when i tried playing games it would load them but before entering to play it would bsod and at times when idling or playing media it bsod’s as well..

  102. You should always create a backup, even if you’re not applying patches.
    Please make sure you uninstall the KB’s listed above before proceeding.

  103. Let me add the following KB’s to this as well, that seem to be malfunctioning for the patch:

    1. How is there not like…. a list of these KBs to uninstall? I’m basically uinstalling half of my security updates just to patch it. I can’t re-install them? Aren’t they supposed to keep my computer secure. So in order to have more than 4 GB of ram, I gotta deal with security vulnerabilities in my system? -_-

      1. I’ve done further testing, you would need to uninstall only the following three: KB3153171, KB3146706 and KB3147071. The others work fine as long as you use the latest patch.

        The reason these 3 don’t work (I think) is that they seem to update the files patched. Maybe an updated version of the patch would be able to solve it.

        1. Lol thank you for the response Liam but I am just going to install a 64 Bit version of Windows. This is way too much effort plus I have 12GB of ram and an i7. I need a system arch that can handle all that I throw at it. Most things are compatible with 64 Bit today anyways because everything basically is 64 Bit.

          1. What a nonsense reply.
            The reason to use 32bit Win results from older, expensive hardware without 64bit drivers.
            If you install 32bit Win just for fun, thats your problem.
            But don’t tell us, that we need 32bit Win further, such a fuzz.

          2. I don’t want to have to re-purchase a particular program which runs acceptably on Windows 7 32-bit but not 64-bit.

          3. In my case I had to repeat the patching after the kernel was updated. I got a bunch of updates and I dont know which, but one installed a new ntkrnlpa.exe with version 6.1.7601.19135 and dated 22/1/2016.
            Regenerating the ntkrnlpx.exe file worked

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

    1. the same is happening to me…my laptop has an nvidia quadro and it blue screens on the nvidia kernel driver. at this point, i would have to have a driver compatible with the patch.

  105. Hi there, finally managed to get it working for Intel HD5xxx series (HD5500 in my case), it should also work for HD6xxx as the driver states it supports it.

    I patched my kernel as described here, I didn’t patch the winloader because of security fixes, but used this method instead (loader only)

    When booting patched kernel windows normaIly had the BSOD because of Intel graphic driver (igdkmd32.sys)
    When booting in safe mode the patched kernel, my memory was recognized, I knew I had to poke around the Intel graphic driver.

    I tried to install the driver from the links provided in the comments but it didn’t work, my graphic adapter was too recent apparently.
    After a bit of research I finally found this one
    to support my graphic adapter and for XP 32 bits

    I installed normally the XP driver from the link when I was in safe mode
    I rebooted my patched kernel Windows normally
    It worked 😀

    Thanks wj32 for all the work, and to all people that commented about solving the driver issues, it helped me to get it working 🙂

  106. Hello Wen Jia, i am using Patch Pae on my windows 7 for 3 years.

    In 3 years, when my computer try to update windows7, Pae is not working.

    Well, i don’t rememember what is happening when we update the windows 7(its probably adds 2GB RAM limit again and don’t lets Pae work)

    Im using windows 7 starter pack 32 bit.

    I can install SP1 update. But i dont know which update is disabling the Pae.

    The update, which disabling Pae is probably a firewall update. But i don’t know anything about codding.

    So, i need to install windows updates for using Visual Studio 2015. But i cant install any updates because i need Pae. I have 3 GB RAM and Pae removes the 2GB RAM limit for my PC.

    I don’t know which update is causing it. But if you going to solve it, i can try all of the updates manually to tell you which update causing the Pae disable.

    Sorry for my bad English.


  107. Windows Update KB3175024 had to be uninstalled for my PAE Patch to work. It was published on Sep. 13, 2016. I hope this helps someone.

  108. I was unable to patch 4. C:\WherePatchPaeIs\PatchPae2.exe -type loader -o winloadp.exe winload.exe
    everytime Failed

    1. Same problem here: all command lines work fine but this single line 4, aiming to disable signature verification, will persistently result in FAILED

      When Rebooting it invokes BOOT RECOVERY going for 6-7 times, killing many System Restore Points as well!

      Anyone have a good suggestion how to successfully proceed?

      1. win 7 right ?
        I found this frustrating too but its a pretty good feeling when it works!
        The boot loader is failing- so the error recovery starts immediately, The error recovery is a sure sign that PAE patched kernel you’ve created is not connected to the boot option.
        I tried this 7 times untill i used copy and paste instead of typing – then it worked.

        You get nice feedback for the first few commands saying patched successfully etc however the bcdedit commands say operation completed but really they dont do much checking so they can be wrong and you wont notice- until you see windows recovery AGAIN..
        save the Win 10,8 ,7 patch from this site. extract zip files contents to the C drive (not in a folder or anywhere else). (This works on win 7)

        – insert the id you get into the {} using copy paste.. (right click top left of cmd- edit-paste)
        Other than that change NOTHING at ALL.

        C:\PatchPae2.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe
        C:\PatchPae2.exe -type loader -o winloadp.exe winload.exe
        bcdedit /copy {current} /d “Windows (PAE Patched)”

        bcdedit /set {} kernel ntkrnlpx.exe

        bcdedit /set {} path \Windows\system32\winloadp.exe

        bcdedit /set {} nointegritychecks 1

  109. Hi, I run my W7 SP1 with 12GB with “pae = ForceEnable” and “increaseuserva = 3072” without any problems or stability issues.

    Many comments in the internet says that “increaseuserva = 3072” reduces the available kernel memory to 1GB. Is this true only in 4GB environments or also in my 12GB environment?

  110. The patch works flawlessly (great job, wj32!); not so the OS, due to a sort of “conflict” between the video card driver and the kernel memory manager.
    This is an intentional situation, I suspect; in fact, such an incompatibility appeared just after the discover of the crippled kernel on the workstation systems. At the same time, any support for the server version ceased. Any attempt to install the video card driver on a server system is frustrated by a BSOD.

    Strangely enough, the “conflict” is resolved by activating the “Desktop Experience”; it would be interesting to take a look to the real composition of the package.

    Since I currently have no access to the “Desktop Experience” files, I put the problem right as follows:

    I bought an old, cheap Radeon card and I installed it beside a newer Geforce card.

    I downloaded Microsoft “DEVCON”; then I wrote two small batch files:

    @echo off



    bcdedit /set {bootmgr} default {nnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnnn}

    shutdown.exe /s /t 00

    @echo off



    bcdedit /set {bootmgr} default {nnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnnn}

    shutdown.exe /s /t 00



    zzzzzzz-zzzz-zzzz-zzzz-zzzzzzzzzzzz is the identifier of the “PAE Patched” boot entry

    nnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnnn is the identifier of the original “Windows 7” boot entry

    By executing the first batch file, the Geforce is disabled, the Radeon is enabled, “PAE Patched” becomes the default boot entry, then the system is shutted down. The second batch file reverts the process (Radeon disabled, Geforce enabled, “Windows 7” default boot entry).

    By using the switch “/r” in place of “/s” the system is rebooted instead of shut down; I use the /r switch because I have to disconnect the monitor from one card reconnecting it to the other one.

    Doing so I can have an 8 GB RAM system with a graphic accelerator, even if not so “sparkling”, or a “usual” Windows 7 system but provided with a decent GPU.

    Hope it helps

  111. Hi,

    How to correct this error?

    C:\Users\Ivan3>bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} kernel ntkrnl
    O tipo de dados do elemento especificado não é reconhecido, ou não se aplica
    à entrada especificada.
    Execute “bcdedit /?” para obter assistência da linha de comando.
    Elemento não encontrado.

  112. Hi Ivan, you are using the wrong path, which is why there is an error.

    You should be in C:\Windows\system32 directory to issue the commands, as explained in wj32’s readme.txt file.

    It is also much easier to put the patchpae.exe in system32, so that paths do not have to be specified in the commands.

  113. The people who have left comments concerning the inability of “PatchPAE” to properly work with winload.exe prove that this is not an isolated case…
    I love the comment about “either you can’t follow directions” or “system won’t allow use of more than 4GB”.
    How about “If the code worked, we wouldn’t be having these problems.”
    I really don’t care that “support” isn’t provided for ‘freeware’, but if you’re going to post code for people to use on their systems, for heaven’s sake PRODUCE FUNCTIONAL CODE!
    Here’s the proof:

    Ran PatchPAE2.exe (beyond Windows 7 SP1)

    Patched Kernel
    FAILED to patch Winload

    Ran PatchPae (Windows 7 SP1, specifically)

    Program ‘stops’ working – doesn’t do a thing; except generate an error –

    “Application has generated an exception that cannot be handled.”
    Process ID=0x17dc (6108), Thread ID=0x113c (4412)

    Command Prompt Window contents:

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>PatchPae2.exe -type loader -o winloadp.exe winload.exe

    C:\Windows\system32>PatchPae.exe -type loader -o winloadp.exe winload.exe

    Unhandled Exception: System.IO.FileNotFoundException: Could not load file or ass
    embly ‘ProcessHacker.Common, Version=, Culture=neutral, PublicKeyToken=n
    ull’ or one of its dependencies. The system cannot find the file specified.
    File name: ‘ProcessHacker.Common, Version=, Culture=neutral, PublicKeyTo
    at PatchPae.Program.Main(String[] originalArgs)

    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\M
    icrosoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure lo
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus

    Something is obviously amiss… Any answers?

  114. Guys, I found this driver from Dell. Maybe this is our solution for 32-bit driver?

    Intel HD Graphics Driver

    This package provides Intel HD Graphics Driver and is supported on Enterprise Servers T20 running the following Operating Systems: Windows Server 2008 R2.
    Fixes & Enhancements – Initial Release.
    Version – Version, A00
    Category – Video
    Release date – 26 May 2015
    Last Updated – 27 May 2015

    File Name: T20_Video_Driver_DCP6V_WN32_10.18.10.3308_A00.EXE

  115. Well, it appears that no one has an answer as yet as to why the “winload patch” fails to apply…

    For those of you who are experiencing this issue, there is a resolve that will allow the system to load with the PAE patch – it is outlined very well here:

    Yes, it has to be translated from German. It can be reached directly at
    They also had an ‘automated’ method of applying the PAE patch. It has been taken down, but they have provided instructions to manually apply the patch.
    (Which very nicely shows precisely what is being done.)

    Yea, there is a ‘watermark’ in Windows afterwards, but that may be the least of the issues encountered by applying the patch.

    Be aware that there is no guarantee the patch will work…

    I myself had issues with the nVidia display driver (who said nVidia drivers worked?) and had to replace it.
    The patch otherwise proved to be incredibly unstable – three BSOD’s within 30 minutes, all related to the patch, either directly or indirectly (i.e. was listed in the stack trace for the fault, either in conjuction with other drivers, or in and of itself in a memory management error – no kidding, since EVERYTHING in the enviroment was designed for 4GB).
    (And yes, the system is compatible – No issue with the hardware itself.)

    Good luck – if there’s need for access to more memory than 4GB, this MAY solve it; if not, having to spend the rest of our lives to reload EVERYTHING in a [new] 64-bit environment sure makes it an alternative worth investigating.
    However, an unviable environment that is continually going ‘belly-up’ is no solution at all;
    particularly if the entire reason for access to more memory doesn’t work – yes, the patch provided more ‘available’ memory as far as Windows was concerned…
    But the entire reason for this ‘exercise’, the ability to open a graphics image that would not due to lack of available memory which WAS NOT RESOLVED by making more memory available in Windows. If your applications can’t access and/or utilize the additional memory, the whole process is essentially as stated, an ‘exercise’, and a useless one at that.

  116. Core i3 3220 w/Intel HD 2500
    all works fine with patched xp driver except Chrome & JxBrowser based on chromium.
    yes, I’m understand it’s because chromium use hardware accel 🙁
    But FireFox works fine.

    any ideas how to fix JxBrowser ?

  117. I found a workaround for this.

    Just leave the Intel driver uninstalled. Or if you have installed it, just uninstall it and select deleting of the driver from the system.

    The PAE patch works very well without the Intel graphics driver installed – default Microsoft driver is just fine. I use the laptop now through Remote Desktop, FullHD screen works etc.

    Next I am going to test with only 4gb of memory WITH the driver. I want to see if I can use the full 4GB with the patch instead of the standard 2.9GB. But this is for fun only.

    The solution of using the pc without the Intel driver and then also through a remote desktop suits me very well for my application.

  118. Intel Hd Graphics 4000 driver on Windows 7 32 bit SP1 on Asus K56c, 8GB Ram.
    Download the Intel driver from Lenovo support site, supporting Windows Server 2008 R2 with SP1, Windows Multipoint Server 2011, Windows Small Business Server 2011 and Windows Server 2012.. Uninstall your driver, without restarting the pc install the driver. Restart and you are done. Windows experience index went 6,5 from 5 previously with aero. For PAE I had use Saferbytes x86 memory bootkit.

  119. I have another idea. Intel has open source driver available for Linux for the HD 3000. Is there a way to port this to Windows 7? I mean, the source code is there and in linux, there are no issues with this driver at all.

    However, when accessing the website for Intel Open Source, it gives “access denied” … Intel wants to kill older gen HD GPU’s …

    As far as the Windows official driver goes, I tested this with 4gb physical memory and the PAE patch… and it gives a BSOD even with only 4GB of RAM …. So the issue is not even with the RAM amount, but the driver itself. In linux you can utilize the full 4 gb and no BSOD appears.


  120. I downloaded the zip-file and followed the instructions in the readme attached to it. In fact am using desktop HP dc7100 CMT 32 bit which runs up to 4GB RAM max. Installed is 4GB but only 3.25 GB is usable. I went through the steps but it failed at Step 4. Could anyone help, please? Thank you in advance.

    I have another machine HP dc7600 CMT which can go up to 8GB max. If this tool works with the 7100 model, it stands to reason it will also with the dc7600 (maybe!). At present, I installed the 8GB to the 7600 unit but only 3.5GB is usable, again.
    Both machines are:
    – 32 bit with win7 ultimate,
    – having ATI Radeon X300/X550/X1050 Series graphics card,
    – with Pentium 4 for cpu, 3.6GHz and 3.8GHz respectively.

    Thank you for help.

  121. Hello
    Here the solution

    Use this file

    Here sources

    And follow instrcutions :

    PatchPae (v2) by wj32.
    Tested on: Windows Vista SP2, Windows 7 SP0, Windows 7 SP1, Windows 8, Windows 8.1, Windows 10 (builds 10240, 10586, 14393, 23569, 23992)

    == Installation ==
    1. Open an elevated Command Prompt window.

    2. cd C:\Windows\system32.
    Make sure the current directory is in fact system32.

    [[ For Windows 8, Windows 8.1 and Windows 10: ]]
    3. C:\WherePatchPaeIs\PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe
    This will patch the kernel to enable a maximum of 128GB of RAM.
    [[ For Windows Vista and Windows 7: ]]
    3. C:\WherePatchPaeIs\PatchPae2.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe
    This will patch the kernel to enable a maximum of 128GB of RAM.

    4. C:\WherePatchPaeIs\PatchPae2.exe -type loader -o winloadp.exe winload.exe
    This will patch the loader to disable signature verification.

    5. bcdedit /copy {current} /d “Windows (PAE Patched)”
    This will create a new boot entry. A message should appear:
    The entry was successfully copied to {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}.

    [[ For Windows 8, Windows 8.1 and Windows 10: ]]
    6. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} kernel ntoskrnx.exe
    This will set our boot entry to load our patched kernel.
    [[ For Windows Vista and Windows 7: ]]
    6. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} kernel ntkrnlpx.exe
    This will set our boot entry to load our patched kernel.

    7. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} path \Windows\system32\winloadp.exe
    This will set our loader to be our patched loader.

    8. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} nointegritychecks 1
    This will disable verification of the loader.

    9. bcdedit /set {bootmgr} default {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
    This will set our boot entry to be the default.

    10. bcdedit /set {bootmgr} timeout 2
    This will set the timeout to be shorter.
    Note: you can change this timeout to whatever you like.

    11. Restart the computer and enjoy.

    == Removal ==
    To remove the patch:
    * Run msconfig, click Boot, highlight the entry named “Windows (PAE Patched)”, and click Delete.
    * Delete the files ntoskrnx.exe (or ntkrnlpx.exe) and winloadp.exe from C:\Windows\system32.

    == Updates ==
    When Windows Update installs new updates on your computer, you should run Step 3 again to ensure
    that you have the latest version of the kernel.

    == Compiling ==
    To compile PatchPae2, you need to get Process Hacker and build it.
    The directory structure should look like this:
    * …\ProcessHacker2\lib\…
    * …\ProcessHacker2\phlib\…
    * …\src\PatchPae2.sln

    1. Hi Samsara, I am trying your steps and I am getting the following message in the command prompt:
      Build 18362, Revision 719
      Unsupported kernel version: 18362
      – Any idea how to solve this?

  122. W7 SP1 patched successfully, booting with patched kernel but additional memory is not there.
    Mobo is ASUS H97. Bios option ‘Memory remap’ description is ‘Memory remap for 64-bit os’. So my opinion is that ASUS blocked PAE for me, btw NX bit is enabled in bios.

  123. Windows 7 sp1 32bit with all necessary last updates. winload.exe ver 6.1.7601.24538 was failed to patch. Although ntkrnlpa.exe was patched successfully. So my only way was to sign patched kernel.

  124. Failed on 4th step on win7 pro SP1 , i checked winloadp.exe in system32 it was there but i finished all the steps successfully expect the 4th , i gave it a try but unfortunately the system boot on safe mode !
    Anyone got a solution or confronted the failed step (4th) ?
    Otherwise tell me how to migrate to 64bit version with the same license (OEM), without losing data 🙂

    by the way it worked on Virtual machine windows 7 home !

  125. Pingback: My Site

Leave a Reply to George Cancel reply