Accueil / Actualités / Logiciels / Windows 10 / Windows 10 build 18317 débarque, le bureau évolue
Windows 10 - Insider Preview Build
Windows 10 - Insider Preview Build

Windows 10 build 18317 débarque, le bureau évolue

Microsoft vient de publier une nouvelle construction de la prochaine mise à niveau de Windows 10, Windows 10 19H1. Elle est proposée dans le cadre du programme Windows Insider et s’adresse aux utilisateurs inscrits sur l’anneau rapide.

Windows 10 build 18317 introduit plusieurs nouveautés importantes pour le bureau notamment la séparation de la recherche et de Cortana.

Windows 10 Build 18317

Ce changement est susceptible de réduire l’exposition globale de Cortana. De son côté le menu Démarrer bénéficie désormais de son propre processus nommé « StartMenuExperienceHost.exe ». Auparavant il faisait partie de « ShellExperienceHost.exe »

Dona Sarkar, responsable du programme Windows Inside, explique

« Cela présente un certain nombre d’avantages, notamment la simplification du débogage et l’isolation du menu démarrer […]  Cela fait maintenant quelques semaines que nous menons l’expérience et nous avons constaté des améliorations mesurables de la fiabilité c’est pourquoi nous la distribuons à tout le monde. »

Windows 10 build 18317, de nombreuses corrections de bugs

Cette build 18317 propose aussi le glisser-déposer dans l’application Paramètres pour une installation rapide des polices.

De son côté la page des paramètres du programme Windows Insider a été simplifié pour aller à l’essentiel.

Windows 10 Build 18317

Microsoft propose également pas mal de nouveauté pour la console Windows.

Comme souvent à tout ceci s’ajoute des tas de petites choses ici et là et la résolution de nombreux problèmes. Enfin nous sommes dans la cadre du programme Windows Insider et tout n’est pas parfait. Le système d’exploitation s’accompagne de soucis.  Vous  trouverez tous les détails ci-dessous.

Windows 10 build 18317, note de version

Windows Console Updates

We’ve made several fixes & improvements in Windows Console in and leading up to build 18317, including:

  • Fixed spurious text artifacts being displayed when running cscope in a Linux VM via ssh
  • Fixed GitHub issue 296 where the incorrect mouse button ID was being reported when a mouse button was released, resulting in an “unexpected mouse-drag behavior” regression
  • Fixed GitHub Issue 313, enabling colors above index #15 to be set via VT OSC 4
    • Colors <= 99 fixed in this build
    • Colors > 99 fixed in up-coming build
  • Corrected sizing issues for Linux alt-buffer apps (e.g. vim, emacs, etc.) resulting in more reliable resizing
  • Fixed some issues with Consoles growing in height if scroll-forward is disabled
  • Fixed ConPTY, enabling underline VT sequences to now pass correctly, allowing ConPTY-enabled apps (e.g. VSCode’s integrated terminal) to correctly receive and display underlined text
  • Made ConPTY flush its output buffer before terminating ensuring apps receive all input and display correct output
  • When running Tmux, correctly restore state after Win + D, resulting in Tmux’s last line of text rendering correctly
  • Fixed Console to preserve a Console window’s currently colored text when executing Cmd.exe
  • If using raster fonts, Console now correctly preserves the user’s font after running .NET Core code (which defaults to UTF-8 codepage 65001)
  • Correct how Console scrolls text region, fixing how text is rendered in Linux’ `screen`
  • Significantly improved performance of ConPTY – perf now very close to “raw pipe”

