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: Most helpful
Most helpful Newest Oldest
  1. lmacri 2,505 Reputation points
    2025-04-23T13:30:49+00:00

    To the OP DonT5 and other Win 10 user affected by this bug:

    See Susan Bradley's 23-Apr-2025 announcement Windows 10 finally gets fix in the AskWoody forum.

    A Preview (BETA) update for Win 10 is now available that should fix our System Guard Runtime Monitor Broker service (SgrmBroker.exe) Event ID 7023 errors, but I'm going to wait for the next stable monthly cumulative Quality Update to be released with the May 2025 Patch Tuesday updates on 13-May-2025 since this bug doesn't appear to cause any noticeable problems on my system.

    Kudos to Susan for posting about the bug fix.

    Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5737 * Firefox v137.0.2 * Microsoft Defender v4.18.25030.2-1.1.25030.1 * Malwarebytes Premium v5.2.11.183-131.0.5227 * Macrium Reflect Free v8.0.7783

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2025-01-19T19:04:41+00:00

    DonTS,

    Thank you for the good work shining a light on this. This issue happened to me while my computer was idle as I turned on my computer and went about some morning house keeping agenda items. I was about to simply write off the PC restarting, but seeing windows performing a "Cleaning" upon restart made me suspicious. I'm glad I investigated; it led me to your thread. I have also opened a feedback report.

    I encourage everyone to do the same. Simply press windows+F and you can open a ticket after creating a title and a general description of the failure.

    I echo DonTS, the more attention on this the quicker our individual system vulnerability as end-users will be addressed.

    You are very welcome Matthew and the more light that is shone on this problem the quicker it will be taken care of.....I hope, as I remember last January's Patch Tuesday security update dealing with the partition that so many users had problems with. There are several posts over in the Windows 10 Forum as well about this error as well and users here are having problems installing this update. Thank you for submitting your feedback report. If I hear anything from MS about this error I will let you and others know. Thank you again.

    Respectfully,

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2025-01-16T12:03:00+00:00

    This service is by default set to Automatic (Trigger Start) in Windows Server.

    Was this answer helpful?

    0 comments