Windows 32 Bit Ram Patch
This patch allows you to use more than 3/4GB of RAM on an x86 Windows system. Works on Windows Vista SP2, Windows 7 SP0, Windows 7 SP1, Windows 8, Windows 8.1 and Windows 10 (build 10586).
Instructions and source code included.Download:Source code:Before using this patch, make sure you have fully removed any other “RAM patches” you may have used. This patch does NOT enable test signing mode and does NOT add any watermarks.Note: I do not offer any support for this.
If this did not work for you, either:. You cannot follow instructions correctly, or. You cannot use more than 4GB of physical memory on 32-bit Windows due to hardware/software conflicts. See the comments on for more information. Still trying.
I’ll try the very newest patch today or tomorrow. On the patch boot, after the normal animated windows loading screen I get half a correct windows ‘welcome’ screen and jagged half white image with little diamonds and weird patterns and no movement. Must hit reset button. Again, in safe mode, I see all 8 gigs and runs fine. Misconfig has memory unchecked as well. Maybe I could try going back 2 years in nvidia graphics drivers they only have been adding support for 3d and physics, both of which I don’t useWorth a try maybe.Any thoughts?
VeganChocolateYou are getting confused. The (unofficial) Win 10 pae patch by evgeny who AFAIK is Russian, has nothing to do whatsoever with this site owner’s (wj32) patch.
The patches are completely separate and independent of one another. The evgeny patch for Win 10 was posted before the latest wj32 Win 10 patch became available.However I have used both with no problems and with no virus’s showing up in either.The file link posted by escape75 back in November is an executable program that uses the evegeny patch for win 10 and installs it automatically, no manual input is required except to run the program. Okay, First, this wj32 and patch has been around quite some time and appears to be the most dependable, robust and actively updated one.There are no viruses in any of this code, but due to how it’s accessing kernals (with your permission) a decent virus/malware should detect something. This is normal, but it’s actually good people pay attention to this sort of thing.From all my reading and experimenting, I will submit there’s a nvidia and other graphic driver problems.I’m going to try loading some legacy win XP graphic drivers and test if there’s a different screen upon booting the pae boot option.I am going this route before screwing around with microsoft updates and such. I believe it’s entirely possible that microsoft has put in code to distrupt this patch from working as they want people to buy another OS like the 64 bit. It’s all marketing as far as I’m concerned. Why else would larger memory work on win 2000 and some other older win OS’s natively and not the newer ones.
I feel just reloading graphic drivers has much less potential for problems.I will report when I’ve got something concrete to say. I had to use a restore point after messing with too many graphic drivers and created another unrelated issue to the patch. After fixing my created problem, I read to check for any ram type 3rd party or memory managers running at the same time as pae. I forgot I had a ram drive program resident from before. I disabled that and when I did second paepatch boot option I saw a lower res windows screen and it comes up ‘windows doing repair’ and it attempts to repair.
I cancel and reboot with same thing in loop.This is different than when the ram program was running so maybe I’m getting somewhere.I will try the nvidia drivers from 2012 or so for win 7, this time with a restore pointwill update results. Always ALWAYS make sure to install this as a second boot option.wj32 clearly designed an excellent almost fool proof program by giving you the dual boot optionUSE IT!!! Thanks for everything.
I have a problem in executing the instructions: you said “make sure the directory is in fact system 32”. Then C:WherePatchPaeis etc., Do you mean I have to change directory from System32 back to C:? Also and since I am not a computer wiz, do I copy the whole command line “PatchPae2.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe ” as is after changing to the patch directory?I have Windows 10 pro, and the message I am getting is: “unable to copy file: The system cannot find the file specified.” Can you please help? I need specific instructions step by step please. Thanks a million.
Windows 32 Bit Ram Patch Download
Applied patch. Started Win 10 X86 version. Start-up says error in starting up and goes into repair mode.Unable to repair it gives various start up options like re booting, system restore etc.Carried out system restore and deleted residual patch files.Additional information my OS build is WIN 10 X86 Build 14393.51Yvgeny can you please help.MY PC is Dell Vostro 3560- ProcessorIntel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 2101 Mhz, 4 Core(s), 8 Logical Processor(s)Installed Physical Memory (RAM)8.00 GBTotal Physical Memory2.39 GBAvailable Physical Memory418 MBTotal Virtual Memory6.01 GBAvailable Virtual Memory2.48 GBPage File Space3.63 GB.
Thank you evgeny. This was true. I installed this patch after upgrading to Win 10.
At the “Anniversary Update” (1607) the computer crashed and I reinstalled everything. With today’s update I again got the BSOD, but this time (after enduring all of MS’s attempts to recover the PC) I chose the non-patched Win 10 and it booted up (without full use of 8 GB of RAM). The update knocked out ntoskrnx.exe, but left winloadapp and the boot option. I followed directions to remove the patch leftovers and now will reinstall it (with thanks to B-Lex for assurance that this version of the patch works with the new update).
SO: apparently any update that modifies the kernel will require (1)booting to Win 10 plain, and (2) reinstalling the PAE3 patch. The BSOD will let you know. Boogie,You need to check whether the patch has actually been applied.Either right click ‘This PC’ icon on desktop and then Properties, or Settings-System-about and check installed RAM. It should say 4GB.If it says some something like 4GB installed, 3.2GB useable, then the patch has not been correctly applied.You can’t actually use all of the 4GB of RAM installed because Windows requires some for overheads, and if you have onboard video, then some more of that 4GB will be used for video memory.The other thing to realise is that only 4GB of ram will be used by any one program, even though there may be say, 8 or more GB installed.
I’m running kind of a complex setup. A little background, my motivation stems from ACT! 2008 not being installable on 64-bit OSs. So, I loaded it on a Windows 10 Enterprise x86 Hyper-V VM along with RDP Wrap, RemoteApp Tool, and PatchPAE3.
All successful. I published the app with RemoteApp, the system shows that it has 8GB of RAM and I have 6 users using it simultaneously from their PCs.The problem is, once the system hits between 3.0 and 3.2 GB of RAM used (the system, as a whole, has never gone past 3.2 GB used), new connections start bombing out with an RDP protocol error of 0x112f. Looking it up seems to point to memory restrictions on the host PC. So, I don’t know if PatchPAE3 isn’t working or if a Windows behavior regarding memory allocation to a single exe even if there are multiple instances of it (so, like a shared pool per exe even if there are six of them running, they all pull from a fixed amountmaybe?). Does anyone know or can point me in the right direction?
Because Win10 only installed the driver for MS Basic Display Adapter for the pre-installed old NVidia GeForce GT120 I tried the latest NVIDIA-Win10-driver 21. Of: Win10 w/o 4GB-patch booted but Win10 with 4GB-patch did not boot to the end.The same effect was with 4GB-patched Win7 and the latest NVIDIA-Win7-driver (same version). I tested all available old Win7-driver from newest to oldest and at last 4GB-patched-Win7 started with the older NVIDIA-Win7-driver 9. Of.Because the oldest Win10-driver is of 07-29-15 (and so not old enough) I tried this Win7-version-9. Also with the 4GB-patched Win10 – and it worked. Surprise, surprise. Now I have updated to Win10-32 v.1607, built 14393.693, and done the modification again with patchpae3 (the same hardware, HP p6029de, 6GB RAM, BIOS 5.43) and it works as with patchpae2 and v.1511.W/o the patch system reports 6GB RAM and useable 3,35GB RAM, with the patch it reports 6GB RAM.I am not very surprised because patchpae3 modifies the same byte-sequences in the kernel-file as patchpae2 and in the same way and so the result should be the same.But of course the problem with the NVidia-driver for GT 120 is the same – I have to use the old Win7-driver 332.21 (9.
This is an origin problem of the driver, not an origin problem of the 4GB-kernel-patch, although this “bug” of the driver only appears with the 4GB-kernel-patch.I have also tested it in an old Medion-PC with a MCI-7204-Motherboard, which can take 4GB RAM only. Surprisingly with and w/o the patch system reports only 3,35GB RAM. Seems as if some some-devices makes Windows to see only 3,35GB and not the actual 4GB. I hoped getting usage of the full 4GB RAM. You will never get 4GB of usable RAM with a 32 bit Windows OS even with PAE. Firstly an integrated graphics video adapter will take up whatever has been allocated in the BIOS, and then there is the RAM used for overheads.With a separate graphics card up to around 3.5GB will be usable, maybe a little less depending on motherboard and the hardware you have. PAE may only give an extra 200+MB or less depending on hardware.So, it is a moot point as to whether the PAE is worthwhile if only 4GB is installed.Interestingly with 8GB installed on a patched win 10 machine and also on a patched win 8.1 machine, both with separate AMD Radeon (ATI) graphics cards, both report in ‘Properties’ that 8GB is installed, there is no statement of ‘usable ‘ memory.
This is not so easy, sorry.With the MSI-7204-Motherboard and 4GB RAM System reports only 3.35GB RAM w/o message about availabe or useable RAM and doesn´t matter whether w/ or w/o the patch. And this although the MSI-7204 does NOT has Video onboard.With the above reported HP p6029de (Motherboard Pegatron Benicia) and 4GB RAM (I have removed one 2GB-module) System reports w/o patch 4GB and useable 3.25GB RAM (Benicia has Video onboard, but disabled due to the used GeForce GT120). And with patch System reports the complete 4GB w/o any limitation to a smaller available/useable RAM.It is the same bevaiour as with 6GB RAM: W/o patch System reports 6GB RAM existing and 3.25GB RAM useable, w/ patch 6GB existing.So with the HP p6029de (Motherboard Pegatron Benicia) the patch really gives access to the “missing” 0.75GB RAM and so to the complete 4GB (if “only” 4 GB is installed).I have another PC available for tests, a HP dc7900. I will test it this evening.
How to roll back from this?Tried on Windows 10 32bit, pc restarted and never start again. Now corrupted the HDD (which is a flash MLC 32GB). Show 12.5GB free space, can´t format it, can´t delete partition tried as external hdd on other pc, tried with aomei partition assistant, tried with easeus partition master, tried on the original pc starting with usb Windows 10 install, can´t repair, can´t reinstall, with CMD can´t format it, even with diskpart can´t do anything. How to solve this?Thank you. I have NVidia Geforce 8400M GT (in laptop) (and latest Win 10 Build 14393) and got the “VIDEO TDR” blue screen using Patchpae3. Based on others having same NVidia issues with patch as well – I installed the oldest one I could find for Win 7 (as post suggested) – which was 8400M GT driver ( – 9.)Win 10 will update that driver to the latest that doesnt work with patch.
You have reboot without patched kernel then “roll back” via device managler.This works most of the time about 90% – but still occasionally crashes and luckily reboots instead of those couple different blue screens. THANK YOU EVGENY!I have a computer running a PC3000 UDMA card for data recovery. It is an older card no longer supported by ACE Lab. There is no way in hell that will ever get a 64-bit driver. And i really needed more than 4GB RAM to be able to run another logical data recovery program at the same time with the PC3000 application, if i tried to run both one of them crashed after a few hours.
The computer is running licensed Windows 7 Professional SP1 32-bit. Windows asked for reactivation after i changed the graphics card, but it verified the license no problem with just a couple clicks. So this patch can be run on a legitimate business copy of Windows.I was able to patch the kernel and loader using your patch, and successfully installed another 4GB DDR3 memory stick and have 8GB RAM recognized and usable.
There was a nVidia 8400GS Rev 3 graphics card in this PC, it started showing artifacts on the shutdown screen with 4GB after applying the patch, and completely crashed when i installed 8GB. I have removed the nVidia card and replaced it with an ATI Radeon HD5450. Installed the last driver version provided by AMD in 2016, the graphics card is fully functional without any issues. The computer behaves well now, and so far the data recovery applications have not crashed again.Many many thanks, you have saved me a lot of frustration (and saved our clients time).
I would like to donate a few bucks for your efforts. Do you have Paypal? PatchPAE3 is command-line utility. It’s PatchPae2 mod.fix128 is GUI for PatchPAE3. It’s compilation of VBScript, 7zip, UPX and some Micro$oft utilities.PAE Patch 2.1 by Escape75 is very simple (GUI without GUI?) wrapper for PatchPAE3 to easy use.PatchPae2.zip is not virus. It’s AV false positives heuristics, because any PatchPae modifies some windows critical kernel files just like virus.
For example, when you run “PatchPae2.exe -type loader ”, you disable DRM, and Micro$oft and AVs worship DRM 🙂. It worked on Win 7 32 bit.
Sp1 Home premium running on Virtual box.My lesson was Make sure I follow the readme intructions exactly! I suggest extract the patch zip to root of drive ie C: seemed to work better than extracting into system 32 folder.You will note in the read me that the path given to the loader is windows not c:windows as I mistakenly used. I’m not sure why that is but just use what the read me has.If anyone little thing is wrong the loader wont work and as soon as you hit enter on the os selection screen it will go into windows recovery – dont give up!
If you wait for the windows recovery to restart – and then select the same boot option again let windows recovery keep running untill it gives an error message – that will help alot – my error was cant find boot loader which helped me notice I had not followed the readme with the path. Note if you get a blue screen error thats different a driver possibly needs rolling back or an older driver installed (from what ive real mainly intel on board graphics)Yay Now in computer properties it shows 6gb ram. Any way to get around this failing?C:WINDOWSsystem32C:PatchPae3.exe -type loader -o winldnew.exe winload.exePatchPAE by wj32:– support for Windows Vista SP1/SP2, 7, 7 SP1, 8, 8.1– Server 2008 SP2evgenb MOD:– added support for Vista SP0, 7 SP1 with KB3033929+,– Windows XP SP2/SP3,– Windows 10 (6/14393)– Server 2003 SP1/SP2/SP2R2, Server 2008 SP1– Server/Windows 2000 SP4 and 2000 SP4 with KernelEx by blackwingcat– Windows Longhorn (4093 stable), Visual C 2010 Redistributable requiredVersion: 0.0.0.45Input file version: 15063Failed. Also upgrade to 1709 (Build 16299) is done. Again the updater updated (unwanted and w/o giving notice) the NVidia-videocard-driver to the newest version. The result was again that after patching the kernel the system does not boot.
Again I went back to the previous driverNVIDIA-Win7-driver 9. Of (see my post of February 18, 2017)and now, as exspected, also the patched 1709-system is booting.
8GB from 8GB are in usage.Testet on an EVGA force 780i SLI FTW motherboard (132-YW-E178) with E8400-CPUs and NVidia GeForce 8800GT. The differences between original and patched 1709-ntoskrnl.exe:original patched002E8. F4 80 625991C1 8B 75 FC 85. F6 74 3F BE 00 00 02 91F1 8B 4D FC 85 C9 74 06. B9 00 00 02 00 90 90The replacements with “BE 00 00 02 00 90 90″/”B9 00 00 02 00 90 90” are well-know form the manually-done Win7-patch.But what is the reason for replacing “87 FD 61” with “F4 80 62”?The differences between original and patched winload.exe:original. Patched00148.AD 5F 59 0A3A5D7 8B F0 33 F63B55C 8B D8 31 DB. PatchPae3 worked fine nearly one year for me until February-Update KB4074588.
Update failed several Times (0x800f0845).So I selected the nonpatched-Entry as default from the Boot-Menu. Then after boot, KB4074588 was installed with now Problems.I delete the old ntoskrnx.exe and winloadp.exe and created them new with– PatchPae3.exe -type kernel -o ntoskrnx.exe ntoskrnl.exe– PatchPae3.exe -type loader -o winloadp.exe winload.exeIn Boot-Menu I selected the patched-Entry as default again and booted: Everything works fine again. – added: windows 10 pre-RS4 (tested with 3; 17623)– added: windows server 2003 sp0– fixed: MmAddPhysicalMemoryEx for windows server 2000/2003– added: Bypass Windows 8 CPU feature checks Patch by Jan1 for Windows 8.1– added: get timedatestamp, if can’t get version number– added: many Windows betas (6801,7000,7022,7048,7057,7068,7077,7100,7127,7137,7201,7231,7260,7264,7850,7955,8102,8250,8400,9431,9841,9926,4,0,9,6,6,1,8,1,3,3,17623)– added: many other improvements. A few problems so far:1) When I boot into Windows 10×86 and run the above Script Windows screams not on my watch and dumps me out without option. Full admin cmd and such.2) OK, I figure replacing the kernal while booted in the OS might be a problem, I’ll just use my dual boot option and run it from there.3) My dual boot is Windows 7×64 16GB dual physical single core CPUs. Running the script throws a x64 bit OS detected error and dumps me out. My XEON CPUs lack the commands necessary to run 8.1+ (believe me, I’ve tried).4) OK, let me try compatibility mode.
No luck.5) My Windows 10×86 install is on F: in case that matters. I’ve got the patch files living in “f:setupPAE Patch”.
Would the space matter?6) The biggest problem I’m having is the readme files seem to have disappeared somewhere along the way making it hard to do the manual install. I’ll try an old one from PatchPae2 but this doesn’t feel right.7) Any chance we can get the very top of this page updated to direct people down here? It took me rather too much time to find the current files.
readme files seem to have disappearedreadme is part of PatchPAE3:cmd.exe – PatchPAE3.exeoutput:. print user guide for patch “4 Gb 32-bit memory limit”:PatchPAE3.EXE -help unlockpaeWhen I boot into Windows 10×86 and run the above Scriptyou can edit script. You can comment first line (@ECHO OFF - rem @ECHO OFF), then run cmd.exe and then run script to see commands output to determine problem line. Or run script with argument ScriptPAE3.cmd NOUACthe script is just good example. Maybe it’s antivirus problem? And UEFI option “secure boot” can’t load patched (pirate) kernel/loader. Maybe problem is in the script’s code page.
And maybe you use non-standard windows loader.5 space matter?No.5 install is on F:I think – no. Having seen the readme unzipped from the top of the thread it never occurred to me to treat the patchpae3.exe as any other command line using standard dos help.Aside from the exe downgrading my Xeons to i386s (inside joke for those who actually owned a 386 once upon a time) and some fat fingers it actually worked. It’s not super intuitive but as mentioned somewhere else, if you can’t translate these instructions yourself you shouldn’t be doing it.Playing with the boot record gave me a third boot option with the patch while leaving my original install safely there in case it’s needed.
Wasn’t expecting that piece of good fortune.Viola. 16GB of ram shown, only 1.2GB used. Without memory hogs like Waterfox it may take me awhile to get programs to actually use that space, but I look forward to it with great anticipation.I’ve accomplished what I came for and learned quite a bit (of trivia?) over the last few days. Thank you for your help.
Let’s talk W8CPUFeaturePatch. Is that really sane to do on my primary personal system? Are these newly required (dumb) commands really so obscure as to practically never execute?
Will my system be stable if I do this? All I’ve ever wanted is a stable Windows 10×64 as God intended. Only now after I’ve got 16GB shown on Windows 10×86 does my forbidden fruit lie so tantalizing close.Alas, my inadequacies lie in the form of PrefechW and LAHF/SAHF. Not mentioned in the patch instructions.
Do I continue to come up short or have you magicians solved this problem too? Confirming programs punch right through 4GB without complaint.Weirdness, my hyperthreading turned off.
It claims to be enabled on in the BIOS. Does some part of what we did turn it off? Firefox is hitting the CPU harder than anticipated. If I can’t get Hyperthreading back am I loosing cycles? Should I disable it in BIOS?Next question, Microsoft never recognized my failed attempts years ago to upgrade this hardware to Windows 10 and never supplied a digital key for it to install. Not really fair, but I don’t have too much standing in court.
Maximum Ram 32 Bit Windows
There used to be many ways to complete a free and legal Windows 10 upgrade. Do any of these remain? I’m willing to install / uninstall / create partition / patch / etc. Yet again if need be. Attention of topic!To the specialists / professionals among you!!Who can help? / knows a link / or has a newer executable programfrom Autodesk / ACAD 2010 for me!?I’m from Germany and 70years old and know the PC history since 1989.My job is electrical technician.My system: WIN 7 pro/ 64bit / 16gb Ram / RX Vega64.My problem:My ACAD 2005 is not running under my system! Hello, I use Windows 7 32 bit with 8G RAM, this patch works fine except for USB such as printing to a printer connected to a USB port.
I replaced USB related DLL files in windowssystem32 folder with USB DLL files from Windows Server 2008 32bit Standard Edition’s evaluation ISO available in Microsoft web site, but the problem remains. This USB problem in PAEpatched Windows XP is solved by bringing USB DLL files from Windows Server 2003 32bit, but apparently not in Windows 7. My question is, 1)has anyone got USB to work reliably in PAEpatched Windows 7 32bit? 2)Does PAEpatched Windows 10 32bit have the same USB problem? Thanks in advance.
Yes, you can. Type in windows search “system configuration” (german: Systemkonfiguraton), and then click on “boot” (german: “start”). Then you can remove the non-patched option.BUT THIS IS NOT RECOMMENDED!!!!!In very rare cases, windows will not start with the patched files after a monthly update.
There is no really option to fix it. Therefore, you need the standard-windows-option to start the system!You can make the “patched” version as default and you can set the time to select to a small value, minimum is 3 seconds. Menu see first sentence of this post.Best regardsakapuma. Solved with PatchPAE3, but:C:WINDOWSsystem32c:UsersxxxPatchPae3.exe -type loader -o winloadp.exe winload.exePatchPAE by wj32:– support for Windows Vista SP1/SP2, 7, 7 SP1, 8, 8.1– Server 2008 SP2evgenb MOD:– added support for Vista SP0, 7 SP1 with KB3033929+,– Windows XP SP2/SP3,– Windows 10 (6/14393)– Server 2003 SP1/SP2/SP2R2, Server 2008 SP1– Server/Windows 2000 SP4 and 2000 SP4 with KernelEx by blackwingcat– Windows Longhorn (4093 stable), Visual C 2010 Redistributable requiredVersion: 0.0.0.45Input file version: 17763Failed.
Hallo, meanwhile I’m a piece further.When I select the nonpatched-Entry from the Boot-Menu, booting is interrupting and starting new. But then there is prompting now Boot-Menu and booting is ending in perfect nonpatched Modus.When stating new in this situation, the Procedure start’s again: Selecting nonpatched-Entry, booting new without Boot-Menu and booting in nonpatched Modus.But when selecting the default patched-Entry, booting always works fine and is not interrupted by a second boot.So what can I do?
First we need a snip of task managerperformance with memory highlighted (see snip)Second win 10 handles memory differently. I suspect you are new to it. The way win 10 works is it takes 1/2 of the available ram and puts it into a fast cache (which is a good thing) so that it can respond faster to a request for memory (likewhen you open another app)The max win 10 32 bit can 'see is 3.25 Gb and what may be happening is that from the 3.25 the fast cache and the shared video memory is deducted so 2.1 left is not unusual. See mineWanikiya and Dyami-Team Zigzag Windows IT-PRO (MS-MVP). First we need a snip of task managerperformance with memory highlighted (see snip)Second win 10 handles memory differently. I suspect you are new to it. The way win 10 works is it takes 1/2 of the available ram and puts it into a fast cache (which is a good thing) so that it can respond faster to a request for memory (likewhen you open another app)The max win 10 32 bit can 'see is 3.25 Gb and what may be happening is that from the 3.25 the fast cache and the shared video memory is deducted so 2.1 left is not unusual.
See mineWanikiya and Dyami-Team Zigzag Windows IT-PRO (MS-MVP). Which version you have installed?Did you update all the drivers?Each version of Windows has its own limit on the amount of RAM it will support, so do the many CPU/motherboard combinations found in PCs both old and new. Therefore, just because your particular Windows version supports a certain amount of RAM, your computer’sCPU/motherboard might support more or less than that amountA bit of history:When MS started making Windows, many years ago now, they knew that it would be called on to run on the systems of the day, with maybe only 256meg's of ram. So, they created the Virtual Memory (Pagefile) to be a supplement to the physical RAM.That works, but it negatively effects the performance of the PC, because accessing files from the hard drive (the Pagefile) is much slower than accessing the same files from RAM memory, by as much as 1000 times.In theory, if you have enough RAM, you don't even need a Pagefile, except that some software expects to see it and may puke if it doesn'tRegards, Regin Ravi.