General changes, improvements, and fixes for PC

  • We fixed an issue resulting in File Explorer unexpectedly having a lock on USBs when trying to safely eject them.
  • We fixed an issue resulting in frequent bugchecks (GSODs) in the last two flights, citing an error with bindflt.sys.
  • We fixed an issue resulting in frequent bugchecks (GSODs) in the last flight, citing error KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION.
  • We fixed an issue resulting in not being able to connect to VMs using Hyper-V console after upgrading to recent flights. This issue also impeded the ability to connect to VMs with Enhanced Sessions enabled.
  • We fixed an issue resulting in some full screen games showing a black screen in recent flights even though they worked in windowed mode.
  • We fixed an issue resulting in CDP User Service periodically unexpectedly using a high amount of CPU in recent flights.
  • We fixed an issue causing text in the Windows Security app to be incorrect or potentially missing altogether.
  • We fixed an issue from recent flights where clicking the network button on the sign-in screen didn’t work.
  • We fixed an issue resulting in certain devices not being able to wake from hibernation recently. There were two possible symptoms on wake if you were impacted – one was a black screen, one was a screen that continued to say “hibernating…”.
  • We fixed an issue resulting in Display Settings crashing in recent builds. If you were impacted, this would have also had the symptom that clicking System or Ease of Access from the main Settings page may crash Settings.
  • We fixed an issue with certain touch keyboard languages where pressing AltGr + [any key] on the full layout would dismiss the touch keyboard.
  • We fixed an issue where Windows Sandbox wouldn’t launch on PCs with multiple GPUs.
  • When Scan Mode is on and Narrator is on a slider, the left and right arrows will decrease and increase the slider. Up and down arrows will continue to navigate to the previous or next paragraph or item. Home and End will move the slider to the beginning or the end.
  • The Narrator list of headings command now works as expected in Chrome.
  • We improved Narrator support for Microsoft Teams.
  • For cursor and pointer, fixed returning to the right mouse pointers when changing back to the original size and colors.
  • We fixed an issue where some devices would fail to install an update with error code If you are updating from 18309 or newer this issue will be fixed for this update, if you are updating from a build prior to 18309 it will be fixed for the next update.

Known issues

  • Windows Subsystem for Linux (WSL) will likely cause a bugcheck (GSOD) when using certain Linux binaries such as VI and tar. If you require WSL to work, please pause taking flights until the issue is fixed [UPDATE 1/17] WSL should work correctly on this build – our apologies for the mix up. 
  • The Windows Security app may show an unknown status for the Virus & threat protection area, or not refresh properly. This may occur after upgrade, restart, or settings changes.
  • Launching games that use anti-cheat software may trigger a bugcheck (GSOD).
  • Clicking your account in Cortana Permissions doesn’t bringing up the UI to sign out from Cortana (if you were already signed in) for some users in this build.
  • Creative X-Fi sound cards are not functioning properly. We are partnering with Creative to resolve this issue.
  • When attempting to update this build some S Mode devices will download and restart but fail the update.
  • Night light functionality is impacted by a bug in this build. We’re working on a fix, and it will be included in an upcoming build.
  • When you open Action Center the quick actions section may be missing.
  • Windows feature update may fail but show up as a successful update in Windows Update history page. If this happens you will see more than one successful install for the same update in the history page.
  • When performing Reset this PC and selecting Keep my files on a device that has Reserved Storage enabled the user will need to initiate an extra reboot to ensure Reserved Storage is working again properly.
  • There is an issue impacting a small number of users enrolled in Microsoft Intune where they may not receive policies. Those policies are not applied and left in a “pending“ state on the server. The workaround is to go to Settings/Accounts/Access work or school and “Disconnect” your Azure AD account and then re-enroll.
  • Some Realtek SD card readers are not functioning properly. We are investigating the issue.
  • Update Orchestrator Service stops working periodically. A fix will be included in an upcoming build. As a result of this issue, you may see an error on Windows Update Settings saying that the update failed to restart. If you see this, restarting using the power menu in Start (“Update and restart”) should work, although there’s a chance that it won’t.
  • Closing the lid to a laptop and re-opening can cause icons in the task bar to appear blank. To fix this open task manager and restart explorer.exe or reboot.
  • If you download a theme from Microsoft Store, it won’t appear in Themes Settings.

Known issues for Developers

  • If you install any of the recent builds from the Fast ring and switch to the Slow ring – optional content such as enabling developer mode will fail. You will have to remain in the Fast ring to add/install/enable optional content. This is because optional content will only install on builds approved for specific rings.

À propos Jérôme Gianoli

Journaliste issu d’une formation scientifique. Aime l'innovation, la High Tech et le développement durable. Soucieux du respect de la vie privée.

Laisser une réponse

Votre adresse email ne sera pas publiéeLes champs requis sont surlignés *

*

x

Check Also

Filtre Windows Defender SmartScreen de Windows 10

Windows 10, comment débloquer un fichier bloqué par le filtre Windows Defender SmartScreen ?

Windows 10 s’accompagne de tout arsenal de sécurité. La plupart de ces ...

Navigateur Microsoft Edge

Windows 10, comment définir Edge Chromium ou Firefox comme navigateur par défaut ?

Microsoft propose depuis quelques jours une première Preview de son nouveau navigateur ...

Windows 10 de Microsoft

Windows 10 et KB4493509 / KB4493464, Microsoft confirme un nouveau bug

Microsoft vient de confirmer un nouveau problème dans plusieurs de ses mises ...