Microsoft Acknowledges Bug in Latest Windows 10 Update but Says It’s Nothing to Worry About

On January 14, 2025, Microsoft rolled out its latest security updates for Windows 10 and 11. Like clockwork, these updates arrived with a list of known bugs, which often expands as users and Microsoft uncover new issues. This time, a bug in Windows 10 has caught some attention, but Microsoft assures users there’s no need for concern.

In its updated support document, Microsoft acknowledges an error related to SgrmBroker.exe that shows up in the Windows Event Viewer. The error reads:

“The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935.”

At first glance, this might sound alarming, but Microsoft explains that the bug is purely cosmetic. Here’s why you don’t need to worry:

• The error is only visible in the Event Viewer, so unless you’re closely monitoring it, you won’t even notice.
• There’s no impact on your system’s performance, functionality, or security.

What is SgrmBroker.exe?

 SgrmBroker.exe refers to the System Guard Runtime Monitor Broker Service. This service was originally part of Microsoft Defender but hasn’t been active in its operation for quite some time. According to Microsoft, the conflict introduced in the January 14 update affects the initialization of this service, but since it’s no longer functional, it doesn’t pose any issues. In fact, this service has already been disabled in other supported versions of Windows and currently serves no purpose.

How to Fix the Error

 If seeing the error in the Event Viewer bothers you, you can disable the System Guard Runtime Monitor Broker Service manually. Here’s how:

1. Open the Command Prompt as an administrator. (Search for “cmd” in the Start menu, then select “Run as administrator.”)
2. Enter the following command:
3. sc.exe config sgrmagent start=disabled
4. After the confirmation message, enter this second command:
5. reg add HKLM\System\CurrentControlSet\Services\SgrmBroker /v Start /d 4 /t REG_DWORD
6. Close the Command Prompt, and the error will no longer appear.

7. Microsoft has also said that a future update will resolve this issue permanently.

   Other Issues in January 2025 Updates

8. While this particular bug is harmless, other issues in the January security updates may be more problematic. For instance, there are compatibility issues with certain Citrix software, causing errors when installing the latest Patch Tuesday update.

   So, rest easy—this SgrmBroker.exe error might look serious, but it’s nothing to lose sleep over.