Xbox Wireless Adapter for Windows issues with Atmos/Sonic spatial audio

Windows 11 uses the same driver for wireless adapter as Windows 10. There won't be any difference no matter the version of Windows you choose. We need proper driver update or a new adapter

Yeah, you're right and the answer makes perfect sense.

but .siehawk's message gave me hope ^^

i just started playing shadow fo the tomb raider and i am having the audio cut outs. i will try out this 5.1 to see if it helps.

thanks for the tip!

Great workaround indeed! Finally I can use the headset for gaming. What a shame M$ does nothing about this issue!

End of January 22 have they at least look at this issue? Latest firmware, latest Win build still no spatial audio fix.

Still no solution (except the Voicemeeter trick) and the Headset is unusable out of the box.

Wired connection also cuts out after power cycling the headphones, then a PC reboot is required. This happens only on my AMD build tho, tested with my laptop there they work fine (wired only of course).

Awesome no one @ MS Semms to give a flying F about this topic.
I have a very simmilar problem to you BUT I don't even need to try to use spatial sounds, Games like Halo infinite or CP2077 will just have audio cut outs no matter what...
I have made several posts here with the answere "well sorry but you gotta write the support directly".
I have made a ticket with 343 and their answere was basically "well that sounds like a YOU problem".

Got a Trutlebeach 700 stealth 2 and this is the very last time I am buying anything from Turtlebeach and honestly... maybe even from microsoft. I am STUNNED how they just ignore a butt load of paying customers.

I have the same problem with the arctic 9x and windows 11 newest version...

After 15 pages there's still no real solution for this problem.

Yes we can disable spatial audio in the sound settings for the adapter, but if the game somehow forces it, you'll still get the drop-outs...

I'll try the Voicemeeter workaround as well and see if it works.

I'm also wondering whether Microsoft is taking this thread seriously?

Isn't there some other way to report this bug, so it actually reaches the department/driver team who could place this on their backlogs?

If yes, then I guess we should all start reporting over there right?

The more people submitting bugs, the bigger chances we have for a software/driver update which fixes this problem.

I dont know if there is any channel where they listen to this problem... I mean there are countless threads on here, reddit, other tech forums. But let me know if Voicemeeter works for you, I will give it a try on the weekend.

Yeah, its quite the shame this isn't being looked into. Perhaps the only way to get visibility is to have someone with a bigger social media following raise the issue. Otherwise all that happens is Microsoft shrugs and says its a problem of the headset maker, game maker etc. Meanwhile they make both the headset and games like Halo and Gears 5 that this has issues with.