SCOM registry {30067863-18D6-4CB8-BF91-616897D1B6DB}\DisplayVersion showing 10.22.10118.0 instead of 10.22.12236.0

Teng Keng Leng 0 Reputation points
2026-09-06T13:35:05.7466667+00:00

I followed the installation steps to install Hotfix for System Center Operations Manager 2022 UR3 from below link.

https://support.microsoft.com/en-us/servicing/management-tools/operations-manager/update/2026/07/hotfix-for-system-center-2022-operations-manager-ur3-componentsvrsnmpupdate

But registry {30067863-18D6-4CB8-BF91-616897D1B6DB}\DisplayVersion is showing 10.22.10118.0 instead of 10.22.12236.0. Why is the registry not showing the updated version but only the RTM version?

System Center Operations Manager
System Center Operations Manager

A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.

0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest
  1. SChalakov 10,861 Reputation points MVP Volunteer Moderator
    2026-09-07T07:40:58.96+00:00

    Hi,

    What you are seeing does not necessarily mean that KB5101442 was not installed successfully.

    The GUID you are checking:

    {30067863-18D6-4CB8-BF91-616897D1B6DB}

    is the RTM ProductCode of the SCOM 2022 Operations Console. Microsoft explicitly identifies it as the RTMProductCodeGuid in the KB5101442 documentation. The corresponding patch has a different PatchCode:

    {59FAAFE9-FFAD-419F-BC9C-113B91141A9B}

    KB5101442 is delivered as an MSP patch applied to the existing SCOM MSI installation; it does not install a new MSI product with a new ProductCode.

    The registry DisplayVersion below the Windows Installer uninstall key is derived from the MSI ProductVersion property. Therefore, this value is not a reliable way of determining the current SCOM Update Rollup/hotfix servicing level.

    10.22.10118.0 is indeed the original SCOM 2022 GA/RTM build for the Management Server and the other components, including the Operations Console. Microsoft lists 10.22.12236.0 separately as the July 2026 KB5101442 build.

    I would verify KB5101442 in one of the following ways:

    1. Check the component information in Administration > Operations Manager Products in the SCOM console.
    2. Check the version of one of the binaries explicitly updated by KB5101442. For example, Microsoft lists URVersion.dll as 10.22.12236.0 after the update.
    3. You can also verify that the KB5101442 Console PatchCode is registered against the Console product using Windows Installer:

    $Installer = New-Object -ComObject WindowsInstaller.Installer

    $Installer.Patches('{30067863-18D6-4CB8-BF91-616897D1B6DB}')

    For KB5101442, the returned patch list should include:

    {59FAAFE9-FFAD-419F-BC9C-113B91141A9B}

    Windows Installer exposes applied patches separately from the underlying MSI product, which is exactly the distinction here.

    Also, the statement in the KB that the hotfix fixes an issue where the Operations Console did not display the updated version of every component refers to the component version information displayed by SCOM, not to the DisplayVersion of the RTM MSI under the Windows uninstall registry key.

    So, if URVersion.dll and the Operations Manager product/component information show 10.22.12236.0 / KB5101442, I would consider the hotfix correctly applied even if the RTM MSI registry DisplayVersion remains at 10.22.10118.0.

    Best Regards
    Stoyan

    "If my response was useful, please consider marking it as the answer. It keeps the forum clean, structured, and more helpful for everyone. Thank you for supporting the community."

    Was this answer helpful?

    1 person found this answer helpful.
    0 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.