Why is my window not showing in a screen share or recording?

Either you shared a single window or a monitor that does not contain it, or the program set a display affinity flag asking Windows to leave its window out of capture. With that flag, the desktop compositor builds the captured frame without the window in it, so Zoom, Teams, Meet and OBS receive an image the window was never drawn into. Check a screenshot first, because screenshots use the same path.

What is the Windows flag that removes a window from screen capture?

It is set with SetWindowDisplayAffinity on a top level window handle. WDA_NONE is normal capture, WDA_MONITOR renders the window to your monitor only and leaves a black rectangle in the capture, and WDA_EXCLUDEFROMCAPTURE removes the window from the captured frame entirely so viewers see whatever sits behind it. The removal value needs Windows 10 version 2004 or later.

How do I test whether a window is excluded from capture?

Press Windows key and Print Screen, then open the PNG saved in your Pictures Screenshots folder. If the window is missing there while you can still see it on your monitor, the flag is set, because a screenshot travels the same compositor path a meeting app does. Confirm by starting a meeting alone, sharing your whole screen, and watching from your phone.

Why can Zoom, Teams or OBS not show a window that is excluded?

Because none of them ever hold those pixels. They ask Windows for a frame through a capture API, and the compositor hands back an image that was assembled without the excluded window. The sharing app is not filtering anything out, so no quality setting, capture mode, driver update or restart inside Zoom, Teams, Meet or OBS restores it.

Why is my window a black rectangle instead of missing entirely?

A black rectangle in the exact shape of the window usually means the older WDA_MONITOR value, which blanks the window region rather than removing it. Protected video playback and a graphics acceleration mismatch also produce black. Missing means the newer removal value. Whether the window vanishes or blanks is decided by the program and the Windows build, not by the meeting app.

Does capture exclusion hide a window from a webcam or a proctor?

No. The flag only affects software that asks Windows for the screen. A webcam, a phone camera pointed at your monitor, an HDMI capture device on the display output, a person in the room, eye tracking and lockdown browsers that inspect running processes are all unaffected, because the window still renders normally to your physical display.

Window Not Showing in Screen Share Recording: Why It Happens

A window you can plainly see on your monitor can be completely absent from a Zoom share, a Teams recording or an OBS capture, and that is usually deliberate rather than broken. Windows lets a program set a display affinity flag on its own window, and one value of that flag tells the desktop compositor to build the frame it hands to capture without that window in it. Zoom, Teams, Meet and OBS then receive a picture the window was never composited into, which is why no setting inside them brings it back. Two duller causes look identical from the outside, so rule those out first.

Rule out the two boring causes in thirty seconds

Most people who search this phrase have not met the flag at all. They have met a scope problem, and it takes half a minute to eliminate.

You shared a window, not a screen. A single window share sends that one window and nothing else. Anything you open afterwards, including dialogs the app itself spawns, may never enter the stream. In a browser, sharing a tab is narrower still: it sends that tab's contents, not the browser around it and not your desktop.
The window is on a display you did not share. Sharing Screen 1 while the window sits on Screen 2 produces exactly the symptom people describe. Drag the window onto the shared display and watch whether it appears.

Two smaller ones are worth a glance. A minimised window can capture as blank or as a stale frame, so keep it open on screen while you test. And a User Account Control prompt runs on a separate secure desktop that no capture tool can read, which freezes or blanks the whole share for as long as the prompt is up.

If you shared the entire display, the window is on that display, it is open and unminimised, and it still does not arrive, you are looking at capture exclusion.

The flag itself: SetWindowDisplayAffinity

Windows exposes a call named SetWindowDisplayAffinity that takes a top level window handle and one of three values. The program that owns the window makes the call on itself. There is no user setting, no registry switch and no meeting app option that sets or clears it on another application's window.

WDA_NONE, value 0x00000000. Normal. The window is composited into everything, capture included.
WDA_MONITOR, value 0x00000001. The window renders to your physical display, but its region comes back blanked in a capture. This is the old behaviour, available for well over a decade, and it is where the classic black rectangle comes from.
WDA_EXCLUDEFROMCAPTURE, value 0x00000011. The window is left out of the captured frame altogether. Viewers see whatever sits behind it, and nothing marks the gap. This value needs Windows 10 version 2004, build 19041, or newer, which neatly explains why one application can produce a black box on an old machine and a clean absence on a current one.

A matching GetWindowDisplayAffinity call reads the value back, which is how a program checks its own state. Password managers, banking clients, credential prompts, protected video players and some overlays use one of the two protective values.

Why the meeting app is not the place to fix it

