Make Windows 7, 8, 10 and Vista 32-bit (x86) Support More Than 4GB Memory

As you’ll know, there has been 2 versions of each Windows starting from XP which are 32-bit and 64-bit editions. Sometimes a Windows 32-bit is referred as x86 and 64-bit as x64. We won’t go into details on what are the differences between x86 and x64 are, but one of the major differences is a 64-bit Windows can support more than 4GB of RAM. If your computer has 4GB of RAM and you’re using a 32-bit Windows, you’ll notice that only about 3GB – 3.5GB is being recognized and the remaining memory is gone. Weirdly, Windows 2003 and 2008 can already address more than 4 GB of memory so why can’t we do that with Vista and newer operating systems?

The answer is: Microsoft doesn’t want that and it’s all just a licensing matter. Contrary to popular belief, there is no physical reason why a 32-bit Windows cannot access memory above 4GB, but it’s more a case of Microsoft opting not to allow it. Read the findings of software analyst Geoff Chappell to find out more.

Install Memory 3.5GB

We can of course go for a 64-bit version of Windows, but even today, there is still quite a lot of software which cannot run properly on x64, which can be inconvenient if you’re someone like us who installs and tests a lot of software. Not only that, Windows 64-bit doesn’t accept unsigned drivers unless you disable driver signature enforcement manually every time you boot. Quite frustrating… Well, here is good news for Windows 8, 7 and Vista users because we have some patches here to make your 32-bit Windows support more than 4GB of memory.

There have been a few 4GB patchers available, but unfortunately most of them haven’t been kept up to date. For example, the RamPatch tool over at works quite well on Windows 7 RTM, but was never updated to reflect the changes to the kernel files in Service Pack 1. Also the program was removed from the website due to many false positives from antivirus software.

32bit RamPatch

We have tracked down the program and you can download and try it out on Windows 7 if you wish. Although some users have reported no issues running the patched kernel file from SP0 on an SP1 install, we suspect there may be stability or compatibility problems that will arise as a result of this at some point. Consider this program a useful tool to test with and perhaps not something to use permanently.

Luckily, there is a method which has been kept more up to date, and although it’s not quite as easy to implement as the RamPatch tool above, it’s still not that difficult. PatchPae2 is by Wen Jia Liu, also known as “wj32” who is behind the excellent Process Hacker task manager software. This is a small command line tool that will patch the needed system files to enable 4GB and more of memory in Windows Vista SP2, Windows 7 RTM and SP1, and Windows 8 RTM 32-bit. Follow the steps below to enable a patched system, the core system files ARE NOT overwritten meaning you can revert back without too much fuss.

1. Download the PatchPae2 command line tool and extract the zip file to a folder of your choice. For our example, we’re extracting to the root of the C drive.

2. Open a Command prompt with Administrator privileges by pressing the Win key, typing cmd into the search box and then simultaneously pressing Ctrl+Shift+Enter. Then type the following:

cd C:\Windows\system32

3. Now, Windows Vista and 7 users type:

C:\PatchPae2.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

Windows 8 users type:

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

This makes a copy of and then patches the Windows kernel file to enable the extra memory of 4GB and above.

4. Type the following to make a copy of and disable signature verification in the Windows loader file:

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

5. Enter this to create an entry in the Window boot menu, you can change the text in quotes to what you want:

bcdedit /copy {current} /d “Windows Vista/7/8 (Patched)”

patchpae2 bcdedit

This should give you a “successfully copied to…” message with a number of BCDID characters returned in brackets, make a note of them as you will need to enter them in the following commands.

6. Enter the following commands in turn, pressing enter after each. Replace BCD_ID with the ID you got from step 5:

bcdedit /set {BCD_ID} kernel ntkrnlpx.exe (for Win 8 use ntoskrnx.exe)

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

bcdedit /set {BCD_ID} nointegritychecks 1

Now reboot your computer and you should get a new entry on the Windows Boot Manager to run the patched operating system.

Windows Boot Manager Patched menu

The good thing here is if you have problems, you can simply switch to the unpatched normal system by rebooting because the kernel files were copied and not overwritten. When you boot the patched system, a quick check should show that your amount of memory is now fully utilized. Do note that you still might not get access to all memory if some of it’s shared with the video adapter, e.g. 512MB onboard graphics.

task manager 6GB ram

As you can see from the image above, we now have a 32-bit Windows 7 showing there is 6GB of installed RAM available.

resource monitor 6GB ram

This next image shows that Windows Resource Monitor confirms there is 6GB of memory installed and ready to be used, with over 5GB still available for use.

If you want to uninstall this patch again from your system, simply boot into the unpatched Windows, press the Win key, type msconfig and press enter. Then select the boot tab and highlight the patched boot entry, click Delete. This screen can also be used for reducing the timeout and selecting the patched install as the default o/s to boot into if you plan on keeping it permanently.

delete boot menu

Also optionally go into C:\Windows\System32 and delete the ntkrnlpx.exe and winloadp.exe files. If after a Windows update you find the patch no longer works, re-run the command from step 3 to patch the kernel file again.

Important Note: Do be aware that PatchPae’s developer offers no support of any kind for this tool and if it works, fine, if it doesn’t, forget about it and move on. It’s also important that you make full backups of your system prior to trying PatchPae. Even though it does not overwrite any system files, that does not stop users from being unable or unwilling to follow the guide correctly, which could stop the system from booting into Windows.

