Dirac Audio Glitch Finally Silenced In Windows 11 24H2

Microsoft has resolved a Windows 11 24H2 problem with devices using Dirac audio as the 25H2 update waits in the wings.

Dirac, according to Microsoft, "enhances audio clarity and precision." However, if you were using Windows 11 24H2 with affected hardware, the only audio you would hear was the sound of silence.

Affected devices included integrated speakers as well as Bluetooth headsets and speakers.

The glitch, according to Microsoft, stemmed from cridspapo.dll, a component of the software required for the devices. By the end of 2024, Microsoft placed a compatibility hold to prevent Windows 11 24H2 from being offered to affected devices.

After a lengthy gestation period, a new driver is now available via Windows Update, and this particular safeguard hold has been removed, just in time for the release of Windows 11 25H2, which uses the same servicing branch as Windows 11 24H2. The main difference between the two is that new features for 25H2 are included in updates for 24H2, just in a disabled state.

• Nano11 cuts Windows 11 down to size, grabbing just 2.8 GB of disk space
• Microsoft readies Windows 11 25H2 while Windows 10 circles the drain
• HP bottom line fattens up on a diet of AI PCs and Windows 11
• How Windows 11 is breaking from its bedrock and moving away

Microsoft has been clearing the house when it comes to flaws with Windows 11 24H2. Woes that arrived with the August 2025 Update – unexpected UAC prompts and borked NDI streaming – were resolved in the September 2025 Update. Considering that 25H2 and 24H2 use the same servicing branch, the experience should be smoother for administrators – unless Microsoft churns out another update that causes fresh breakage.

Still, it's good to see the company fixing issues introduced in its own software. The resolution of the Dirac audio problem means there is no avoiding Windows 11 24H2.

That said, Microsoft is not averse to applying a safeguard hold when bugs are found. In April, it noted compatibility problems with the sprotect.sys driver and said it was working with SenseShield Technology to deal with them.

The troubles manifested as blue or black screen errors, or affected devices became unresponsive. Five months on, Microsoft is still investigating the issue, and affected devices are blocked from Windows 11 24H2. ®