Problem with fresh install of SCOM 2022 on Windows Server 2022

Magnus Sörensson 6 Reputation points


I am trying to install SCOM 2022 ona Windows Server 2022. I am doing everything according to Holmans Quick Start Guide and the installation goes through and shows no error.

After this I can start the Console but the Management Server never gets green and I get a lot of problems in the Event Logs where I can see that the MonitoringHost.exe is crashing. This is what is shown in the eventlog.

Faulting application name: MonitoringHost.exe, version: 10.22.10056.0, time stamp: 0x620207a1
Faulting module name: ntdll.dll, version: 10.0.20348.803, time stamp: 0xbee6f04c
Exception code: 0xc0000409
Fault offset: 0x00000000000a3cf6
Faulting process id: 0x18f0
Faulting application start time: 0x01d8f9d0dcdf6088
Faulting application path: C:\Program Files\Microsoft System Center\Operations Manager\Server\MonitoringHost.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 43650fe6-e7bc-42ef-98dc-f29263e23237
Faulting package full name:
Faulting package-relative application ID:


And in the Operations Manager log I get this


Doing the exact same installation on Windows Server 2019 everything is working as expected. I have tried with original Windows Server 2022 and a fully updated but still got the same problem.

Any suggestions on this?

Operations Manager
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.
1,275 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. SChalakov 9,551 Reputation points MVP

    Hey Magnus (@Magnus Sörensson ),

    I just remembered that I have seen this somehwre and looked for it. Strange enough other users are reportoing the exact same behavior in the comment section of Kevin's blog article:


    According to Kevin it might be a bug, although I have already a couple of Installations of SCOM 2022 omn WS 2022 and haven't encountered the issue yet. You can try Kevin's suggetstion and if you do not solve it you can open a case with Microsoft. If I am not mistaken they will grant you the case for free if it is really a bug.

    I hope I was able to help!


    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
    Stoyan Chalakov

    1 person found this answer helpful.
    0 comments No comments

  2. Magnus Sörensson 6 Reputation points

    Hi Stoyan (@SChalakov ),

    A bit update on this Issue.

    I have tried to troubleshoot this and also tried what Kevin suggested but with no luck. A bit background is that I am installing a new lab environment and have 2 Intel NUC. I had installed Windows Server 2022 on them and enabled Hyper-V. On that I installed new W2022 Servers and tried to install SCOM 2022 but run into the problem i described.

    Today I tried using the same ISO files installing SCOM 2022 on W2022 VM's in the same way in my old environment which is a W2019 Server with Hyper-V. To my surprise everything worked as expected.

    I then tried to reinstall one of Intel NUC with Windows 11, enabled Hyper-V and tried to do the installation again in the same way. But got the same errors again and a SCOM that is not working.

    So what i did then was to reinstall the Intel NUC with W2019 and then enabled Hyper-V. After that I installed SCOM 2022 on W2022 servers and everything worked as expected.

    What I suspect is that there is some thing in Hyper-V in Windows 11 and Windows 2022 that is not compatible with having a guest running SCOM.

    Is there anyone else out there which has tried installing W2022 and SCOM 2022 on top of W11/W2022 Hyper-V?

    Will try to do an upgrade of W2019 to W2022 and see if I get problems in SCOM afterwards.

    1 person found this answer helpful.
    0 comments No comments

  3. Gerben Plantinga 5 Reputation points

    We were able to get the agent work with disabling "Hardware-enforced Stack Protection" for the MonitoringHost.exe process. We achieved this via this Powershell command and the crashes were no longer observable:


    Set-ProcessMitigation -Name MonitoringHost.exe -Disable UserShadowStack

    Restart-Service -Name HealthService

    1 person found this answer helpful.
    0 comments No comments