Win 10 System Guard Runtime Monitor Broker service

If you use Windows Defender and started seeing error messages in Windows Event Viewer after the Jan-14-25 Win 10 updates about System Guard Runtime Monitor Broker service, either terminating unexpectedly or failing to start, Microsoft says you can ignore them.

Supposedly that service was used by Microsoft Defender but has long since ceased to be part of the active Defender components.  This service was disabled in other supported versions of Windows, and SgrmBroker.exe currently serves no purpose in Win 10.  

So why didn't they disable this service in Win 10 too?  And unfortunately, services.msc doesn't allow me to set System Windows Guard's Startup type to disabled so it won't try to load and stop throwing errors....

FWIW, I'm also seeing Error 29:  Windows failed fast startup with error status 0xC00000D4 since the last Win 10 updates too.   Still looking for explanations and fixes for this one...

And they wonder why everyone hates Microsoft...