155 Comments - Write a Comment

  1. Zlatko 4 years ago
  2. @MicrosoftCorporation 4 years ago
    • HAL9000 4 years ago
      • RoboCop 3 years ago
        • magusiss 3 years ago
  3. Paul 4 years ago
  4. Sergi Tolstoy 4 years ago
  5. Martín 4 years ago
  6. David 4 years ago
    • pete 4 years ago
  7. Jeff 4 years ago
  8. Laszlo Pilinszki-Nagy 5 years ago
  9. Stefan 5 years ago
    • HAL9000 5 years ago
  10. David 5 years ago
    • Tomkan 5 years ago
  11. EMILE 5 years ago
    • HAL9000 5 years ago
      • EMILE 5 years ago
        • HAL9000 5 years ago
          • Al 5 years ago
          • Cristóbal 4 years ago
          • HAL9000 4 years ago
          • Cristobal 4 years ago
          • HAL9000 4 years ago
  12. Alex 5 years ago
  13. Hi All 5 years ago
  14. Luis Gilliam 5 years ago
  15. Greg Harbs 5 years ago
    • Vineet Garg 5 years ago
  16. innovative 5 years ago
  17. Marc 7 years ago
    • tony 5 years ago
  18. Lul 7 years ago
  19. Edwin Barton 8 years ago
    • Edwin Barton 8 years ago
      • Edwin Barton 8 years ago
    • Paul 7 years ago
      • Paul 7 years ago
      • Martin Bolt 7 years ago
  20. Harry 8 years ago
  21. Oleg 8 years ago
    • Vikram Dhiman 8 years ago
  22. HAL9000 8 years ago
  23. Mudakun 9 years ago
    • Mudakun 9 years ago
  24. Alvin Loh 9 years ago
  25. Alvin Loh 9 years ago
  26. devnullius 9 years ago
  27. goe 9 years ago
  28. Tim Edwards 9 years ago
  29. Tim Edwards 9 years ago
  30. Chuck 9 years ago
  31. Pedro 9 years ago
  32. Eric 9 years ago
  33. Jay 9 years ago
  34. Rajendra 9 years ago
    • HAL9000 9 years ago
      • Christopher 8 years ago
  35. Lachlan 9 years ago
  36. Corner 9 years ago
  37. Hakimojah 9 years ago
  38. Chris 9 years ago
  39. joe 9 years ago
    • David 9 years ago
  40. Kevin 9 years ago
    • HAL9000 9 years ago
  41. TheMaddBadgerr 9 years ago
  42. stukov 9 years ago
    • HAL9000 9 years ago
  43. Davide 9 years ago
  44. dennis 9 years ago
  45. John_T 9 years ago
  46. WindFabre 10 years ago
  47. Ruud de Bruin 10 years ago
  48. gabe 10 years ago
  49. Rowan 10 years ago
  50. Dap 10 years ago
  51. mike 10 years ago
  52. RS 10 years ago
  53. ovi 10 years ago
  54. Condor 10 years ago
  55. Lib 10 years ago
  56. Cody 10 years ago
  57. Swan 10 years ago
    • HAL9000 10 years ago
  58. riezky 10 years ago
    • mike 10 years ago
  59. Ringy 10 years ago
  60. Ringy 10 years ago
    • HAL9000 10 years ago
    • Aster Clarke 9 years ago
  61. Megan 10 years ago
    • HAL9000 10 years ago
  62. basheer 10 years ago
    • Jon Paulsen 10 years ago
    • Linux x86_64 10 years ago
  63. Linux x86_64 10 years ago
  64. stan 10 years ago
  65. Remz 10 years ago
    • HAL9000 10 years ago
  66. jason 10 years ago
  67. Jem 10 years ago
  68. biplab dansena 10 years ago
    • Starflare5 10 years ago
    • Starflare5 10 years ago
  69. Cristian 10 years ago
  70. darthvader45 10 years ago
  71. Jack 10 years ago
  72. Russ6163 10 years ago
  73. kekipark 10 years ago
  74. [email protected] 11 years ago
    • darthvader45 10 years ago
  75. Harry7 11 years ago
  76. Sid 11 years ago
    • HAL9000 11 years ago
  77. Dieter 11 years ago
  78. erwin 11 years ago
  79. Blair 11 years ago
  80. David 11 years ago
  81. Ed 11 years ago
  82. Blair 11 years ago
  83. Alvysyngr 11 years ago
  84. Enders 11 years ago
    • Edward 11 years ago
  85. John pick 11 years ago
  86. jimiweber 11 years ago
  87. FooFoo 11 years ago
  88. Vic 11 years ago
    • HAL9000 11 years ago
  89. Ammar Hossam 14 years ago
  90. remy 14 years ago
  91. mike 14 years ago
  92. Googy 14 years ago
  93. Remy 14 years ago
  94. And81 14 years ago
  95. killerb255 14 years ago
  96. ricksne 14 years ago
  97. vjramk 14 years ago
  98. TomTom71 14 years ago
  99. Ady 14 years ago
  100. David 14 years ago
  101. Trevor 14 years ago
  102. Gigabyte 14 years ago
  103. Glad 14 years ago
  104. Doug 15 years ago
  105. Arto LEonall 15 years ago
  106. dibyajyoti 15 years ago
  107. Rafael Mussi 15 years ago
  108. Kaldy 15 years ago
  109. nguyen tien dung 15 years ago
  110. Makaldoy 15 years ago
  111. reeven 15 years ago
  112. ask vp 15 years ago
  113. azim61 15 years ago

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Your comment is subject to approval. Read our Terms of Use. If you are seeking additional information on this article, please contact us directly.