Advertisement When you consider Windows versions, you might immediately think of the Windows 10 Pro offers more features, but also carries a $99 price tag to upgrade from the Home edition. Here's what you need to know to decide if professional features are worth the upgrade. While they are different, there’s another factor that separates Windows versions — whether the system is 32-bit or 64-bit. You might have heard the terms 32-bit and 64-bit thrown around, but never really understood them. Let’s take a look at where these designations come from, and what they mean for your computing experience. How Is the Number of Bits Determined?

Whether your computer architecture is 32-bit or 64-bit depends on the processor (also called the ) inside your computer. Currently, the majority of computer processors fall into one of these two categories. 64-bit processors are exponentially more powerful than their 32-bit counterparts, because they can hold and process so much more information. To understand the magnitude of the differences between the two, you have to understand a bit about. Unlike our decimal system, which has ten digits per place, binary only has two — 0 or 1.

How Windows Differentiates If you’re using a 64-bit processor, you also need to use a 64-bit version of Windows to take advantage of it. 32-bit versions of Windows work on 64-bit processors, but can’t use the extra power.

You can’t install a 64-bit version of Windows on 32-bit processors, but 64-bit Windows is backwards compatible with 32-bit software, as we’ll discuss. MSDN should really have a giant ARE YOU SURE? Dialog that pops up if you choose to download 32 bit Windows in 2016 or later — Steve Smith (@ardalis) There are two big places you’ll notice this difference in Windows. One is that a 32-bit version of Windows can only utilize up to 4 GB of RAM (or less). Thus, if you RAM is like short term memory. The more you multitask, the more you need.

Download PatchPae: Server 1 Server 2. Tested and working on: Windows Vista SP2; Windows 7 SP1. Operating system patched in this video: Windows 7 Ultimate SP1. Initial memory usable: 3.5 GB (only 70%) Memory usable after patching: 5 GB (100%) After patching Windows 7 (32bit) the memory limit will be 128GB.

Find out how much your computer has, how to get the most out of it, or how to get more. In a 32-bit installation of Windows, you’re not actually using more than 4 GB. The other place you’ll find a difference is the Program Files folder. On a 32-bit version of Windows, apps will install to the only Program Files folder. 64-bit systems, though, have an additional Program Files (x86) folder. This is because writing software for a 32-bit architecture is vastly different from writing it for a 64-bit system.

Ancient versions of Windows, like Windows 3.1, ran 16-bit software. 32-bit versions of Windows are. If you have a 64-bit machine, however, you can’t run older 16-bit software. You’ll have to turn to. 32-bit and 64-bit Programs Whenever you, it varies by vendor whether you get a 32-bit or 64-bit version. Some developers only provide a 32-bit version, sometimes they, and still others automatically install the right version for you.

If you’re running a 64-bit version of Windows, you should install the 64-bit versions of software whenever you can. Keep an eye out for links such as Versions or Editions on vendors’ download pages to see if they offer a 64-bit version. Because 32-bit software works for everyone, it’s understandably the default for most vendors. Of course, if you’re on a 32-bit system, only 32-bit software will work for you. What Am I Running and Can I Upgrade?

Now that we’ve discussed all the details about 32 and 64-bit versions of Windows, we can Are you using a processor that supports a 64-bit operating system and are you running a 64-bit operating system? The average off-and-on PC user probably doesn't know the answers to these questions, although they should.

There are plenty of ways to do this, but the easiest is to open the System dialogue. On Windows 8 or Windows 10, and choose System. On Windows 7 or earlier, right-click Computer and choose Properties. You can also use the Windows Key + Pause to open this menu.

Here you’ll see, such as whether your version of Windows is a Home or Pro version. Under System type, Windows will tell you if your operating system and processor are 64-bit or not. You can also see your Installed RAM here. On a 32-bit system, this will note something like 4 GB usable if you have over 4 GB installed.

Your processor and operating system bit sizes should match, but if they don’t, you might be able to upgrade. If you’re running a 32-bit version of Windows 10 on a 64-bit processor, you can follow Is your Windows 10 installation limited to 3.75 GB of RAM because it's the 32-bit version? We show you how to upgrade to 64-bit, so you can finally enjoy advanced features and performance. Those running a 32-bit version of Windows on a 32-bit processor can’t upgrade; you’ll need to purchase a new machine to take advantage of 64-bit. Enough Bits The packaging of a computer or computer hardware is crowded with technical terms and badges. One of the more prominent ones is 64-bit.

