Why does one window show as a black rectangle when I share my screen?

Three things cause it. Protected video playback blanks its own video surface so no capture tool receives the frames. A hardware acceleration mismatch means the meeting app's window capture path cannot read what your GPU is drawing. Or the application has deliberately marked its window as excluded from capture. Swapping a window share for a full screen share separates the second cause from the other two in about ten seconds.

Why is Netflix or a streaming video black when I share my screen?

That is digital rights management behaving as designed. Protected playback runs through a path that will not hand decoded frames to any capture tool, so viewers get a black rectangle where the video sits while the player controls, the page around it and usually the audio come through normally. No browser change, driver update or setting removes it, because the blanking is the point.

How do I fix a black window in Zoom or Teams caused by hardware acceleration?

Share the whole display instead of the single window, which works immediately. Then turn off graphics acceleration in the source application, for example under Settings then System in Chrome, and relaunch it. On a laptop with two graphics chips, open Windows Settings, System, Display, Graphics and set the source app and the meeting app to the same GPU.

How can I tell DRM apart from a capture bug?

Look at exactly which pixels are black. DRM blanks only the video rectangle and leaves the player controls, browser tabs and surrounding page visible, and the sound usually keeps playing. A broken capture path blanks the entire window including its title bar and menus. If the window looks perfectly normal on your own monitor and only viewers see black, it is never a rendering fault.

Does a black rectangle mean someone is hiding something from me?

Usually not. The common causes are protected video and a graphics capture mismatch, both accidental. Windows does let an application blank or remove its own window from capture, which password managers, banking apps and some overlays use. The newer method removes the window from the frame entirely rather than blacking it, so a visible black box points more often at a bug or at DRM.

Why does my share freeze or go black during a Windows permission prompt?

A User Account Control prompt runs on a separate secure desktop that no capture tool can read. Viewers see a frozen frame or a black screen for as long as the prompt is up on your monitor, then the picture resumes the moment you answer it. Nothing is broken and no setting changes it. Approve or cancel the prompt and the share continues.

Window Shows Black When Screen Sharing: Causes and Fixes

A window that arrives as a black rectangle while the rest of your share looks normal has three realistic causes: protected video playback blanking its own frames, a hardware acceleration mismatch between the app you are sharing and the app doing the capturing, or a window that has deliberately marked itself as uncapturable. To a viewer all three look identical. Three short tests tell them apart, and only one of the three has a fix.

Run the tree in this order

Each test rules out a branch, so working through them in order costs less than guessing. The whole sequence takes under two minutes, and you can run it in a meeting with only yourself in it.

Is it black on your own monitor too?

Look at the actual window on your desk, not the meeting preview. If it is black there as well, sharing is not involved at all. The application has failed to draw: a crashed browser renderer, a video overlay that lost its surface, a stale display driver. Close it and reopen it, and if that helps only until the next time, install the display driver from the GPU vendor's own installer rather than relying on Windows Update. Stop here. If the window looks perfectly normal to you and only the viewers get black, keep going.

Swap the window share for a whole screen share

Stop sharing, start again, and this time pick the entire display instead of the single window. If the black rectangle fills in and viewers can suddenly see the app, the per-window capture path was the problem, which is the acceleration branch below. If it stays black with the whole screen shared, the content is blanking itself and no meeting setting will change that.

Look at exactly which pixels are black

Only the video rectangle, with the player controls, browser tabs and page around it still visible, and audio still playing: that is protected playback. The whole window black edge to edge including its title bar and menus, in something like a password manager, a banking client or a floating overlay: that is deliberate capture exclusion. Press Windows key and Print Screen, then open the saved PNG in your Pictures folder to confirm, because a plain screenshot travels the same path a meeting app does.

What you see	Cause	The test that proves it	Fixable?
Black to viewers on a window share, fine on a full screen share	Hardware acceleration mismatch in the capture path	Switching to whole screen makes the app appear	Yes. Toggle acceleration or align the GPUs
Only the video rectangle black, controls and page visible, sound normal	Protected playback, DRM	Pause the video: the still frame and the page behind it render for viewers	No. This is the designed behaviour
Whole window black in both share modes, normal on your monitor	Deliberate capture exclusion, older blanking flag	The same black box appears in a Windows key and Print Screen screenshot	No, unless that app ships its own switch
Window absent entirely, desktop visible where it should be	Deliberate capture exclusion, newer removal flag	The screenshot shows the desktop, not a black shape	No. Nothing arrives to be shown
Everything freezes or blacks out for a few seconds, then returns	A Windows permission prompt on the secure desktop	A UAC dialog is sitting on your screen at that moment	Yes. Answer the prompt
Black on your own monitor as well	The app or the driver, not the share	Visible before you ever press Share	Yes. Restart the app, update the driver

Branch one: protected playback

