Hardware resrve issue with windows 2022

J. Helm 0 Reputation points
2025-10-22T15:59:05.93+00:00

After installing Windows 2022 on older 2012 hardware at some point in the enabling of roles the hardware reserve was using 62gb of the 64gb RAM installed. Thinking this might be hardware related, we migrated to new updated hardware restored from backup and the issue persisted. I tried all the tricks mentioned online. I did a fresh install just to see if it was the hardware. The new install showed 384mb of hardware reserve, what I would expect. I tried updating all the drivers. Nothing changed. So I eliminated bad memory, bios, and max memory option in msconfig. The issue stays with the original setup. Re-installing windows is not ideal at all as the software that was installed costs $3500 to install. I need to be able to correct this without losing the software being used.

Windows for business | Windows Server | Performance | Windows desktop and shell experience
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Jason Nguyen Tran 4,250 Reputation points Independent Advisor
    2025-10-22T16:43:05.01+00:00

    It seems the excessive “Hardware Reserved” memory (62GB of 64GB) on the original setup isn’t hardware-related but more likely caused by a memory mapping or firmware-level configuration issue persisting in the OS after migration. Here are a few things to check before considering a reinstall:

    1. Check memory remapping in BIOS/UEFI - Even if BIOS was updated, ensure “Memory Remap Feature” (or similar) is enabled.
    2. Verify NUMA/Memory configuration - Run SYSTEMINFO or check in Task Manager > Performance > Memory > Slots used, to ensure all memory nodes are detected correctly.
    3. Confirm firmware and chipset drivers - Especially for the motherboard, as older boards may need specific chipset packages for Windows Server 2022 to properly map RAM.
    4. Boot Configuration Data (BCD) - Run an elevated Command Prompt and execute: SQL:
      bcdedit /deletevalue truncatememory bcdedit /deletevalue removememory Then restart the server. These values, if present, can cause Windows to reserve large memory blocks.
    5. Device conflicts or driver-level reservation - Check Device Manager (View > Resources by type) for devices reserving large address ranges.

    If none of these resolve the issue, we can perform an in-place upgrade repair - this will refresh system files without removing installed software or roles.

    Please give these a try and let me know the results. If this helps fix the issue, kindly click “Accept answer” so others can benefit as well 😊

    0 comments No comments

  2. J. Helm 0 Reputation points
    2025-10-24T18:20:15.5733333+00:00

    First off, thank you for your attention on this matter and the quick response.

    Check memory remapping in BIOS/UEFI - Even if BIOS was updated, ensure “Memory Remap Feature” (or similar) is enabled.

    It is a Supermicro x13sra-tf with latest bios, I can find no reference in the bios nor on-line about memory remapping for this mobo.

    Without changing anything in bios after restore, I can re-install new windows and problem goes away.

    Verify NUMA/Memory configuration - Run SYSTEMINFO or check in Task Manager > Performance > Memory > Slots used, to ensure all memory nodes are detected correctly.

    When all 4 are in no matter which slots I put them in, it recognizes all slots. When 1 to 3 sticks are in; the hardware reserve drops to 4.9gb which is still high.

    This was the same on the other machine as well.

    Confirm firmware and chipset drivers - Especially for the motherboard, as older boards may need specific chipset packages for Windows Server 2022 to properly map RAM.

    Updated to the latest chip set on the new hardware, no change.

    Boot Configuration Data (BCD) - Run an elevated Command Prompt and execute: SQL:

    bcdedit /deletevalue truncatememory bcdedit /deletevalue removememory Then restart the server. These values, if present, can cause Windows to reserve large memory blocks.

    Both commands return "Element not found"

    Device conflicts or driver-level reservation - Check Device Manager (View > Resources by type) for devices reserving large address ranges.

    I'm working on this one, it's not easy to read. Or at least calculate the difference in hex. Unless there is an easy trick to it that I missed.

    If none of these resolve the issue, we can perform an in-place upgrade repair - this will refresh system files without removing installed software or roles.

    I tried that but it requires win 2022 to be activated and I can't activate until I shut the older one down. The older one is still being used with 48gb (because hardware reserve is 4.9gb) and substandard operation, because it's mission critical.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.