Microsoft vient de publier une nouvelle mise à jour cumulative pour Windows 10 Fall Creators Update (v1709). Elle propose de nombreuses corrections de bugs.
L’installation de KB4457136 permet au système d’exploitation d’évoluer en version 16299.699. Vous pouvez vérifier ce chiffre en exécutant « winver » dans « Exécuter » (WIN+R).
Il est faut noter que cette mise à jour a été relancée en raison de ce que Microsoft appelle «une solution manquante». Un certain nombre de systèmes ont installer la mise à jour mais ont évolué en version 16299.697. S votre version n’est pas en 16299.699, assurez-vous de télécharger et installer le correctif le plus récent.
Windows 10 et KB4457136, des corrections
La note de version dresse une liste conséquente de changement, de corrections de bugs ou encore d’améliorations. Vous trouverez également des correctifs qui faisaient partie des mises à jour cumulatives précédentes, telles que celles concernant les problèmes d’installation des packages appx chiffrés ou encore des améliorations pour évaluer « l’état de compatibilité de l’écosystème Windows pour garantir la compatibilité des applications et des périphériques ».
Un changement important concerne les ordinateurs portables pour lesquels des soucis de « Sign-out process » sont rencontrés. Microsoft explique
«Nous avons résolu un problème sur certains ordinateurs portables qui empêche la finalisation de la signature. Le problème se produit lorsqu’un client se déconnecte et ferme immédiatement l’ordinateur portable. En conséquence, lorsque l’ordinateur portable est rouvert, le périphérique doit être redémarré »
Vous pouvez consulter la note de version en fin d’article. KB4457136 s’accompagne d’aucun problème connu. Tous les systèmes sont donc censés pouvoir l’installer correctement.
KB4457136, note de version
- 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 hintfield. 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.