{"id":219829,"date":"2019-06-27T08:09:25","date_gmt":"2019-06-27T06:09:25","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=219829"},"modified":"2019-06-27T10:57:17","modified_gmt":"2019-06-27T08:57:17","slug":"windows-10-v1809-update-kb4509479","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2019\/06\/27\/windows-10-v1809-update-kb4509479\/","title":{"rendered":"Windows 10: Update KB4509479, KB4509478, KB4509477, KB4509476 (26.6.2019)"},"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\" \/>[<a href=\"https:\/\/borncity.com\/win\/2019\/06\/27\/windows-10-update-kb4509479-kb4509478-kb4509477-kb4509476-06-26-2019\/\" target=\"_blank\" rel=\"noopener noreferrer\">English<\/a>]Microsoft hat zum 26. Juni 2019 das kumulative Update KB4509479 f\u00fcr Windows 10 Version 1809, Windows Server Version 1809 und Windows Server 2019 freigegeben. <strong>Erg\u00e4nzung:<\/strong> F\u00fcr \u00e4ltere Windows 10-Versionen steht der gleiche Fix unter anderen KB-Nummern zur Verf\u00fcgung.<\/p>\n<p><!--more--><\/p>\n<h2><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg07.met.vgwort.de\/na\/ee982a05ea49407cbaf5083c9224246d\" alt=\"\" width=\"1\" height=\"1\" \/>Update KB4509479 f\u00fcr Windows 10 V1809<\/h2>\n<p>Update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4509479\/windows-10-update-kb4509479\" target=\"_blank\" rel=\"noopener noreferrer\">KB4509479<\/a> hebt die OS Build auf die Version 17763.593. Das kumulative Update adressiert einen Fehler im Bereich Storage Area Network (SAN), der nach Installation von Update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4497934\" target=\"_blank\" rel=\"noopener noreferrer\">KB4497934<\/a> zu Verbindungsproblemen f\u00fchrt:<\/p>\n<blockquote><p>Addresses an issue that may prevent devices from connecting to some Storage Area Network (SAN) devices using Internet Small Computer System Interface (iSCSI) after installing <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4497934\" target=\"_blank\" rel=\"noopener noreferrer\">KB4497934<\/a>. You may also receive an error in the <strong>System <\/strong>log section of <strong>Event Viewer <\/strong>with Event ID 43 from iScsiPrt and a description of \"Target failed to respond in time for a login request.\"<\/p><\/blockquote>\n<p>Sind fr\u00fchere Updates installiert, werden nur die neuen Fixes in diesem Paket heruntergeladen und auf Ihrem Ger\u00e4t installiert.<\/p>\n<blockquote><p>Verbesserungen bei Windows Update<\/p>\n<p>Zudem hat Microsoft den Windows Update Client direkt aktualisiert, um dessen Zuverl\u00e4ssigkeit zu verbessern. Das Update wird auf jedem Windows 10 vorgenommen, bei dem keine Update-Verz\u00f6gerung konfiguriert ist (gilt auch f\u00fcr Enterprise und Pro, nicht aber f\u00fcr die LTSC-Editionen).<\/p><\/blockquote>\n<p>Microsoft empfiehlt dringend, dass das neueste Service Stack Update (SSU) f\u00fcr Windows 10 vor dem kumulativen Update (LCU) zu installieren. Die SSUs verbessern die Zuverl\u00e4ssigkeit der Update-Installation von kumulativen Updates. Wird Windows Update verwendet, sollte das neueste SSU (KB4504369) automatisch installiert werden.<\/p>\n<p>Das optionale Update steht \u00fcber die Update-Suche zur Verf\u00fcgung (die Seite <em>Windows Update <\/em>aufrufen und die Schaltfl\u00e4che <em>Nach Updates suchen <\/em>anw\u00e4hlen). Das Paket l\u00e4sst sich auch per <a href=\"http:\/\/www.catalog.update.microsoft.com\/home.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Update Catalog<\/a> herunterladen und manuell installieren.<\/p>\n<h2>Eine ganze Latte bekannter Probleme<\/h2>\n<p>Im <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4509479\/windows-10-update-kb4509479\" target=\"_blank\" rel=\"noopener noreferrer\">KB-Artikel<\/a> listet Microsoft aber gleich eine ganze Latte an bekannten Problemen f\u00fcr dieses Update auf.<\/p>\n<table border=\"1\" width=\"640\" cellspacing=\"0\" cellpadding=\"2\">\n<tbody>\n<tr>\n<td valign=\"top\" width=\"320\"><strong>Symptom<\/strong><\/td>\n<td valign=\"top\" width=\"320\"><strong>Workaround<\/strong><\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"320\">Certain operations, such as <strong>rename<\/strong>, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\". This occurs when you perform the operation on a CSV owner node from a process that doesn't have administrator privilege.<\/td>\n<td valign=\"top\" width=\"320\">Do one of the following:<\/p>\n<ul>\n<li>Perform the operation from a process that has administrator privilege.<\/li>\n<li>Perform the operation from a node that doesn't have CSV ownership.<\/li>\n<\/ul>\n<p>Microsoft is working on a resolution and will provide an update in an upcoming release.<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"320\">After installing <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4493509\" target=\"_blank\" rel=\"noopener noreferrer\">KB4493509<\/a>, devices with some Asian language packs installed may receive the error, \"0x800f0982 &#8211; PSFX_E_MATCHING_COMPONENT<br \/>\n_NOT_FOUND.\"<\/td>\n<td valign=\"top\" width=\"320\">\n<ol>\n<li>Uninstall and reinstall any recently added language packs. For instructions, see <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4496404\" target=\"_blank\" rel=\"noopener noreferrer\">Manage the input and display language settings in Windows 10<\/a>.<\/li>\n<li>Select <strong>Check for Updates<\/strong> and install the April 2019 Cumulative Update. For instructions, see <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4027667\" target=\"_blank\" rel=\"noopener noreferrer\">Update Windows 10<\/a>.<\/li>\n<\/ol>\n<p><strong>Note<\/strong> If reinstalling the language pack does not mitigate the issue, reset your PC as follows:<\/p>\n<ol>\n<li>Go to the <strong>Settings <\/strong>app &gt; <strong>Recovery<\/strong>.<\/li>\n<li>Select <strong>Get Started<\/strong> under the <strong>Reset this PC<\/strong> recovery option.<\/li>\n<li>Select <strong>Keep my Files<\/strong>.<\/li>\n<\/ol>\n<p>Microsoft is working on a resolution and will provide an update in an upcoming release.<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\" width=\"320\">\n<ol>We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.<\/ol>\n<\/td>\n<td valign=\"top\" width=\"320\">To mitigate this issue, press <strong>Ctrl+Alt+Delete, <\/strong>then select the <strong>Power <\/strong>button in the lower right corner of the screen and select <strong>Restart<\/strong>. Your device should now restart normally.<\/p>\n<p>We are working on a resolution and will provide an update in an upcoming release.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Die Fehler ziehen sich bereits durch die letzten Update-Pakete. Hier wird der Nachteil des Ansatzes der kumulativen Updates sichtbar. Ein Fehler f\u00fcr einen Fix zieht sich oft monatelang hin. So muss man entscheiden, ob man die obigen Bug behebt und neue Fehler akzeptiert, oder das Update (in Enterprise und Pro) verz\u00f6gert.<\/p>\n<h2>Updates f\u00fcr Windows 10 V1703 bis V1803<\/h2>\n<p>F\u00fcr die \u00e4lteren Windows 10-Versionen stehen ebenfalls Updates f\u00fcr den obigen Fehler bereit. Hier die betreffenden KB-Nummern:<\/p>\n<ul>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4509478\" target=\"_blank\" rel=\"noopener noreferrer\">KB4509478<\/a>: F\u00fcr Windows 10 1803, hebt die OS-Build auf 17134.860,<\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4509477\" target=\"_blank\" rel=\"noopener noreferrer\">KB4509477:<\/a> F\u00fcr Windows 10 1709, hebt die OS-Build auf 16299.1239,<\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4509476\" target=\"_blank\" rel=\"noopener noreferrer\">KB4509476<\/a>: F\u00fcr Windows 10, 1703, hebt die OS-Build auf 15063.1898<\/li>\n<\/ul>\n<p>Zu beachten ist aber, dass die Windows 10 Versionen 1703 und 1709 in den Home- und Pro-Varianten aus dem Support gefallen sind, nur noch die Version 1803 bekommt dort noch bis November 2019 Updates. Das hei\u00dft, die letztgenannten obigen Updates kommen nur noch f\u00fcr die Enterprise-SKUs.<\/p>\n<p><strong>\u00c4hnliche Artikel:<\/strong><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2019\/06\/12\/patchday-windows-10-updates-11-juni-2019\/\">Patchday Windows 10-Updates (11. Juni 2019)<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2019\/06\/19\/windows-10-updates-18-juni-2019\/\">Windows 10-Updates (18. Juni 2019)<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2019\/06\/25\/windows-10-updates-kb4501375-kb4504360-kb4506933\/\">Windows 10: Updates KB4501375, KB4504360, KB4506933<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2019\/06\/27\/windows-10-zuverlssigkeitsupdate-kb4023057-20-6-2019\/\">Windows 10: Zuverl\u00e4ssigkeitsupdate KB4023057 (20.6.2019)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[English]Microsoft hat zum 26. Juni 2019 das kumulative Update KB4509479 f\u00fcr Windows 10 Version 1809, Windows Server Version 1809 und Windows Server 2019 freigegeben. Erg\u00e4nzung: F\u00fcr \u00e4ltere Windows 10-Versionen steht der gleiche Fix unter anderen KB-Nummern zur Verf\u00fcgung.<\/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":[7646,7645,7644,7643,4378],"class_list":["post-219829","post","type-post","status-publish","format-standard","hentry","category-update","category-windows-10","tag-kb4509476","tag-kb4509477","tag-kb4509478","tag-update-kb4509479","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/219829","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=219829"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/219829\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=219829"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=219829"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=219829"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}