This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have upgraded to Windows 11 24H2 (26100.712) and am having issues with getting my USB Audio systems to stay awake. Whenever there is no sound playing, my USB audio system turns itself off, thinking that there is no power to the USB port that it's connected to.
I've changed the setting in advanced power options to disable selective suspend, but this does not do anything. I've also disabled powering down the drive setting in Device Manager (for USB ports), and still no luck.
My machine is pretty much useless as a work machine now, as my USB audio (Bose Companion 5) system turns off within minutes of no audio, silencing my machine so I'm unable to hear notifications or calls.
This bug has only happened since installing 24H2, I've checked device manager and there seems to have been new drivers installed with this update, so potentially some changes there.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thanks Ruud, great to hear that solution works.
Prefer my machine updated to the latest version with regards to security fixes, etc. This is a lack of taking responsibility at Microsoft to actually fix this bug, since nowhere I've read yet that Microsoft acknowledges this bug exists.
Great to put out a large upgrade of Windows, but at least they could take customers seriously, which is lacking.
Regards,
Berry
They know about it now. In my support calls they agreed that 24H2 was the culprit, as they helped me roll back. But if and when fixed, I will have no idea that this has been done. I stop pausing updates, and I take a chance. Either the upgrade works, or I have to go through rolling back again.
I have researched the problem with the BOSE Companions 5's more. First, this page lists the versions:
My PC was updated to 24H2 on 11/22, with the update dated 11/21. As you can see along the left of that page, there were many 24H2 versions that my PC was not given.
The first rollback attempt failed, as the rep did a restore point first, which negated the built-in rollback option. My next rollback, with a new rep, required an ISO file for a new install. Running winver, I now find I was rolled back to 24H2 with the version dated Sept. 10th. Now I have the problem of the pod going orange after five minutes of no sound, and then red about four minutes thereafter. But as I play music, this is not a big deal. What happened with the Nov. 21 update was no sound at all. So an update between these dates completely broke the sound. And that is what I reported, not the pod turning off. Which I can live with.
As for what I plan to do. There aren't going to be updates in December. So come January I will look at the link above, and when I see a new version, I will read it, and consider making a try. And expect the built-in rollback to work.
So, I was upgraded to 24H2 release and lost my integrated echo cancelation microphone from my HP E273m monitor, that comes through USB, but speakers still work. Reverting is not an option, so any way to get a fix for this as it seems widespread?
What does this problem have to do with the BOSE Companion 5 speakers? That is what this thread is on.
