Evanesco was one of the first open-source tools to make SetWindowDisplayAffinity accessible through a GUI. It remains a valid choice for developers, privacy enthusiasts, and anyone who prefers to inspect code before running it. But "free" and "open-source" come with operational costs that are not obvious until you have used the tool in a professional context.
This post is not a teardown of Evanesco. It is a realistic map of where Evanesco ends and where NoCapture begins.
What Evanesco Offers
Evanesco is available at github.com/k4yt3x/Evanesco. It provides:
- A basic GUI for selecting processes and toggling capture exclusion
- Support for both x86 and x64 windows
- Portable and installable versions
- No cost
For a developer who wants to understand exactly how WDA_EXCLUDEFROMCAPTURE works, Evanesco is an excellent reference implementation.
The Hidden Costs of Free
Using Evanesco in a professional workflow reveals friction that does not appear in the README:
- No live preview. You must manually verify the capture stream with Snipping Tool or OBS every time you enable protection. If you forget, you do not know what leaked until someone tells you.
- No title masking. The window may be hidden from capture, but its title still appears in Alt-Tab and taskbar previews. In a client presentation, "Slack — Recruiter: Offer letter" is a leak even if the window itself is blacked out.
- No notification shield. A cloaked app can still throw a banner over your shared screen. Evanesco does not intercept notifications.
- No routines or hotkeys. You manually select and hide apps every session. If your workflow involves five apps, that is five clicks every time.
- No enterprise support. No MSI, no Intune, no admin dashboard, no team-wide policy enforcement.
These are not flaws in Evanesco. They are simply outside its scope. Evanesco is a utility. It was never designed to be a workflow product.
What NoCapture Adds for Professionals
NoCapture assumes you share screens daily and that verification time matters.
- Live preview pane. See the capture stream before you share. This turns a two-minute manual verification into a two-second glance.
- Title masking. Sanitize window titles in taskbar, Alt-Tab, and window lists. This closes the metadata leak that Evanesco leaves open.
- Notification shield. Suppress banners from protected apps during active shares.
- Smart routines. "Daily Standup" auto-cloaks Slack and email. "Streaming" hides Discord and Spotify. Set once, trigger instantly.
- Teams deployment. Roll out across a remote team with MSI, Intune, and centralized policies.
The Decision
Use Evanesco if:
- You are a developer or researcher who wants to inspect the implementation
- You hide one or two windows occasionally
- You do not need title masking, notification suppression, or automation
- You prefer open-source on principle and accept the manual overhead
Use NoCapture if:
- You share screens professionally and cannot afford verification errors
- You need metadata protection, not just pixel protection
- You want to automate privacy so you do not have to think about it
- You are deploying across a team
The Technical Honesty
Both tools use the same Windows API. Both are subject to the same limitations documented by Microsoft. Neither stops kernel-level bypasses or physical cameras. The difference is not in the capture-exclusion mechanism. The difference is in what happens around it.
We wrote about the three layers of screen-share privacy here. Pixel protection is layer one. Evanesco covers layer one well. NoCapture covers all three.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
