{"id":36039,"date":"2018-01-09T11:25:26","date_gmt":"2018-01-09T10:25:26","guid":{"rendered":"http:\/\/www.planet3dnow.de\/cms\/?p=36039"},"modified":"2018-01-09T15:25:47","modified_gmt":"2018-01-09T14:25:47","slug":"microsoft-zieht-meltdown-patch-fuer-amd-systeme-zurueck","status":"publish","type":"post","link":"https:\/\/www.planet3dnow.de\/cms\/36039-microsoft-zieht-meltdown-patch-fuer-amd-systeme-zurueck\/","title":{"rendered":"Microsoft zieht Meltdown-Patch f\u00fcr AMD-Systeme zur\u00fcck"},"content":{"rendered":"

Vor eini\u00adgen Tagen bereits haben wir im Rah\u00admen unse\u00adrer aus\u00adf\u00fchr\u00adli\u00adchen Zusam\u00admen\u00adfas\u00adsung<\/a> \u00fcber die ent\u00addeck\u00adten Sicher\u00adheits\u00adl\u00fc\u00adcken Spect\u00adre und Melt\u00addown berich\u00adtet, dass Micro\u00adsoft ein kumu\u00adla\u00adti\u00adves Updates ver\u00ad\u00f6f\u00adfent\u00adlich hat, das ers\u00adte Fixes ent\u00adh\u00e4lt. Das f\u00fcr Win\u00addows 10 KB4056892<\/span> genann\u00adte Paket soll die Melt\u00addown-L\u00fccke schlie\u00ad\u00dfen. Obwohl AMD<\/span> beteu\u00adert, von Melt\u00addown auf\u00adgrund von Archi\u00adtek\u00adtur\u00adun\u00adter\u00adschie\u00adden zu Intel nicht betrof\u00adfen zu sein, wur\u00adde der Fix von Micro\u00adsoft auch an AMD-User verteilt.<\/p>\n

Doch anschei\u00adnend war der Patch mit zu hei\u00ad\u00dfer Nadel gestrickt, denn nun berich\u00adten eini\u00adge AMD-User<\/a>, dass der PC<\/span> nach Instal\u00adla\u00adti\u00adon des Updates nicht mehr star\u00adtet und sich statt\u00addes\u00adsen in einer Blue\u00adscreen-Schlei\u00adfe ver\u00adhed\u00addert; BSOD<\/span> stop: 0x000000c4. Daher hat Micro\u00adsoft die betref\u00adfen\u00adden Updates f\u00fcr AMD<\/span> vor\u00ad\u00fcber\u00adge\u00adhend zur\u00fcck\u00adge\u00adzo\u00adgen<\/a>. Es han\u00addelt sich dabei um fol\u00adgen\u00adde Pakete:<\/p>\n

Janu\u00adary 3, 2018\u2014KB4056897<\/span> (Secu\u00adri\u00adty-only update)
\nJanu\u00adary 9, 2018\u2014KB4056894<\/span> (Month\u00adly Rollup)
\nJanu\u00adary 3, 2018\u2014KB4056888<\/span> (OS<\/span> Build 10586.1356)
\nJanu\u00adary 3, 2018\u2014KB4056892<\/span> (OS<\/span> Build 16299.192)
\nJanu\u00adary 3, 2018\u2014KB4056891<\/span> (OS<\/span> Build 15063.850)
\nJanu\u00adary 3, 2018\u2014KB4056890<\/span> (OS<\/span> Build 14393.2007)
\nJanu\u00adary 3, 2018\u2014KB4056898<\/span> (Secu\u00adri\u00adty-only update)
\nJanu\u00adary 3, 2018\u2014KB4056893<\/span> (OS<\/span> Build 10240.17735)
\nJanu\u00adary 9, 2018\u2014KB4056895<\/span> (Month\u00adly Rollup)<\/p><\/blockquote>\n

Den schwar\u00adzen Peter daf\u00fcr schiebt Micro\u00adsoft offen\u00adbar zu AMD<\/span>. Die f\u00fcr die Ent\u00adwick\u00adlung der Patches zur Ver\u00adf\u00fc\u00adgung gestell\u00adte Doku\u00admen\u00adta\u00adti\u00adon eini\u00adger Chip\u00ads\u00e4t\u00adze wei\u00adche von der Rea\u00adli\u00adt\u00e4t ab, wes\u00adhalb es zu den Pro\u00adble\u00admen gekom\u00admen sei:<\/p>\n

Micro\u00adsoft has reports of cus\u00adto\u00admers with some AMD<\/span> devices get\u00adting into an unboota\u00adble sta\u00adte after instal\u00adling recent Win\u00addows ope\u00adra\u00adting sys\u00adtem secu\u00adri\u00adty updates. After inves\u00adti\u00adga\u00adting, Micro\u00adsoft has deter\u00admi\u00adned that some AMD<\/span> chip\u00adsets do not con\u00adform to the docu\u00admen\u00adta\u00adti\u00adon pre\u00advious\u00adly pro\u00advi\u00added to Micro\u00adsoft to deve\u00adlop the Win\u00addows ope\u00adra\u00adting sys\u00adtem miti\u00adga\u00adti\u00adons to pro\u00adtect against the chip\u00adset vul\u00adnerabi\u00adli\u00adties known as Spect\u00adre and Meltdown<\/p><\/blockquote>\n

Um das Sys\u00adtem wie\u00adder gang\u00adbar zu machen, muss man das ent\u00adspre\u00adchen\u00adde Update wie\u00adder los\u00adwer\u00adden; was gar nicht so ein\u00adfach ist wenn das Sys\u00adtem nicht mehr boo\u00adtet, da man es nicht ein\u00adfach \u00fcber die Sys\u00adtem\u00adsteue\u00adrung deinstal\u00adlie\u00adren kann. Statt\u00addes\u00adsen muss man das Sys\u00adtem in die Repa\u00adra\u00adtur-Umge\u00adbung star\u00adten. Wer den Com\u00adpu\u00adter\u00adschutz akti\u00adviert hat\u00adte (Stan\u00addard bei Win\u00addows 7), kann mit\u00adtels Sys\u00adtem\u00adwie\u00adder\u00adher\u00adstel\u00adlung auf den letz\u00adten Punkt vor dem Update zur\u00fcck\u00adset\u00adzen. Wer nicht (oft bei Win\u00addows 10 der Fall), muss in der Kon\u00adso\u00adle mit DISM<\/span> arbei\u00adten. Zun\u00e4chst ein\u00admal kann man sich mit\u2026<\/p>\n

DISM \/online \/get-packages \/format:table | findstr 16299.192<\/code><\/p>\n

\u2026den voll\u00adst\u00e4n\u00addi\u00adgen Paket\u00adna\u00admen des Updates anzei\u00adgen las\u00adsen. Der Wert nach find\u00adstr ist die Build-Num\u00admer und weicht je nach Sys\u00adtem ab; sie\u00adhe Lis\u00adte oben. Nach\u00addem man den Namen her\u00adaus\u00adge\u00adfun\u00adden hat, ent\u00adfernt fol\u00adgen\u00adder Befehl das Paket aus dem System:<\/p>\n

DISM \/online \/remove-package \/packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9<\/code><\/p>\n

Hier ist der Wert nach \u201cpacka\u00adge\u00adna\u00adme:\u201d jener, den der Befehl zuvor aus\u00adge\u00adspuckt hat. Neu\u00adstart machen, anschlie\u00ad\u00dfend in der Administrator-Eingabeaufforderung:<\/p>\n

DISM \/online \/cleanup-image \/startcomponentcleanup<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"

Obwohl AMD<\/span> beteu\u00adert, von Melt\u00addown auf\u00adgrund von Archi\u00adtek\u00adtur\u00adun\u00adter\u00adschie\u00adden zu Intel nicht betrof\u00adfen zu sein, wur\u00adde der Fix von Micro\u00adsoft auch an AMD-User ver\u00adteilt. Doch anschei\u00adnend war der Patch mit zu hei\u00ad\u00dfer Nadel gestrickt, denn nun berich\u00adten eini\u00adge AMD-User, dass der PC<\/span> nach Instal\u00adla\u00adti\u00adon des Updates nicht mehr star\u00adtet und sich statt\u00addes\u00adsen in einer Blue\u00adscreen-Schlei\u00adfe ver\u00adhed\u00addert. (\u2026) Wei\u00adter\u00adle\u00adsen \u00bb<\/a><\/p>\n","protected":false},"author":2,"featured_media":35751,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wp_typography_post_enhancements_disabled":false,"ngg_post_thumbnail":0,"footnotes":""},"categories":[12,16],"tags":[966,1419,968,1420],"class_list":["post-36039","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aktuelles","category-patches","tag-amd","tag-meltdown","tag-microsoft","tag-spectre","entry"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/posts\/36039","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/comments?post=36039"}],"version-history":[{"count":16,"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/posts\/36039\/revisions"}],"predecessor-version":[{"id":36059,"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/posts\/36039\/revisions\/36059"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/media\/35751"}],"wp:attachment":[{"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/media?parent=36039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/categories?post=36039"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.planet3dnow.de\/cms\/wp-json\/wp\/v2\/tags?post=36039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}