microsoft / microsoft/CSS-Exchange

[Issue] - Health Checker - Memory Size / Capacity

Open
#2,531 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Awaiting feedback Health Checker Issue
Dominant language
PowerShell
Stars
1.3k
Forks
395
Avg merge
14h 7m
Merged PRs (30d)
5

Description

Provide Version Number
26.03.12.1424

Describe the issue
Health Checker is telling me I'm using 1GB but its ~ 26GB

Expected behavior
Should detect 26GB

Script Output
Physical Memory: 1 GB
Warning: We recommend for the best performance to have a minimum of 128GB of RAM installed on the machine.

Additional context
Seems to be related to QEMU / Virtualization. Looks like the Capacity

Health Checker is telling me I'm using 1GB, but in the XML its:
27911188480
Helpful outputs?

PS C:\Admin\scripts\Health-Checker> Get-CimInstance Win32_ComputerSystem | Select-Object TotalPhysicalMemory
TotalPhysicalMemory
-------------------
        27911188480
$cs = Get-CimInstance Win32_ComputerSystem
[math]::Round($cs.TotalPhysicalMemory / 1GB, 2)
25.99
 Get-CimInstance Win32_PhysicalMemory | Measure-Object Capacity -Sum | Select-Object @{Name="GB";Expression={[math]::Round($_.Sum / 1GB, 2)}}

GB
--
 1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Health Checker code that reports Physical Memory and compare its calculation with the provided Get-CimInstance Win32_ComputerSystem and Win32_PhysicalMemory outputs. Reproduce the discrepancy in the QEMU or virtualized environment, then verify that the reported capacity matches the 25.99 GB TotalPhysicalMemory value rather than the 1 GB component capacity.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.