{"id":199854,"date":"2018-01-18T00:57:00","date_gmt":"2018-01-17T23:57:00","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=199854"},"modified":"2018-01-22T17:50:39","modified_gmt":"2018-01-22T16:50:39","slug":"windows-8-1-server-2012-fix-fr-amd-bootprobleme","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2018\/01\/18\/windows-8-1-server-2012-fix-fr-amd-bootprobleme\/","title":{"rendered":"Windows 8.1\/Server 2012: Fix f&uuml;r AMD-Bootprobleme und Updates"},"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\/2013\/03\/winb.jpg\" width=\"58\" height=\"58\" align=\"left\" \/>[<a href=\"https:\/\/borncity.com\/win\/2018\/01\/18\/windows-8-1-server-2012-updates-and-amd-boot-issue-fix\/\" target=\"_blank\" rel=\"noopener\">English<\/a>]Microsoft hat einen Fix zum Beheben von Boot-Problemen auf AMD-Systemen bereitgestellt, die nach Installation der Updates KB4056898 oder KB4056895\u00a0 auftraten. <strong>Erg\u00e4nzung:<\/strong> Zudem gibt es das Update KB4057401 (Preview of Monthly Rollup) f\u00fcr Windows 8.1 und das Update KB4057402 (Preview of Monthly Rollup) f\u00fcr Windows Server 2012.<\/p>\n<p><!--more--><\/p>\n<h2><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/e07e25cba66c4c53a94706b44fc0fe70\" alt=\"\" width=\"1\" height=\"1\" \/>Update KB4057401 f\u00fcr Windows 8.1\/Server 2012 R2<\/h2>\n<p>Update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4057402\/windows-server-20112-update-kb4057402\" target=\"_blank\" rel=\"noopener\">KB4057401<\/a> (Preview of Monthly Rollup) f\u00fcr Windows 8.1 und <em><span class=\"c-meta-text display-inline comma-appended ng-binding ng-scope\" aria-hidden=\"false\">Windows Server 2012 R2 Standard <\/span><\/em>ist kein sicherheitsrelevantes Update. Es enth\u00e4lt Verbesserungen und Korrekturen, die Teil von KB4056896 (ver\u00f6ffentlicht am 4. Januar 2018) waren, und enth\u00e4lt auch diese neuen Qualit\u00e4tsverbesserungen als Vorschau auf das n\u00e4chste monatliche Rollup-Update:<\/p>\n<ul>\n<li>Addresses issue where every smart card logon to a Windows Terminal Server\/Remote Desktop Server may result in a handle leak in the certprop service. Token leaks result in session leaks on computers that have installed MS16-111\/<u>KB3175024<\/u> and superseding fixes.<\/li>\n<li>Addresses issue where servers running AppLocker stop working.<\/li>\n<li>Addresses issue where an unexpected system restart occurs because of exception code 0xc0000005 (Access Violation) in LSASS.exe, where the faulting module is cryptnet.dll.<\/li>\n<li>Addresses issue where, if the Online Certificate Status Protocol (OCSP) renewal date comes after the certificate expiration date, the OCSP-stapled response is used until the renewal date even though the certificate has expired.<\/li>\n<li>Addresses multiple symptoms that occur during power transitions including a stop error 0x9F (0000009F) when a device tries to enter sleep mode or restart. USB PnP devices may also be unusable after waking from sleep.<\/li>\n<li>Addresses issue where the iSCSI Initiator Properties <strong>Devices<\/strong> list doesn't display certain targets.<\/li>\n<li>Addresses issue where Event ID 1511 appears when you start a task that is created in Task Scheduler.<\/li>\n<li>Addresses issue where a race condition in memory management may lead to Error 0x50 or 0x149 when trimming sparse files.<\/li>\n<li>Addresses issue where AD FS incorrectly processed the wct parameter in a ws-federation request as a local time instead of a UTC value. This affects customers that federate AD FS with other third-party identity providers. Authentication failed because incorrect wct values implied bad or old requests.<\/li>\n<li>Addresses issue where attempts to view the previous versions of a file on a file share fail. This occurs after a disk that hosts file shares goes offline and comes back online.<\/li>\n<li>Addresses the following issues with the WinRM service:\n<ul>\n<li>A threading issue that may cause the WinRM service to crash under load. This is a client-side solution, so you must apply it to the affected computers(s) and the computers that communicate with the WinRM service.<\/li>\n<li>A system performance issue that may cause logon to stop responding with the message, \"Please wait for the Remote Desktop Configuration\". This was caused by a deadlock in the WinRM service.<\/li>\n<\/ul>\n<\/li>\n<li>Addresses issue originally called out in KB4056895 where calling CoInitializeSecurity with the authentication parameter set to RPC_C_AUTHN_LEVEL_NONE resulted in the error STATUS_BAD_IMPERSONATION_LEVEL.<\/li>\n<\/ul>\n<p>Es ist anzumerken, dass dieses Update nur per Windows Update angeboten wird, wenn die installierte Antivirus-Software auf dem System \u00fcber einen Registrierungseintrag signalisiert, dass diese kompatibel ist. Das Thema zieht sich durch alle Updates seit Januar 2018 und wurde z.B. im Blog-Beitrag <a href=\"https:\/\/borncity.com\/blog\/2018\/01\/04\/kritische-sicherheitsupdates-fr-windows-7-8-1-3-1-2018\/\" rel=\"bookmark\">Kritische Sicherheitsupdates f\u00fcr Windows 7\/8.1\/Server (3.\/4.1.2018)<\/a> angesprochen. Der Schl\u00fcssel ist auch im Beitrag\u00a0 <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4057402\/windows-server-20112-update-kb4057402\" target=\"_blank\" rel=\"noopener\">KB4057401<\/a> angegeben.<\/p>\n<p>Das Update wird per Windows Update verteilt, kann aber auch \u00fcber den <a href=\"http:\/\/catalog.update.microsoft.com\/v7\/site\/Search.aspx?q=KB4057401\" target=\"_blank\" rel=\"noopener\" data-content-type=\"\" data-content-id=\"\">Microsoft Update Catalog<\/a> bezogen werden. Da es ein Preview Rollup ist, muss es nicht wirklich installiert werden &#8211; es wird ja n\u00e4chsten Monat angeboten.<\/p>\n<h2>Update KB4057402 f\u00fcr <span class=\"c-meta-text display-inline comma-appended ng-binding ng-scope\" aria-hidden=\"false\">Windows Server 2012 Standard<\/span><\/h2>\n<p>Update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4057402\/windows-server-20112-update-kb4057402\" target=\"_blank\" rel=\"noopener\">KB4057402<\/a> (Preview of Monthly Rollup) f\u00fcr <span class=\"c-meta-text display-inline comma-appended ng-binding ng-scope\" aria-hidden=\"false\">Windows Server 2012\u00a0 Standard <\/span>ist ebenfalls kein sicherheitsrelevantes Update. Es enth\u00e4lt Verbesserungen und Korrekturen, die Teil von <a class=\"managed-link content-anchor-link\" tabindex=\"0\" href=\"https:\/\/support.microsoft.com\/en-us\/help\/4056896\" target=\"_blank\" rel=\"noopener\" aria-live=\"rude\" data-content-type=\"article\" data-content-id=\"4056896\" data-bi-name=\"content-anchor-link\">KB4056896<\/a> (ver\u00f6ffentlicht am 4. Januar 2018) waren, und enth\u00e4lt auch diese neuen Qualit\u00e4tsverbesserungen als Vorschau auf das n\u00e4chste monatliche Rollup-Update:<\/p>\n<ul>\n<li>Addresses issue where every smart card logon to a Windows Terminal Server\/Remote Desktop Server may result in a handle leak in the certprop service. Token leaks result in session leaks on computers that have installed MS16-111\/<a class=\"managed-link content-anchor-link\" tabindex=\"0\" href=\"https:\/\/support.microsoft.com\/en-us\/help\/3175024\" target=\"_blank\" rel=\"noopener\" aria-live=\"rude\" data-content-type=\"article\" data-content-id=\"3175024\" data-bi-name=\"content-anchor-link\"><u>KB3175024<\/u><\/a> and superseding fixes.<\/li>\n<li>Addresses the following issues with the WinRM service:\n<ul>\n<li>A threading issue that may cause the WinRM service to crash under load. This is a client-side solution, so you must apply it to the affected computers(s) and the computers that communicate with the WinRM service.<\/li>\n<li>A system performance issue that may cause logon to stop responding with the message, \"Please wait for the Remote Desktop Configuration\". This was caused by a deadlock in the WinRM service.<\/li>\n<\/ul>\n<\/li>\n<li>Addresses issue originally called out in KB4056896 where calling CoInitializeSecurity with the authentication parameter set to RPC_C_AUTHN_LEVEL_NONE resulted in the error STATUS_BAD_IMPERSONATION_LEVEL.<\/li>\n<\/ul>\n<p>Das Update wird per Windows Update verteilt, kann aber auch \u00fcber den <a href=\"http:\/\/catalog.update.microsoft.com\/v7\/site\/Search.aspx?q=KB4057402\" target=\"_blank\" rel=\"noopener\" data-content-type=\"\" data-content-id=\"\">Microsoft Update Catalog<\/a> bezogen werden. Hier ist nichts von einem Registrierungseintrag erw\u00e4hnt und AMD-Bootprobleme werden auch nicht adressiert. Da es ein Preview Rollup ist, muss es nicht wirklich installiert werden &#8211; es wird ja n\u00e4chsten Monat angeboten.<\/p>\n<h2>Beitrag zum AMD-Boot-Problem<\/h2>\n<p>Microsoft hatte am Jahresanfang schnell Sicherheitsupdates zum h\u00e4rten von Windows gegen\u00fcber Meltdown-\/Spectre-Angriffen freigegeben. Die am 3. Januar 2017 freigegebenen Update <a href=\"https:\/\/support.microsoft.com\/de-de\/help\/4056898\" target=\"_blank\" rel=\"noopener\">January 3, 2018\u2014KB4056898 (Security-only update)<\/a> und <a href=\"https:\/\/support.microsoft.com\/en-in\/help\/4056895\" target=\"_blank\" rel=\"noopener\">January 8, 2018\u2014KB4056895 (Monthly Rollup)<\/a> f\u00fcr Windows 8.1 und Windows Server 2012 R2 machten aber Probleme. Auf AMD-Systemen kam es zu BlueScreens und viele Systeme konnten nicht mehr booten.<\/p>\n<p>Unter der KB-Nummer <a href=\"https:\/\/support.microsoft.com\/en-in\/help\/4073576\/unbootable-state-for-amd-devices-windows-8-1-windows-server-2012-r2\" target=\"_blank\" rel=\"noopener\">4073576<\/a> findet sich ein Dokument, welches auf das Boot-Problem eingeht. Das neue Update\u00a0KB4073576\u00a0ist als stand-alone Paket \u00fcber <a href=\"http:\/\/www.catalog.update.microsoft.com\/Search.aspx?q=KB4073576\" target=\"_blank\" rel=\"noopener\">Microsoft Update Catalog<\/a> abrufbar. Allerdings frage ich mich, wie Windows 8.1-Nutzer den Fix installieren sollen, wenn das Betriebssystem nicht mehr bootet.<\/p>\n<p>Weiterhin gibt es das Update\u00a0<a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4073578\/unbootable-state-for-amd-devices-in-windows-7-sp1-windows-server-2008\" target=\"_blank\" rel=\"noopener\">KB4073578<\/a> f\u00fcr Windows 7.1 (und Windows Server 2008 R2 SP1) zum Beheben von Boot-Problemen auf AMD-Systemen.\u00a0Das neue Update KB4073578 ist als stand-alone Paket \u00fcber <a href=\"http:\/\/www.catalog.update.microsoft.com\/Search.aspx?q=KB4073578\" target=\"_blank\" rel=\"noopener\">Microsoft Update Catalog<\/a> abrufbar.<\/p>\n<p><strong>\u00c4hnliche Artikel:<\/strong><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/01\/09\/amd-gau-av-rger-neues-zu-windows-sicherheitsupdates\/\">AMD-GAU &amp; AV-\u00c4rger: Neues zu Windows-Sicherheitsupdates<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/01\/07\/windows10-update-kb4056892-killt-amd-systeme-error-0x800f0845\/\">Windows10: Update KB4056892 killt AMD-Systeme (Error 0x800f0845)<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/01\/09\/windows-updates-kb4056892-kb4056894-etc-fr-amd-temporr-zurckgezogen\/\">Windows Updates (KB4056892, KB4056894 etc.) f\u00fcr AMD tempor\u00e4r zur\u00fcckgezogen<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/01\/08\/windows81-monthly-rollup-update-kb4056895-verfgbar\/\">Windows 8.1: Monthly Rollup Update KB4056895 verf\u00fcgbar<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/01\/04\/kritische-sicherheitsupdates-fr-windows-7-8-1-3-1-2018\/\">Kritische Sicherheitsupdates f\u00fcr Windows 7\/8.1\/Server (3.\/4.1.2018)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[English]Microsoft hat einen Fix zum Beheben von Boot-Problemen auf AMD-Systemen bereitgestellt, die nach Installation der Updates KB4056898 oder KB4056895\u00a0 auftraten. Erg\u00e4nzung: Zudem gibt es das Update KB4057401 (Preview of Monthly Rollup) f\u00fcr Windows 8.1 und das Update KB4057402 (Preview of &hellip; <a href=\"https:\/\/borncity.com\/blog\/2018\/01\/18\/windows-8-1-server-2012-fix-fr-amd-bootprobleme\/\">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":[11,185,301],"tags":[6758,6746,6770,6769,6783,6784,2539,4315,4366,5508],"class_list":["post-199854","post","type-post","status-publish","format-standard","hentry","category-problemlosung","category-update","category-windows","tag-kb4056895","tag-kb4056898","tag-kb4057401","tag-kb4057402","tag-kb4073576","tag-kb4073578","tag-problembehandlung","tag-update","tag-windows-8-1","tag-windows-server-2012"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/199854","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=199854"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/199854\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=199854"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=199854"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=199854"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}