Windows 11 introduced visual changes that most users noticed: rounded corners, centered taskbar, new Start menu. It also introduced technical changes that most users did not notice: DWM compositor updates, new Snipping Tool architecture, and revised capture APIs. For screen privacy tools, these changes matter.
WDA_EXCLUDEFROMCAPTURE: Unchanged
The core API that powers NoCapture — SetWindowDisplayAffinity with WDA_EXCLUDEFROMCAPTURE — works identically on Windows 10 version 2004 and later and on Windows 11. Microsoft did not modify this API between versions. If a tool works on Windows 10, it works on Windows 11 at the API level.
DWM Compositor Changes
Windows 11 updated the Desktop Window Manager with new rendering paths for rounded corners, Mica material, and snap layouts. These changes do not affect capture exclusion directly, but they do affect how thumbnails and previews are generated.
What this means for NoCapture: The live preview pane renders DWM thumbnails. On Windows 11, these thumbnails include the rounded corner mask and Mica transparency. The preview is more visually accurate, but the underlying capture exclusion behavior is unchanged.
What this means for users: Nothing functional changes. A cloaked window is still excluded. The preview just looks more like the actual desktop.
Snipping Tool Overhaul
Windows 11 replaced the legacy Snipping Tool with a new version built on a different capture framework. The new Snipping Tool uses Windows.Graphics.Capture instead of GDI for some operations.
What this means: WDA_EXCLUDEFROMCAPTURE blocks both the old and new Snipping Tool. NoCapture's verification test with Snipping Tool remains valid on Windows 11.
One caveat: The new Snipping Tool has a screen recording feature. This feature respects WDA_EXCLUDEFROMCAPTURE identically to the screenshot feature. If you test screen recording rather than screenshots, the cloaked window should still appear black or omitted.
Teams Integration
Windows 11 deepens Microsoft Teams integration into the taskbar. The Chat icon is pinned by default and uses a lightweight Teams client.
What this means for NoCapture: The lightweight Teams client is still a standard Windows application. NoCapture can cloak it, mask its title, and suppress its notifications. The deeper OS integration does not create a capture bypass.
Performance
Windows 11's DWM is more efficient on newer hardware. On machines with compatible GPUs, the compositor uses hardware-accelerated rendering paths that reduce CPU load. For NoCapture users, this means the live preview pane and thumbnail generation are slightly faster on Windows 11.
On older hardware without compatible GPUs, Windows 11 may feel slower than Windows 10. NoCapture itself does not contribute to this slowdown, but the OS baseline is higher.
The Windows 10 Sunset
Microsoft has announced end-of-support dates for Windows 10. NoCapture will continue to support Windows 10 version 2004 and later for the foreseeable future. We do not plan to drop Windows 10 support before Microsoft does.
Should You Upgrade for Privacy?
No. Windows 11 does not offer better screen privacy than Windows 10. The APIs are the same. The protection is the same. Upgrade for the UI, the performance, or the support lifecycle. Do not upgrade expecting superior capture exclusion.
We wrote about testing your window cloaking on any Windows version here.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
