Windows 10 kb5014023 is now available as an optional update to users in production channels. This optional update does not come with new features of the operating system. It can be obtained by setting up the application. As usual, you can also download the offline installer for windows 10 kb5014023 to install this patch.
Kb5014023 will not be installed automatically. It is marked as "Preview" cumulative update for a reason. Optional updates come with specific non security fixes that you should install only if you immediately need the bug fixes included in the patch.
If you do have the problems mentioned in the release notes, you can install them in advance or wait until the next "Patch Tuesday" update. Generally speaking, the optional updates are stable for most configurations.
If you check for updates today, you will see the following patches in the optional updates section:
2022-05 windows 10 21h2 cumulative update preview based on x64 system (kb5014023)
Windows 10 kb5014023 direct download link, 64 bit and 32-bit (x86):
Windows 10 kb5014023 (build 19044.1741) full update log:
As part of the optional update of windows 10 in May 2022, Microsoft is updating the built-in sorting function, which should solve the sorting problem that may affect Japanese half width katakana.
Another error has been fixed, which may prevent registration by disconnecting the Internet connection.
Microsoft has also fixed a problem that may run anycpu application as a 32-bit process. Another bug has also been fixed, that is, adding trusted users, groups or computers will fail, and the error message "the selected object does not match the type of the target source" will appear.
The above bug fixes are targeted at enterprises, but Microsoft has fixed some problems that will directly affect consumers.
For example, windows 10 build 19044.1741 has fixed a problem that caused file copying to be slower than usual. Copying files between partitions or drives is essential for anyone, but an error in the operating system has been slowing down the copy process.
Miscalculation of write buffers in the cache manager has been causing problems for users, and has been fixed in this release.
Similarly, a rare problem that caused excel and outlook to crash was fixed in this update. A related memory leak has also been fixed.
The following is a list of bug fixes in Windows 10 build 19044.1682:
Fixed a problem that affected the Internet Explorer mode window frame.
Fixed a problem that prevented internet shortcut updates on windows.
Fixed a problem that caused printing to fail at a low integrity level (lowil).
Fixed a problem that may affect the service reliability of the terminal services gateway (TS gateway).
Fixed a problem where the system would stop responding if the user quits the Microsoft onedrive account they are using.
Fixed a problem where BitLocker encryption does not work on devices that use the silent encryption option.
Microsoft has fixed a problem that affects Microsoft defender application protection (mdag) and Microsoft office And poor performance of mouse pointer in Microsoft edge. This error is obviously related to a function called virtual graphics processing unit (GPU), but it is not as common as it sounds.
A problem that caused yellow exclamation marks to appear in device manager has been fixed. This bug is obviously affecting Bluetooth remote devices with advanced audio distribution specification (A2DP).
In addition to the above bug fixes, Microsoft also fixed a problem that users cannot use recovery discs (CDs or DVDs) to recover their operating systems, especially if you create them using the windows 7 era backup and recovery feature in the control panel.
A common problem that affects some GPUs and crashes applications that rely on Direct3D 9 has been fixed. According to Microsoft's release notes, your application should not crash after deploying cumulative updates.
There is also an important error related to the performance of the problem. According to the release notes, Microsoft has fixed a problem that the windows management instrumentation (WMI) provider (clustmwmi.dll) caused high CPU utilization.