{"id":36878,"date":"2025-01-16T23:15:28","date_gmt":"2025-01-16T22:15:28","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=36878"},"modified":"2025-01-17T10:32:43","modified_gmt":"2025-01-17T09:32:43","slug":"windows-10-server-2022-sgrmbroker-service-no-longer-starts-after-jan-2025-update-kb5049981","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2025\/01\/16\/windows-10-server-2022-sgrmbroker-service-no-longer-starts-after-jan-2025-update-kb5049981\/","title":{"rendered":"Windows 10\/Server 2022: SgrmBroker service no longer starts after Jan. 2025 update (KB5049981)"},"content":{"rendered":"

\"Windows\"[German<\/a>]Microsoft has distributed the security update KB5049981 for Windows 10 21H2-22H2 for the January 2025 Patchday (14.1.2025). After installing this update, administrators notice that the SgrmBroker<\/em> service (broker for runtime monitoring of system monitoring) no longer starts. Administrators also notice the same behavior under Windows Server 2022. I will summarize the information I have in this regard.<\/p>\n

<\/p>\n

Windows 10 Update KB5049981<\/h2>\n

\"\"Cumulative Update KB5049981<\/a> is available for Windows 10 version 21H2 (Enterprise and Education) and all Windows 10 22H2 variants. The update contains security fixes and updates the Windows Kernel Vulnerable Driver Blocklist file (DriverSiPolicy.p7b). I had reported in the blog post Patchday: Windows 10\/11 Updates (January 14, 2025)<\/a>.<\/p>\n

SgrmBroker service no longer starts<\/h2>\n

German blog reader armin<\/em> has responded promptly with this comment<\/a> and writes that after installing the January 2025 security updates, the SgrmBroker<\/em> service (broker for runtime monitoring of system monitoring) no longer starts.<\/p>\n

The name System Guard Runtime Monitor<\/em> indicates that the service is part of System Guard and the exploit protection of Defender. You can find more information in this article<\/a> and here<\/a>. And here<\/a> is also an analysis of the feature, that hasn't been updated for y yars.The reader writes in his comment that in the folder:<\/p>\n

C:\\WINDOWS\\system32\\<\/p>\n

four files with the corresponding name have the date of the update installation from timestamps. After uninstalling the January 2025 update, the problem was resolved.<\/p>\n

The reader has previously observed this behavior with some Windows 10 clients (update KB5049981<\/a>) and Windows Server 2022 (update \u00a0KB5049983<\/a>) in virtual machines (VMs), where the VMs were running under Hyper-V.<\/p>\n

This observation by the blog reader was confirmed by other blog readers. Bolko writes that the error code 0x80070005 (access denied) is thrown. This means that the service can no longer monitor the integrity of Windows – Microsoft has shot itself down.<\/p>\n

Post on Microsoft Answers<\/h2>\n

On Microsoft Answers there is the thread Error 7023 Service Control Manager….System Guard Runtime Monitor Broker.exe terminated<\/a>, in which an affected person also confirms the problem as of January 15, 2025. Affected are a HP Omen Desktop and a HP Envy Laptop with Windows 10 22H2.<\/p>\n

Since installing the January 2025 update KB5049981, the System Guard Runtime Monitor Broker service (SgrmBroker.exe) no longer starts. Event 7023 is displayed in the Event Viewer with the following data:<\/p>\n

Log Name:      System\r\nSource:        Service Control Manager\r\nDate:          1\/14\/2025 3:48:16 PM\r\nEvent ID:      7023\r\nTask Category: None\r\nLevel:         Error\r\nKeywords:      Classic\r\nUser:          N\/A\r\nComputer:      DESKTOP-\r\nDescription:\r\n\r\nThe System Guard Runtime Monitor Broker service terminated with the following error:\r\n\r\n%%3489660935\r\n\r\nEvent Xml:\r\n<Event xmlns=\"http:\/\/schemas.microsoft.com\/win\/2004\/08\/events\/event\">\r\n <System>\r\n\u00a0 <Provider Name=\"Service Control Manager\" Guid=\"{555908d1-a6d7-4695-8e1e-26931d2012f4}\" EventSourceName=\"Service Control Manager\" \/>\r\n<EventID Qualifiers=\"49152\">7023<\/EventID>\r\n\u00a0\u00a0 <Version>0<\/Version>\r\n\u00a0\u00a0\u00a0 <Level>2<\/Level>\r\n\u00a0\u00a0\u00a0 <Task>0<\/Task>\r\n\u00a0 <Opcode>0<\/Opcode>\r\n[...}<\/pre>\n
Another affected person confirms this problem for Windows 10 and an administrator has posted the following screenshot from Windows Server 2022 online.<\/p>\n
\"System<\/p>\n
On reddit.com, the problem with the broken service is also confirmed in this thread<\/a> and in this thread<\/a>. It doesn't have such a direct impact if the service is no longer running – Windows can simply no longer determine its own integrity. Let's see when Microsoft will comment on this.<\/p>\n
Similar articles<\/strong>
\nMicrosoft Security Update Summary (January 14, 2025)<\/a>
\nPatchday: Windows 10\/11 Updates (January 14, 2025)<\/a>
\nPatchday: Windows Server Updates (January 14, 2025)<\/a>
\nPatchday: Microsoft Office Updates (January 2025)<\/a><\/p>\n
Review: Windows Patchday issues January 2025<\/a>
\nWindows 10\/Server 2022: SgrmBroker service no longer starts after Jan. 2025 update (KB5049981)<\/a>
\nAttention: Problems with Windows January 2025 updates and Citrix environments (session recordings)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
[German]Microsoft has distributed the security update KB5049981 for Windows 10 21H2-22H2 for the January 2025 Patchday (14.1.2025). After installing this update, administrators notice that the SgrmBroker service (broker for runtime monitoring of system monitoring) no longer starts. Administrators also notice … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,2],"tags":[166,2890,195,194],"class_list":["post-36878","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-issues","tag-patchday-1-2025","tag-update","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36878","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=36878"}],"version-history":[{"count":6,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36878\/revisions"}],"predecessor-version":[{"id":36897,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/36878\/revisions\/36897"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=36878"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=36878"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=36878"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}