No Microsoft Teams Red Sharing Border (nor controls) on External Monitors

[pgam]

I'm on MacOS Sequoia 15.1 and DisplayLink Manager 1.11.0. For a few months now, whenever I'm in a Microsoft Teams (new Teams) meeting, I do not get a red sharing border and control bar when I share my external monitor screens. All I get is the DisplayLink icon in the upper left. I only get a red sharing border and control bar when sharing the built-in screen on my Mac. This used to work, but broke at some point after a software upgrade. Is DisplayLink aware of this? A Google search reveals others are having the same issue.

Built-in Monitor:

https://i.ibb.co/MBNtZxv/IMG-1401.jpg

External Monitors:

https://i.ibb.co/R0gy6Qn/IMG-1402.jpg

[DanielSznicer]

I'm on MacOS Sequoia 15.1 and DisplayLink Manager 1.11.0. For a few months now, whenever I'm in a Microsoft Teams (new Teams) meeting, I do not get a red sharing border and control bar when I share my external monitor screens. All I get is the DisplayLink icon in the upper left. I only get a red sharing border and control bar when sharing the built-in screen on my Mac. This used to work, but broke at some point after a software upgrade. Is DisplayLink aware of this? A Google search reveals others are having the same issue.

Built-in Monitor:

https://i.ibb.co/MBNtZxv/IMG-1401.jpg

External Monitors:

https://i.ibb.co/R0gy6Qn/IMG-1402.jpg

Hello,

Thank you for reporting the problem, we have already created an internal ticket for this issue and are working on a solution.
We want to include the fix in the next release of our driver.

[pgam]

Hello,

Thank you for reporting the problem, we have already created an internal ticket for this issue and are working on a solution.
We want to include the fix in the next release of our driver.

Thank you!

[JayS]

Daniel, I concur with the reporter of this issue.
One other issue also linked to sharing is with Teams. When you share more than 4 tabs of a browser, the browser seems to lock up for a while. This also does not happen on the internal Mac display - only on DisplayLink monitors.

Hello,

Thank you for reporting the problem, we have already created an internal ticket for this issue and are working on a solution.
We want to include the fix in the next release of our driver.

[thisisjagan]

Any update on this issue? It is quite annoying...

[Dak]

Daniel, I concur with the reporter of this issue.
One other issue also linked to sharing is with Teams. When you share more than 4 tabs of a browser, the browser seems to lock up for a while. This also does not happen on the internal Mac display - only on DisplayLink monitors.

I get this issue consistently as well. I will be presenting a Chrome web browser with sometimes up to 6 tabs, it locks up, and you have to stop sharing and reshare to move from tab to tab. It's not an issue on Mac alone, just when running DisplayLink.

[JustinSarto]

Hello,

Thank you for reporting the problem, we have already created an internal ticket for this issue and are working on a solution.
We want to include the fix in the next release of our driver.

Hey is there any update on this issue or an expected timeline for a fix? I have a large amount of users experiencing this issue.

Thanks

[djzoidberg]

Hello,
I have the same issue reported in posts before. It's pretty annoying. I'm working with 2 external monitors and MS Teams overlays have not been captured by the DisplayLink app. Every time that I try to click on the top-center of the "main" monitor I accidentally stop the sharing or hit some other button.
Minimizing the screen I can't see the mini window always on top to mute and unmute the microphone and it's impossible to join group calls because the windows do not appear.
The last time a newer version of the DisplayLink app was been released solving this issue.

Please push this issue to the developers. We need an urgent fix.

[pcbl]

Hey Folks,

Happy New Year!

t has been 3 long months without a version update of the driver. We are eager for this fix because it really affects myself and a lot more on my organisation.

BR

[djzoidberg]

Yeah.. Same problem here, 13k users with the same problem. No updates in 3 months.

Please @DanielSznicer can you help us somehow?

[eller82]

Just upgrade to Mac OS 15. Problem seems to be still existing. Last Software Update in October last year. Can we expect any fix soon?

[dbienkowski]

Hi,
We would like to provide an update on our progress in this matter. During our analysis, it has become clear that the resolution of this issue is not fully within our control. However, we fully understand the seriousness of the situation and remain committed to getting it resolved. We are actively collaborating with our partners to find a solution.
Thank you for your understanding.

[abrug]

just to jump on this thread as well - same problem here

[djzoidberg]

@dbienkowski

Thanks for answering.
I can understand that the problem is caused by a couple of elements, like the OS upgrade and relative changes by Apple regarding the screen recording system.
However, the first public beta of macOS Sequoia was released on July 15, 2024, and the official version was released on September 16, 2024. The problem was there from the beginning. Months later, we still struggle with our working setup and related issues.

Please help us to push developers for a fix.

[cmg]

@dbienkowski

I want to echo that my org is also eagerly awaiting a fix - if there is any diagnostic information that the field can provide, please let us know...

[djzoidberg]

Hello again,
there are news about the release date of the DisplayLink Manager Graphics Connectivity app with this fix?

[dbienkowski]

