Windows 10 Build 19044.1741 se déploie, quoi de neuf ?

Forum dédié à Windows 10
Répondre
Avatar du membre
chtimi054
Administrateur du site
Administrateur du site
Messages : 5815
Enregistré le : ven. 26 juil. 2013 06:56
A remercié : 73 fois
A été remercié : 143 fois
    unknown unknown

Windows 10 Build 19044.1741 se déploie, quoi de neuf ?

Message par chtimi054 »

[size=150]Windows 10 Build 19044.1741 se déploie, quoi de neuf ?[/size]

[align=center][img]https://zupimages.net/up/22/22/tf3u.jpg[/img][/align]

Microsoft publie une nouvelle construction de Windows 10 21H2 au travers du canal Release Preview du programme Windows Insider. Windows 10 Build 19044.1741 est disponible au travers d’une mise à jour, KB5014023.

La mise à jour KB5014023 vise les PC Windows 10 inscrits sur le canal Release Preview. Il s’agit d’une mise à jour cumulative. Son installation permet à Windows 10 d’évoluer en version 19044.1741. Ce numéro est important car il permet de s’assurer que le téléchargement et l’installation se sont déroulés avec succès. Vous pouvez le dénicher en lancement « winver.exe » dans Executer (WIN+R).

[b]Windows 10 et KB5014023, quoi de neuf ?[/b]

Son contenu n’apporte pas de changement ni de nouveauté. Microsoft corrige seulement un problème. En clair nous avons qu’un correctif. Il s’attaque au code de contrôles du système de fichier (FSCTL_SET_INTEGRITY_INFORMATION_EX) qui ne gère pas correctement son paramètre d’entrée. A cela s’ajoute tous les correctifs de la semaine dernière. Vous trouverez tous les détails en fin d’article.

Enfin Microsoft indique qu’il n’y a aucun problème connu. Il s’agit d’une « mise à jour C ». Elle est donc facultative. Windows Update ne l’installe pas automatiquement sur le PC. Il est nécessaire d’intervenir dans Windows Update. Ce type de mise à jour est généralement publiée au cours de la troisième ou de la quatrième semaine du mois. Elle permet de tester les dernières corrections de bugs et améliorations non liées à la sécurité.

[quote][b]KB5014023 – note de version[/b]

New! We introduced new sorting version 6.4.3, which addresses the sorting issue that affects Japanese half-width katakana.
We fixed an issue that prevents the file system control code (FSCTL_SET_INTEGRITY_INFORMATION_EX) from handling its input parameter correctly
We prevented users from bypassing forced enrollment by disconnecting from the internet when they sign into Azure Active Directory (AAD).
We fixed an issue that might run an AnyCPU application as a 32-bit process.
We fixed an issue that prevents Azure Desired State Configuration (DSC) scenarios that have multiple partial configurations from working as expected.
We fixed an issue that affects remote procedure calls (RPC) to the Win32_User or Win32_Group WMI class. The domain member that runs the RPC contacts the primary domain controller (PDC). When multiple RPCs occur simultaneously on many domain members, this might overwhelm the PDC.
We fixed an issue that occurs when adding a trusted user, group, or computer that has a one-way trust in place. The error message, “The object selected doesn’t match the type of destination source” appears.
We fixed an issue that fails to display the Application Counters section in the performance reports of the Performance Monitor tool.
We fixed an issue that might affect some apps that use d3d9.dll with certain graphics cards and might cause those apps to close unexpectedly. [UPDATED 6/1] We fixed a known issue that affects certain GPUs and might cause apps to close unexpectedly or cause intermittent issues that affect some apps that use Direct3D 9. You might also receive an error in the Event Log in Windows Logs/Applications, and the faulting module is d3d9on12.dll and the exception code is 0xc0000094.
We fixed a rare issue that prevents Microsoft Excel or Microsoft Outlook from opening.
We fixed a memory leak issue that affects Windows systems that are in use 24 hours each day of the week.
We fixed an issue that affects the IE mode window frame.
We fixed an issue that prevents internet shortcuts from updating.
We fixed an issue that causes an Input Method Editor (IME) to discard a character if you enter the character while the IME is converting previous text.
We fixed an issue that causes print failures when a low integrity level (LowIL) application prints to a null port.
We fixed an issue that prevents BitLocker from encrypting when you use the silent encryption option.
We fixed an issue that occurs when you apply multiple WDAC policies. Doing that might prevent scripts from running when the policies allow scripts to run.
We fixed an issue that affects the behavior and shape orientation of a mouse cursor for Microsoft Defender Application Guard (MDAG), Microsoft Office, and Microsoft Edge. This issue occurs when you turn on a virtual graphics processing unit (GPU).
We fixed an issue that might cause the Remote Desktop client application to stop working when you end a session.
We fixed a reliability issue in the Terminal Services Gateway (TS Gateway) service that randomly causes clients to disconnect.
We deployed search highlights to devices that are domain-joined. For more information about the feature, see Group configuration: search highlights in Windows. You can configure search highlights at the enterprise scale using Group Policy settings defined in the Search.admx file and Policy CSP – Search.
We fixed an issue that displays the wrong image for the Input Method Editor (IME) mode indicator icon when you turn on the Font Mitigation policy.
We fixed an issue that causes a yellow exclamation point to display in Device Manager. This occurs when a Bluetooth remote device advertises the Advanced Audio Distribution Profile (A2DP) source (SRC).
We fixed an issue in which the Cluster Windows Management Instrumentation (WMI) provider (ClustWMI.dll) generates high CPU usage in WMIPRVSE.EXE.
We fixed an issue that causes Microsoft’s deduplication driver to consume large amounts of nonpaged pool memory. As a result, this depletes all the physical memory on the machine, which causes the server to stop responding.
We fixed an issue that causes file copying to be slower.
We fixed an issue that might cause a system to stop responding when a user signs out if Microsoft OneDrive is in use.
We fixed a known issue that might prevent recovery discs (CD or DVD) from starting if you created them using the Backup and Restore (Windows 7) app in Control Panel. This issue occurs after installing Windows updates released January 11, 2022 or later.
[/quote]

[size=85]merci à [url=https://www.ginjfo.com/actualites/logic ... f-20220603]Ginjfo [/url][/size]
Répondre