Is becoming the new standard, but it’s been a rough road getting here. While there were 64-bit versions of Windows XP available, it was a headache to deal with its compatibility issues, so not many people used it. Use of 64-bit systems didn’t become too popular until Windows 7, and it’s continued up to Windows 10 today. 4 GB of RAM, which was an unfathomable amount when CPUs were first designed, is still a workable amount of memory in 2016. However, as component prices continue to drop, low-end machines will likely ship with more RAM, making 32-bit systems eventually obsolete. This in turn will make developers focus on developing 64-bit software, which will be the standard for a long, long time.

We probably won’t hit the ceiling of 2,305 It is easy to see that 500GB is more than 100GB. But how do different sizes compare? What is a gigabyte to a terabyte? Where does a petabyte fit in? Let's clear it up!

Anytime soon! Are you running a 32-bit or 64-bit version of Windows! Let us know what you learned in the comments!

Originally written by Karl L. Gechlik on February 23, 2010.

I’m running Win 7 Pro on 64bit hardware, fully patched as of 8/25/17. I was able to successfully patch the kernel as per step 3. When doing step 4 (PatchPae2.exe -type loader -o winloadp.exe winload.exe) I get the response “Failed”. Just in case I finished up the steps and rebooted to the patched OS and it crashed.

I deleted the patched Boot entry in msconfg, and started over rebuilding the patched OS but using the original winload.exe (skipping step 4 and skipping the bcdedit for winloadp.exe in step 6). Still crashes. Any thoughts or suggestions? It seems to me your article is aimed at people who are running 32 bit windows on 64 bit systems. If however they are using it on a 32 bit system (32 bit processor such as say Pentium IV or so for example), then there is indeed a physical reason why the OS cannot access memory up to and possibly above 4Gb and that has to do with the systems possible inability to actually address that memory at a hardware level, in order to do so the system must support PAE (Physical Address Extensions), but even then, PAE is not supported on all 32 bit systems and is typically only present on some of the most recent 32 bit motherboards (say within the last 10-12 years or so roughly). Of course if they are using a 32 bit version of Windows on a 32 bit system that supports PAE then there is also no real need for software like you mentioned in your article to enable support for PAE in the OS as versions of Windows from Windows XP on up already have support for PAE built in. Though admittedly in the case of Windows XP at least it may not be enabled by default and may need to be enabled through the use of a boot.ini modification.

The details of which can be found easily enough using google. Additonally there are boot.ini modifications for XP that can be used to enable support for processors using HyperThreading or similar technology which can also help to improve performance for those using XP on a newer motherboard based system. On another note there are also a few utilities available that can be used to patch 32 bit programs so that they may be able to take advantage of memory above roughly 2Gb making them hence LMA (Large Memory Aware), I myself have used one such program to patch the program Bryce 7.1 Pro from DAZ so that it can utilize additional memory (after all why have that additional memory accessible only by the OS when some Programs may also benefit from its use too).

One such utility can be found at ntcore.com/4gb_patch.php persons using this patch however should be aware that not all programs my behave correctly after applying it, which is one of the reasons the patcher makes a backup of the original.exe file before patching it so that it’s easy to revert to using the unpatched executable just by deleting the patched one and renaming the backup one. While your comment is correct, there are no motherboards built into which more than 4GB of ram can be installed that don’t support either 64bit or PAE. A Pentium IV might have 4 DIMM slots that each take 1GB maxing out at 4GB. To put more than 4GB in you’d need larger than 1GB DIMMs.

But you’ll note one of the two situations: 1GB is the largest DIMM ever manufactured for that technology (SD-RAM for example) OR the system will not boot with any of the larger DIMMs (a single 2GB DDR2 stick will prevent the BIOS from posting). Economics Dan Moynihan Brian Titley Pdf To Word here. So it pretty much goes without saying that if your motherboard doesn’t support more than 4GB of RAM, you can’t install more than 4GB of ram and get windows to use it, since if you do then the system won’t boot.

But if your system boots with 4GB of RAM installed I guarantee it’s either a a 64bit system or supports PAE. So if it boots, you can hack windows to use it. Hi, I tried to use PatchPae to make my laptops see the 4Gig memory I’ve just installed.

