Forum Discussion
Solved
Unable to select microphone or speaker device in Microsoft Teams (Windows 10)
Microsoft Teams is currently unable to make/receive calls due to the app being unable to set a Microphone or speaker device.
The 'Audio Devices' profile within settings is set to 'Custom Setup' and no other option is available in the drop down (screenshot attached).
When try to continue using the custom setup, no devices are available as the drop-downs are unclickable (screenshot attached).
Other useful info:
- OS: Windows 10 - latest
- Microsoft Teams Version: 1.2.00.24753 (64 bit). It was last updated on 22/09/2019.
- I have uninstalled and re-installed teams.
- Audio devices work fine in all other applications
- No other application is using the devices when Teams is being tested.
I posted about this on the regular Microsoft community forums and someone pointed out that their issue was that Teams seemingly has an incompatibility Elgato's 4K60 Pro Mk2 Capture Card, and this was definitely the issue for me.
No solution still, other than simply removing the cards from my system (not really an option)... so the workaround is just using the browser version of Teams which is inferior, especially for screen sharing and video calls. Hopefully they can fix it sometime, but seeing the volume of people coming forward with this bug I'm sure there is a variety of other hardware that is incompatible.
Nevertheless, quite odd especially considering that said hardware works with the browser version of Teams which must share almost entirely the same code base.
FWIW my problem was with VMWare Horizon taking exclusive control of my devices. The only resolution was to uninstall the VMWare Horizon agent from my PC. After that Teams was one again able to connect to my camera, mic, and speakers.
- This is also the case for me. Thanks for sharing.
Going to the Sound Mixer Options in Windows 10 (which appears to possibly be named the App Volume device preferences. Applications with volume, output, and input devices are listed here. This started functioning again in the Teams app after switching the Output device setting from the default to the particular one for my headset.
My brother has the same problem on a dell laptop with Teams (mic/headset not working & settings greyed out); but it works perfectly in most places & fails only in one particular location - his parents' house. The problem persists whether he uses the home Wi-Fi here, or uses his phone as a mobile hotspot; using the phone as a hotspot works in other places & the mic functions normally. I'm curious how this problem can occur intermittently, & at just one location.
Thanks to all who've posted troubleshooting advice & fixes.
Louja
- I am also facing the same issue
Microphone does not work with Teams
Sometimes it starts working but most of the time it does not work
However it works fine every time I test on GoogleHi Priyank2065 ,
Per the thread - in my case it was a matter of uninstalling ChromaCam and uninstalling/reinstalling Teams. So... check that you don't have a camera "app" that might be causing the issue (stick with a generic cam... The only thing that ChromaCam allowed was custom/tailored backgrounds, which was nice, but not worth crashing Teams...).
JW
- Uninstall Chroma Cam or any similar applications
EliottI tried this but was still unable to figure it out.
...until i realized that devices are often "locked"
In Win10 open sound settings.
Go to Manage Sound devices.
Check the "output" and "input" lists of devices, and make sure you have nothing blocking or weird devices there.
For me under "input" i had "Elgato Game capture" , I clicked that and selected DISABLE, as well as disabling my Elgato Sound Capture application that was running.
Also went into the device properties and REMOVED the abilitiy for software to take exclusive control of the Headset/mic i was using.
After fiddling back and forth suddently i got the drop-down boxes.
Removing TEAMS from the machine did nothing.
So most likely if you cannot see ANY devices in the TEAMS list of devices...it means:
- Something has taken exclusive control of your device (disable setting)
- Something is locking your sound devices from being used by other apps (check setting)
- Make sure no other possible apps that uses sound input and output are running like games, capture, sound recorders, speech recognition etc. Make sure Teams is the only app running that is going to use the device.
- Most likely teams may show devices again. Try a few reboots too. With shutdown.
Toffys Service
Norway
The culprit for me was definitely chromacam.me - it is totally incompatible with Teams. I tried everything else and the only thing that worked was to uninstall chromacam and to delete all remnants of it from my system - Teams then resumed working perfectly!!
- It was Chromacam for me too.
Clicking the Reset Chromacam button in the app resolved the issue.
Chromacam is still installed and working. As a few others have mentioned, ChromaCam was the culprit for me. If you use Teams, do not install ChromaCam, it'll lock up mic and camera settings in Teams. After uninstalling ChromaCam, Teams started worked again.
I have the same issues since yesterday. I could not select my regular speaker (Audinst HUD). Whenever I select it, it changes my microphone to the speaker instead. Screenshot an image below. Can anyone help me with this?
This happened to me last night, i am still unable to fix it, I am a tutor and need this to work.
Has anyone been able to fix this yet?I can confirm that by disabling the pci express channel my Elgato 4k60 was installed in fixed my issue, thanks for the feedback on this.
No amount of install, uninstall or registry or deleting of user data worked for me.DougBrooks Eliott Jonathan Lawton Adam03 StreamTech
Elgato has released beta drivers that fix this issue.
The behavior is still odd for the first 30-60 seconds after opening the app, but then it finally lets you choose your input / output devices, even lets me set the 4K60 Pro MK.2 as my camera.
As far as I can tell they only released this driver for the HD60 Pro and the 4K60Pro MK.2, but maybe there was never an issue with their other cards (HD60 S, 4K60 Pro MK.1). Keep in mind that the driver is technically in beta from what I've been told, so you may experience other bugs elsewhere.
But for me this has completely resolved the issue and I have yet to run into any other issues with this driver installed, what a relief.
4K60 Pro MK.2 Driver:
https://edge.elgato.com/egc/windows/drivers/4k60-pro-mk2/Game_Capture_4K60_Pro_MK2_1.1.0.191.0.exe
HD60 Pro Driver:
https://edge.elgato.com/egc/windows/drivers/hd60-pro/Game_Capture_HD60_Pro_1.1.0.191.exe
