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)
I updated to MacOS Catalina and now I cannot share my app screens. I can share my desktop, but that is all others can see.
Additional features, settings, or issues not covered by specific Microsoft Teams categories
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.
Found it.
System Preferences
Security & Privacy
Privacy
Screen Recording
My system had an entry (unchecked) for Microsoft teams. I think it asked me as I was launching but I blew by it. Not sure how you'd add it if it's not there. You just have to turn it on, and Teams screen sharing will work.
The same thing happened to me trying to teach in Teams today. How did you fix it?
JRoss
I am experiencing this issue. It works for me when I quit Microsoft Teams and then reopen the app. However, once I enter a new meeting and try to share my screen it will not work again until I quit teams and reopen.
I am getting this error:
I have the permission activated:
I am running these versions of Teams and Catalina:
I rely on Teams every day for work and this is a very frustrating issue that causes a lot of mishaps during meetings. Please help!
Don's solution did not work for me long term. As soon as I attempt again or close and restart, I get the error. Running in full screen did not work as well.
The setting is checked as needed. I have even removed the app, deleted the trash can and then reinstalled. All to no avail.
Mine has been working properly for the past few weeks. It appears the latest update solved the problem.