In the past, I broke major applications by turning compatibility settings off in Group Policy and I am currently not in favour of this approach. I have my reasons and they are good reasons. I routinely install them, but I am not asking anyone else to do so. The maximum memory limitation varies by operating system for instance, the 4GB memory limitation doesn't exist in 64-bit versions of Windows.Install all updates, turn CEIP off (why was this not common practice since the release of Windows 7?) and allow KB2952664/KB31501513 as Optional, even if they are Recommended. However, if you've maxed out the DRAM in your system, this amount will be deducted from your physical memory, so you can't use 100% of your DRAM. The amount of memory needed for these devices is calculated by your system at startup if you haven't maxed out the memory in your system, it's invisible to you, and all your physical memory (the RAM that's installed) is available for use. What happens is that some of the addressable memory (regardless of how much you have physically installed) is reserved for use by page files or by some of the devices that you are using, such as a graphics card, PCI card, integrated network connections, etc., so it's unavailable for use as normal main memory. Windows allows for 4GB of memory to be addressed, but this isn't 100 percent the same as having 4GB of physical memory.
There isn't a problem with the memory in this instance. There is a maximum amount of memory that your computer motherboard can accept, there is also a maximum amount of memory that your operating system (OS) can accept.įor instance, when you install 4GB of memory in a 32-bit Windows® operating system your system will see (and utilize) only 3GB or 3.5GB.
The maximum amount of memory that your system can use is limited in two ways.