Update KB5049981 Causes Event ID 7023 Error For Service Control Manager....System Guard Runtime Monitor Broker.exe terminated with Error %%3489660935

Anonymous
2025-01-14T23:56:45+00:00

Hello all. I am on Win10 Home Version 22H2  OS Build 19045.5371 on a HP Omen Desktop and a HP Envy Laptop. I noticed today upon checking my Event Viewer after installing patch Tuesday updates Cumulative Update for Windows 10 Version 22H2 for x64-based Systems KB5049981 and KB5050188 and also KB890830 I started seeing the below Event 7023 Service Control Manager....SgrmBroker.exe (System Guard Runtime Monitor Broker] Terminated with Error %%3489660935 after restarting my computer. I have run SFC and DISM and did not find any integrity violations. I am not seeing any other computer problems except this error. Tried to change the System Guard Runtime Monitor Broker Service but access is denied and remains on Delayed Start. I do not use Windows Defender but I use Norton 360 Select Plus on both computers. Is anyone else seeing this and is there a solution for this error. I have tried everything including the registry “HKEY_Local_MACHINE\SYSTEM\CurrentControlSet\Services” Start setting change from 3 to 4 but that causes a lot of Security SPP errors so I changed the value back and did a system restore that I had made before hand. It would appear the Update problem is with KB5049981. Microsoft this needs to be fixed as I feel the integrity of the Windows platform is at risk with this service not starting like it is suppose to do.

Respectfully,

Don

Log Name:      System

Source:        Service Control Manager

Date:          1/14/2025 3:48:16 PM

Event ID:      7023

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-

Description:

The System Guard Runtime Monitor Broker service terminated with the following error:

%%3489660935

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

    <EventID Qualifiers="49152">7023</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2025-01-14T20:48:16.2255419Z" />

    <EventRecordID>243885</EventRecordID>

    <Correlation />

    <Execution ProcessID="468" ThreadID="7164" />

    <Channel>System</Channel>

    <Computer>DESKTOP-             </Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">System Guard Runtime Monitor Broker</Data>

    <Data Name="param2">%%3489660935</Data>

    <Binary>5300670072006D00420072006F006B00650072000000</Binary>

  </EventData>

</Event>

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
lmacri 2,505 Reputation points
2025-02-05T12:08:24+00:00

... It's definitely unsettling, as the System Guard Runtime Monitor is an important security feature, particularly if the hardware doesn't support Secure Launch. It has to be a bug. I hope that Microsoft will prioritize fixing this.

Hi Jay G4:

User 0xb1a’s 20-Jan-2025 post <here> in this topic includes the contents of Microsoft bulletin WI982633 stating that Microsoft is aware of this bug and has marked the status as "Mitigated". From that bulletin:

"This service was originally created for Microsoft Defender, but it has not been a part of its operation for a very long time*. Although Windows updates released January 14, 2025 conflict with the initialization of this service, no impact to performance or functionality should be observed.*

There is no change to the security level of a device resulting from this issue. This service has already been disabled in other supported versions of Windows, and SgrmBroker.exe presently serves no purpose*.*

Note: There is no need to manually start this service or configure it in any way (doing so might trigger errors unnecessarily). Future Windows updates will adjust the components used by this service and SgrmBroker.exe. For this reason, please do not attempt to manually uninstall or remove this service or its components."

The "Known Issues" section of the release notes for KB5049981 (OS Build 19045.5371, released 14-Jan-2025 ) at https://support.microsoft.com/help/5049981 states that "We are working on a resolution and will provide an update in an upcoming release" so I'm hoping the February 2025 Patch Tuesday updates scheduled for 11-Feb-2025 will include a bug fix that stops these System Guard Runtime Monitor Broker service (SgrmBroker.exe) Event ID 7023 errors.

Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5371 * Firefox v135.0.0 * Microsoft Defender v4.18.24090.11-1.1.24090.11 * Malwarebytes Premium v5.2.5.158-1.0.5135 * Macrium Reflect Free v8.0.7783

Was this answer helpful?

10+ people found this answer helpful.
0 comments

82 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2025-01-19T21:51:28+00:00

    El mismo problema aquí. Desde el martes con este problema siempre al iniciar la pc.

    Me hago eco de DonTS y Mathew: cuanto más atención se preste a esto, más rápido se abordará la vulnerabilidad individual de nuestro sistema como usuarios finales.

    Respetuosamente

    Muchas gracias por su respuesta y espero que MS solucione esto.

    Respetuosamente,

    Don

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2025-01-20T04:54:38+00:00

    Your systems aren't vulnerable.

    I have never seen a Windows event log that is error free. Ever.

    Based on my experience in patching this appears to be one of those errors that doesn't cause any impact to the system and in a month or so will go away when they finally fix it in a future patch. In the meantime the best way to bring this to Microsoft's attention is to file a Windows feedback item.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2025-01-20T09:44:02+00:00

    I am not particularly happy to say this but it is established that AI would eventually replace programmers; MS's notwithstanding. In the next version of Windows, I would like so see MS using AI to help users make sense of and better configure events, tasks, etc in order to genuinely meet users' needs. I think that would make many users reaffirm their satisfaction with MS's services.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-01-20T10:14:42+00:00

    Microsoft informed some customers:

    Event Viewer displays an error for System Guard Runtime Monitor Broker service

    Status: Mitigated

    Affected platforms:

    OS Versions Message ID Originating KB Resolved KB
    Windows 10, version 22H2 WI982633 KB5049981 -
    Windows Server 2022 WI982632 KB5049983 -

    The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices which have installed Windows updates released January 14, 2025 (the Originating KBs listed above) or later.

    This error can be found underWindows Logs > System as Event 7023, with text similar to 'The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935'.

    This error is only observable if the Windows Event Viewer is monitored closely. It is otherwise silent and does not appear as a dialog box or notification.

    SgrmBroker.exe refers to the System Guard Runtime Monitor Broker Service.
    This service was originally created for Microsoft Defender, but it has not been a part of its operation for a very long time.
    Although Windows updates released January 14, 2025 conflict with the initialization of this service, no impact to performance or functionality should be observed.
    There is no change to the security level of a device resulting from this issue.
    This service has already been disabled in other supported versions of Windows, and SgrmBroker.exe presently serves no purpose.

    Note: There is no need to manually start this service or configure it in any way (doing so might trigger errors unnecessarily).
    Future Windows updates will adjust the components used by this service and SgrmBroker.exe.
    For this reason,please do not attempt to manually uninstall or remove this service or its components.

    Workaround:

    No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer.
    To do so, you can follow these steps:

    1) Open a Command Prompt window. This can be accomplished by opening the Start menu and typing 'cmd'.
    The results will include "Command Prompt" as a System application. Select the arrow to the right of "Command Prompt" and select "Run as administrator".

    2) Once the window is open, carefully enter the following text:

        sc.exe config sgrmagent start=disabled

    3) A message may appear afterwards. Next, enter the following text:

        reg add HKLM\System\CurrentControlSet\Services\SgrmBroker /v Start /d 4 /t REG_DWORD

    4) Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up.

    Note that some of these steps might be restricted by group policy set by your organization.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments