The screen privacy tool market has a credibility problem. Search for "hide windows from screen capture" and you'll find claims of "framework-blind" protection, "undetectable" cloaking, and "whole-PC shields" that suggest these tools are digital invisibility cloaks.
They're not. They're useful. They're not magic. Here's the honest technical reality.
What WDA_EXCLUDEFROMCAPTURE Actually Does
Windows 10 version 2004 introduced SetWindowDisplayAffinity with the flag WDA_EXCLUDEFROMCAPTURE. When a process calls this on its own window, the DWM compositor removes that window from the frame buffer sent to supported capture APIs.
Supported capture paths include:
- GDI/BitBlt
- DXGI Desktop Duplication
- Windows.Graphics.Capture
- Most screen recorders (OBS, Zoom, Teams, Snipping Tool)
What Microsoft explicitly says it does NOT stop:
- A camera pointed at your monitor.
- Kernel-level capture bypasses (publicly demonstrated).
- Every possible third-party tool.
Microsoft's documentation: "This is not a security boundary and is not intended to protect against malicious code or hardware."
The "Framework-Blind" Myth
Some tools claim to be "framework-blind" — meaning they work with Qt, WinForms, WPF, UWP, or any UI framework.
The truth: WDA works at the compositor level, not the application level. The framework that drew the window is irrelevant. The DWM handles the exclusion after the window is composed. Every tool that uses WDA gets this "for free." It's not a unique feature of any product. It's a property of the Windows API itself.
Claiming "framework-blind" as a differentiator is like claiming a car is "air-breathing" because it uses an internal combustion engine. It's technically true and applies to every competitor.
The "Undetectable" Myth
No tool that runs in user mode is undetectable. CaptureGuard, Evanesco, WinHider, and NoCapture all use DLL injection or process manipulation to apply WDA to third-party windows. Security software can detect this. EDR tools can flag it. Task managers can see the processes.
What "undetectable" usually means in marketing: "The screen capture tool doesn't see the window." That's true for supported capture paths. It's not true for kernel-level tools, and it's not true for endpoint security monitoring the injection itself.
The "Whole-PC Shield" Myth
WDA is per-window. There is no system-wide switch that says "never capture anything on this PC." Each window must be individually excluded, and the exclusion only applies while the process is running and the API call is active.
Tools that claim "whole-PC shield" are either:
- Applying WDA to every visible window iteratively (which is what NoCapture routines do), or
- Exaggerating.
What Actually Differentiates Tools
What Actually Differentiates Tools
NoCapture brings these capabilities together in one solution, so you don't need to piece together multiple tools for different parts of the screen-sharing workflow.
Live preview — See the capture stream before sharing and verify exactly what others will see. Title masking — Sanitize window titles in the taskbar and Alt-Tab to protect metadata. Notification shield — Suppress banners from protected apps during capture. Routines/hotkeys — Use one-click presets for common workflows. Taskbar/Alt-Tab hide — Remove protected apps from visible enumeration. Store distribution — Install through the Microsoft Store or winget for corporate environments. Multi-monitor — Protect windows across all displays.
NoCapture combines these layers of protection into a single workflow, making it easier to keep sensitive apps and information out of your screen share.
We compared the five strongest tools on these exact dimensions here.
CaptureGuard: A Case Study in Honest Documentation
GitHub: xzulab/CaptureGuard
CaptureGuard's README is worth reading because it lists limitations upfront:
- 64-bit only.
- Admin may be required.
- Security software may block injection.
- Multi-process apps (UWP, some browsers) may not be fully protected.
This is how every tool in this space should document itself. NoCapture follows the same principle: we explicitly state that no tool can guarantee protection against every capture method.
The Bottom Line
WDA_EXCLUDEFROMCAPTURE is a useful API, not a magic spell. The tools that use it — Evanesco, CaptureGuard, WinHider, Cloakly, NoCapture — all provide genuine protection against supported software capture. The differences are in workflow features, metadata protection, and honesty about limitations.
Don't trust a tool that claims to be "undetectable" or "framework-blind." Trust a tool that tells you exactly what it does, exactly what it doesn't do, and lets you verify it yourself.
We wrote about the three layers of privacy — pixels, metadata, and workflow — here. That's the framework for evaluating these tools honestly.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
