How Do You Find the Memory Size, Speed, and Type in Windows 11?

To find the installed memory size, configured speed, and type in Windows 11 without opening the PC, run a targeted Win32_PhysicalMemory query in a normal PowerShell tab. It lists each populated memory bank, its capacity in gigabytes, the configured clock-speed value, and the raw SMBIOS memory-type code. A second read-only summary can compare installed module capacity with memory Windows exposes as usable.

I reproduced both checks on Windows 11 version 25H2, build 26220.7872. The PC reported two 8 GB modules, for 16 GB installed, with a ConfiguredClockSpeed value of 3200 and SMBIOSMemoryType 26, which maps to DDR4. The comparison showed 15.42 GB usable. No firmware, memory timing, page-file, diagnostic, or hardware setting changed.

What do memory size, speed, and type mean?

Capacity is the amount of storage on each physical memory module. Adding the module capacities gives the installed total. ConfiguredClockSpeed is the speed value the firmware exposes for the module's current configuration. SMBIOSMemoryType is a numeric code from the platform's SMBIOS inventory; code 26 represents DDR4.

Microsoft's Win32_PhysicalMemory reference describes the class as a physical memory device and documents Capacity, ConfiguredClockSpeed, and SMBIOSMemoryType as read-only properties. It also exposes potentially identifying properties such as SerialNumber and PartNumber, which the command in this guide deliberately does not request.

The reported speed is inventory data, not a stability test or proof of a memory profile's advertised transfer rate. Firmware, module design, and platform reporting can affect the value. If the property is zero or missing, record it as unavailable rather than guessing from a product listing.

Table of contents

What should you know before checking RAM details?

Open a standard, non-administrator PowerShell session. The commands only retrieve local inventory and do not require elevation on the reproduced PC. Close unrelated tabs before sharing screenshots because an ordinary prompt can expose a user name or working directory. The retained evidence used a disposable maximized Terminal session with an anonymous prompt.

This procedure does not test memory for faults, calculate upgrade compatibility, inspect physical labels, or change XMP/EXPO settings. A capacity or speed value alone cannot prove that a module is healthy. It also cannot tell you whether a different kit is supported by a specific motherboard or laptop.

The article reports the two populated banks visible on the reproduced device. Another PC can show one module, several modules, different bank labels, or no reliable speed/type value. Read your own output rather than treating the example as a requirement.

How do you list each memory module's size, speed, and type?

1. Open Windows Terminal.
2. Make sure the active tab is PowerShell.
3. Enter this focused command:

Get-CimInstance Win32_PhysicalMemory | select BankLabel,@{N='GB';E={$_.Capacity/1GB}},ConfiguredClockSpeed,SMBIOSMemoryType

4. Press Enter.
5. Count the returned rows to see how many memory devices Windows reports.
6. Read GB, ConfiguredClockSpeed, and SMBIOSMemoryType for each row.

The two 8 GB rows add up to 16 GB installed. The bank labels identify the firmware-reported locations, not necessarily the printed slot names in a service manual. Type code 26 corresponds to DDR4 in the documented SMBIOS enumeration. If two modules report different capacities or speeds, preserve each row separately rather than averaging them.

How do you compare installed and usable memory?

Run these two PowerShell lines. The first adds the capacities of the physical-memory objects. The second displays that installed total beside the memory exposed through Win32_ComputerSystem:

$installed = (Get-CimInstance Win32_PhysicalMemory | Measure-Object Capacity -Sum).Sum
[pscustomobject]@{InstalledGB=$installed/1GB;UsableGB=[math]::Round((Get-CimInstance Win32_ComputerSystem).TotalPhysicalMemory/1GB,2)}

Press Enter after the final line and compare the two columns.

Microsoft's Win32_ComputerSystem documentation identifies TotalPhysicalMemory as the total physical memory available through the computer-system object and warns that reserved memory can make it less accurate for installed capacity. That is why the module sum is used for InstalledGB and the computer-system value is labeled UsableGB here.

Why can installed and usable memory differ?

Firmware and hardware can reserve part of physical memory for integrated graphics, device mappings, or other platform needs. Windows may therefore expose slightly less usable memory than the capacities printed on the installed modules. In the reproduced result, 16 GB installed and 15.42 GB usable is a difference in scope, not evidence that a module has disappeared.

A very large or unexpected difference deserves investigation, but this inventory alone cannot diagnose the cause. Compare firmware settings, Task Manager's Memory view, hardware-reserved memory, and the device manufacturer's documentation before changing anything. Do not alter firmware allocation or page-file settings merely to make two numbers match.

How should you interpret the SMBIOS memory-type code?

The type property is a raw integer because Windows receives structured inventory from SMBIOS. Code 26 maps to DDR4. Other systems can report a different documented code, zero, or an unknown value. Treat the raw number as reported platform data, and verify its mapping in current documentation before naming the generation.

The code does not identify every electrical detail needed for an upgrade. It does not replace the device service manual, supported-capacity table, form factor, rank layout, voltage, or manufacturer compatibility list. Avoid publishing serial and part numbers while asking for help; share only the minimum properties required.

What can you do if the command returns incomplete information?

If Get-CimInstance is not recognized, use Windows PowerShell or a supported PowerShell installation with the CIM cmdlets. If no rows appear, confirm that you are querying the local Windows system and retry in a fresh standard-user session. A managed PC may restrict inventory access.

If ConfiguredClockSpeed or SMBIOSMemoryType is zero, the firmware may not expose a usable value. Check Task Manager or the official device support tool for corroboration, but do not invent a missing type. If capacity looks wrong, restart once and compare the module sum with the firmware or manufacturer inventory before opening the device.

If you suspect faulty memory, use a separate diagnostic workflow. The commands here read inventory only; they do not stress memory, scan for errors, or validate stability.

Frequently Asked Questions

Record module details and totals separately

Use Win32_PhysicalMemory to read each module's capacity, configured speed, and raw type code, then calculate installed capacity separately from the usable computer-system total. This keeps the inventory precise without exposing serial numbers, running diagnostics, or changing hardware settings.

For more interesting articles, stay tuned to WinSides.com!