Thank you Jon, Luca, and Metal Jazz for your update to the situation. Mine has not been solved yet with the recent patches that came in April.
May I ask what your set up is and what version of USB driver you have? I have a Dell laptop (12th gen Intel chip) with Logitech 960 headset. I have experimented with updated drivers from NVidia, Genesys, and Intel audio drivers (From the Dell support site) with no solution.
Apparently there have been changes to the audio API... whether they are related to copilot or "audio enhancements" that use AI as part of the "studio pack" I do not yet know. Enterprise versions of Windows 11 without copilot are NOT exhibiting this issue. 24h2 has been nothing but problems since November of 2024 and I thought I was safe in Feb of 2025 but it only got worse in March and April patches. A total bucket of cr$$. it should have never been released into production as it obviously wasn't ready. I wonder if Microsoft's intent was to train their AI by sampling all these open mics?
I am also experimenting with turning off TLS2 network protocol. This makes copilot not have telemetry with the mother ship. The effect on the mic unmute issue is not conclusive yet. I would like to hear what others are experiencing. 1) the time spent by end users debugging Windows 24h2 updates should be compensated. You're paying you're programmers to cause this mess that we have to try to fix ourselves because Microsoft is silent. 2) if it is found out the audio issue is caused by Big Brother copilot listening, this should be a class action. Even if they try to hide behind a clause like "we periodically take audio samples in order to improve our service" which wasn't openly disclosed with 24h2.