{"id":32881,"date":"2024-01-18T19:37:29","date_gmt":"2024-01-18T18:37:29","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=32881"},"modified":"2024-10-01T15:26:49","modified_gmt":"2024-10-01T13:26:49","slug":"windows-server-2022-update-kb5034129-kills-browser-chrome-edge-firefox","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2024\/01\/18\/windows-server-2022-update-kb5034129-kills-browser-chrome-edge-firefox\/","title":{"rendered":"Windows Server 2022: Update KB5034129 kills Browser (Chrome, Edge, Firefox)"},"content":{"rendered":"

\"Windows\"[German<\/a>]I got reports from some administrators of Windows Server 2022. After they have installed the KB5034129 update from January 9, 2024 on this OS platform may no longer be able to use a browser. This actually affects all known browsers such as Google Chrome, Microsoft Edge or Firefox. The browsers crash with a white screen when the security update is installed and can no longer be used. However, there is a workaround, which has also been discussed by administrators in comments on the blog. And I got a report, that Windows 10 22H2 may also be affected. I will summarize the situation below.<\/p>\n

<\/p>\n

Windows Server 2022 Update KB5034129<\/h2>\n

\"\"For Windows Server 2022, cumulative update KB5034129<\/a> was released on January 9, 2024 (mentioned in the blog post Patchday: Windows 11\/Server 2022 Updates (January 9, 2024)<\/a>). The linked support article contains a long list of bugs that Microsoft claims to have fixed with this update. It is also a security update that addresses a number of vulnerabilities.<\/p>\n

Browser crashes after update installation<\/h2>\n

I had only vaguely noticed it so far from comments within my German blog. But German blog reader 1ST1 pointed out the problem to me in this comment<\/a> (thanks for that).<\/p>\n

Reports I received within my blog<\/h3>\n

The issue has already been addressed by administrators within my German blog post Patchday: Windows 11\/Server 2022-Updates (9. Januar 2024)<\/a>. In the German comment here<\/a>, Thomas reports problems on a Windows Server 2022 that provides remote apps. The reader observed an extremely high CPU load due to the .NET Framework Optimization Service.<\/p>\n

But even more serious is the observation that the Edge no longer starts. Only a white screen is displayed. After uninstalling KB5034272 and KB5034129, it runs normally again Thomas supposed that KB5034272<\/a> (January 9, 2024-KB5034272 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Azure Stack HCI, Version 22H2) is the culprit.<\/p>\n

Kai-Uwe Dziala then confirms the crash problem with a white browser screen for Microsoft Edge and Google Chrome in this comment<\/a>. He states that uninstalling the Windows Server 2022 security update KB5034129<\/a> fixed the issue with the browser. Further confirmations from Frank Seidel<\/a>, Stefan<\/a> and other affected persons are now available as comments. And I read somewhere, that also Firefox has this issue<\/a>.<\/p>\n

Affects only Upgrades?<\/h3>\n

According to the comments I received for my German blog post, only Windows Server 2022 instances that have been upgraded to this OS version via (inplace) upgrade seem to be affected.<\/p>\n

Also Windows 10 Disk2VHD VMs affected<\/h3>\n

In addition, Julian Mooren contacted me on X and wrote<\/a> that he had also noticed this in a customer environment on Windows 10 22H2. This is reproducible from 2023-12 CU and higher (i.e. since the December 2023 update). The search service is also corrupt.<\/p>\n

However, the issue mentioned by Mooren only occurs as soon as a virtual machine is moved from a physical system to a VHD image using a tool such as Disk2VHD. The use case is the creation of a golden image for a VDI environment. The master VM is not affected by this at any time, he writes. Mooren has been opening a support case with Microsoft for over two weeks, but has not yet received any reasonable feedback.<\/p>\n

A workaround for the problem<\/h2>\n

In this German comment<\/a>, Kai-Uwe Dziala describes a workaround to bring the browsers (Edge and Chrome) back to life. To fix the crashes with white screens, delete the following entries in the Windows Server 2022 registry:<\/p>\n

HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File Execution Options\\chrome.exe\r\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File Execution Options\\msedge.exe\r\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Image File Execution Options\\msedgewebview2.exe<\/pre>\n
The entries above are the cumulative information from several comments. In this comment, Michael Bl\u00f6chinger then pointed to this Google Support post, where this information can also be found. Deleting the entries for the Image File Execution options seems to fix the crash problem. If Firefox is affected, simply check whether there is also an entry for the browser in the above registry branch and delete it.<\/p>\n
Similar articles:
\n<\/strong>Office update KB5002500 from January 2, 2023 fixes OneNote 2016 sync problem<\/a>
\nMicrosoft Security Update Summary (January 9, 2024)<\/a>
\nPatchday: Windows 10 Updates (January 9, 2024)<\/a>
\nPatchday: Windows 11\/Server 2022 Updates (January 9, 2024)<\/a>
\nWindows 7\/Server 2008 R2; Server 2012 R2: Updates (January 9, 2024)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
[German]I got reports from some administrators of Windows Server 2022. After they have installed the KB5034129 update from January 9, 2024 on this OS platform may no longer be able to use a browser. This actually affects all known browsers … 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":[47,195,2680],"class_list":["post-32881","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-issue","tag-update","tag-windows-server-2022"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/32881","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=32881"}],"version-history":[{"count":3,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/32881\/revisions"}],"predecessor-version":[{"id":38229,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/32881\/revisions\/38229"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=32881"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=32881"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=32881"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}