Forum Discussion
7/17/2020 - Latest Teams update breaks Virtual Cameras - Microsoft Teams Version 1.3.00.18164
- Jul 31, 2020
https://answers.microsoft.com/en-us/msteams/forum/all/microsoft-teams-mac-os-client-is-not-recognizing/d9e863be-d9a4-4d03-a4b8-1b5c7df58828?auth=1
Solution for running two separate terminal commands seem to work in here for me.
Please a have a look.
Temporarily, I was able to completely remove the updated version and was thankfully presented with the slightly older version 1.3.00.15561 which restored virtual camera capabilities. I've worked to fuddle up the teams updater daemon to hold off for a couple of versions to hopefully have the functionality restored.
eRayHarrison Would it be possible for you to post instructions for how you successfully downgraded and are blocking the auto-update for now? Thank you!
- AWMooneyJul 28, 2020Copper Contributor
AndrewBonham Did you ever get any answer to how to downgrade Teams for Mac to a version that doesn't break the OBS Virtual Camera?
I can get the OBS Virtual Camera to show up and operate in the preview devices, but as soon as I connect it freezes.
- StmpyJul 31, 2020Copper Contributor
AWMooney I managed to get around this (temporarily) on macOS by doing the following;
- In Word, click on "Help"
- Click on "Check for updates"
- Uncheck "Automatic updates"
- Restored a previous version of Teams from TimeMachine
This allowed me to continue to use Teams on an older version which worked with Virtual Cameras (iglasses in my case) and stopped the autoupdate from MS.
I hope that helps?
Obviously this means that no MS updates will load automatically but hopefully, MS will sort the Teams issue out soon...
- eRayHarrisonJul 31, 2020Brass Contributor
Stmpy Thank you for this information! Unfortunately, in our organization, Teams updates roll out separately and there's no way for us to turn them off. Only by editing the Teams update plist file to set updates to 'No' and turning off system writes to that file afterwards allowed me to keep a previous version. Hopefully, the next update will restore that functionality.