The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935 how to fix

Question

i dont know how to fix it and i think its why my pc is crashing

Answer 1

Dear silent pilot

Thank you for posting in the Microsoft community.

This issue appears in some Windows 10 (KB5049981) and Windows Server 2022 (KB5049983) virtual machines (Hyper-V environments) and is accompanied by the error code 0x80070005 (Access Denied).

The SgrmBroker service was originally developed for Microsoft Defender, but has long since ceased to be its active component.

While the January 14, 2024 update conflicts with its initialization, it does not affect system performance or functionality, nor does it change device security levels.

This service has been disabled in other versions of Windows and has no real effect at this time.

You do not need to manually start or configure this service, and future Windows updates will adjust the relevant components without uninstalling or removing the service and its components. To avoid recurring error messages, you can safely disable the service:

Press WIN+S and type CMD - Run Command Prompt as administrator.

sc.exe config sgrmagent start=disabled

Subsequently enter the command:

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

Close the Command Prompt window.

Restart the computer.

Disclaimer: Modifying the registry or workgroups is usually geared towards advanced users, administrators, and IT professionals, and it can help fix some problems, however, improper registry modifications can cause serious problems. Therefore, please make sure to strictly follow the steps below. For further protection, make a backup of the registry before modifying it. For more information on how to backup and restore the registry ref:

 How to back up and restore the registry in Windows - Microsoft Support

I hope the above information helps and look forward to your good news.

Best Wish

Shawn.Z-MSFT | Microsoft Community Support Specialist

Answer 2

Further to my comments above, I just looked at event viewer, and there is a new message re this.

Persistent, isn't it?

Guess I will just have to ignore it, and hope it will eventually go away with the next update.

Answer 3

Dear KennethStarick

I'm glad to hear from you,

Windows will be fixing this configuration error in a security update in the future, and as mentioned above, this is just a display error with no real functional impact on the end user.

Best Wish

Shawn.Z-MSFT | Microsoft Community Support Specialist

Answer 4

Thanks for the honest answer. I have secure boot and hypervisor enforced code integrity but apparently my hardware doesn't support secure launch. The system guard runtime monitor seemed like a good thing for those of us with older but still otherwise good machines that lack some of the newer security features.

Answer 5

Tried your first suggestion, and it seemed to go through successfully.

Re-booted PC and checked events,

Error message as per screen shot.

Still a problem, or do I ignore?