- Microsoft has confirmed that an error is taking audio on some PCs
- It is affecting all Windows 11 versions, and also Windows 10, mainly pressing those who use a DAC with their PC configuration
- A solution is in process, they tell us
Microsoft has confirmed that Windows 11 has an audio error (which we report yesterday), a failure that can eliminate the sound of the PC completely, and now it is clear that this affects multiple versions of Windows.
That means not only those in Windows 11 24h2 (an update that is still being implemented), but people who execute 23h2 and 22h2, and also Windows 10, which makes this an unusually widespread error, for saying at least.
This problem was first noticed by Windows Last and is on the prowl within the cumulative updates of January 2025 for these versions of the operating system.
The technology site was found with the problem after installing the January update for Windows 11 (24h2), with which the audio of its PC stopped working immediately.
Apparently, this error mainly affects those with a DAC Audio use (digital to analog) connected through USB, but can happen to any Windows 11 (or 10) user who takes the last patch.
As seen in Windows last, Microsoft has confirmed the problem, stating that: “After installing this security update, you can experience problems with USB audio devices. This problem is more likely to experience if you are using a DAC based on the USB 1.0 audio controller in its audio configuration. “
Unfortunately, there is no solution, and the only way to prevent your audio from being torpedo is to eliminate external DAC (assuming that you are using one, and this is what the problem is causing). In other words, simply connect the audio device directly to your PC, instead of through the DAC.
Microsoft also points out: “We are working on a resolution and we will provide an update in an upcoming version.”
ANALYSIS: A RARE OF UPDATE DONE
This is a strange for a couple of reasons. First, it is unusual to see an error that interrupts each available version of Windows 11, and Windows 10, which represents an alarming dominoes.
Second, the January update does not bring anything on the path of new characteristics (to any of these versions of the operating system). It is a very simple patch that applies security corrections, and that is. Therefore, it really should not cause any problem, but clearly, it is.
Because? Well, your assumption is as good as mine, but if you want to listen to my stab in the dark, it is that someone has been adjusting something deep inside the windows as part of those security measures. Why do I say that? Since the error is present in all versions, returning to Windows 10, surely it must have been an ancient and central part of the operating system code base that was adjusted (and broke something).
Whatever the case, this is another discomfort for Windows 11 users, particularly those in 24h2, some of whom have been experiencing a very difficult time lately, with a seemingly implacable flow of errors that are dragged into the general direction of those those Users. More recently, that includes another audio error and a lot of evil that has been visited in PC players in one way or another.
Some of those 24h2 users are doing a lot? I would say that it is likely, particularly the players, but I hope that the dentition problems caused by what I suppose is that the transition under the cape to the Germanio platform (introduced with 24h2, and a key element for co -pilot+ PC ) Soon it will begin to settle.
However, in the case of this audio error, it clearly has nothing to do with Germanio that sees its generalized presence outside 24h2. With luck, Microsoft’s promised solution will not take long.