Streaming services that enforce content protection decode video through a path that never hands finished frames to a capture tool. The player is not detecting your meeting and reacting to it. The frames simply do not exist anywhere a screen capture can reach, so the capture composites black into that rectangle instead.

The signature is precise and worth memorising. Blanking is limited to the video surface. Play and pause buttons, the progress bar, the page around the player, the browser chrome and the other tabs all come through fine, and the audio usually keeps going, which is why people describe it as sound with a black hole. Pause the video and the still frame or the artwork behind it often reappears for viewers, because a paused player is no longer pushing protected frames.

There is no fix. Not a browser flag, not a driver update, not a different meeting platform, because the protection sits underneath all of them. Forcing software decoding sometimes changes the outcome, but on several services it instead drops the picture to a lower quality tier or refuses to play, and the behaviour varies between browsers and service versions, so treat that as something to test rather than something to expect. If you genuinely need a group to watch something together, use whatever shared viewing feature the service itself provides.

Branch two: the acceleration mismatch, and how to actually clear it

This is the only branch where you can change the outcome, and in ordinary work calls it is the most common one. Sharing a single window makes the meeting app capture that window's own surface. When the source application renders through the GPU in a way that route cannot read, or when two graphics chips are involved and each app is pinned to a different one, the capture comes back empty and you get black. Sharing the whole display uses a different route, which is exactly why the full screen test works.

Work through these in order and re-test after each one. Stop at the first that works, since the later steps cost you performance you would rather keep.

Share the entire display instead of the window. Not elegant, but it works instantly, and it is the right move if you are three minutes into a call with people waiting. Close anything you do not want seen first, because the whole desktop is now in the stream.
Turn off graphics acceleration in the source app, then relaunch it. In Chrome and Edge it sits under Settings, then System, worded roughly as using graphics acceleration when available. Desktop apps built on the same engine, such as many chat and note clients, usually have an equivalent under advanced settings. The exact wording moves between versions, so search the settings box for the word acceleration instead of following a fixed menu path.
Check the meeting client's own video and sharing options. Zoom, Teams and similar clients expose their own acceleration switches for capture and encoding. Turning them off is a fair test even if you turn them back on once you know the answer.
Align both apps to the same GPU. On a laptop with integrated and discrete graphics, open Windows Settings, then System, Display, Graphics. Add both the source application and the meeting client and set both to the same preference. Both on high performance, or both on power saving. Which one you choose matters far less than the two of them matching.
Install the display driver from the vendor. The version Windows ships is frequently older than the one that fixed a capture regression.
Verify from a second device. Join the same meeting from your phone, share the window again, and look at the phone. A local preview is drawn on your own machine and is not evidence of what anyone else receives.

Two related traps are worth naming. A minimised window can capture as black or as a stale frame, so leave it open and on screen while you test. And a window dragged onto a monitor with different scaling, a different refresh rate or HDR enabled sometimes captures badly on that display alone. If the black rectangle follows one particular monitor, turn HDR off for that display in Windows Settings and re-test before you blame the app.

Branch three: the window is excluding itself on purpose

Windows lets an application set a property on its own top-level window telling the compositor how to treat it during capture. One value blanks that window's pixels in the capture stream, which produces the tidy black rectangle in the exact shape and position of the window. A newer value removes the window from the capture frame altogether, so viewers see the desktop behind it and nothing hints that a window was ever there. Password managers, banking clients, credential prompts and some overlays use one or the other.

Nothing on the receiving end changes this. The meeting app is not filtering the window out, it is handed an image that never contained those pixels, so no Zoom or Teams setting can restore them. Only the application itself can, and only if it exposes a screen security option of its own. This is also why a black box is more likely a bug or DRM than someone concealing something from you: the modern approach makes a window absent rather than black, and a moving black hole is close to the most conspicuous artefact you can put on a call. The overlay in OfferPilot AI uses the removal behaviour for that reason, staying readable on your own monitor while being absent from Zoom, Teams, Meet, OBS and screenshots. That covers software asking Windows for the screen and nothing else. It does not affect a webcam, a phone camera pointed at your monitor, a lockdown browser, eye tracking, or a person sitting in the room with you.

Where this page, and our product, will not help you

If your black rectangle is DRM, the honest answer is that the video is not going into that call and no article changes it. If you are on macOS or Linux, the acceleration steps above are Windows specific and the GPU preference screen does not exist for you, though the three way diagnosis still holds. And OfferPilot AI is an interview assistant for Windows 10 and 11, not a screen sharing repair tool, so if you landed here with a broken work presentation there is nothing here for you to install: run the tree, take the fix in branch two, and get on with your call. If you are sitting a proctored assessment under rules you agreed to, with a lockdown browser or a live invigilator, none of this is a workaround for that either.

The compressed version. Black on your monitor means the app. Black only to viewers but fine on a full screen share means acceleration. Black on both with the page around it intact means DRM. Black on both with the whole window gone means the window asked to be left out.

Why a window shows up black when you share your screen