https://www.displayfusion.com/Discussions/RSS/?TopicID=019cf8d4-db5c-76de-ab68-bf135ec88043 DisplayFusion RSS: App compatibility and newer M365 applications - specifically Teams Thu, 21 May 2026 14:07:16 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=019cf8d4-db5c-76de-ab68-bf135ec88043 https://www.displayfusion.com/Discussions/View/app-compatibility-and-newer-m365-applications-specifically-teams/?ID=019cf8d4-db5c-76de-ab68-bf135ec88043#2 Tue, 17 Mar 2026 18:27:42 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/app-compatibility-and-newer-m365-applications-specifically-teams/?ID=019cf8d4-db5c-76de-ab68-bf135ec88043#2 DisplayFusion You can use an asterisk as a wilcard and it should catch it, like this: *teams.exe ]]> https://www.displayfusion.com/Discussions/View/app-compatibility-and-newer-m365-applications-specifically-teams/?ID=019cf8d4-db5c-76de-ab68-bf135ec88043 Mon, 16 Mar 2026 22:47:05 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/app-compatibility-and-newer-m365-applications-specifically-teams/?ID=019cf8d4-db5c-76de-ab68-bf135ec88043 DisplayFusion Ok, so I've just been dealing with this for a while and it's not a fault or bug. The issue is that for some of Microsoft's newer apps, in my case I'm dealing with Teams, when the app gets updated it creates the new version in a folder structure based on the version of the app. Where the issue comes in is that the app compatibility in Display Fusion is strictly path based. So, every time the app is updated the compatibility settings no longer work.

I was wondering if it might be possible to ask that the path requirement be changed to allow just the executable name instead of the full path. That would be an improvement for me and probably anyone else using app compatiblity settings. ]]>