Windows 10 Build 19044.1739 (KB5014023) in Release Preview channel fixes app crash

Windows Insiders on Windows 10 21H2 received a new cumulative update today, and perhaps notably in this release is a further attempt to fix a dependency on d3d9 on some graphics cards. dll when the application closes unexpectedly. This update also includes preventing Microsoft Excel and Outlook applications from opening.

New build 19044.1739 (21H2) (KB5014023) is optional and tests whether certain non-security fixes will make it through the next Patch Tuesday, and is now available through the Release Preview channel.

This update includes the following improvements:

• New! We have introduced a new sorting version 6.4.3, which resolves a sorting issue affecting Japanese half-width katakana.
• We prevent users from bypassing forced registration by disconnecting from the internet when logging into Azure Active Directory (AAD).
• We fixed an issue that could cause AnyCPU applications to run as 32-bit processes.
• We fixed an issue that prevented Azure Desired State Configuration (DSC) scenarios with multiple partial configurations from working as expected.
• We fixed an issue affecting remote procedure calls (RPC) to the Win32_User or Win32_Group WMI classes. Domain members running RPC contact the primary domain controller (PDC). This can overwhelm the PDC when multiple RPCs occur simultaneously on many domain members.
• We fixed an issue that occurred when adding a trusted user, group, or computer with one-way trust. The error message "The selected object does not match the type of the target source" appears.
• We fixed an issue that prevented the Application Counters section from displaying in the Performance Monitor tool's performance report.
• We fixed an issue that could affect some applications that use d3d9.dll with certain graphics cards and could cause those applications to close unexpectedly.
• We fixed a rare issue that prevented Microsoft Excel or Microsoft Excel from opening Outlook.
• We fixed a memory leak that affected Windows systems that were used 24 hours a day, every day of the week.
• We fixed an issue affecting IE modal window frames.
• We fixed an issue that prevented Internet shortcuts from updating.
• We fixed an issue that caused the Input Method Editor (IME) to discard characters if you entered them while the IME was converting previous text.
• We fixed an issue that caused printing to fail when a low integrity level (LowIL) application printed to an empty port.
• We fixed an issue that prevented BitLocker encryption when you used the silent encryption option.
• We fixed an issue when applying multiple WDAC policies. Doing so may prevent the script from running when the policy allows the script to run.
• We fixed an issue affecting the behavior and shape orientation of the Microsoft mouse cursor in 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 could cause the Remote Desktop client application to stop working when you end your session.
• We fixed a reliability issue in the Terminal Services Gateway (TS Gateway) service that randomly caused clients to disconnect.
• We deploy search highlights to domain-joined devices. For more information about this feature, see Group Configuration: Search Highlights in Windows. You can configure search highlights enterprise-wide using Group Policy settings defined in the Search.admx file and Policy CSP – Search.
• We fixed an issue where the Input Method Editor (IME) mode indicator icon displayed the wrong image when you turned on font mitigation policies.
• We fixed an issue that caused a yellow exclamation mark to appear in Device Manager. This occurs when a Bluetooth remote device advertises an Advanced Audio Distribution Profile (A2DP) source (SRC).
• We fixed an issue that caused the Clustered Windows Management Instrumentation (WMI) provider ( ClustWMI.dll) to produce high CPU usage in WMIPRVSE.EXE.
• We fixed an issue that caused Microsoft's deduplication driver to consume large amounts of non-paged pool memory. As a result, this uses up all the physical memory on the machine, causing the server to stop responding.
• We fixed an issue that caused file copying to be slower.
• We fixed an issue that could cause the system to stop responding when users exited Microsoft OneDrive while in use.
• We fixed a known issue where recovery discs (CDs or DVDs) may not start if you create them using the Backup and Restore (Windows 7) application in Control Panel. This issue occurs after installing Windows updates released on or after January 11, 2022.

This release does not contain any known issues and, as stated, there are no new features. To check and see which version of Windows 10 you're running, just type winver in the Windows Search box on the taskbar (or right-click Start and select Run, then type winver ). It should read "Version 21H2".

This is an optional "C update", usually released in the third or fourth week of each month, designed to test new bug fixes and other improvements to non-security issues . C updates are optional and Windows Update will not automatically install them on your PC if they are available outside the Windows Insider channel.

The above is the detailed content of Windows 10 Build 19044.1739 (KB5014023) in Release Preview channel fixes app crash. For more information, please follow other related articles on the PHP Chinese website!