I tried the 2 modules in one machine, it worked fine, I tried them in my machine and the machine will boot up but will eventually blue screen and I have to revert to the original boot. The 1st machine worked perfectly, seeing all 4Gig of memory. I’ve been more technically harsh on my machine over the years, so could have something conflicting. Where should I look? How do I find out what’s conflicting, or should I just leave it as unsolve-able.

I’m a hardware tech, with not much background in software, but am always willing to diagnose. Oh, the laptop is an Acer Aspire 5735. I got the same problem as Tim Edwards. However I have not tried disabling my antivirus yet during the patch of the 2nd command line for creation of winloadp.exe by cloning winload.exe My view is that failing this important step is causing the “checking” of the installation files. So if this step fails for you. Try turning off antivirus and whatever that may protect your computer from probable viral attacks. This also means it may be more advisable to work in a non-networked environment.

I will be trying again by turning off antivirus and unplugging my lan later when i get back home tonight to attempt this again. Tim, if you read this. And can try it now.

Do give it a shot and let me know if it helped. 1 month ago is pretty long. As I said I would look at Rampatch and report back. I have ran the program and received a copy of ntkrlICE which is a patched copy of ntkrlpa which is the original kernel. The program does NOT at least for me write a boot load change and make it available on a reboot. The fact is, it wants to review and repair the load just as it does for patchpae. I edited the command structure from patchpae to get the boot loader added.

I suspect the issue is in the boot loader. I added a copy and rename winloader (winloadICE) to create the second load option using BCDEDIT as per the instructions in patchpae. The author of rampatch says the program will edit the boot load file, if that is the case how and where does this happen? Poor documentation is more the norm than quality writing. I am using Windows 7 build 7601 with service pack 1 and a recent ASUS motherboard. Nothing works.

Some users report mixed results as well as working versions. I find nothing to work for me. I am through with this moon walk and hope someone else will report a DETAILED writing of how they got a working version for either patchpae or rampatch.

Best of luck. C: WherePatchPaeIs PatchPae2.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe: This line patches properly. C: WherePatchPaeIs PatchPae2.exe -type loader -o winloadp.exe winload.exe: This line displays a FAILED flag upon completion. Upon several trials it never works.

The pathing to the folder used for the installation does not allow (at least me) to run the file from CMD. I placed the files directly in windows system32. The operations at least worked until the above failure. Everything else seems to be in place and will work. Except the program forces windows to scan it’s installation and reboots. In short it fails all the way around.

I am an old DOS guy so I am with in my element. The program is not right. I placed the main sub folder with the exe thinking it might be missing some sort of library. The same results.

Unless the author refines his exe it is dead in the water. The first version had the same results. I never have gotten it to work. Somethings missing. I really would like to avoid using 64 bit software. I will try the other Rampatch and see what it is missing. Hello, first I would like to say that this patch works alright.

I have Windows 7 Ultimate 32-bit and when I restart after doing all the procedures and change to the patched version it starts normally, so its fine up to tht point. But when I stut my computer down and the next day I try to start the patched version again it enters the Startup Repair mode but it does not fix anything at all, it simply enters an infinite loop. I know someone has already posted a similar comment above since I have read them all in hope of finding a solution for this but no luck. If anyone has found a way to fix this Startup Repair thing please help. Again, this patch actually works. Basheer, I’ve done 5 or 6 laptops and all worked until this one, then this one was looping as yours is. In my case all Dell Lat E6410’s with Core i5 CPU’s, 8GB RAM and updated w7-32 SP1.

I have been doing these over several months, so they were at different levels of win update. I have always run the mem patch process in an elevated cmd window (start menu accessories cmd, rt clcik, run as admin). I just followed the instructions to remove the patch in msconfig, the ran through the commands again, and it’s working now. I’m dyslexic, so I copied/pasted the commands from this website and also copied/pasted the BCD_ID into notepad to past back into the cmd window. Another thing I did different between the failed and good attempt, on the failed attempt, I just googled patchpae2 and downloaded from another site.

Maybe a bad copy. On the good attempt, I came to this site and downloaded. If going back through fails to resolve for you, you might try deleting again, then running “sfc /scannow” at an elevated cmd prompt with your win7 disk in the drive. I followed all the instructions on my Core-i5 machine running Windows 7 Pro 32-bit. It seems to work although, since I’ve only just done it, I can’t vouch for its stability. There is, however, one problem. Every time I boot the patched version I get a window saying “NTVDM.EXE has stopped working”.

