Windows detects less RAM: what to compare

The short answer: If Windows shows less memory than is physically installed after an upgrade, first compare the capacity detected in BIOS/UEFI with the installed and total physical memory reported by msinfo32. Then check the “Hardware reserved” value in Task Manager. Where the amount disappears—either in BIOS or only after Windows starts—will determine whether you should investigate a physical installation issue or a software and licensing issue.

First, establish what you are actually comparing

When a customer says that their computer “cannot see all the memory,” they usually mean a number shown somewhere in Windows. That number, however, is the result of an entire chain: physical module → slot → memory controller and BIOS → Windows edition limit → hardware reservations → operating system. Comparing two points in this chain reveals where the apparent loss occurs.

The two basic values to compare are:

• Capacity reported by BIOS/UEFI – what the firmware detects from the physically installed modules.
• Values reported by Windows – installed and total physical memory in msinfo32, supplemented by the “Hardware reserved” value in Task Manager.

This article addresses missing capacity after an upgrade. For guidance on how much memory you need in the first place, see how much RAM you need in 2026. I recommend writing down both figures before making any changes. Without this record, diagnostics quickly turn into random trial and error, leaving no reliable way to verify the result.

Step 1: Only record the capacity detected in BIOS/UEFI

Dell’s instructions for installing and upgrading memory recommend checking the documentation for the specific model to confirm the memory type, maximum capacity, and slot configuration. For this comparison, therefore, do not change anything in BIOS—only read the value (Dell: Install or upgrade RAM).

Procedure:

1. Restart the computer and open Setup (usually by pressing F2; some manufacturers use Del or Esc—consult the manual for the exact key for your model).
2. Find the section containing system or memory information (its name varies by firmware manufacturer).
3. Record the total detected capacity and the number of installed modules, if shown.
4. Exit Setup without saving any changes by selecting “Exit without saving.”

Expected result: the figure matches the sum of the rated capacities of all installed modules—for example, 32 GB with two 16 GB modules.

Safe path if it does not: If BIOS reports less memory—for example, only 16 GB out of 32 GB—the problem lies at the firmware–slot–module level. Leave BIOS unchanged, do not reset its settings, and continue with the physical inspection path described below. For a business or customer computer, document the finding and leave physical handling to a service technician.

Step 2: Windows—Task Manager, Performance → Memory

Once you know the figure reported by BIOS, open Task Manager:

1. Press Ctrl + Shift + Esc.
2. Open the Performance tab and select Memory.
3. Record the main capacity figure at the top and the “Hardware reserved” figure at the bottom. Labels may vary by version, so also check the installed and total capacity in msinfo32 during the next step.

Important: do not use the “Available” value for this comparison. It represents memory currently available to applications, including reusable standby memory, and changes according to the software that is running. Diagnosing missing capacity from the “Available” value leads to the false conclusion that memory is “missing” when it is merely in use.

Expected result: you can distinguish between total capacity and the amount reserved for hardware. There is no universally correct reservation size; compare it with the documentation and configuration of the specific device.

Next path: supplement these figures with the value from msinfo32. If the difference is unexpected for that model, keep a record of it and do not try to remove the reservation by changing settings at random.

Step 3: Check msinfo32, the Windows edition, and architecture

Microsoft’s documentation states that accessible physical memory limits depend on the Windows edition and architecture. Lower usable memory therefore cannot automatically be blamed on a faulty module (Microsoft: Memory limits Windows).

Procedure:

1. Press Win + R, enter msinfo32, and press Enter.
2. In System Summary, record “Total Physical Memory” and “Installed Physical Memory (RAM).”
3. Record the Windows edition and system type. You can find the necessary details under Settings → System → About or directly in msinfo32. Windows 11 has no 32-bit edition, so the general limitations of older 32-bit systems do not explain a problem on a Windows 11 computer.

Expected result: you now know the capacity recognised by the firmware, the installed capacity reported by Windows, and the capacity usable by the system. A difference may be related to a reservation or limit; by itself, it proves neither that a module is faulty nor that the configuration is correct.

Decision table: where the capacity disappears

What the test proves—and what it does not

This is the boundary that must be made clear to both the customer and yourself:

The test proves:

• Whether the firmware detects the installed capacity.
• How much installed and usable capacity Windows reports.
• The size of the identified difference. Its exact cause must still be verified; it cannot automatically be attributed solely to an integrated graphics reservation.