Hi All,
As I mentioned earlier, the solution to the problem is not up to us, however given how problematic this can be for many I can assure you that we are working with our partners all the time to resolve the issue.

Thank you for understanding.

[JPyre]

This exact issue happened once before a year ago.

You guys previously fixed the red boarder issue on v1.9 with 1.10.2 ?...
I'm almost 100% sure.

[dbienkowski]

Hi JPyre,
We can only work around this problem, however, this has other consequences so our goal now is a complete solution.

[djzoidberg]

This is understandable but if the new complete solution will require several months we will probably encounter the same issue in the next MacOS update that will come a few months later.

In the meanwhile, we are working every day without screen overlays captured like MS Teams, KeePass, and so forth on so on.

[pcbl]

Hey guys,
Any update on this topic @dbienkowski ?

Your last update was about 1 month ago... I am facing this issue since October and Sequoia 15.1 ...

BR
Pedro

[dbienkowski]

Hi all,
Microsoft has recognised the problem and expressed a willingness to fix it, so the fix will take place on the MS Teams side. More details can be found here (https://support.microsoft.com/en-us/office/present-content-in-microsoft-teams-meetings-fcc2bf59-aecd-4481-8f99-ce55dd836ce8)

[tshinners]

I agree, this is the exact issue that happened before about a year ago.

Your team fixed the red boarder issue on v1.9 with 1.10.2 ?...or something like that, and then when Sequoia was released it all broke again immediately. I have been searching for answers to this since Sept when Sequoia was released, exchanged emails with support who all said download the latest driver, that has not changed anything. Uninstall and reinstall, nothing.

And last week when I updated the OS, now I get this new error of Turn on Reactions... Screenshot attached. You can't click the X to get it to go away, and I can't find anything to set up the reactions or re-enable, etc.

This link you sent for MS Teams Guide, has nothing relevant, it is a user guide. I have all of those settings enabled and I have chased this down with Microsoft as well. They tell me it is a driver/software setting from DisplayLink causing the issue. I can confirm the last time this was fixed was when I updated the firmware from DL before moving to Sequoia.

Everything on my system is completely up to date with Microsoft, Apple, and DisplayLink, and it still doesn't work.

I am and I know we all are very frustrated with this and we just need it to work. Please help.

[pgam]

More details can be found here (https://support.microsoft.com/en-us/office/present-content-in-microsoft-teams-meetings-fcc2bf59-aecd-4481-8f99-ce55dd836ce8)

More details on what, because I don't see anything about the issue at that link.

[dbienkowski]

I understand that the problem is frustrating, so what I can suggest until Microsoft fixes this issue you can still use DisplayLink Manager 1.9 on which the problem will not occur.

[rboerner]

More details on what, because I don't see anything about the issue at that link.

When visiting this link --> https://support.microsoft.com/en-us/office/present-content-in-microsoft-teams-meetings-fcc2bf59-aecd-4481-8f99-ce55dd836ce8

Scroll down until you see the section entitled, 'Present content from a Mac'. Below that heading is the information related to DisplayLink.

Alternatively, you can also search the page for the word, 'displaylink'.

For reference, this is what the Microsoft page currently states:

"Important: Please be aware of a known issue with the sharing experience affecting sharing indicators and control panels when using DisplayLink or other versions of a docking station on MacOS 14 and higher."

[rcervan3]

I understand that the problem is frustrating, so what I can suggest until Microsoft fixes this issue you can still use DisplayLink Manager 1.10.2 or 1.9 on which the problem will not occur.

Hello, has anyone been able to confirm if given version fixes the Teams controls or only the red banner?

Please advise

[dbienkowski]

Hi rcervan3,
If you will install 1.9.0 you will not experience the problem.

[airtao]

Hi rcervan3,
If you will install 1.9.0 you will not experience the problem.

yes, 1.9.0 works on my M1 MacBook Pro. not only "Teams" but also "Authenticator". :)

[pcbl]

Hey, same for me. 1.9.0 worked on my M1! :-)
I wish I knew this before... My assumption was that older versions were not compatible to Sequoia.

[cmg]

does reverting to 1.9 re-introduces any bugs or issues?

if 1.9 is working, would be be possible to build a 1.9.x maintenance release that contains a backport of fixes/improvements in the 1.10.x branch?

[ClassicChaps]

I installed version 1.12 that was released Feb 28, 2025 with no noticeable change. I know we're waiting on Microsoft to fix Teams (at least I think that's our current issue), but was hopeful some type of fix was available in 1.12.

[airtao]

This should be a problem with the displaylink driver because, not only Teams, but also other software doesn't work correctly under 1.12. For example, Authenticator
https://authenticator.2stable.com/

[pcbl]

Hi rcervan3,
If you will install 1.9.0 you will not experience the problem.

As I posted previously, it seems fine, but I am noticing that the application sometimes seems to update itself from 1.9 to 1.12, which is the version released this week.

For me what is not clear is: If this is a MS Teams issue, why if I downgrade the version it works?

[domidetres]

Hey there,

also using company managed macOS - and deployed the newest version of displaylink software on my device with intune.

