{"id":268848,"date":"2022-06-24T11:52:40","date_gmt":"2022-06-24T09:52:40","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=268848"},"modified":"2022-07-06T10:59:19","modified_gmt":"2022-07-06T08:59:19","slug":"microsoft-defender-update-kb4052623-version-4-18-2205-7-liefert-fehler-0x80070643","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2022\/06\/24\/microsoft-defender-update-kb4052623-version-4-18-2205-7-liefert-fehler-0x80070643\/","title":{"rendered":"Microsoft Defender-Update KB4052623 (Version 4.18.2205.7) liefert Fehler 0x80070643"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" title=\"Windows\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2021\/04\/Windows-klein.jpg\" alt=\"Windows\" width=\"200\" align=\"left\" \/>Blog-Leser J.E. hat mich gerade per Mail kontaktiert. Auf seinen 2016er und 2019er Hyper-V Core Servern l\u00e4sst sich das Update f\u00fcr Microsoft Defender Antivirus-Antischadsoftwareplattform \u2013 KB4052623 (Version 4.18.2205.7) vom 22.06.2022 nicht installieren. Die Installation bricht immer mit dem Fehler 0x80070643 ab.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg04.met.vgwort.de\/na\/f822cf96df674031ab6e4aa3959a9676\" alt=\"\" width=\"1\" height=\"1\" \/>Jen hat die Installation per WSUS als auch per Installer mit einem Download aus dem Microsoft Update Katalog versucht. Kurze Frage in die Runde: Hat noch jemand dieses Problem? Gibt eine <a href=\"https:\/\/twitter.com\/Tekkie_Boy\/status\/1540283370080555009\" target=\"_blank\" rel=\"noopener\">R\u00fcckmeldung auf Twitter<\/a>, dass es mit Windows 10 S zu tun haben k\u00f6nnte.<\/p>\n<h2>Erg\u00e4nzung Juli 2022<\/h2>\n<p>Seit dem 4. Juli 2022 scheint das Thema nun auch andernorts hochzukochen. Blog-Leser Niels weist ja in <a href=\"https:\/\/borncity.com\/blog\/2022\/06\/24\/microsoft-defender-update-kb4052623-version-4-18-2205-7-liefert-fehler-0x80070643\/#comment-128486\">diesem Kommentar<\/a> auf den Spiceworks-Beitrag\u00a0<a href=\"https:\/\/community.spiceworks.com\/topic\/2456488-hyper-v-servers-fail-to-install-defender-update-kb4052623\" target=\"_blank\" rel=\"noopener\">Hyper-V servers fail to install Defender update (KB4052623)<\/a> hin. Dort schreibt Siegfried Beitl zum 4. Juli 2022:<\/p>\n<blockquote><p>The update with the number KB4052623 has been around for a long time but it keeps getting new revisions. The latest revision (4.18.2205.7) refuses to install on any of the Hyper-V servers. There are 7 of those servers.<\/p>\n<p>The update is displayed as 'Update for Microsoft Defender Antivirus antimalware platform &#8211; KB4052623 (Version 4.18.2205.7)'<\/p>\n<p>These are physical servers running standalone Hyper-V server 2019 with the Hyper-V role enabled and pretty much nothing else. These are not fully fledged Windows Server 2019 running the core installation. It is the free version of Hyper-V server. The only other software is the Veeam agent. There is no third party AV.<\/p>\n<p>So far, I have tried, without success<\/p>\n<ul>\n<li>Declining the Update in WSUS, deleting the update through server cleanup wizard and re-approving it (thereby re-downloading it).<\/li>\n<li>Manually download it through the Update Catalog and installing the cab file. This leads to:<\/li>\n<\/ul>\n<p>Powershell<\/p>\n<pre><span class=\"n\">C<\/span><span class=\"err\">:<\/span><span class=\"p\">\\<\/span><span class=\"n\">Users<\/span><span class=\"p\">\\<\/span><span class=\"n\">siegfried<\/span><span class=\"p\">.<\/span><span class=\"n\">beitl<\/span><span class=\"p\">\\<\/span><span class=\"n\">Downloads<\/span><span class=\"p\">&gt;<\/span><span class=\"n\">dism<\/span> <span class=\"p\">\/<\/span><span class=\"n\">online<\/span> <span class=\"p\">\/<\/span><span class=\"nb\">add-package<\/span> <span class=\"p\">\/<\/span><span class=\"n\">packagepath<\/span><span class=\"err\">:<\/span><span class=\"s2\">\"c:\\Users\\siegfried.beitl\\Downloads\\37049705_04c96011b32d783314a49ed52845bfe05357f68f.cab\"<\/span><span class=\"n\">Deployment<\/span> <span class=\"n\">Image<\/span> <span class=\"n\">Servicing<\/span> <span class=\"n\">and<\/span> <span class=\"n\">Management<\/span> <span class=\"n\">toolVersion<\/span><span class=\"err\">:<\/span> <span class=\"n\">10<\/span><span class=\"p\">.<\/span><span class=\"n\">0<\/span><span class=\"p\">.<\/span><span class=\"n\">17763<\/span><span class=\"p\">.<\/span><span class=\"n\">1697Image<\/span> <span class=\"n\">Version<\/span><span class=\"err\">:<\/span> <span class=\"n\">10<\/span><span class=\"p\">.<\/span><span class=\"n\">0<\/span><span class=\"p\">.<\/span><span class=\"n\">17763<\/span><span class=\"p\">.<\/span><span class=\"n\">3046An<\/span> <span class=\"n\">error<\/span> <span class=\"n\">occurred<\/span> <span class=\"n\">trying<\/span> <span class=\"n\">to<\/span> <span class=\"n\">open<\/span> <span class=\"p\">-<\/span> <span class=\"n\">c<\/span><span class=\"err\">:<\/span><span class=\"p\">\\<\/span><span class=\"n\">Users<\/span><span class=\"p\">\\<\/span><span class=\"n\">siegfried<\/span><span class=\"p\">.<\/span><span class=\"n\">beitl<\/span><span class=\"p\">\\<\/span><span class=\"n\">Downloads<\/span><span class=\"p\">\\<\/span><span class=\"n\">37049705_04c96011b32d783314a49ed52845bfe05357f68f<\/span><span class=\"p\">.<\/span><span class=\"n\">cab<\/span> <span class=\"n\">Error<\/span><span class=\"err\">:<\/span> <span class=\"n\">0x80070002Error<\/span><span class=\"err\">:<\/span> <span class=\"n\">2The<\/span> <span class=\"n\">system<\/span> <span class=\"n\">cannot<\/span> <span class=\"n\">find<\/span> <span class=\"n\">the<\/span> <span class=\"n\">file<\/span> <span class=\"n\">specified<\/span><span class=\"p\">.<\/span>\r\n<\/pre>\n<ul>\n<li>the above looks like the cab file does not exits, but it does.<\/li>\n<li>Running chkdsk, DISM\u00a0Scanhealth, SFC. No errors.<\/li>\n<\/ul>\n<p>What should I do? Does anybody else have this issue? I find it interesting that only the Hyper-V servers without GUI are affected. Other servers that run Windows Server 2019 with GUI are not affected.<\/p>\n<p>In the application log there is an entry: source: Windows Error Reporting, event ID 1001<\/p>\n<div class=\"highlight\">\n<div class=\"language-name\">Text<\/div>\n<pre>Fault bucket 2151933532759585987, type 5\r\nEvent Name: MpTelemetry\r\nResponse: Not available\r\nCab Id: 0\r\n\r\nProblem signature:\r\nP1: 0x800705b4\r\nP2: ValidateUpdate\r\nP3: Platform update\r\nP4: 1.1.18500.10,4.18.2205.7\r\nP5: mpsigstub.exe\r\nP6: 4.18.2203.5\r\nP7: Microsoft Windows Defender (RS1+)\r\nP8: \r\nP9: \r\nP10:<\/pre>\n<\/div>\n<\/blockquote>\n<p>Im Thread wird der Effekt von zwei Nutzern best\u00e4tigt &#8211; einer hat einen neuen Hyper-V Server 2019 installiert &#8211; es liegt also nicht an der Server-Konfiguration.<\/p>\n<p>Der im Thread in einem Log erw\u00e4hnte Fehler\u00a0<em>0x800705B4\u00a0<\/em>tritt auf, wenn der Windows\u00a0Defender inaktiv ist und sich nicht wieder aktivieren l\u00e4sst.\u00a0Falls jemand betroffen ist, vielleicht auch mal den nachfolgenden Beitrag lesen, um diesen Efffekt auszuschlie\u00dfen.<\/p>\n<p><strong>\u00c4hnliche Artikel:<\/strong><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2022\/06\/14\/microsoft-defender-neues-feature-hacked-device-isolation-neues-sandboxing-problem\/\">Microsoft Defender: Neues Feature \"Hacked Device-Isolation\" &amp; neues \"Sandboxing\"-Problem<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Blog-Leser J.E. hat mich gerade per Mail kontaktiert. Auf seinen 2016er und 2019er Hyper-V Core Servern l\u00e4sst sich das Update f\u00fcr Microsoft Defender Antivirus-Antischadsoftwareplattform \u2013 KB4052623 (Version 4.18.2205.7) vom 22.06.2022 nicht installieren. Die Installation bricht immer mit dem Fehler 0x80070643 &hellip; <a href=\"https:\/\/borncity.com\/blog\/2022\/06\/24\/microsoft-defender-update-kb4052623-version-4-18-2205-7-liefert-fehler-0x80070643\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[185,161,301],"tags":[2699,58,4315,3288],"class_list":["post-268848","post","type-post","status-publish","format-standard","hentry","category-update","category-virenschutz","category-windows","tag-defender","tag-fehler","tag-update","tag-windows-en"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/268848","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=268848"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/268848\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=268848"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=268848"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=268848"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}