On Windows, PowerShell's Get-CimInstance against Win32_PhysicalMemory and Win32_PhysicalMemoryArray reports capacity, speed, part number and slot count directly from SMBIOS data - wmic is deprecated and being removed. On Linux, dmidecode -t memory reads the same underlying BIOS-reported SMBIOS tables. Both have a real gap: reliable rank (1Rx4/2Rx8-style) reporting is not something either OS documents cleanly. We could not source Dell iDRAC or HPE iLO's own documented procedure this session - see the gap noted below rather than a guessed menu path.
Updated ยท vendor documents read 16 September 2026
This is the entry point for the rest of our server-RAM compatibility cluster: once you know what's actually installed, our DDR4-vs-DDR5, RDIMM-vs-UDIMM, LRDIMM, ECC, ranks, mixing-rules and population-rules pages tell you whether an upgrade module is actually compatible with it.
Microsoft's own documentation is explicit that the older command-line tool is on its way out: "The WMI command-line (WMIC) utility is deprecated as of Windows 10, version 21H1... superseded by Windows PowerShell for WMI," and further, "Starting in August 2026, Windows 11, versions 24H2 and 25H2 no longer include the [WMIC] utility and it can't be added back as a Feature on Demand (FoD)."
The supported path is Get-CimInstance against two classes. Per-stick detail comes from Win32_PhysicalMemory:
Per Microsoft's own field documentation, Capacity is "Total capacity of the physical memory - in bytes... comes from the Memory Device structure in the SMBIOS version information"; PartNumber is "Part number assigned by the organization responsible for producing or manufacturing the physical element... comes from the Part Number member"; Speed is documented in nanoseconds internally but derived from the same SMBIOS Speed field sellers and manufacturers quote in MT/s.
Slot count and platform-level maximum capacity come from a separate class, Win32_PhysicalMemoryArray:
Per Microsoft: MemoryDevices is "Number of physical slots or sockets available in this memory array" - the total DIMM slot count, filled or not - and MaxCapacityEx is "Maximum memory size (in kilobytes) installable for this particular memory array," with the older byte-based MaxCapacity field documented as deprecated in its favor.
Windows does carry a rank-related field, but it is not a clean answer. Microsoft's own Win32_PhysicalMemory documentation states the Attributes property "Represents the RANK. This value comes from the Attributes member of the Memory Device structure in the SMBIOS information," explicitly gated: "This property is not supported before Windows Server 2016 and Windows 10." Unlike FormFactor or MemoryType, which Microsoft documents with full enumerated value tables, Attributes has no published bit-to-rank decode table on that reference page - so on a current Windows Server the raw value is retrievable, but turning it into "2Rx4" is not something we could source a documented method for this session. See our ranks-explained page for what that notation means where it is documented.
The Ubuntu project's own manual page for dmidecode confirms the relevant option and type mapping: "-t, --type TYPE" with keyword "memory" mapping to DMI types "5, 6, 16, 17" (Memory Controller, Memory Module, Physical Memory Array, Memory Device).
This reads directly from files the manual page names explicitly: /dev/mem and, on Linux, /sys/firmware/dmi/tables/ - which is why the command typically needs elevated permissions to return complete output, even though the man page itself does not spell out a root requirement as its own sentence.
Read the project's own reliability caveat before trusting the output blindly. dmidecode's own site states: "Beware that DMI data have proven to be too unreliable to be blindly trusted. Dmidecode does not scan your hardware, it only reports what the BIOS told it to." And the Ubuntu man page's own BUGS section: "More often than not, information contained in the DMI tables is inaccurate, incomplete or simply wrong."
We could not confirm from current official documentation whether modern dmidecode reports rank at all. The one official sample output the project publishes is from an old SMBIOS 2.3-era system, which predates several fields (Manufacturer, Serial Number, Part Number, and rank/Attributes) added in SMBIOS 2.6 and later - so that sample can neither confirm nor rule out what a current dmidecode build reports for rank. We are stating this as an open gap rather than asserting either answer.
A server's baseboard management controller can usually show installed memory without logging into the OS at all - but we were not able to source and render Dell's or HPE's own current documentation of the exact steps this session. Every Dell knowledge-base URL we tried either 404'd or sat behind a sign-in wall; HPE's support-portal doc pages returned a technically-successful response with no readable content to a fetch without a JavaScript runtime. Rather than describe a menu path from memory, we are naming the gap directly: look for the System Information or Memory panel in your iDRAC or iLO web console, or check Dell's or HPE's own current support site. See our OEM-verified platform pages for the memory specifications we have sourced for specific server models.
What these tools report is what is physically installed - not what your platform supports. Compare the result against your server's own supported-memory documentation, linked from our OEM-verified platform pages, before planning an upgrade.
Cheapest in-stock modules across the catalogue right now, computed live.
| Brand | Module | Capacity | Type | $/GB | |
|---|---|---|---|---|---|
| SK Hynix | HMAA8GL7MMR4N | 64GB DDR4 | RDIMM | $4.61 | Buy Now |
| A-Tech | M393A2G40DB0-CPB | 16GB DDR4 | RDIMM | $5.44 | Buy Now |
| Samsung | M393A8K40B22-CWD | 64GB DDR4 | RDIMM | $6.23 | Buy Now |
| Supermicro | B07DFLTWN3 | 64GB DDR4 | LRDIMM | $6.23 | Buy Now |
| Samsung | M393A2G40EB1-CPB | 16GB DDR4 | RDIMM | $7.12 | Buy Now |
| MICRON | MTA36ASF4G72PZ | 32GB DDR4 | RDIMM | $7.19 | Buy Now |
| Samsung | M393A2K43CB2-CTD8Q | 16GB DDR4 | RDIMM | $8.75 | Buy Now |
| SK Hynix | HMA84GR7CJR4N-VK | 32GB DDR4 | RDIMM | $8.84 | Buy Now |
| A-Tech | B083Q3F5DX | 32GB DDR4 | RDIMM | $8.91 | Buy Now |
| A-Tech | B0BPN4L74H | 32GB DDR4 | RDIMM | $8.95 | Buy Now |
PowerShell's Get-CimInstance against the Win32_PhysicalMemory class, not wmic - Microsoft's own documentation states wmic "is deprecated as of Windows 10, version 21H1... superseded by Windows PowerShell for WMI," and adds that "Starting in August 2026, Windows 11, versions 24H2 and 25H2 no longer include the [WMIC] utility and it can't be added back as a Feature on Demand."
Partially, and with a real gap. Microsoft's own Win32_PhysicalMemory documentation states the Attributes property "Represents the RANK," gated to "not supported before Windows Server 2016 and Windows 10" - so the data exists in CIM/WMI on current systems. But Microsoft's own reference page gives no bit-to-rank decode table for that field, so the raw value alone doesn't tell you 1Rx4 versus 2Rx8 without further decoding we could not source this session.
It reads SMBIOS/DMI tables the BIOS provides, covering slot count, per-DIMM size, speed, and (on newer SMBIOS versions) manufacturer/part number/serial. Read the project's own reliability caveat before trusting it blindly: "Beware that DMI data have proven to be too unreliable to be blindly trusted. Dmidecode does not scan your hardware, it only reports what the BIOS told it to."
We could not confirm this from current official documentation either way. The only official sample output we could source is from an old SMBIOS 2.3 system, predating the SMBIOS fields (Manufacturer, Serial Number, Part Number, rank/Attributes) that were added in SMBIOS 2.6+ - so it can neither confirm nor rule out what a modern dmidecode reports for rank. We're stating that as an open gap rather than guessing.
In practice yes, because it reads /dev/mem directly - though the Ubuntu manual page we checked doesn't spell out a root requirement as an explicit sentence, only implicitly via the files it reads. If a run returns empty or truncated output, permissions are the first thing to check.
We were not able to source and render Dell's or HPE's own BMC documentation for this specific procedure this session - Dell's relevant knowledge-base article sat behind a sign-in wall on every URL we could resolve, and HPE's support portal pages returned empty content to a non-JavaScript fetch. Rather than describe a menu path from memory, we're naming this gap directly: check the System Information or Memory panel in your iDRAC or iLO web console, or see Dell's or HPE's own current support site for the exact steps.
Specification claims on this page were checked against the pages below on 16 September 2026. Where a widely-repeated figure did not survive that check, we report what the source says now and say so in the text rather than repeating the familiar number.