System Guard service error still won’t be fixed

Topic

New Reply

When the preview releases come out at the end of the month, they are a clue of nonsecurity fixes that will be included in the following month’s securi
[See the full post at: System Guard service error still won’t be fixed]

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

CAS, lmacri, Alex5723

Reply | Quote

Replies

..but USB printers bug, will

Microsoft confirms KB5053657 fixes USB printers broken by Windows 11 KB5050092

..Resolution:

This issue was resolved by Windows updates released March 25, 2025 (KB5053657), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.

If you have an enterprise-managed device and have installed the update released March 25, 2025 (KB5053657) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue…

Reply | Quote

Perhaps we’re better off if they continue to slow walk a fix for the System Guard service event log problem.  The negative consequences of a botched patch probably outweigh the benefit of a fix to a cosmetic issue.  I have no doubt that there are more significant issues to which MS should devote whatever resources are allocated to Win10 maintenance.

The sloppiness is annoying, but IMHO cosmetic issues are the least of Microsoft’s problems.

 

 

Reply | Quote

This fix is clearly on a slow boat. Identified in January, not yet fixed, and no sign of it for April.

Hi Susan:

The good news is that I only see these harmless System Guard Runtime Monitor Broker service (SgrmBroker.exe) Event ID 7023 errors when I boot up in the morning or restart Windows.

Don’t forget the DeviceSetupManager Event ID 131 errors that were discussed in Tex265’s 18-Dec-2023 Event Viewer Metadata Entries – 131 & 201 due to Microsoft Registry Error as well as your own 06-Sep-2024 topic New Windows 11, lots of Events 131. I still see dozens of these Event ID 131 logged every day in my Event Viewer at Applications and Services Logs | Microsoft | Windows | DeviceSetupManager | Admin (see attached image). I didn’t bother to apply the workaround I posted 06-Sep-2024 in post # 2701956 of your topic since these errors don’t seem to impact my system performance, but affected users have been waiting for Microsoft to release a bug fix for over a year now.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.5608 * Firefox v136.0.3 * Microsoft Defender v4.18.25010.11-1.1.25020.1007 * Malwarebytes Premium v5.2.9.176-129.0.5196 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

EricB

Reply | Quote

More event log detritus to be ignored.

Reply | Quote

According to Susan’s post #2741096 in the System Guard runtime broker service Error… thread, info she obtained directly from an “official” Microsoft source indicates…

Susan Bradley wrote:

This service has already been disabled in other supported versions of Windows, and SgrmBroker.exe presently serves no purpose.

The same post includes instructions for a workaround (disabling SgrmBroker.exe) to prevent the related error from appearing in the Event Viewer on subsequent device start up.

I did this on my own system back in late January when I saw her post and the errors did stop and there’s be absolutely no apparent adverse effects on my OS!

Reply | Quote