{"id":26112,"date":"2022-08-09T00:04:00","date_gmt":"2022-08-08T22:04:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=26112"},"modified":"2022-08-08T15:36:05","modified_gmt":"2022-08-08T13:36:05","slug":"windows-server-2019-update-kb5015811-verursacht-performance-probleme","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/08\/09\/windows-server-2019-update-kb5015811-verursacht-performance-probleme\/","title":{"rendered":"Windows Server 2019: Update KB5015811 causes (performance) problems"},"content":{"rendered":"

\"Windows\"[German<\/a>]In advance of the August 2022 patchday on 8\/9\/2022, another quick note for administrators responsible for Windows Server 2019 (or LTSC versions of Windows 10 Enterprise 1909). There is still little on the internet – but feedback in my blogs suggests that the July 12, 2022 security update KB5015811 is responsible for various issues with Exchange, SCCM and with PowerShell scripts. <\/p>\n

<\/p>\n

Windows Update KB5015811<\/h2>\n

\"\"Cumulative update KB5015811<\/a> was released by Microsoft on July 12, 2022 for Windows 10 Enterprise 2019 LTSC as well as Windows Server 2019. The patch addressed security vulnerabilities and fixed a PowerShell issue. Microsoft has not released a lot of information about this update (see also Patchday: Windows 10-Updates (July 12 2022)<\/a>). Those interested in the details of the fixes are more likely to find answers in the cumulative preview update KB5014669. This is because a number of problems have been patched. <\/p>\n

Issues reported with update KB5015811<\/h2>\n

I had asked in the blog post Is Windows Update KB5015811 causing Exchange performance issues?<\/a>  whether the observations of blog reader Wolfgang P. can be confirmed. Wolfgang wrote:<\/p>\n

\n

My Exchange 2019 DAG suffered a massive performance loss after installing KB5015811. Forwarding mails of e.g. 3 MB size was acknowledged with a pop-up \"Outlook is trying to retrieve data from the server\". The process was then completed successfully, but took about 3 minutes.<\/p>\n<\/blockquote>\n

He only got out of this problem by uninstalling the security update. In the German comment here<\/a>, this is confirmed by a second Exchange administrator. There were other comments on the blog post with problem reports, with this German comment<\/a> being interesting:<\/p>\n

\n

We have massive issues with KB5015811 here on servers running a lot of powershell scripts. Just today a monitoring server went to the limit and produced full CPU load with Powershell.<\/p>\n

After uninstalling the KB everything runs normal again. Not exactly related to Exchange, but in any case I see a connection with Powershell which is also relevant in Exchange.<\/p>\n<\/blockquote>\n

This indicates, that something is consuming up performance due to the fixes in the security update. In the English blog post Is Windows Update KB5015811 causing Exchange performance issues?<\/a>  is also this comment<\/a>: <\/p>\n

\n

We have also facing the issues with WMI connection in SCCM server windows 2019 server. <\/p>\n

After uninstall it worked, <\/p>\n

Do any one knows why it happening with this KB ?<\/p>\n<\/blockquote>\n

So another problem, though I haven't found a second message about this bug yet. Maybe just keep an eye on it around August patchday. <\/p>\n

Similar articles:
<\/strong>Patchday: Windows 10-Updates (July 12, 2022) <\/a>
Microsoft July 2022 Patchday issues (Windows, Office)<\/a>
Is Windows Update KB5015811 causing Exchange performance issues?<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]In advance of the August 2022 patchday on 8\/9\/2022, another quick note for administrators responsible for Windows Server 2019 (or LTSC versions of Windows 10 Enterprise 1909). There is still little on the internet – but feedback in my blogs … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22],"tags":[166,195,159],"class_list":["post-26112","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","tag-issues","tag-update","tag-windows-server"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/26112","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=26112"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/26112\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=26112"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=26112"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=26112"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}