It helps to follow the pixels. Your application draws into a surface. The Desktop Window Manager composites all those surfaces into the image sent to your monitor. Separately, when something asks to capture, the compositor assembles an output for capture, and it is at that assembly step that an excluded window is skipped. Only then does a capture API hand the result over: Desktop Duplication for many older tools, Windows Graphics Capture for the modern picker, the same stack underneath getDisplayMedia when Google Meet or any other browser based platform asks Chrome for your screen. Zoom, Teams, Meet, OBS and the Xbox Game Bar recorder all sit downstream of that step.

So the sharing app is not filtering, hiding or censoring anything. It receives a frame in which those pixels never existed, then encodes it and sends it. That is the whole reason changing capture mode, lowering quality, restarting the client, updating a driver or switching platforms changes nothing. The decision was made one layer below all of them, before any of those tools was handed a single frame.

How to test it, in order

Run these on the machine that owns the window. The first step alone answers the question in most cases.

Take a screenshot with Windows key and Print Screen

Open the PNG that lands in Pictures, then Screenshots. A screenshot travels the same compositor path a meeting app does, so it is a faithful proxy for what viewers get without needing a second person. Window visible on your monitor but missing from the file means the removal value. Present as a black rectangle in the file means the blanking value, or protected video, or a graphics acceleration mismatch.

Start a meeting with only yourself in it

Open Zoom, Teams or Meet, start a meeting, share the whole screen, then join that same meeting from your phone and look at the phone. Never trust the local preview thumbnail. It is drawn on your own machine and is not evidence of what leaves it. This is also the only step that tests the exact platform you care about.

Compare Display Capture and Window Capture in OBS

Add a Display Capture source, then a Window Capture source pointed at the same window. Display Capture reads the composited desktop, so an excluded window is simply not in it. Window Capture targets the handle directly and typically returns black or nothing at all. Two different capture routes agreeing is strong evidence that the exclusion sits on the window rather than in one tool.

Record ten seconds and watch the file back

Use the Game Bar with Windows key, Alt and R, or record the meeting itself, then play the file. Recording and live sharing draw on the same capture path, so a window absent from one is absent from the other. Worth doing explicitly if what matters to you is a recording somebody reviews later rather than a live share.

Check the owning application's own settings

If you want the window back, the only place that can grant it is the program that owns the window. Some apps expose a screen security or privacy toggle that flips the flag. If it does not, the window stays out, and nothing the person receiving your share does will override it.

What viewers get	Underlying cause	Fastest proof	Can it be changed?
Window absent, desktop visible behind it	Capture exclusion, removal value	A Windows key and Print Screen file with no window in it	Only by the app itself
Black rectangle shaped exactly like the window	Capture exclusion, older blanking value	Same screenshot, but a black box appears in it	Only by the app itself
Only a video area black, page and controls fine	Protected playback	Pause it: the still frame often returns	No. Designed behaviour
Black on a window share, fine on a full screen share	Graphics acceleration mismatch	Switch to whole screen and it appears	Yes. Align both apps to one GPU
Window missing, but you shared one window or one tab	Share scope, not exclusion	Reshare the entire display instead	Yes, immediately
Everything frozen or blank for a few seconds	A UAC prompt on the secure desktop	A permission dialog is open right now	Yes. Answer the prompt

What the flag does not touch, stated plainly

Display affinity affects software that asks Windows for the screen. It does not affect the picture going to your monitor, because that is the entire point of the mechanism, and everything downstream of the monitor is therefore untouched.

A webcam, or a phone propped up pointing at your display, records what your eyes see.
A capture device sitting on the HDMI or DisplayPort output generally sees the window, since it reads the display signal rather than a compositor frame.
A live proctor in the room, eye tracking, and lockdown browsers that enumerate running processes are all unaffected by a rendering flag.
Behaviour inside a virtual machine, or through Remote Desktop, varies by configuration and is worth testing rather than assuming.

The overlay in OfferPilot AI uses the removal value for exactly the reason described above, which is why it is absent from Zoom, Teams, Meet, OBS and screenshots while staying readable on the user's own monitor. That is a statement about screen capture and nothing more. It is not a claim about cameras, proctors or supervised exams.

When this page, and our product, are the wrong answer

If you came here because a colleague cannot see your app in a work call, your fix is in the boring causes section or the acceleration row of the table, and there is nothing here for you to install. If you are on macOS or Linux there is no equivalent of this exact flag to go hunting for, and OfferPilot AI does not run there at all, since it is Windows 10 and 11 only with no mobile app and no browser extension. And if you are sitting an assessment under rules you agreed to, with a lockdown browser or a live invigilator, capture exclusion is not a workaround for that, and we will not describe it as one. The positioning is preparation, live assistance and accessibility, on calls where the choice to use it is yours to make.

Short version. Missing from a screenshot as well means the window asked Windows to leave it out, and only its own developer can change that. Missing only from the share means you shared the wrong scope. Black rather than missing means the older blanking value, protected video or a graphics mismatch, and the last of those is the only one you can fix from your side.

Why some windows never appear in a screen recording