Windows Shows Less RAM Than I Actually Installed
Short answer
Open Task Manager → Performance → Memory and compare the figure at the top right with what Windows reports as usable. A gap of a few hundred megabytes to around 2GB is integrated graphics and firmware reserving memory, which is normal and not recoverable. A gap of 4GB or more means a maximum memory limit set in msconfig, a failed module, or 32-bit Windows.
On this page
There are two completely different versions of this question, and they have nothing to do with each other.
A machine showing 15.8GB usable out of 16GB installed is working normally and there is nothing to fix. A machine showing 8GB usable out of 16GB installed has a real problem, and it is usually one of three specific things.
The size of the gap tells you which conversation you are in.
Read the numbers properly
Open Task Manager with Ctrl+Shift+Esc, go to Performance and click Memory. The top right shows total installed. Below the graph, Hardware reserved shows what is unavailable to Windows.
| Gap | Meaning |
|---|---|
| Under 1GB | Normal. Firmware and device mapping. |
| 1–2GB on a laptop | Normal. Integrated graphics allocation. |
| Exactly half your total | A module or slot is not detected |
| Everything above ~3.4GB | 32-bit Windows |
| Several GB, no pattern | Memory limit set in msconfig |
The Memory page also shows Slots used, for example “2 of 4”. If you fitted four sticks and it reports two, the problem is physical and the rest of the software checks are wasted effort.
The normal reservation, and why you cannot get it back
Some memory addresses are not backed by RAM at all. They are mapped to hardware: the firmware, the TPM, PCIe device address space, and on machines with integrated graphics, a block of system memory set aside as video memory.
The graphics allocation is the largest piece on most laptops. Integrated Intel and AMD graphics have no memory of their own, so they take between 512MB and 2GB of system RAM, depending on the BIOS setting and total installed.
Some desktop motherboards expose a DVMT Pre-Allocated or shared memory size option in the BIOS, and reducing it recovers a few hundred megabytes. On most laptops the option does not exist, and on machines that use dynamic allocation the figure adjusts itself anyway.
The practical answer: a reservation under 2GB is not worth pursuing. The memory is in use, not lost.
The msconfig limit that catches everyone
This is the most common cause of a large unexplained gap, and it is almost always self-inflicted. Someone enabled a maximum memory setting during troubleshooting years ago and never cleared it.
- Press Win+R, type
msconfig, press Enter. - Go to the Boot tab and click Advanced options.
- Check the Maximum memory box. It should be unticked.
- If it is ticked, untick it, click OK, and restart.
A value here overrides everything. Windows will faithfully use only what the box says, no matter how much is installed, and nothing else in Windows indicates that the limit exists.
While you are there, leave Number of processors unticked too. Same logic, same source, same effect on CPU cores.
32-bit Windows
A 32-bit operating system can address 4GB total, and device address space is carved out of that same 4GB. The usable figure lands around 3.2–3.5GB regardless of how much is installed.
Check at Settings → System → About, under System type. It reports both the OS architecture and whether the processor is 64-bit capable.
If it says 32-bit operating system on an x64-based processor, you are losing memory to an architecture limit. The only fix is a clean install of 64-bit Windows — there is no in-place upgrade path between architectures, so you will need to back up your files and reinstall your applications afterwards.
On any machine capable of running Windows 11, this should be rare, since Windows 11 is 64-bit only. It still appears on older hardware that was upgraded through several versions.
A module or slot that is not working
If the figure is close to exactly half, or exactly one module’s worth short, the hardware is not all being seen.
Check the BIOS first. Enter it with F2 or Del during boot and find the memory information page. It lists what is detected per slot. The BIOS and Windows agreeing on a low figure means the module is genuinely not detected; the BIOS seeing all of it while Windows does not points back at msconfig.
Reseat the modules. Power off, unplug, press and hold the power button for ten seconds to discharge, then open the case or the laptop’s memory hatch. Release the clips, remove each stick, and refit it firmly until both clips click home. Partially seated memory is extremely common after a machine has been moved, and it produces exactly this symptom.
Test one at a time. Fit a single module in the slot the manual designates as first, and boot. Repeat with each module, then with each slot. This identifies whether a stick or a slot is at fault, and it is the only reliable way to tell them apart.
Check for mixed modules. Sticks of different speeds, capacities or ranks do not always run together. The motherboard manual’s qualified vendor list and supported configurations table is the authority, and dual-channel configurations usually require matched pairs in specific slots — often slots 2 and 4 rather than 1 and 2.
Run a memory test. Search Start for Windows Memory Diagnostic. It restarts and tests before Windows loads. A pass is reassuring but not conclusive; MemTest86 from a USB stick, run for several passes, is the thorough version.
Also check the edition limit
Windows editions impose their own maximums. Windows 11 Home supports up to 128GB and Pro up to 2TB, so for ordinary machines this never binds. It is worth knowing it exists if you are fitting a great deal of memory to a Home installation and finding a ceiling.
Check your edition at Settings → System → About under Windows specifications.
What to do if the memory is all there and still not enough
Sometimes the number is correct and the machine is still short. That is a different problem with a different answer.
Watch Task Manager → Performance → Memory during normal use. If In use sits above 85%, or Committed exceeds installed RAM, the system is paging to disk, which presents as a storage bottleneck rather than a memory one. Windows 11 in particular uses more RAM than Windows 10 did on the same machine, which is covered in whether Windows 11 is slower than Windows 10.
The browser is almost always the largest consumer, and reducing Chrome’s memory use is usually the cheapest available improvement before buying anything.
What does not help
- “RAM optimiser” and memory cleaner utilities. They flush working sets to disk. The number improves, everything gets slower, nothing is gained.
- Changing the page file size to recover physical memory. Unrelated mechanism.
- BIOS updates as a first step. Occasionally they do fix memory detection on a specific board, and a failed flash bricks the machine, so reseat first.
- Deleting the hibernation file. That reclaims disk space, not RAM.
Realistic expectations
A gap under 2GB is normal and the correct response is to stop looking at it.
A large gap is almost always the msconfig maximum memory box, and unticking it plus a restart returns the full amount immediately. That check costs thirty seconds and should be the first thing anyone tries.
If the BIOS also reports less than you installed, it is hardware, and reseating resolves a good share of those. What remains is a failed module or a failed slot, and testing one stick at a time in one slot at a time is the only way to be certain which.