Pretty soon, Windows 10 is going to get its own version 22H2, just like Windows 11 has. Until then, however, Microsoft needed to take care of some problems. This bug that we are referring to has actually been triggered by the Patch Tuesday update rollout, so something clearly needed to be done.

A closer look at OOB builds 19042.2132, 19043.2132, and 19044.2132

Just as in the case of Windows 11 (KB5020387), Microsoft has released a new update for Windows 10 devices as well, in the form of KB5020435. And, exactly like in the new OS, this patch is here to address an issue with Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. Needless to say, the highlights in builds 19042.2132, 19043.2132, and 19044.2132 are the same for Windows 10 20H2, 21H1, and 21H2. As you know, this update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

Highlights

Addressed an issue that might affect some types of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. These connections might have handshake failures. For developers, the affected connections are likely to receive one or more records followed by a partial record with a size of less than 5 bytes within a single input buffer. If the connection fails, your app will receive the error, SEC_E_ILLEGAL_MESSAGE.

Known issues

Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later.

After installing this update, some Windows devices might have issues with audio not working. Some affected Windows devices might have no audio, but other affected Windows devices might only have issues on certain ports, certain audio devices or only within certain applications. Most affected audio devices drivers have the audio enhancements setting disabled before installing this update or the sound device driver has issues with the audio enhancements feature.

This is what we are looking at for the moment, Nothing too much or over the top, as thie is simply an OOB update. Don’t forget to report any other issues you might come across, in order for Microsoft to address and improve the overall OS experience for us all. This is everything you can expect if you are a Windows 10 user. Leave a comment below if you found any issues since installing this Insider build.

Name * Email * Commenting as . Not you? Save information for future comments
Comment

Δ