Screen sharing fails in two very different ways, and which one you’re hitting tells you where to look. Either the Share button is greyed out or missing so you can’t even start, or you share fine but everyone else sees a black rectangle. The first is almost always a policy or role problem. The second is nearly always graphics. Mixing the two up sends people down the wrong path for an hour.
This guide splits the problem the same way the symptoms do. Work out whether you can’t start a share or your share shows nothing, then jump to that half. Each fix takes a minute or two, and most screen-share tickets end before the driver section.
Share button greyed out: check policy and your role
A greyed-out or absent Share control isn’t a glitch you can click your way past. Two things switch it off.
The first is your role in the meeting. If the organizer set “Who can present” to a specific group — or to Only me — attendees outside that group don’t get a Share button. Ask the organizer to make you a presenter from the participant list (… > Make a presenter), or to change the presenter setting in meeting options.
The second is a tenant-level meeting policy. Admins control screen sharing with the ScreenSharingMode setting on a Teams meeting policy. If it’s set to Disabled, nobody on that policy can share their screen, full stop. There’s nothing to fix on the client — it’s an admin decision.
If you’re the admin, you can check and set this in PowerShell:
# See the current setting on the global (default) policy
Get-CsTeamsMeetingPolicy -Identity Global | Select-Object Identity, ScreenSharingMode
# Allow entire-screen sharing on that policy
Set-CsTeamsMeetingPolicy -Identity Global -ScreenSharingMode EntireScreen
On macOS, grant the Screen Recording permission
This is the single most common reason Mac users can’t share, and it catches people right after they install or update Teams. macOS won’t let any app capture the screen until you explicitly allow it.
Go to System Settings > Privacy & Security > Screen Recording and switch on Microsoft Teams. On older macOS versions the path is System Preferences > Security & Privacy > Privacy > Screen Recording.
The catch that wastes the most time: after you enable the toggle, macOS requires you to quit and reopen Teams completely before the permission takes effect. Closing the window isn’t enough — use Quit from the menu bar or the Dock. Until you do, the toggle looks on but sharing still shows a black screen to everyone else.
Can't start a share — first pass
- You're a presenter, not just an attendee (ask the organizer to promote you)
- The meeting's 'Who can present' setting isn't locked to the organizer
- Your admin's meeting policy has ScreenSharingMode enabled, not Disabled
- On macOS: Screen Recording is on for Teams in Privacy & Security
- On macOS: you fully quit and reopened Teams after granting permission
Black screen when sharing: turn off GPU hardware acceleration
If you can start a share but participants see a black or frozen rectangle, the problem has moved from permissions to graphics. Teams uses GPU hardware acceleration to render and capture, and on some systems — particularly laptops with switchable Intel/NVIDIA or AMD graphics — that capture path produces a black frame.
In classic Teams, open Settings > General and tick Disable GPU hardware acceleration, then fully restart Teams. The naming is confusing: enabling that checkbox turns acceleration off, which is exactly what you want to test. New Teams moved many of these knobs, so if you don’t see the toggle, the equivalent fix is updating the app and your graphics driver (covered below).
On laptops with two GPUs, make sure Teams and the app you’re sharing both run on the same graphics processor. If Teams renders on the integrated GPU but your app runs on the discrete one, the capture can come back black. In Windows Settings > System > Display > Graphics, you can set a specific GPU preference per app.
Multi-monitor and display scaling problems
When you share with more than one screen connected, Teams lists each display separately in the share tray — Screen 1, Screen 2, and any open windows. Two things go wrong here.
First, people simply pick the wrong monitor. If viewers see your empty second desktop instead of your slides, stop the share and choose the display the content is actually on, or share the specific window rather than a whole screen. Window sharing sidesteps the which-monitor guessing game entirely.
Second, mismatched display scaling makes the share blurry, cropped, or oversized. If one monitor runs at 150% scaling and another at 100%, the captured image can look soft or get clipped. Where you can, set both displays to the same scaling percentage in Settings > System > Display. If you can’t, sharing a single window is the more reliable choice.
Share the right thing for the situation
| Demoing one app | Share that window — cleaner and avoids monitor confusion |
|---|---|
| Switching between several apps | Share the screen those apps live on |
| Mismatched monitor scaling | Share a window, or match scaling first |
| Showing a video with motion | Share screen and tick 'Include sound' / 'Optimize for motion' |
Update Teams and the graphics driver
An out-of-date client or graphics driver is behind a fair share of capture failures, especially black-screen shares that started after a Windows feature update.
Update Teams first. In classic Teams, click your profile picture and choose Check for updates — it installs in the background and applies on the next restart. New Teams updates through the Microsoft Store / app installer, so confirm it’s current there.
Then update the graphics driver. Don’t rely only on Windows Update for this — get the current driver straight from Intel, NVIDIA, or AMD for your exact GPU. If sharing broke right after a driver update, the reverse can also be true: roll the driver back in Device Manager > Display adapters > Properties > Driver > Roll Back Driver.
1. Teams (classic): profile picture > Check for updates > restart
2. Teams (new): update via Microsoft Store / app installer
3. GPU driver: download from Intel / NVIDIA / AMD for your exact model
4. Broke after a GPU update? Device Manager > Display adapters > Roll Back Driver
Clear the Teams cache as a last resort
When policy allows sharing, permissions are granted, hardware acceleration is sorted, and it still won’t work, a corrupted cache can leave the share controls unresponsive or the screen picker empty. Clearing it forces a clean rebuild on the next launch.
Quit Teams completely first — right-click the tray icon and choose Quit, or end the process in Task Manager. The cache can’t be cleared while the app holds the files. Then delete the cache folder for your client version.
Teams cache locations
| Classic Teams | %appdata%\Microsoft\Teams |
|---|---|
| New Teams | %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache |
For classic Teams you can clear it from PowerShell after quitting the app:
Get-Process -Name Teams -ErrorAction SilentlyContinue | Stop-Process -Force
Remove-Item -Path "$env:APPDATA\Microsoft\Teams\*" -Recurse -Force -ErrorAction SilentlyContinue
After clearing, relaunch Teams, sign in, and try sharing again. The first load is slower while the cache rebuilds.
Still stuck? Narrow it down fast
If you’ve worked through the relevant half and sharing still fails, a couple of quick splits point to where the fault lives:
- Try the Teams web client. Open a meeting in Edge or Chrome and try sharing there. If the browser shares fine but the desktop app won’t, the desktop client is at fault — recheck hardware acceleration and clear the cache. The browser uses its own screen-capture permission, so a working web share rules out a tenant policy block.
- Have someone else try. If a colleague on the same meeting policy can share and you can’t, the problem is local to your machine, not the policy.
- Share a window instead of a screen. If a single window shares but a full screen doesn’t, you’re looking at a multi-monitor or capture issue, not a permission block.
For the broader set of meeting faults — join failures, dead microphones, and audio quality — see the full Microsoft Teams meeting troubleshooting guide. If your mic is also acting up, the microphone fix walkthrough follows the same diagnostic order.
Wrapping up
Screen sharing breaks in two camps. If you can’t start a share, it’s a meeting role, a tenant policy, or the macOS Screen Recording permission — none of which you fix by reinstalling. If you can share but viewers see black, it’s GPU hardware acceleration or a multi-monitor mismatch, and toggling acceleration plus updating the driver clears most of those. Sort out which symptom you have first, work that half top to bottom, and leave the cache clear for the rare case where everything else checks out.