i am also experiencing the same issue - version 1.9 is working fine - red border is shown and the sharing tile is there - using version 1.12 it is not working.

Any goal at the dev when to implement that in the new client?

BR
Dom

[sebvit]

Microsoft has recognised the problem and expressed a willingness to fix it, so the fix will take place on the MS Teams side.

@dbienkowski - Do you know if the Slack team have been "given the same opportunity"? Sharing my screen via Huddle has the exact same issue as described here, but is fixed if I downgrade to 1.9.0. Are there any plans to fix this?


Also, I'm sorry about all the duplicated questions/messages you must face on this forum. I myself didn't learn about the downgrading solution until today, and I've read on this forum since mid-november. So possibly there is a question on Slack as well, but I haven't found it.

[djzoidberg]

I've tested for a couple of weeks 1.9 version and it works great.
This confirms the issue reported by the support as "Microsoft issues" or "Apple issues" are bullshits.

They took months to release the garbage version 1.12 and it's unuseful.

For everyone who is struggling against this issue just roll back to version 1.9.

Companies like you have to stop selling hardware without maintaining good software.


Side note, change the download front page image the chair is floating. That reflects the quality of your products.

[pgam]

@dbienkowski or anyone else, what's the proper way to downgrade to 1.9 on my Mac? Whenever I try to install it, I get this: "DisplayLink Manager can't be installed on this disk. A newer version is already installed."

[mjaroch]

Hello pgam,

To return to version 1.9, you should download the End-User Cleaner tool and the DisplayLink Manager app again.
You can do it by following this link (https://www.synaptics.com/products/displaylink-graphics/downloads/macOS-installation-cleaner).

[simonbach]

1.12.1 was just released no mention of this bug, we can't all stay on 1.9 forever:(

[manuecg]

:mad:1.12.1 was just released no mention of this bug, we can't all stay on 1.9 forever:(

:mad:

[renan]

We are all currently using version 1.9.0 due to numerous bugs introduced in later releases.

However, even with version 1.9.0 — or 1.12 for that matter — my third monitor is no longer being detected after updating to macOS Sequoia 15.4.

It's been a real nightmare.

[mjaroch]

Hello renan,

If you have any issues, please let us know about it and contact us directly by following these (https://support.displaylink.com/knowledgebase/articles/755301) steps.

[Szymon]

However, even with version 1.9.0 — or 1.12 for that matter — my third monitor is no longer being detected after updating to macOS Sequoia 15.4.


Hi renan,

If by chance your product is the Dell UD22 and the third monitor that is not working is connected to the HDMI output of the dock, please follow this thread:
HDMI Monitor Not Working After macOS 15.4 Update with Dell UD22 Dock (https://www.displaylink.org/forum/showthread.php?t=69602)

Regards,
Szymon

[kfo21]

Is there no updates at all on this? :(

Super frustrating!!

[NotATanaka]

1.12.2 update released with no mention of bug fix:



C Changes in this release
=========================- Fixed incorrectly set up or blank monitors after resuming from sleep when a dock is connected to a Mac during sleep (VIFR-5802).
- [DL-7xxx] Fixed occasional blank HDMI monitor after dock reconnection (VIFR-5820).
- [DL-7xxx] Fixed inability to set up 4K 144 Hz mode on some monitors using DP (DSC) output (VIFR-5862).
- [DL-7xxx] Prevented unexpected splash screen from briefly appearing during machine reboot (VIFR-5982, VIFR-6138).
- [DL-7xxx] Fixed unexpectedly appearing splash screen while Mac is in sleep (VIFR-6059, VIFR-6120).

[pgam]

1.12.2 update released with no mention of bug fix:



C Changes in this release
=========================- Fixed incorrectly set up or blank monitors after resuming from sleep when a dock is connected to a Mac during sleep (VIFR-5802).
- [DL-7xxx] Fixed occasional blank HDMI monitor after dock reconnection (VIFR-5820).
- [DL-7xxx] Fixed inability to set up 4K 144 Hz mode on some monitors using DP (DSC) output (VIFR-5862).
- [DL-7xxx] Prevented unexpected splash screen from briefly appearing during machine reboot (VIFR-5982, VIFR-6138).
- [DL-7xxx] Fixed unexpectedly appearing splash screen while Mac is in sleep (VIFR-6059, VIFR-6120).

Anyone know if 1.12.2 fixes it? I'm guessing no.

[Mysterion]

Anyone know if 1.12.2 fixes it? I'm guessing no.



it does not

[Szymon]

Progress on the solution and updates related to this problem will published in this thread:
Invisible MS Teams controls while sharing screen (https://www.displaylink.org/forum/showthread.php?t=69627)

[KorriganQC]

Hello Szymon. Do you have any update on the new release?

[pgam]

Anyone able to confirm DisplayLink Manager 13.0 resolves this issue?

[airtao]

Anyone able to confirm DisplayLink Manager 13.0 resolves this issue?

yes, 13.0 resolved this issue

[ClassicChaps]

The latest update (13.0.0 Build 33 -- what's with the new version format??) seems to have addressed this for me.