The Windows 11 24H2 update remains inaccessible for some users. Microsoft acknowledges that an audio bug is still preventing its deployment to some PCs. A solution is still pending, several months after the problem appeared.
The updates Windows updates often bring useful new features, but also unexpected ones. When a technical problem is detected, Microsoft blocks the installation to prevent more serious malfunctions. These blocks generally concern specific cases, such as an incompatible hardware component or software. In some cases, the resolution is quick. But sometimes the fix takes several months to arrive.
This is the case with the Windows 11 24H2 update for certain devices equipped with Dirac Audio technology. The issue has been known since December 2024. It affects a specific file, “cridspapo.dll,” which causes audio output to be completely disabled after installation. Built-in speakers, Bluetooth speakers, or wireless headsets stop working. Worse still, neither Microsoft nor third-party applications recognize these devices. While waiting for a fix, these PCs remain stuck at the upgrade stage.
Microsoft confirms that it continues to block Windows 11 24H2 at Due to a bug with Dirac Audio
Microsoft has just changed the status of this bug in its official dashboard. The problem is no longer considered partially fixed, but rather confirmed. This means that the update remains unavailable for affected devices via Windows Update. The block is still active under the identifier 54283088. No corrective driver has been released to date. The only alternative is to manually force the installation, a solution reserved for advanced users who know the basics. perform in the system registry.
This announcement comes just days after the lifting of another block on Windows 11 24H2. This one affected games like Asphalt 8 or certain titles using an outdated version of Easy Anti-Cheat, which caused crashes. With these problems having been resolved, players can now install the update. However, users affected by the audio bug will have to wait still, with no clear indication of when it will be resolved.
0 Comments