Hello everyone
is there a solution for this issue?
Or any recommendation on how to handle it?
Hi Carlos and everyone else on this thread. hopefully the following information is helpful for you and your company(ies).
In our internal investigations we were able to determine that this issue happens on Windows 10 PCs that use Realtek audio.
Further
profiling revealed that it was (unfortunately) likely caused by an
issue with background windows process that attempts to disable the currently installed; known good Realtek vendor
drivers to activate an old generic Microsoft driver that is
well documented to not work. It was observed that this activity was not
present when MS meetings was closed, but was triggers when the
application attempts to enumerate audio devices. On some system the action was fairly infrequent; but on other system as frequently as every 10 seconds. Frustrating at any frequency for the end users affected by this.
We surmised that the failed attempt
to change the driver momentarily breaks connection to the audio device that MS
Teams is using. Because the applications isn't written in a fashion to
re-cycle the interrupted device, it remains
broken until the user changes the microphone device to another option
and then back again.... only then to be re-broken on the next cycle.
Given
that this is an interaction is occurring between two articles of Microsoft software,
our engineering team determined that there was a less than 1% chance
that it would ever be fixed. The decision was made that the company would not
continue to waste valuable time and resources on trying to find a
fix or hold out hope that requests for support from Microsoft would not just fall of deaf ears. This thread serve only as the documentation rendering that judgement
as objectively correct, given that it has been a known issue for approximately a year and Microsoft hasn't acknowledged, attempted or
otherwise delivered any form of workaround or solution.
We ultimately solved this issue by:
- Start -> Control Panel -> Add/Remove programs; uninstall Microsoft Teams.
- Visiting the website and installing anyother teleconference solutions. a non-exhaustive list to choose from here:
- Zoom
- Skype
-
Microsoft Teams
- Cisco Webex Meetings
- GoToMeeting
- BlueJeans Meetings
- Google Hangouts Meet
- Jabber
- Jami
- join.me
- UberConference
- Sending
setting auto-responder emails at corporate level such that incoming emails containing Microsoft Teams urls/links are sent indicating that organization doesn't
participate in calls using the solutions.
Hopefully that information is helpful. While the solution wasn't the desired one, it absolutely produces the desired outcome. We have not experienced any repeat issues with telepresence since performing these steps.