It is precisely because I need to use 16-bit Dos programs on a very regular basis that I am using 32-bit Windows rather than 64-bit Windows, which can’t run them. Without NTVDM, I can’t run them on 32-bit Windows either. I’ve got 16Gb of RAM and I want a large RAMdisk and lots of memory to run programs in without having them paged to disk all the time. Any suggestions would be very much appreciated. I see a lot of 64 bit users insult this patch a lot. A few things they say is true a 64 bit operating system will run your memory faster helping in benchmarks.

However this patch will definitely improve memory use, memory speed and benchmarks in your 32 bit operating system. Yes the 64bit operating system is faster. But not by much if you have a good video card. If you hate to spend money and need a good video card, The 650ti will give the high end performance of an expensive card at half the price, and better specs.

It should play all new game titles for at least the next 2 years. $114 plus $25 rebate and free delivery. I got mine in 6 days. Newegg.com/Product/Product.aspx?Item=N7725 A 650ti in my old i5 750 8gb ripjaw 1600 matches benchmarks of 64bit users with a card around the same specs. Hope this helps you not to feel so bad when the 64 bitters start to rip on you.

However I plan on using 64bit operating system as soon as I can find a replacement modem. Like a lot of you my modem is why I had to use 32bit operating system. Unfortunately, it didn’t work on my Win 7 Ultimate system. I am not sure if the new release of Microsoft update (I keeped mine up to date) prevent it from working, but it seems I cannot avoid the forced startup check even I have done the step 5.

When I chose to start with the patch, Windows just forced me to come to the startup repair and actually fixed nothing. Safemode also didn’t work for it. Although I tought if I debug it command by command I might find out why, I really did not have energy to do that. The original system works as before, anyway.

If anyone think out how to solve the problem, please tell me. The same problem with me. I have Win 7 Ultimate, and the command lines worked, a new patched version appeared in the boot screen, but after that the Startup Repair jumped in and tryied to correct something. I let it do that, and after that it just restarted again, so if I don’t start the default system I keep going in circles with the patched version If you have a solution for this, please contact me!

PS: Thanks for the tips! I don’t have IT skills at all but theese steps guided me through and succeeded. Hi everybody, I just wanted to testify that this patch is really working How To Install Windows 2000 On Virtualbox Linux. !!!! I used to work with Win7 x64 since the the first released betas, just to take advantage of the 4gb installed in my HP Pavilion laptop DV5. Last week I decided to test by myself and installed Win7 32bits which first said ” 4gb and 3gb usable ” and my nvidia declared 1,5gb of total memory (including shared) and after applying the patch the system reports 4Gb of total RAM and the nvidia reports 2Gb of total memory.

I Don’t have any issue for now, and all my applications run just fine including all the games I play. So to say: THANK YOU GUYS, YOU MADE A HAPPY MAN! My 2 cents: Does this work? Sure it does. Does Microsoft want people doing this? Probably not. Two reasons: 1) Licensing.

Yeah, it sucks, but this is one of the reasons. I haven’t confirmed this for myself, but I heard that device drivers will go haywire on a system running uncrippled PAE when the driver tries to address space above the 4 GB “ceiling.” So for those two reasons (the latter good, the former not so good), Microsoft keeps XP/Vista/7 at the 4 GB barrier with hardware mapped within that limit (not above it). Microsoft Server OSes don’t have crippled PAE because server manufacturers usually follow a strict hardware compatibility list (HCL), and the drivers are written to take advantage of PAE.

Also, the actual limit on a 32-bit OS is actually 2^36, or about 64 GB of RAM (not 128 GB like Ady (#83 above) says). Try it for windows 7, works perfect!!, about limitations in 32 bit architecture: stop acting like Microsoft kids, i remember the Z80 back in old days on 8 bits which theoretical can address 64 K and back then where lots of sinclairs with 128K. How was that possible? How a 32 bit operating system can access 128 GB ( yes i tried this patch with 16 GB and there are not just numbers, the memory it is accessible and usable). Think twice before posting, microsoft it’s full of bull with pae and other crappy methods.

Paging memory can be done in many other ways and of course: THX RAYMOND!!! Problem solved.