[24h2 / lts 2024] YeaLink WH62 Win 11 volume forced to 0?

[Garacesh]

We've purchased a YeaLink WH62 (MSTeams flavour) for a user here.

 

Plug the device in via USB, devices appear in device manager

 

If I fire up a Teams test call, the base station lights up, the headset icon turns green, and if I press the pre-programmed mute button on the headset, the mute light toggles on and off. Wunderbar!

.. except, there's no audio input. Output works. I can hear the test teams man tell me to record a message, but there's no mic.

 

Finish the call, end up with this message:

 

Windows settings shows the device, but the volume is fixed at 0. If I move the slider, it jitteringly resets to 0.

 

Sound settings in old-style control panel show the device, but there's no volume bar next to it.

If I go into the Properties, Levels, the levels page is blank. The typical Microphone array slider isn't there.

If I set the device to Listen, no audio plays back.

 

In the Yealink USB Connect software, I've set the Call Device to be Soft Phone and PC Softphone Teams rather than its default Desk phone (which I assume requires the other USB port to be plugged into a physical hardlined or IP phone), and successfully loaded the latest firmware.

I've disabled Automatically adjust mic sensitivity in Teams and ensured Microphone is set to Headset Microphone (Yealink WH62)

 

Pulling my hair out over this one. I found one page that said don't use Yealink USB Connect, but that bore no fruit.

 

Edit: Oh, and, yes, we've confirmed the microphone works on a non-Windows device. Much to my chagrin.

Edit2: It works on Windows 10 Why does it work on 10 and not 11

Edited October 29, 2024 by Garacesh

[Str8buttah]

@Garacesh

I was having this exact same issue with my WH62 on Windows 11. I found several items across the Interverse but nothing seemed to fix it. I wanted to come out here and provide what fixed it for me in case anyone else comes across this post and is pulling their hair out.

 

My problem was related to the Microsoft Teams Setting under devices to automatically adjust mic sensitivity. I basically just had to turn that value off and that allowed me to adjust the Microphone Input Volume slider.

 

Once I did that step, I was able to turn that setting back on and it continued to work as expected. Now I don't recall if that was the exact steps. There may have been some form of turn that setting off, then plug in the headset, adjust the slider, then turn it back on but I know turning that setting off adjusting the slider allowed my microphone to start working again.

 

I know it has been sever months since you posted this and perhaps you found the solution already but if not, I hope this works.

[Garacesh]

I didn't ever find the solution. The user in question I was prepping the headset for was on a W10 device so it turned out this was a non-issue (perhaps it would have been but he may have disabled this setting himself at some point), but with the demise of 10 I expect it'll crop up again as we migrate users, so much appreciated nonetheless 🙂

Edited April 4, 2025 by Garacesh

[Str8buttah]

Well, a small update. I logged in this morning and had the same issue. So, it seems as though you need to disable the 'Intel Smart Sound Technology for USB Audio' device as well in Device Manager. I had done that yesterday by itself and it did not fix the issue, so I assumed that was not the problem and I turned the device back on after getting the Mic working with the steps above. I'll keep using it the next couple of days with this disabled and see how it goes.

 

Also here is my Hardware in case that matters for anyone.

 

Dell Latitude 5450 - BIOS v1.12.2
Windows 11 24H2

Teams (new) - Don't think the version matters as long as it is the New Teams because I have had this issue for a while and just got back to troubleshooting yesterday.

 

 

 

[dudetwoshoes]

I created an account to let you know - I found this solution after many Google searches. Disabling this driver solved my problem!!! Thank you!!!!

[Str8buttah]

Glad it helped. Mine is continuing to work and I have not seen any negative issues with keeping that device disabled since I posted.

[DreadVector]

I ran into the same problem on a 24H2 machine and disabling Intel Smart Sound Technology for USB Audio in Device Manager fixed it. No issues since and the mic works normally.