Windows 10: Updates KB4458469, KB4457136 (26.09.2018)

[English]Zum 26. September 2018 hat Microsoft die Kompatibilitätsupdates KB4458469 für Windows 10 V1803 und KB4457136 für Windows 10 V1709 veröffentlicht.


Anzeige

Ich interpretiere dies so, dass es sich um ein Re-Release handeln muss, da diese Updates unter den gleichen KB-Nummern bereits am 20. September 2018 für die jeweiligen Windows-Versionen freigegeben wurden (siehe Windows 10: Kumulative Updates (20. September 2018). Wobei diese Updates jetzt mit dem Datum 17. September 2018 in der Windows 10 Update History aufgeführt werden.

Update KB4458469 für Windows 10 V1803

Update KB4458469 für Windows 10 V1803 vom 26. September 2018 hebt die Betriebssystembuild auf 17134.320 (die vorherige Version erzeugte die 17134.319) und enthält folgende Fixes:

  • Addresses an issue that causes the prompt “You’ll need a new app to open” to appear. This occurs when reloading a website on a non-standard port by pressing Enter .
  • Addresses an issue that causes downloads to fail because Mark of the Web (MOTW) isn’t supported at the download location.
  • Addresses an issue that prevents the DefaultSearchProvider policy from working when the FirstRunPage policy is in use.
  • Addresses issue that causes the address bar to lose focus when a new tab is opened and the Allow web content on New Tab page policy is off.
  • Addresses an issue that prevents the Microsoft Edge Configure Password Manager policy from suppressing the Save password prompt when the policy is disabled.
  • Addresses an issue that causes downloads to WebDAV locations to fail.
  • Addresses an issue with the file previewer for .html, .mht, and email (MIME) attachments in Microsoft Outlook.
  • Addresses an issue that causes Internet Explorer security and certificate dialogs to display prompts in the background instead of the foreground in certain circumstances.
  • Addresses an issue that may cause the system to become unresponsive when applications call the EnableEUDC API.
  • Addresses an issue in multi-monitor scenarios that causes a spell checker context menu to appear on the wrong monitor. This issue occurs when the customer right-clicks a misspelled word in Internet Explorer.
  • Addresses an issue that occurs when entering Japanese characters in a remote desktop session (mstsc.exe).
  • Addresses an issue that occurs when using low-level mouse hooks with high integrity-level processes.
  • Addresses an issue that prevents custom keyboard layouts from working correctly.
  • Makes the visibility policy for the Settings Page available under User Configuration. The GPO is at the following path: User Configuration/Administrative Template/Control Panel/Settings Page Visibility
  • Addresses an issue that prevents some Bluetooth devices from pairing with Windows.
  • Addresses an issue in the Universal CRT that returns the expected output or a null character when calling _getch().
  • Addresses an issue in the Universal CRT that returns unexpected characters when calling the _findfirst() or _findnext() functions.
  • Addresses an issue in the Universal CRT that prevents some functions from accepting narrow input or producing proper output with certain ANSI Code Pages. This issue affects setargv.obj when using wildcard parsing and calls to get the current module name for debug windows. The issue also affects the following functions:
  • _chdir()
  • _exec()
  • _fullpath()
  • _loaddll
  • _popen()
  • _system()
  • _spawn() (and variants)
  • Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • Addresses an issue with the diagnostic pipeline for devices enrolled in Windows Analytics when the CommercialID registry key, “HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\DataCollection” is present.
  • Addresses an issue that prevents the App-V client’s scheduled task from syncing if the Device Guard lockdown policy is enabled.
  • Addresses an issue that may cause the Local Security Authority Subsystem Service (LSASS) process to stop working when attempting to process a malformed security identifier (SID).
  • Addresses an issue that causes a delay in unlocking or signing in to a computer that was moved to a different network. For example, a delay occurs when moving from a corporate LAN or WLAN to a home LAN where domain controllers can’t be reached.
  • Addresses an issue on some laptops that prevents sign-out from completing. The issue occurs when a customer signs out and immediately closes the laptop. As a result, when the laptop is reopened,  the device must be restarted.
  • Addresses an issue that occurs when enabling BitLocker from a local administrator account.
  • Addresses an issue on devices with fingerprint sensors that were upgraded from Windows 10, version 1709. After the upgrade, users can’t use the fingerprint sensor to log in.
  • Addresses an issue that causes some systems to take as much as 60 seconds longer to start. This occurs on systems that don’t have a smart card reader installed.
  • Addresses an issue that prevents customers from logging in to a Windows 10S device with a PIN after upgrading to Windows 10, version 1803. Customers see the error “Your PIN is no longer available due to a change to the security settings on this device.”
  • Addresses an issue that causes a Direct Access connection to fail when the client authentication certificate is stored in the TPM device.
  • Addresses an issue that causes the system to log negative events for drivers that are valid and should be trusted. The issue occurs when running Windows Defender Application Control (Device Guard) in audit mode.
  • Addresses an issue that causes a third-party VPN provider’s user interface to stop working after dynamically unloading Cryptui.dll.
  • Addresses an issue that causes logging on to a Remote Desktop Session Host Server to occasionally stop responding.
  • Addresses an issue that causes printing to an open or existing file to fail without displaying an error. This issue occurs when using Microsoft Print to PDF or XPS Document Writer.
  • Addresses an issue where a daily, repetitive task starts unexpectedly when the task is first created or starts when the task is updated.
  • Addresses an issue that prevents running subsequent actions when you create multiple actions in a task using Task Scheduler and the task is scheduled under the Stop the existing instance rule.
  • Addresses an issue with a task that has a repetition setting. The task fails to be scheduled and doesn’t start after disabling and re-enabling the task. The Next Run Time in Task Scheduler displays the correct time, but the task doesn’t start at that time.
  • Addresses an issue that prevents the debugging of minimized UWP applications.
  • Addresses an issue with Visual Studio UWP Deployments that displays the error “The operation could not be completed because an unexpected host ID was encountered”.
  • Addresses an issue that ignores the MM_DONT_ZERO_ALLOCATION flag. This issue leads to degraded performance, and, occasionally, error 0x139 appears.
  • Addresses an issue that causes NTLTEST, DCLOCATOR, or joining an Active Directory and SAMBA domain to fail when using the NetBIOS domain name. The error is “An Active Directory domain Controller (AD DC) for the domain %domain% could not be contacted”. This also addresses connection issues for applications that use mailslots to communicate.
  • Addresses an issue that occurs when using encrypted email. If the customer selects Cancel when first asked for a PIN, multiple PIN prompts appear before the prompt finally goes away.
  • Addresses an issue that prevents the Microsoft Help Viewer from rendering HTML content inside a Windows Help .chm file when the .chm file is stored on a network location.
  • Addresses an issue in which the lock screen shows a solid color instead of an image specified by a policy before a customer signs in for the first time.
  • Addresses an issue that causes Microsoft Edge to stop working when printing a PDF in a size 0 window.
  • Addresses an issue that causes Microsoft Edge to stop working and to close associated webpage tabs. This occurs when certain PDF documents have timing issues when loading.
  • Addresses an issue with a scheduled task that has an indefinite duration. The task starts immediately after it is created instead of starting at the time specified in the Triggers tab.
  • Addresses an issue where GetSystemTime() may sometimes return an invalid value after using SetSystemTime() immediately before.
  • Addresses an issue that occurs when using the “X509HintsNeeded” group policy to prepopulate the Username hint field. The Username hint field is unexpectedly empty when unlocking a machine after a successful logon. Username hint caching is expected to only work for lock and unlock scenarios and is not designed for logoff and logon scenarios.
  • Addresses an issue that fails to maintain the tile layout after upgrading to Windows 10, version 1803 from Windows 10, versions 1703 and 1607.
  • Addresses an issue that returns temporary values for the new Japanese Calendar Era.
  • Addresses an issue in which Background Apps settings the user configured are lost when the device restarts because of incorrect registry ACLs.
  • Addresses an issue that prevents Microsoft Centennial apps and some OS apps from displaying toast notifications.
  • Addresses an issue in which all Guest Virtual Machines running Unicast NLB fail to respond to NLB requests after the Virtual Machines restart.
  • Addresses an issue that prevents dual tunnel AlwaysOn VPN configurations that use trusted network detection from having both tunnels operational.

Kumulative Windows-Updates erfordern, dass Sie vorher das neueste Service Stack Update (SSU) für Windows installieren, bevor Sie das neueste kumulative Update (LCU) installieren. Dies hilft, mögliche Probleme bei der Installation der LCU zu minimieren.

Wenn Sie Windows Update verwenden, wird Ihnen automatisch die neueste SSU (KB4456655) angeboten. Um das eigenständige Paket für die neueste SSU zu erhalten, besuchen Sie den Microsoft Update Catalog. Probleme mit diesem Update sind Microsoft keine bekannt.

Update KB4457136 für Windows 10 V1709

Update KB4457136 für Windows 10 V1709 (und Windows Server 2016) hebt die Betriebssystembuild auf 16299.699 (das vorherige Release erzeugte die Build 16299.697) und enthält folgende Fixes:

  • Addresses an issue with the file previewer for .html, .mht, and email (MIME) attachments in Microsoft Outlook.
  • Addresses an issue that causes Internet Explorer security and certificate dialogs to display prompts in the background instead of the foreground in certain circumstances.
  • Addresses an issue that causes downloads to WebDAV locations to fail.
  • Addresses an issue that causes downloads to fail because Mark of the Web (MOTW) was not supported at the download location.
  • Addresses an issue that prevents Microsoft Narrator from accessing the contents of Windows Security dialogs displayed by a low integrity level process.
  • Addresses an issue that, in some cases, prevents installing encrypted .appx packages.
  • Addresses an issue that may cause the system to become unresponsive when applications call the EnableEUDC API.
  • Addresses an issue that occurs when entering Japanese characters in a remote desktop session (mstsc.exe).
  • Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • Enables reading the CommercialId registry key written by Windows Analytics onboarding and adds it to the JSON of telemetry events. Additionally, there’s a different server URL (v10c.data instead of v10.data) when the CommercialId is set.
  • Addresses an issue that prevents the App-V client’s scheduled task from synching if the Device Guard lockdown policy is enabled.
  • Addresses an issue that causes login to fail when using a smart card to log in to a Remote Desktop Server. The error is “STATUS_LOGON_FAILURE”.
  • Addresses an issue that causes a delay in unlocking or signing in to a computer that was moved to a different network. For example, a delay occurs when moving from a corporate LAN or WLAN to a home LAN where domain controllers aren’t reachable.
  • Addresses an issue that occurs when using encrypted email. If the customer selects Cancel when first asked for a PIN, multiple PIN prompts appear before the prompt finally goes away.
  • Addresses an issue that causes a Direct Access connection to fail when the client authentication certificate is stored in the TPM device.
  • Addresses an issue on some laptops that prevents sign-out from completing. The issue occurs when a customer signs out and immediately closes the laptop. As a result, when the laptop is reopened,  the device must be restarted.
  • Addresses an issue that causes the system to log negative events for drivers that are valid and should be trusted. The issue occurs when running Windows Defender Application Control (Device Guard) in audit mode.
  • Addresses an issue that may cause the Local Security Authority Subsystem Service (LSASS) process to stop working when attempting to process a malformed security identifier (SID).
  • Addresses an issue that causes logging on to a Remote Desktop Session Host Server to occasionally stop responding.
  • Addresses an issue that causes printing to an open or existing file to fail without displaying an error. This issue occurs when using Microsoft Print to PDF or XPS Document Writer.
  • Addresses an issue with scheduled tasks that don’t start at the time that they are configured to start on a specific day of the week.
  • Addresses an issue with a scheduled task that has an indefinite duration. The task starts immediately after it’s created instead of starting at the time specified in the Triggers tab.
  • Addresses an issue that prevents the running of subsequent actions in a task. This issue occurs when you create multiple actions in a task using Task Scheduler and the task is scheduled under the Stop the existing instance rule.
  • Addresses an issue with a task that has a repetition setting. The task fails to be scheduled and doesn’t start after disabling and re-enabling the task. The Next Run Time in Task Scheduler displays the correct time, but the task doesn’t start at that time.
  • Addresses an issue that may cause Service Control Manager (SCM) and Netlogon to stop working when one or more services are configured to run with domain credentials (service accounts).
  • Addresses an issue where a daily, repetitive task starts unexpectedly when the task is first created or starts when the task is updated.
  • Addresses an issue in which GetSystemTime() may sometimes return an invalid value after using SetSystemTime() immediately before.
  • Addresses an issue that occurs when using the “X509HintsNeeded” group policy to prepopulate the Username hint field. The Username hint field is unexpectedly empty when unlocking a machine after a successful logon. Username hint caching is expected to only work for lock and unlock scenarios and is not designed for logoff and logon scenarios.
  • Addresses an issue that fails to maintain the tile layout after upgrading to Windows 10, version 1709 from Windows 10, versions 1703 and 1607.

Kumulative Windows-Updates erfordern, dass Sie vorher das neueste Service Stack Update (SSU) für Windows installieren, bevor Sie das neueste kumulative Update (LCU) installieren. Dies hilft, mögliche Probleme bei der Installation der LCU zu minimieren.

Wenn Sie Windows Update verwenden, wird Ihnen automatisch die neueste SSU (KB4339420) angeboten. Um das eigenständige Paket für die neueste SSU zu erhalten, besuchen Sie den Microsoft Update Catalog. Probleme mit diesem Update sind Microsoft keine bekannt.


Anzeige

Ähnliche Artikel:
Adobe Flash Player: Update Version 30.0.0.154
Microsoft Office-Updates (4.9.2018)
Microsoft Security Update Summary 11. September 2018
Patchday: Updates für Windows 7/8.1/Server 11. Sept. 2018
Patchday Windows 10-Updates (11. September 2018)
Patchday Microsoft Office Updates (11. September 2018)
Microsoft Patchday: Weitere Updates zum 11. September 2018
Windows 10 Updates KB4464217 und KB4464218
Windows 7/8.1 und Server: Updates (20 Sept. 2018)
Windows 10: Kumulative Updates (20. September 2018

Patchday-Probleme Updates, WSUS (11. September 2018)


Anzeige


Dieser Beitrag wurde unter Update, Windows 10 abgelegt und mit , , , verschlagwortet. Setze ein Lesezeichen auf den Permalink.

12 Antworten zu Windows 10: Updates KB4458469, KB4457136 (26.09.2018)


  1. Anzeige
  2. Georg S. sagt:

    Vorbereitung für das Herbst-Update?

  3. Herr IngoW sagt:

    Das Update für W10 1803 KB4458469 war ja vorher (20.09.2018) nur im Windows-Update-Katalog zum Download. Beim normalen Win-Update kam er erst Heute.
    Die Liste der Änderungen ist ja richtig Lang. Bis jetzt noch kein Problem zu erkennen, mal noch Testen ob hier soweit alles geht.

    • Roland Moser sagt:

      Ich habe es am 20.9.2018 erhalten, aber auf dem normalen Weg. Den Windows Update Katalog kenne ich gar nicht :-)
      Und jetzt 27.9.2018wird es wieder installiert.

    • Roland Moser sagt:

      Ich habe den PC neu gestartet.
      Jetzt habe ich das Update 2 mal im Updateverlauf. 1 mal am 20. und einmal am 27.9.2018

  4. Anzeige

  5. Doc WP sagt:

    Ich hab das Update auch am 20.9. auf keinem meiner Maschinen automatisch angeboten gekommen, wohl aber heute auf allen PCs. Bisher keine Probleme bemerkt.

  6. Markus Klocker sagt:

    Achso, der rerelease war, weil sie die ganzen fixes beim ersten mal vergessen haben!

  7. L. v. Ay sagt:

    Ich bekam das KU letzte Woche auch nicht über WinUpdate; habe es aus dem Update-Katalog geholt.

    Heute bekam ich es mit Windows Update nochmal! Es ließ sich auch nochmal installieren! Im Updateverlauf sind auch beide Installationen aufgeführt.

    Hier gibt es eine Erklärung:
    https://www.pcwelt.de/a/windows-10-microsoft-fixt-sammel-updates,3452341

    • wufuc_MaD sagt:

      die erklärung ist, dass der link zum update ein anderer ist,

      es ist beim manuellen download eindeutig ein “-v2” drangehängt…

      der rekord soweit mir bekannt ist ein (logischerweise schädliches) v7 update.. für windows 7

      der knaller heute war nach dem durchlauf meines decrap skripts dass 5 wichtige updates danach wieder auf die maschine wollten, alle 23KB groß ^^

      aber der sack ist inzwischen zu, das kb2952664 erscheint nicht mehr in der “angebotsliste”. wer jetzt noch adressierungen und neue dateien für 7 von microsoft bezieht ist selbst schuld (und doof!)

      ich behaupte übrigens dass ms mit diesem “v2” noch ein paar sachen (man betrachte die changelog (kein wort von sicherheit)) die in der 1809 untergebracht sind testen wollen. aus meiner sicht sollte microsoft zerschlagen / verboten werden wegen gefährdung der nutzer / pot. sachschäden und verstoß gegen die allgemeine sittlichkeit durch mindestens fahrlässige fehlleistungen mit utopischer häufigkeit!

      ich hab die 1809 auch schon mal auf meinem notebook installiert, die aufhübschung durch den konsequenten dark-mode hat dann doch den ausschlag gegeben. aber die unistack dienste entrümpeln und WU entrempln wird viel arbeit. ;-)

      achja, kleiner tip noch, alternative zu execTI:
      ps://github.com/M2Team/NSudo

  8. Stefan sagt:

    Verlief soweit auch problemlos

  9. Anzeige

  10. Andreas R. sagt:

    KB 4458469 kam heute nach manueller Suche, die automatische Suche hat nichts angezeigt. Am 20.09. wurde das Update nicht angeboten.

    • wufuc_MaD sagt:

      mmm

      der windows update dienst “sollte” auf “manuell” stehen (womöglich hat das seit… jetzt, entsprechende auswirkungen) – darauf hingewiesen wird nicht.. widerspräche der roadmap (geldhagel durch kommende charged ms remote services)

      das update 320 ist nach wie vor for inssiders ;-)

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht.

Hinweis: Bitte beachtet die Regeln zum Kommentieren im Blog (Erstkommentare und Verlinktes landet in der Moderation, gebe ich alle paar Stunden frei, SEO-Posts/SPAM lösche ich rigoros). Kommentare abseits des Themas bitte unter Diskussion.