Some users are experiencing a bug after updating to Windows 11 24H2 where sound levels are unexpectedly increasing to 100 percent, and it’s mainly happening on gaming-focused PCs. There are no error messages or indications other than suddenly loud volume.
As of a few days, Microsoft has confirmed the bug and found that it occurs when one or more of the following are true:
- Your PC has updated to Windows 11 24H2.
- You’re using the Creative Sound BlasterX G6 external USB digital audio converter (DAC) sound system.
- You manually put your PC into sleep mode and then manually wake your PC from sleep mode.
- You attach and then immediately detach the external DAC sound system from your Windows system.
- You adjust the volume of the external DAC sound system and then immediately detach the external DAC sound system from your Windows system.
According to Microsoft, this issue is due to a timing problem in the AudioEndpointBuilder service. No further details were given, but Microsoft is working on a fix and will provide more information as it becomes available on the issue’s support page.
Some users are experiencing a bug after updating to Windows 11 24H2 where sound levels are unexpectedly increasing to 100 percent, and it’s mainly happening on gaming-focused PCs. There are no error messages or indications other than suddenly loud volume.
As of a few days, Microsoft has confirmed the bug and found that it occurs when one or more of the following are true:
Your PC has updated to Windows 11 24H2.
You’re using the Creative Sound BlasterX G6 external USB digital audio converter (DAC) sound system.
You manually put your PC into sleep mode and then manually wake your PC from sleep mode.
You attach and then immediately detach the external DAC sound system from your Windows system.
You adjust the volume of the external DAC sound system and then immediately detach the external DAC sound system from your Windows system.
According to Microsoft, this issue is due to a timing problem in the AudioEndpointBuilder service. No further details were given, but Microsoft is working on a fix and will provide more information as it becomes available on the issue’s support page. Read More