Microsoft vient de publier une nouvelle mise à jour cumulative, KB4512941 pour Windows 10 v1903. Elle n’est pas inconnue puisque des tests ont été menés au travers de l’anneau Release Preview du programme Windows Insider.
L’installation de KB4512941 fait évoluer le système d’exploitation en version 18362.329. Sa note de version propose une longue liste d’amélioration. Vous trouverez tous les détails en fin d’article.
Parmi les différents correctifs proposés nous avons la correction d’un problème connu depuis plusieurs années. Il est à l’origine de l’utilisation du nom du package par défaut et non du nom réel après l’installation d’une application. A ce sujet Microsoft explique
“Nous avons corrigé un bug entraînant l’affichage du nom d’une application non prise en charge sous forme de texte par défaut, tel que
"ms-resource:AppName/Text"dans le menu Démarrer après la mise à niveau du système d’exploitation. “
En parallèle, un correctif vise Windows Sandbox. Ce nouvel outil de sécurité permet d’exécuter une application dans une instance distincte afin d’isoler tous ses processus. En raison d’un problème, Windows Sandbox peut, dans certains cas, « planter ». KB4512941 corrige le souci enfin de restaurer le comportement normal du logiciel.
“Nous avons corrigé un problème susceptible d’empêcher Windows Sandbox de démarrer correctement. L’opération se solde par l’erreur “ERROR_FILE_NOT_FOUND (0x80070002) “. Cela se produit sur les périphériques où la langue du système d’exploitation est modifiée au cours du processus de mise à niveau lors de l’installation de Windows 10 v1903.”
KB4512941 est proposée au travers du service Windows Update.
KB4512941 pour Windows 10 v1903, note de version
- Addresses an issue that displays a black screen when you use Remote Desktop to connect to a machine running Windows 10, version 1903.
- Addresses an issue that may prevent the Windows Sandbox from starting with the error, “ERROR_FILE_NOT_FOUND (0x80070002).” This occurs on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
- Increases the number of supported interrupts per device to 512 on systems that have x2APIC enabled.
- Addresses an issue that prevents some Trusted Platform Module (TPM) devices from being used for Next Generation Credentials.
- Addresses an issue that causes a workstation to stop working when you sign in using an updated user principal name (UPN) (for example, changing UserN@contoso.com to User.Name@contoso.com).
- Addresses an issue that prevents Windows Defender Advanced Threat Protection (ATP) from running automated forensic data collection when using registry-based proxy configuration.
- Addresses an issue that prevents Windows Defender Advanced Threat Protection (ATP) from sending cyberspace events for paths beginning with \\tsclient.
- Addresses a possible compatibility issue when Windows Defender Advanced Threat Protection (ATP) accesses case-sensitive Server Message Block (SMB) shares.
- Addresses a rare issue that occurs when the mssecflt.sys driver takes too much space on the kernel stack. This results in the error, “STOP 0x7F: UNEXPECTED_KERNEL_MODE_TRAP”, and Parameter 1 is set to “EXCEPTION_DOUBLE_FAULT.”
- Addresses an issue that leads to excessive memory utilization in Windows Defender Advanced Threat Protection (ATP).
- Improves the detection accuracy of Microsoft Defender ATP Threat & Vulnerability Management.
- Addresses an issue in which Windows Defender Application Control will not allow third-party binaries to be loaded from a Universal Windows Platform application. CodeIntegrity event error 3033 appears as, “Code Integrity determined that a process () attempted to load that did not meet the Store signing level requirements.”
- Addresses an issue that causes devices to have truncated device names when Autopilot provisioning automatically assigns a name to them.
- Addresses an issue in which the product description of Windows Server 2019 was incorrect when queried using slmgr /dlv.
- Addresses an issue that causes the Windows Management Instrumentation (WMI) class Win32_PhysicalMemory to report that 32 GB memory chips have a missing Capacity value.
- Addresses an issue that prevents you from copying and pasting compound documents (formerly OLE objects) between an application that hosts the RichEdit control and other applications.
- Addresses an issue that prevents certain games from leveraging Spatial Audio capabilities.
- Addresses an issue that fails to provide a cursor when you select a text input element using touch.
- Addresses an issue that may cause the name of an unsupported application to appear as default text, such as “ms-resource:AppName/Text” in the Start menu after upgrading the operating system.
- Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.
- Addresses an issue with downloading digital rights management (DRM) files from certain websites using Microsoft Edge and Internet Explorer.
- Improves the user experience and app compatibility so that more Win32 apps will work with Windows Mixed Reality.
- Addresses an issue with LdapPermissiveModify requests, which fail to make Active Directory (AD) group membership changes if the Lightweight Directory Access Protocol (LDAP) client uses the Security Identifier (SID) syntax. In this scenario, Active Directory returns a “SUCCESS” status even though the change did not occur.
- Addresses an issue that may prevent devices from starting when they start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM). The error is, “Status: 0xc0000001, Info: A required device isn’t connected or can’t be accessed.”
- Addresses an issue that may prevent devices from starting up or cause them to continue restarting if they are connected to a domain that is configured to use MIT Kerberos realms. Domain controllers and domain members are both affected.
- Addresses an issue that may cause the following to stop responding:
- Applications that were made using Visual Basic 6 (VB6).
- Macros that use Visual Basic for Applications (VBA).
- Scripts or apps that use Visual Basic Scripting Edition (VBScript).
You may also receive an “Invalid procedure call” error.
