Sorry to revive this thread, but I have seemingly the same or similar issue as this user: MS Teams (new, not classic) pinned to a DisplayFusion taskbar and acting up if using DisplayFusion 11. I don't experience any freezing of MS Teams since 11.0.3 or 11.0.4, but even with the new 11.1.0 there are issues with the display of video during video calls.
I can see the video captured from my webcam within the MS Teams device settings just fine, but in the pop-up window for calls it is just empty (see attached image). The video displays fine again if I downgrade to DisplayFusion 10.1.2 and restart MS Teams (restart is required).
If that is a DisplayFusion feature, then I don't know of it. I've attached the debug-info archive as generated by DisplayFusion 10.1.2. I've also tried the new 11.1.1 today, but it didn't fix the issue for me.
Hi, I installed 11.1.1 again and created the log. It starts just before I start up MS Teams, create the issue and then close the application and click the button to export. At around 19:55:19 the call-window was open and failed to show the video from my webcam. I then created the also attached screenshot of it using an application called "screenpresso".
Strange, nothing seems to stand out in the log, and I can't seem to reproudce this on my end. If you add Teams to the compatibility list in DisplayFusion and turn on "Disable application hooks", does the issue persist?
Strange, nothing seems to stand out in the log, and I can't seem to reproudce this on my end. If you add Teams to the compatibility list in DisplayFusion and turn on "Disable application hooks", does the issue persist?
I tried the application hooks and other compatibilty options without success. The only way to get the video to show in the call window with DisplayFusion 11.x installed is to not start MS Teams from the DisplayFusion taskbar shortcut. From a Windows taskbar shortcut or the startmenu it works just as it does from the DisplayFusion 10.x taskbar. Deleting the old shortcut from the DisplayFusion taskbar and creating a new shortcut has no effect.
