{"id":221012,"date":"2019-07-25T01:48:44","date_gmt":"2019-07-24T23:48:44","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=221012"},"modified":"2019-07-25T01:49:42","modified_gmt":"2019-07-24T23:49:42","slug":"windows-10-20h1-microsoft-besttigt-versehentliche-freigabe-der-build-18947","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2019\/07\/25\/windows-10-20h1-microsoft-besttigt-versehentliche-freigabe-der-build-18947\/","title":{"rendered":"Windows 10 20H1: Microsoft best&auml;tigt versehentliche Freigabe der Build 18947"},"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\" align=\"left\" height=\"58\"\/>Vor einigen Stunden hat Microsoft ja 'versehentlich' die Build 18947 von Windows 10 (20H1 Entwicklungszweig) an Windows Insider \u00fcber alle Ringe verteilt. Das Malheur wurde jetzt durch Microsoft best\u00e4tigt und es gibt Hinweise, wie das Problem korrigiert werden kann.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg08.met.vgwort.de\/na\/acd613b50d904830918f7aaefe82fd13\" width=\"1\" height=\"1\"\/>\u00dcber den Lapsus hatte ich im Blog-Beitrag <a href=\"https:\/\/borncity.com\/blog\/2019\/07\/24\/windows-10-19h2-ungetestete-build-18947-freigegeben\/\">Windows 10 20H1: Ungetestete Build 18947 freigegeben<\/a> berichtet.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">Windows 10 build 18947 is being pushed to Insiders in *ALL RINGS* on 32-bit machines. 18947 is a canary build, and has not been tested internally yet (it was compiled less than a day ago.) Seems an error has caused the rollout.<\/p>\n<p>\u2014 Zac Bowden (@zacbowden) <a href=\"https:\/\/twitter.com\/zacbowden\/status\/1153971182628167681?ref_src=twsrc%5Etfw\">July 24, 2019<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script> <\/p>\n<p>Es war eine ungetesteste Canary Build, die eigentlich nie freigegeben werden sollte. Jason von Microsoft hat in <a href=\"https:\/\/answers.microsoft.com\/en-us\/insider\/forum\/insider_wintp-insider_update-insiderplat_pc\/insider-build-18947-information-and-how-to\/3c371d12-e61b-4152-93e9-0975a2643208?tm=1564004251681&amp;auth=1\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Answers<\/a> folgenden Text gepostet:<\/p>\n<blockquote>\n<h3>Insider Build 18947 &#8211; Information and How To Rollback<\/h3>\n<p>Hello Insiders!<br \/>We'd like to share information with you regarding build 18947 as released to Windows Insider audiences earlier today. We'll cover what happened and how to revert your device to your desired state.<\/p>\n<\/blockquote>\n<p>Zur Frage 'Wie konnte das passieren', liefert Jason eine einfache Antwort.  <\/p>\n<blockquote>\n<p>Windows Insiders may be wondering what caused this scenario. We actively test and validate each of our preview builds internally before sharing them externally, however a configuration change allowed this build to release to multiple rings simultaneously, including external rings. We have made the necessary remediation in our Flighting service and have implemented additional changes to help prevent from this happening in the future. We apologize for any troubles this may have caused for affected Insiders and appreciate your assistance in bringing this to our attention so we could make the necessary changes as quickly as possible.<\/p>\n<\/blockquote>\n<p>Microsoft testet und validiert aktiv jeden der Preview-Builds intern, bevor sie extern freigegeben wird. Aber eine Konfigurations\u00e4nderung am Rollout-Mechanismus f\u00fchrte dazu, dass diese Build gleichzeitig in mehreren Ringen gleichzeitig ver\u00f6ffentlicht wurde. Damit kamen nicht nur interne, sondern auch externe Ringe in den 'Genuss' dieser Build. Die Microsoftler haben die notwendigen Korrekturen in dem betreffenden Verteilmechanismus vorgenommen, um dies in Zukunft zu verhindern.  <\/p>\n<p>Nach einer Entschuldigung f\u00fcr die dadurch verursachten Probleme bei betroffenen Insidern gibt Jason Hinweise, wie diese Nutzer ein Rollback auf die vorherige Windows 10-Build durchf\u00fchren k\u00f6nnen. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Vor einigen Stunden hat Microsoft ja 'versehentlich' die Build 18947 von Windows 10 (20H1 Entwicklungszweig) an Windows Insider \u00fcber alle Ringe verteilt. Das Malheur wurde jetzt durch Microsoft best\u00e4tigt und es gibt Hinweise, wie das Problem korrigiert werden kann.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[185,3694],"tags":[4378],"class_list":["post-221012","post","type-post","status-publish","format-standard","hentry","category-update","category-windows-10","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/221012","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=221012"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/221012\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=221012"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=221012"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=221012"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}