Windows 10: Sony WH-1000XM5 mic stopped working after update to 22H2

A few days ago my Windows 11 updated to 22H2 and my Bluetooth Headphones Sony WH-1000XM5 microphone isn't working anymore. A few points to consider:Before the update, everything was working as expectedBefore the update, Windows and apps like Teams or Discord would show me 2 devices: Headphones WH-1000 MX5 Stereo and Headset WH-1000XM5 Hands-Free Audio. Now it only shows Headphones WH-1000 MX5 Stereo.Note: Only the second option would work to use the microphoneI have another computer with Windows 10 installed, and the above scenario applies to it. It shows the two options and the seco

:)

 

Can't use Sony WH-1000XM5's microphone on PC

Hi, I can use my Sony WH-1000XM5's microphone on my work laptop (win11), but somehow the microphone doesn't work on my personal computer (win11). Is there any settings that I need to check to resolve this?

What I've done

1. re-pairing the headphones

2. re-installing the bluetooth drivers for the headphones

3. making sure my PC is fully updated

Please help. Thank you

 

Microphone on Sony WH 1000 XM4 stopped working on Windows 11

I've been using a Sony WH 1000 XM4 with Windows 10 and (after the upgrade) Windows 11 without problem for approx. 2 years now. Both for output and inpupt.

Recently, something broke. Maybe one of the latest upgrades. Symptoms:

• Output still working fine.
  
• Input via XM4 no longer working. I don't get any input via that device whatsoever. Tried via
  
• Mic Test reports "Apparently, your microphone is being used or blocked by another application. To start your microphone, you must temporarily close that application."
  
• Windows Sound Recorder app says "No audio input source available".
  
• Troubleshooter says: "Audio services not responding" and doesn't offer any further help.
  
• Mute button on my keyboard has no effect.
  
• Built-in mic still working.
  

Current workaround:

• I put the XM4 mic to "don't allow".
  
• That way, I use the internal mic but use the headset for audio output.
  
• Also, the mute button on the keyboard works again that way.
  
• Update: The workaround above doesn't work. When I do that, the internal mic doesn't work either. So I need to enable the XM4 input device but then use the internal mic. That way, the internal mic at least works. The mute key on the keyboard doesn't work however and software such as Google Meet reports that it can't access the mic settings. Bummer.
  

Things I tried:

• Basically everything listed here 18 Ways to fix Audio Services not responding issue on Windows 11 and here https://thegeekpage.com/fix-audio-services-not-responding-in-windows-10/
  
• Some sources also suggest to turn off "handsfree telephony". If I do that however, the headset disconnects altogether.
  
• Also installed the very latest Bluetooth drivers https://www.intel.com/content/www/u...-bluetooth-for-windows-10-and-windows-11.html
  

Specs:

Processor 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz 2.80 GHz

System type 64-bit operating system, x64-based processor

Edition Windows 11 Pro

Version 22H2

Installed on ‎2022-‎10-‎15

OS build 22621.819

Experience Windows Feature Experience Pack 1000.22636.1000.0

Any help would be much appreciated, thanks!

 

Bluetooth Audio Output/Input for Sony WH-1000XM4 Not Working

I have the same problem with Sony WH-1000XM4 headphones with my Windows 11 PC. It was working all fine and suddenly stopped working.

The device connects via bluetooth and is detected by the PC, the sound is coming fine, but its not enabling the microphone.

1. Checked all microphone settings to ensure those are enabled.
   
2. The headphone works fine on other devices - so no problem with the headphone itself
   
3. I have already reset the headphone and paired from scratch - still the problem is not resolved
   
4. Updated all the drivers - still the problem is not resolved.
   
5. I tested a different bluetooth headphones with the PC and it works fine.
   

So the problem is specific to Sony WH-1000XM4 headphones with Windows 11 PC and it started happening after an update around late April.