I'm surprised I'm having to state this but a screenshot showing "Quest 3S" does not guarantee the correct physical device, driver, or audio endpoint is actually being used.
After updates, software can
Re-enumerate devices,
Reuse cached profiles,
Mislabel headset variants,
Bind audio to stale / virtual endpoints.
It’s entirely possible for a Quest 3 to appear as a 3S (or vice-versa) while the underlying audio device fails to initialise correctly. This is a known class of issue with Link-based audio routing.
That’s why update timing, headset confirmation, and device changes matter, they’re used to identify whether the problem is:
Driver re-registration
Audio endpoint mismatch
Runtime failure
Or a post-update regression
There is a reason why a lot of basic information is confirmed in many fields, not just support. Basic diagnostic steps before guessing at fixes.
If the goal is to actually solve the issue, narrowing those variables is necessary.