{"id":34033,"date":"2024-05-27T13:07:53","date_gmt":"2024-05-27T11:07:53","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=34033"},"modified":"2024-05-27T14:38:42","modified_gmt":"2024-05-27T12:38:42","slug":"windows-server-2019-oob-update-kb5039705-fails-in-citrix-with-error-0x8007371b","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2024\/05\/27\/windows-server-2019-oob-update-kb5039705-fails-in-citrix-with-error-0x8007371b\/","title":{"rendered":"Windows Server 2019 OOB update KB5039705: Fails on Citrix with error 0x8007371B"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" title=\"Windows\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2021\/04\/Windows-klein.jpg\" alt=\"Windows\" width=\"200\" align=\"left\" \/>[<a href=\"https:\/\/www.borncity.com\/blog\/2024\/05\/27\/windows-server-2019-oob-update-kb5039705-citrix-fehler-0x8007371b\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]In mid-May 2024, Microsoft released the out-of-band update KB5039705 for Windows Server 2019, which is intended to correct the installation error 0x800f0982 of the security update KB5037765 from May 2024 on systems with a non-English language pack. However, administrators in a Citrix environment run into the problem that update KB5039705 fails with installation error 0x8007371b. However, there is a solution that can be used to try and resolve the problem.<\/p>\n<p><!--more--><\/p>\n<h2>Out-of-band update KB5039705<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg07.met.vgwort.de\/na\/2b523669e1ce42108a7ab4fbc423e081\" alt=\"\" width=\"1\" height=\"1\" \/>Cumulative update KB5037765, released on May 14, 2024, fails during installation on non-English-speaking Windows Server 2019 instances with error 0x800f0982. The reason for this was that the language pack en-us, which was required for installation, was missing. Systems that contained the language pack usually allowed the installation of update KB5037765. Microsoft then withdrew the security update from May 14, 2024.<\/p>\n<p>Microsoft then released the out-of-band update KB5039705 on May 23, 2024 to fix the above installation problem with the KB5037765 update to Windows Server 2019. However, this update caused further issues on some systems, and I wrote about this in the article <a href=\"https:\/\/borncity.com\/win\/2024\/05\/25\/windows-server-2019-install-errors-with-out-of-band-update-kb5039705-from-may-23-2024\/\">Windows Server 2019: Install errors with out-of-band update KB5039705 from May 23, 2024<\/a>.<\/p>\n<h2>Citrix: Update KB5039705 fails with 0x8007371B<\/h2>\n<p>As early as May 24, 2024, blog reader Horst reported in<a href=\"https:\/\/www.borncity.com\/blog\/2024\/05\/24\/windows-server-2019-out-of-band-update-kb5039705-verffentlicht-23-mai-2024\/#comment-182709\" target=\"_blank\" rel=\"noopener\"> this German comment<\/a> that the out-of-band update KB5039705 fails during installation in a Windows Server 2019 RDS environment with Citrix VDA 1912 and reports the installation error 0x8007371B. Other readers confirm this problem in the Citrix environment.<\/p>\n<p>Here in the blog there is <a href=\"https:\/\/borncity.com\/win\/2024\/05\/25\/windows-server-2019-install-errors-with-out-of-band-update-kb5039705-from-may-23-2024\/#comment-16988\">this comment<\/a> from a user who has the installation error 0x8007371b in connection with the RDS environment. He was able to find out that it depends on the installed RDS role. If he uninstalls the RDS role, he can install the update, but then the RDS role is no longer installed, the installation error 0x8007371B is also reported there.<\/p>\n<p>On reddit.com there is <a href=\"https:\/\/www.reddit.com\/r\/sysadmin\/comments\/1cu23nm\/comment\/l5iggaw\/\" target=\"_blank\" rel=\"noopener\">this thread<\/a> with corresponding confirmations of the error. Another source is <a href=\"https:\/\/learn.microsoft.com\/en-us\/answers\/questions\/1688015\/unable-to-install-patch-kb5039705-win-server-2019\" target=\"_blank\" rel=\"noopener\">this post<\/a> at Microsoft Q&amp;A.<\/p>\n<h2>A workaround for the error<\/h2>\n<p>German blog reader MOM20xx then posted <a href=\"https:\/\/www.borncity.com\/blog\/2024\/05\/24\/windows-server-2019-out-of-band-update-kb5039705-verffentlicht-23-mai-2024\/#comment-182765\" target=\"_blank\" rel=\"noopener\">this comment<\/a> (thanks for that). After analyzing the<em> cbs.log<\/em> file he found the clue to the cause of the installation error. There the error:<\/p>\n<p>STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE<\/p>\n<p>pointing to a file <em>edgehtmlpolicy.bin <\/em>that's port of the following component:<\/p>\n<p><em>amd64_microsoft-Windows-w..formplugins*<\/em><\/p>\n<p>that's missing in folder <em>C:\\Windows\\WinSxS<\/em>.<\/p>\n<p>The fix is to copy the folder of this component with version .1 from another \"good\" Windows Server 2019 to the folder C:\\Windows\\WinSxS of the failing system. Then set the permissions accordingly. In a further step, use the registry editor (requires administrative permissions) to navigate to the key:<\/p>\n<pre>HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\SideBySide\\Winners\\amd64_microsoft-Windows-w..formplugins*<\/pre>\n<p>Set the <em>default<\/em> value to version .1 and delete all other entries with higher version numbers. he installation should now go through on the next installation attempt. The source for this workaround can be found in the article <a href=\"https:\/\/michlstechblog.info\/blog\/windows-windows-update-error\/\" target=\"_blank\" rel=\"noopener\">Windows: Windows Update error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE<\/a> from Michls Tech Blog, although the article is from 2019.<\/p>\n<p>The exact package names that are to be copied and permitted via the registration entry may vary (this is probably indicated by the * in the above entry). Jiri Bergman has named a package with its full name in <a href=\"https:\/\/www.borncity.com\/blog\/2024\/05\/24\/windows-server-2019-out-of-band-update-kb5039705-verffentlicht-23-mai-2024\/#comment-182765\" target=\"_blank\" rel=\"noopener\">this comment<\/a>. Blog reader MOM20xx wrote that after the installation and a reboot, he ran a system repair for Windows Server 2019 using the following instructions.<\/p>\n<pre>DISM \/cleanup-image \/online \/scanhealth\r\nDISM \/cleanup-image \/online \/checkhealth\r\nDISM \/cleanup-image \/online \/analyzecomponentstore und\r\nDISM \/cleanup-image \/online\/startcomponentcleanup \/resetbase gemacht<\/pre>\n<p>However, there are now several confirmations that the repair approach has probably worked. Perhaps it will help.<\/p>\n<p><strong>Similar articles:<br \/>\n<\/strong><a href=\"https:\/\/borncity.com\/win\/2024\/05\/14\/microsoft-security-update-summary-may-14-2024\/\" target=\"_blank\" rel=\"noopener\">Microsoft Security Update Summary (May 14, 2024)<\/a><a href=\"https:\/\/www.borncity.com\/blog\/2024\/05\/14\/microsoft-security-update-summary-14-mai-2024\/\"><br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2024\/05\/15\/patchday-windows-10-updates-may-14-2024\/\">Patchday: Windows 10-Updates (May 14, 2024)<\/a><a href=\"https:\/\/www.borncity.com\/blog\/2024\/05\/14\/microsoft-security-update-summary-14-mai-2024\/\"><br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2024\/05\/15\/patchday-windows-11-server-2022-updates-may-14-2024\/\">Patchday: Windows 11\/Server 2022-Updates (May 14, 2024)<\/a><a href=\"https:\/\/www.borncity.com\/blog\/2024\/05\/14\/microsoft-security-update-summary-14-mai-2024\/\"><br \/>\n<\/a><a href=\"https:\/\/borncity.com\/win\/2024\/05\/16\/windows-server-2012-r2-and-windows-7-may-14-2024\/\">Windows Server 2012 \/ R2 and Windows 7 (May 14, 2024)<\/a><\/p>\n<p><a href=\"https:\/\/borncity.com\/win\/2024\/05\/15\/windows-server-2019-update-kb5036896-fails-with-error-0x800f0982\/\">Windows Server 2019: Update KB5037765 fails with error 0x800f0982<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2024\/05\/16\/windows-server-2019-update-kb5037765-install-error-0x800f0982-confirmed\/\">Windows Server 2019 Update KB5037765: Install error 0x800f0982 confirmed<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2024\/05\/20\/windows-server-2019-revised-update-kb5037765-with-wsus-detection-bug\/\" rel=\"bookmark\">Windows Server 2019: Revised update KB5037765 with WSUS detection bug?<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2024\/05\/24\/windows-server-2019-out-of-band-update-kb5039705-released-may-23-2024\/\" rel=\"bookmark\">Windows Server 2019: Out-of-Band-Update KB5039705 released (May 23, 2024)<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2024\/05\/25\/windows-server-2019-install-errors-with-out-of-band-update-kb5039705-from-may-23-2024\/\">Windows Server 2019: Install errors with out-of-band update KB5039705 from May 23, 2024<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]In mid-May 2024, Microsoft released the out-of-band update KB5039705 for Windows Server 2019, which is intended to correct the installation error 0x800f0982 of the security update KB5037765 from May 2024 on systems with a non-English language pack. However, administrators in &hellip; <a href=\"https:\/\/borncity.com\/win\/2024\/05\/27\/windows-server-2019-oob-update-kb5039705-fails-in-citrix-with-error-0x8007371b\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/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,194],"class_list":["post-34033","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-issue","tag-update","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34033","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=34033"}],"version-history":[{"count":4,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34033\/revisions"}],"predecessor-version":[{"id":34037,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34033\/revisions\/34037"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=34033"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=34033"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=34033"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}