Last month, we reported that Microsoft had acknowledged that a new bug in Windows 11, version 24H2, automatically increased the audio volume level to 100%.
While the company is still working on a fix to resolve this audio issue, a new issue has been observed on some devices containing Dirac Audio.
The newly discovered audio output bug is affecting devices equipped with Dirac Audio technology with the software component cridspapo.dll, which is part of these devices’ audio processing software, following the installation of Windows 11, version 24H2.
“After installing Windows 11, version 24H2, some users reported that their device’s integrated speakers, Bluetooth speakers, and Bluetooth headsets stopped functioning. They also reported that both first-party and third-party applications didn’t recognize these devices,” the company wrote in a new support document published on the official Windows Health Dashboard website.
For those unaware, Dirac Audio is a digital sound improvement technology that aims to better audio clarity, spatial separation, and precision.
To safeguard users from encountering this audio issue, Microsoft has applied a compatibility safeguard hold on devices containing Dirac Audio with cridspapo.dll. These devices will not be offered to install Windows 11, version 24H2, via the Windows Update release channel.
To know whether your computer has a compatibility safeguard hold, go to Start > Settings > Windows Update > select Check for Windows updates.
If your computer is placed on a compatibility safeguard hold, you will see the message, “Upgrade to Windows 11 is on its way to your device. There is nothing that requires your attention at the moment. Once the update is ready for your device, you’ll see it available on this page.”
Microsoft strongly recommends that the affected users not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue is resolved.
Currently, there are no workarounds for the newly discovered audio bug. Microsoft says that once the manufacturer releases the driver addressing this issue, it will partner with the manufacturer to offer the new version of the driver (cridspapo.dll) via Windows Update to fix the audio issue.
Once the issue is resolved on end-user devices, the Redmond giant will lift the safeguard hold, blocking the upgrade to version 24H2.
It is important to note that the newly discovered audio issue only affects client systems running Windows 11 version 24H2, not those upgrading from Windows 10 to Windows 11 version 23H2.
