{"id":213989,"date":"2019-01-22T00:07:00","date_gmt":"2019-01-21T23:07:00","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=213989"},"modified":"2019-02-13T08:17:11","modified_gmt":"2019-02-13T07:17:11","slug":"windows-10-server-2016-hyper-v-problem-durch-update-kb4480977-besttigt","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2019\/01\/22\/windows-10-server-2016-hyper-v-problem-durch-update-kb4480977-besttigt\/","title":{"rendered":"Windows 10\/Server 2016: Hyper-V-Problem durch Update KB4480977 best&auml;tigt"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2015\/01\/win102.jpg\" width=\"58\" height=\"58\" align=\"left\" \/>Das Update KB4480977 vom 17. Januar 2019 f\u00fcr Windows 10 V1607 und Windows Server 2016 bringt Probleme in Hyper-V-Umgebungen. Inzwischen hat Microsoft das offiziell best\u00e4tigt.<\/p>\n<p><!--more--><\/p>\n<h2>Update KB4480977 f\u00fcr Windows 10\/Server 2016<\/h2>\n<p>\u00dcber Update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480977\">KB4480977<\/a> hatte ich im Blog-Beitrag <a href=\"https:\/\/borncity.com\/blog\/2019\/01\/18\/windows-10-v1607-update-kb4480977-17-1-2019\/\">Windows 10 V1607: Update KB4480977 (17.1.2019)<\/a> berichtet. Das Update steht f\u00fcr Windows 10 V1607 Enterprise LTSC und f\u00fcr Windows Server 2016 zur Verf\u00fcgung. Zus\u00e4tzlich hat Microsoft f\u00fcr Systeme mit Intel \"Clovertrail\" Chipset Updates bis Januar 2023 zugesagt.<\/p>\n<h2>Viele bekannte Probleme, auch in Hyper-V<\/h2>\n<p>Bereits im Blog-Beitrag <a href=\"https:\/\/borncity.com\/blog\/2019\/01\/18\/windows-10-v1607-update-kb4480977-17-1-2019\/\">Windows 10 V1607: Update KB4480977 (17.1.2019)<\/a> hatte ich darauf verwiesen, dass das kumulative Update KB4480977 eine ganze Latte an 'known issues' habe. Unter bekannten Problemen wird auch folgender Fehler aufgef\u00fchrt:<\/p>\n<blockquote><p>System Center Virtual Machine Manager (SCVMM) managed workloads are noticing infrastructure management issues after VMM refresh as the Windows Management Instrumentation (WMI) class around network port is being unregistered on Hyper-V hosts.<\/p><\/blockquote>\n<p>Auf den Hyper-V-Hosts wird die WMI-Klasse im Bereich Netzwerk-Ports de-registriert, so dass es zu Infrastrukturproblemen beim Refresh eine VMM kommen kann. Microsoft schl\u00e4gt folgenden Workaround vor:<\/p>\n<blockquote><p>Run <em>mofcomp<\/em> for the <em>scvmmswitchportsettings.mof<\/em>, <em>VMMDHCPSvr.mof<\/em>, and other relevant SCVMM MOF Files. Please upgrade thru the <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4463450\/update-rollup-6-for-system-center-2016-virtual-machine-manager\" target=\"_blank\" rel=\"noopener\">SCVMM 2016 Update Rollup 6 (UR6)<\/a> to expedite the Host Refresh activities after running <em>mofcomp<\/em> command.<\/p><\/blockquote>\n<p>Der Bug d\u00fcrfte nur noch wenige Windows 10-Nutzer treffen, da die V1607 aus dem Support gefallen ist. Aber Windows Server 2016-Maschinen mit Hyper-V werden wohl noch einige laufen. (<a href=\"https:\/\/www.bleepingcomputer.com\/news\/security\/windows-zero-day-bug-that-overwrites-files-gets-interim-fix\/\" target=\"_blank\" rel=\"noopener\">via<\/a>)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Das Update KB4480977 vom 17. Januar 2019 f\u00fcr Windows 10 V1607 und Windows Server 2016 bringt Probleme in Hyper-V-Umgebungen. Inzwischen hat Microsoft das offiziell best\u00e4tigt.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,3694,2557],"tags":[1169,24,4315,4378,4380],"class_list":["post-213989","post","type-post","status-publish","format-standard","hentry","category-virtualisierung","category-windows-10","category-windows-server","tag-hyper-v","tag-problem","tag-update","tag-windows-10","tag-windows-server-2016"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/213989","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=213989"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/213989\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=213989"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=213989"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=213989"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}