This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
accessory center.desktop bridge.device service.exe freezing MS teams application.
When I use the Microsoft Modern Wireless Headset 8JR-00001 with MS Teams call it freezes the MS teams application. I unplug the USB receiver that it comes with then re-plug it into the computer then it works. I have tried the following as a work around:
When I got to the Microsoft accessory center I reset the headset to factory default and it resolves some of issues that were reported.
The other fix I have found is to connect the headset via Bluetooth
please let me know if anyone else has had this issue.
I am starting to look at this application : accessory center.desktop bridge.device service.exe
to see if this has something to do with this.
What has not worked is : removing MS teams and clearing out all folders that have files after the uninstall of the MS teams APP.
I opened a new box and got a new headset and that still didnt work.
*******************************************************************************UPDATE Aug 2023*******************************************************
For my environment the issue has now gone away with Microsoft sending the update to our tenant. For each user that was using the work around (Bluetooth or a different brand of headset) the dongle is now working once again. If your org still is having issue please open a formal ticket using with the Admin for of the Microsoft Teams. Then I would refer them to this thread for support.
thanks for helping guys
-Joshua R.
Managing sound and video settings during Teams meetings and calls for optimal communication
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Sorry I should have mentioned, we have already had to swap users to wired headsets or direct blue tooth connections as the dongles have become useless to us.
I am having this issue as well.
With the USB Link and Microsft Teams headset Teams will freeze about 90% of the time trying to log into a conference call. I went back to my wired logitech usb headset for now and it works fine.
I've uninstalled and reinstalled teams, the usb reciever, Cleared the applications cache etc it is so frustrating as it was working fine until a month or two ago and now this expensive headset is uselesss to me.
I don't know if Microsoft have started pushing out potential fixes, but none of our Teams calls are going through at all, no matter wireless/wired/dongle/bluetooth.
We have found the only fix is to push users onto the pre release of Teams which in itself is hit and miss as there's no time frame on when this applies to the user. We have also found this means that calls cannot be transferred to CQ's as Teams shows unknown user once you select a CQ and then fails to transfer.
This is interesting. I have been on the 'pre' release of Teams for a few months now. I didn't start seeing this issue immediately after upgrading, but consistent with others - I've been seeing it since late June. In my case - it happens roughly 3-4 times a day and I just unplug dongle and plug back in.
I don't know if Microsoft have started pushing out potential fixes, but none of our Teams calls are going through at all, no matter wireless/wired/dongle/bluetooth.
We have found the only fix is to push users onto the pre release of Teams which in itself is hit and miss as there's no time frame on when this applies to the user. We have also found this means that calls cannot be transferred to CQ's as Teams shows unknown user once you select a CQ and then fails to transfer.