Windows 10 21H1 : la première mise à jour propose beaucoup de correctifs

 

Microsoft annonce une trentaine de correctifs pour la version 21H1 de Windows 10.

Windows 10 21H1 : la première mise à jour propose beaucoup de correctifs

La mise à jour 21H1 de Windows 10 est disponible en téléchargement. Si elle ne contient pas énormément de nouveautés, elle a le mérite d’intégrer toutes les modifications du système à date, avec les mises à jour de sécurité. Une bonne base en attendant la mise à jour Sun Valley attendue pour la fin de l’année. Après le démarrage du déploiement, la nouvelle mise à jour KB5003214 vient corriger un grand nombre de petits problèmes.

Une grande liste de correctifs

La mise à jour fait passer Windows 10 à la version 19042.1023. Elle est pour le moment proposée au programme Insider dans le canal Release Preview. On imagine que la version stable et grand public sera déployée dès le début du mois de juin, à l’occasion du « Patch Tuesday » de Microsoft.

Sur son site officiel, Microsoft décrit une trentaine de changements importants tout de même. Difficile de juger quels sont les bugs les plus répandus qui ont été corrigés avec cette mise à jour. On peut toutefois relever un support des fichiers images .hif (HEIF), une correction au niveau des métadonnées de fichiers FLAC (de l’audio lossless), plusieurs problèmes de fuites mémoire et des corrections pour les casques Bluetooth audio.

Voici le verbatim en anglais des corrections proposées dans cette mise à jour.

  • We fixed an issue with the just-in-time (JIT) behavior of jscript9.dll.
  • We fixed an issue that might prevent users from opening phone apps that are pinned to the taskbar. This issue occurs after they update to Windows 10, version 2004 and then use the Your Phone app.
  • We fixed an issue that prevents certain Win32 apps from opening when using the runas command.
  • We fixed an issue that prevents certain Win32 apps from opening when the “BlockNonAdminUserInstall” Group Policy is turned on.
  • We fixed an issue that displays progressive web application (PWA) icons as blank when you pin them to the taskbar.
  • We fixed an issue that fails to properly manage memory for touch input before a session ends.
  • We fixed a memory leak in ctfmon.exe that occurs when you refresh an application that has an editable box.
  • We fixed an issue that prevents a touch device from working as a serial mouse in multiple monitor situations.
    We fixed an issue that unexpectedly displays the Settings page text “Let’s finish setting up your device” at startup.
  • We fixed an issue that might display items on the desktop after you have deleted them from the desktop.
    We fixed an issue that prevents users from viewing the Mouse settings page after the Settings Page Visibility Group Policy is set to “showonly:easeofaccess-mousepointer”.
  • We fixed an issue in Safe Mode that prevents users from signing in if Web Sign-in is enabled.
  • We fixed an issue in Active Directory (AD) Admin Center that displays an error when it lists many organizational units (OU)or container objects and PowerShell Transcription is enabled. The error message is, “Collection was modified after the enumerator was instantiated”.
  • We fixed an issue that causes Screen Readers to report the wrong UI information. This issue occurs because UI Automation reports inaccurate property information for some controls, such as IsDialog and IsControl.
  • We fixed an issue that fails to apply BitLocker encryption automatically using a Group Policy. This issue occurs on external drives that have a master boot record (MBR) active boot partition.
    We fixed a memory leak issue in PKU2U that causes cluster nodes to run out of memory.
  • We fixed an issue with the Autopilot Reset command taking too long to process after it has been sent.
  • We fixed an issue that might prevent the Windows Dynamic Host Configuration Protocol (DHCP) Server from offering a lease to a DHCPv6 client after the client moves to a different virtual LAN (VLAN).
  • We fixed an issue that prevents a task from working correctly when you set the condition “Start only if the following network connection is available” for the task.
  • We fixed an issue that might display the “Device Removed” error when Direct3D developers use the SetStablePowerState() API in Windows Developer Mode.
  • We fixed an error that might cause video playback to fail when you switch from an external high-dynamic-range (HDR) display to a built-in non-HDR display.
  • We fixed an issue that fails to apply the spatial audio effect to sounds when you enable spatial audio.
  • We fixed an issue with noise when you enable spatial audio and use Bluetooth USB headphones.
    We fixed a metadata encoding issue that causes Free Lossless Audio Codec (FLAC) music files to become unplayable if you change their title, artist, or other metadata.
  • We added support for the .hif file extension for High Efficiency Image File (HEIF) images.
  • We fixed an issue that might cause a system to stop working when using Remote Desktop for USB redirection of an Xbox One controller.
  • We fixed an issue that might cause a RemoteApp window to flicker or move to another area of the screen when using touch or pen input.
  • We fixed an issue with the PerfMon API that might cause handle leaks, which slow performance.
  • We fixed an issue that might cause endless replication when you promote a new domain controller and the Active Directory Recycle Bin feature is enabled.
  • We fixed an issue that sporadically prevents the Resource Host Subsystem (RHS) from registering network name resources in the Domain Name System (DNS). As a result, Event ID 1196 appears.
  • We fixed an issue with devices that were configured using mobile device management (MDM) RestrictedGroups, LocalUsersAndGroups, or UserRights policies. These devices incorrectly continue to receive the policy after you use MDM to remove the configuration profile that has the policy. As a result, users of the affected devices might have incorrect group memberships and UserRights assignments or other symptoms. This issue occurs after installing Windows updates from October 29, 2020 and later.
  • We fixed an issue that prevents users from receiving geographic location information even when all the geolocation UI settings are enabled correctly, and the device contains a location sensor.
  • We fixed an issue that fails to register a DNS update to an A record and a PTR when Azure virtual machines update against corporate DNS zones.
  • We fixed a timing issue that might cause a RemoteApp to intermittently duplicate characters that were entered on the local keyboard or pasted from the Windows clipboard.

Cette mise à jour est disponible dès à présent dans le programme Insider.

Les derniers articles