vCenter UI displays Windows Server 2025 as the Guest OS version for a Windows Server 2019 virtual machine

Products

• VMware vSphere ESXi

Issue/Introduction

• A virtual machine provisioned with a Windows Server 2019 guest operating system incorrectly reports its version as Windows Server 2025 within the VMware vCenter Server UI.
• This discrepancy is also present when monitoring the virtual machine directly via the ESXi Host Client.
• When VMware Tools is enabled and running, vCenter displays the guest OS version as Windows Server 2025.
• When VMware Tools is stopped or not installed, vCenter correctly displays the configured guest OS as Windows Server 2019.

Environment

vCenter Server 8.x
VMware vSphere ESXi 8.x

Cause

When VMware Tools is running, vCenter obtains guest OS information directly from the virtual machine's operating system registry.

In this scenario, there is a data inconsistency within the Windows guest OS registry. The registry key CurrentBuild incorrectly reports a value of 26100 (which corresponds to Windows Server 2025), while the CurrentBuildNumber correctly reports 17763 (Windows Server 2019).

VMware Tools accurately reports the CurrentBuild string provided by the guest OS to vCenter, leading to the version mismatch in the UI. VMware Tools does not alter the OS version; it only reports what is provided by the guest operating system.

To verify if your virtual machine is experiencing this specific registry inconsistency:

1. Open PowerShell as an administrator within the Guest OS of the affected virtual machine.

2. Run the following command:
   Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object ProductName, CurrentBuild, CurrentBuildNumber

3. Observe the output. An affected system will show a mismatch similar to the following:

   • ProductName: Windows Server 2019 Standard

   • CurrentBuild: 26100 (Build 26100 corresponds to Windows Server 2025)

   • CurrentBuildNumber: 17763 (Build 17763 corresponds to Windows Server 2019)

Resolution

This behavior originates from inconsistent version metadata within the Windows Guest OS registry. As the required resolution involves modifying internal operating system configurations, the fix must be applied within the Windows environment.
After confirming the registry mismatch using the preceding validation steps, please engage Microsoft Support for further assistance.