{"id":34808,"date":"2024-08-16T00:01:40","date_gmt":"2024-08-15T22:01:40","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=34808"},"modified":"2024-08-16T14:21:28","modified_gmt":"2024-08-16T12:21:28","slug":"windows-server-2019-windows-10-enterprise-2019-ltsc-issues-with-update-kb5041578","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2024\/08\/16\/windows-server-2019-windows-10-enterprise-2019-ltsc-issues-with-update-kb5041578\/","title":{"rendered":"Windows Server 2019\/Windows 10 Enterprise 2019 LTSC: Performance Issues with Update KB5041578"},"content":{"rendered":"

\"Windows\"[German<\/a>]The cumulative update KB5041578 for Windows 10 Enterprise 2019 LTSC and Windows Server 2019 was released on August 13, 2024 (second Tuesday of the month, patch day at Microsoft). In the meantime, I have received reports from readers about serious problems with the update. From slow systems to black screens, various error patterns are reported. Here is a brief overview of this topic and a possible workaround.<\/p>\n

<\/p>\n

Windows Update KB5041578<\/h2>\n

\"\"Cumulative Update KB5041578<\/a> is only available for Windows 10 2019 Enterprise LTSC and Windows 10 2019 IoT Enterprise LTSC as well as Windows Server 2019 (Patchday: Windows 10\/Server Updates (August 13, 2024)<\/a>). The update contains a number of bug fixes, which are listed in the support article. Among other things, the Bitlocker problem from the July 2024 update is fixed. And various hardening measures for Windows are activated.\"\"<\/p>\n

Due to the Windows TCP\/IP Remote Code Execution vulnerability\u00a0CVE-2024-38063<\/a><\/u>, which is classified as critical (CVEv3 Score 9.8), see Microsoft Security Update Summary (August 13, 2024)<\/a>, the update should be installed promptly. The critical RCE vulnerability in Windows TCP\/IP is classified as \"Exploitation More Likely\". An attacker can exploit this vulnerability remotely by sending specially crafted IPv6 packets to a host. Microsoft recommends disabling IPv6, as only IPv6 packets can be abused to exploit this vulnerability.<\/p>\n

Performance issues with the KB5041578 update<\/h2>\n

Cumulative Update KB5041578<\/a> seems to cause problems with Windows 10 as well as Windows Server 2019 in certain constellations.<\/p>\n

Report 1: Windows 10 Enterprise 2019 LTSC<\/h3>\n

German blog reader Arthur contacted me by email because he has run into massive problems with the KB5041578 update on Windows 10 2019 Enterprise LTSC systems in his environment. He writes that the devices take ages to log on after the update. The desktop then remains black for several minutes. Once the desktop is loaded, the system runs so slowly that affected devices cannot be used. Remote Powershell also does not work in this state.<\/p>\n

According to the reader, it is mainly legacy BIOS devices that are affected in his environment. However, he writes that some UEFI computers are also affected. If the update is uninstalled, everything returns to normal, writes the reader. As soon as the update is reinstalled, the error pattern returns. He asks whether the problem is known in the community, as he couldn't find anything about it online? I myself can't find anything like this on my Windows 10 2019 IoT Enterprise LTSC system, the system runs as it did before the update.<\/p>\n

Report 2: Windows Server 2019<\/h3>\n

Addendum:<\/strong> German blog reader Michael has contacted me now by e-mail, because update KB5041578 caused serious issues on 3 servers. The [Windows Server 2019] machines ran extreme slowly after the update installation because the systems were busy. What he found worst of all was the fact that the remote desktop no longer worked or only responded very, very slowly. Remote working was no longer possible. He then used PowerShell to uninstall the updates, which he said took hours.<\/p>\n

Report 3: Windows Server 2019<\/h3>\n

In the meantime, comments have been left in the German blog on the article Patchday: Windows 10\/Server-Updates (13. August 2024)<\/a>, that report something similar. Hary writes in this German comment<\/a> that he ran into the problem that after the update to Windows Server 2029, the RDP connection only showed a black screen.<\/p>\n

After about an hour, an desktop image did appear on the remote desktop. However, the system and the connection responded extremely slowly and no interaction was possible. Not even the task manager could be opened, and the administrator only has access to the system via RDP. The error details sounds like the description above.<\/p>\n

Another confirmation and a workaround<\/h2>\n

In this German comment<\/a> Hary specifies this error description. Another reader points to this reddit.com thread<\/a>, where the error pattern (some lagging servers 2019) is also described.<\/p>\n

kb5041578 is causing us issues on a few 2019 servers (but not all) , when installed it causes lagging and apps are unresponsive at times. Once uninstalled everything returns to normal. Does anyone have any ideas on what might be going on? We haven't been able to identify a pattern to this issue.<\/p><\/blockquote>\n

What I recognized: It doesn't affect all users of Windows Server 2019 or Windows 10 2019 Enterprise LTSC and Windows 10 2019 IoT Enterprise LTSC.<\/p>\n

Solution Empty catroot2 folder?<\/h3>\n

But there may be an explanation and a fix. A user responds that deleting the contents of the folder:<\/p>\n

C:\\Windows\\System32\\catroot2<\/p>\n

seems to fix this problem in his environment. According to the user, deleting the contents of the folder before patching does not seem to cause the problem at all. However, I have not been able to test this – as I am not affected myself. But I got now confirmation, that this works (see also the comment below).<\/p>\n

What could be the root cause?<\/h3>\n

The interesting question is why it affects servers and clients for some people, but not others. In the Reddit.com thread linked above, I may have found the root cause. The person affected was asked on Reddit how he came up with the above solution.<\/p>\n

The affected person noticed a high CPU utilization by the encryption services on all affected computers. He states that something was quickly writing and deleting logs in catroot2. After that, he simply googled for possible causes and solutions.<\/p>\n

Another user notes that some systems stop the cryptographic service, getting stuck in the stop-pending phase for several minutes. Then the log files are searched and the system calms down. Then the cryptographic service runs again.\u00a0However, the log files in System32\\catroot2 are recreated every 2 minutes on problematic systems.<\/p>\n

Perhaps it will help those affected. Thanks to Arthur and the other blog readers for the tips and also for the feedback below.<\/p>\n

Similar articles:<\/strong>
\n<\/strong>Microsoft Security Update Summary (August 13, 2024)<\/a>
\nPatchday: Windows 10\/Server Updates (August 13, 2024)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]The cumulative update KB5041578 for Windows 10 Enterprise 2019 LTSC and Windows Server 2019 was released on August 13, 2024 (second Tuesday of the month, patch day at Microsoft). In the meantime, I have received reports from readers about serious … 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,580,22,2],"tags":[47,2872,69,195,194],"class_list":["post-34808","post","type-post","status-publish","format-standard","hentry","category-issue","category-security","category-update","category-windows","tag-issue","tag-patchday-8-2024","tag-security","tag-update","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34808","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=34808"}],"version-history":[{"count":8,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34808\/revisions"}],"predecessor-version":[{"id":34819,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34808\/revisions\/34819"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=34808"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=34808"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=34808"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}