Windows 10 version 1903 has a new non-security update that addresses a problem in which users are unable to use USB Audio 2.0 multi-channel microphones in many applications, such as Voice Recorder.

Don't forget to whitelist our website. This notification will not disappear until you do so.
You hate ads, we get it. We do as well. Unfortunately, this is the only way for us to continue providing stellar content and guides on how to fix your biggest tech issues. You can support our team of 30 members to continue doing their job by whitelisting our website. We only serve a handful of ads per page, without obstructing your access to content.

KB4516421 is a servicing stack update (SSU). These updates are important for enhancing the reliability of the entire update process. Therefore, Microsoft recommends installing this update before installing the cumulative update released on September 10 Patch Tuesday.

So, you receive KB4516421 automatically through Windows Update. Also, keep in mind that this update is not available on Microsoft Update Catalog.

Fix sound recording problems in Windows 10 like a true technician with the help of our guide!

Microsoft explains that there is no need to have this update in a certain patch because it will be automatically updated on affected operating systems and services.

It is worth mentioning that KB4516421 is available for Windows Server Update Services (WSUS) as well.

KB4516421 solves a recent audio issue

After installing the cumulative update KB4515384, many users encountered a major problem with the audio in gaming. Like any other cumulative update, the latest patch was designed to solve several problems in Windows 10 May 2019 Update.

As we can see, it made things worse. Fortunately, KB4516421 saves the day and solves the recent problem that prevents people to use USB Audio 2.0 multi-channel microphones in apps such as Voice Recorder.

Moreover, the culprit might be a compatibility change, though there are not many reports on the bug to confirm this.

How did you found this update? Did it solve the issue for you? Do let us know in the comments section below!