The test DOES NOT PROVE:

• Which specific module is faulty when several are installed. That would require testing the modules individually, with the power disconnected, in accordance with the service manual for that model, and by a qualified person. For memory type, maximum capacity, and slot configuration, Dell repeatedly refers users to the documentation for the specific computer rather than offering universal instructions (Dell: Install or upgrade RAM).
• That a module is genuinely incompatible. Startup behaviour can have several causes, and a single detection failure cannot conclusively confirm or rule out compatibility.
• That the “missing” gigabytes are harmful. Hardware reservations are intentional on many systems.

Safe troubleshooting paths

Path A—the problem is in BIOS, which reports less than is installed:

• Leave the firmware settings unchanged.
• Arrange service based on the manual for the specific model: the technician should check module installation, slots, and compatibility against the manufacturer’s documentation for that model.
• Address the data before handing over the computer: make a backup, and ensure that the device owner retains the encryption keys, such as the BitLocker recovery key. Never send keys by email, through forms, or via chat.
• If the storage medium is faulty and contains sensitive original data, do not repair or repeatedly access it—the diagnostics concern the device, not the data.

Path B—BIOS is correct, but Windows reports less:

• Verify the edition and architecture. Usable memory limits differ between Windows editions and cannot be attributed to hardware (Microsoft: Memory limits Windows).
• Determine how much memory is listed as “Hardware reserved.” Integrated graphics may reserve some memory, but check the correct range for the specific model.
• If none of these explanations accounts for the difference, give the service technician an exact record of the values from steps 1–3.

These diagnostics do not include setting maximum memory through msconfig or resetting BIOS. Both actions alter the configuration, which there is no reason to change during a simple comparison, and they may cause more harm than good.

Handover checklist and result verification

If you hand the computer over to a customer, colleague, or service centre, include:

• The recorded BIOS/UEFI capacity and number of modules
• The capacity and “Hardware reserved” value from Task Manager
• “Installed Physical Memory (RAM)” and “Total Physical Memory” from msinfo32
• The system type (64-bit) and Windows edition
• A note stating whether a backup was made and who holds the encryption keys
• A note explaining what has and has not been ruled out

Verifying the result after any intervention: repeat steps 1 and 2. This produces a comparable record: BIOS reports the full installed capacity, the Windows “Installed” value matches it, and the “Hardware reserved” amount is appropriate for the device configuration. Without this repeated measurement, you cannot claim that the intervention solved anything. Also remember that advice involving a restart applies to personal computers and should not be followed indiscriminately on every business server.

Frequently asked questions

Why does Windows show a different amount of RAM than BIOS?

The difference may be caused by hardware reservations, edition limits, or configuration. Assess its size in the context of the specific computer. Compare installed and total physical memory with BIOS, not the amount currently shown as “Available.”

Does a lower amount of “Available” memory indicate a fault?

Not by itself. It represents the capacity available to applications at that moment and changes over time. Check installed and total physical memory in msinfo32, then find the hardware-reserved amount in Task Manager.

Should I change anything in BIOS if it cannot detect the memory?

No. Only record the capacity detected in BIOS; do not change anything. Compatibility, installation, firmware, or a slot may be responsible. A technician should investigate these factors using the service manual for the specific model, rather than changing settings.

How can I tell whether the Windows edition is causing the problem?

Run msinfo32 and compare “Installed Physical Memory (RAM)” with “Total Physical Memory.” Also check the system type under System → About in Settings. Accessible memory limits depend on the edition and architecture, so a lower value does not necessarily mean that a module is faulty.

Can I test the modules myself, one at a time?

Individual testing requires physical handling with the power disconnected, following the service manual for that model, so it should be performed by a qualified person. Back up the data first and ensure that the owner retains the encryption keys—never send keys through chat, email, or a form.

When professional service makes sense

Describe a persistent fault in the service request: include the exact model, the symptom, when it began, and what you have already checked safely. For device repair and further assistance, use ITHOPE PC and laptop repair services. If unbacked-up data is also at risk, address the data first. The price and scope of the work can be determined once the cause has been identified.

Sources and review date

The technical sources were reviewed on 4 October 2026.

• Dell: Install or upgrade RAM
• Microsoft: Memory limits Windows