Every screen privacy tool claims to hide your windows. Most of them actually do — under ideal conditions. The problem is that your conditions are never ideal. A Windows update changes DWM behavior. A multi-process browser spawns a render thread in a different process. A security tool blocks the DLL injection mid-flight.
You should verify your setup before every high-stakes share. Not because the tool is unreliable, but because computers are complex and assumptions kill privacy.
Here is the verification protocol we recommend. It works for NoCapture, Evanesco, CaptureGuard, WinHider, or any tool that uses WDA_EXCLUDEFROMCAPTURE.
Test 1: Snipping Tool
This is the fastest check. After cloaking your target window:
- Press
Win + Shift + S - Select the region where the cloaked window sits
- Paste the capture into Paint or your chat window
Pass: The window appears black, transparent, or is omitted entirely.
Fail: The window content is visible.
What to do: Check that the target process is 64-bit if your tool requires bitness matching. Try running the cloaking tool as administrator. Restart the target application and re-apply protection.
Test 2: OBS Display Capture
If you stream or record:
- Add a Display Capture source in OBS
- Confirm the cloaked window is absent from the OBS canvas
- Move the window around your monitor while watching the canvas
- Resize the window and check again
Pass: The window never appears, even during movement and resize.
Fail: The window flickers into view during movement or resize.
What to do: Some tools apply protection only to the initial window handle and miss child windows created during resize. NoCapture recursively protects child windows. Free tools may not. Save your routine and re-apply after any window state change.
Test 3: Zoom Screen Share Preview
Before joining a real meeting:
- Start a private Zoom meeting with no other participants
- Click Share Screen
- Select your full desktop
- Look at the preview thumbnail before clicking the final Share button
Pass: The cloaked window is absent from the preview.
Fail: The window is visible in the preview.
What to do: Zoom's preview is a reliable proxy for what participants will see. If the window leaks here, it will leak to everyone. Do not proceed until fixed.
Test 4: Alt-Tab and Taskbar
If your tool offers title masking:
- Alt-Tab while screen sharing is active
- Check if the cloaked app's title appears in the switcher
- Hover over the taskbar icon and read the tooltip
Pass: The title is generic or the app is absent from the switcher.
Fail: The real title is readable.
What to do: Title masking is a separate feature from pixel cloaking. Evanesco and CaptureGuard do not offer this. WinHider hides from taskbar but does not rewrite titles. Only NoCapture sanitizes titles in the switcher. If you need this layer, verify your tool supports it.
We wrote about why title masking matters here.
Test 5: Notification Banner
If your tool has notification shielding:
- Cloak a messaging app like Slack or Discord
- Ask a friend to send you a DM
- Watch for the banner while screen sharing
Pass: No banner appears over your shared screen.
Fail: The banner draws on top of your presentation.
What to do: Notification shielding is rare. Most free tools do not intercept system notifications. If banners leak, disable OS notifications entirely before sharing, or use a tool with native shielding.
We covered notification shielding in detail here.
Test 6: Multi-Monitor
If you use multiple displays:
- Cloak a window on Monitor 2
- Share Monitor 1 via Display Capture
- Check if the Monitor 2 window bleeds into the capture
Pass: Monitor 2 content is fully isolated.
Fail: The cloaked window appears in the shared monitor's frame.
What to do: Some tools protect only the primary display. Verify your tool explicitly supports multi-monitor. NoCapture's live preview spans all displays for this reason.
Test 7: The Browser Tab Test
If you cloak a browser:
- Cloak Chrome or Edge
- Open three tabs: Gmail, a banking site, and a news site
- Switch between tabs while capturing
Pass: The browser window is absent from capture regardless of active tab.
Fail: A specific tab or the tab bar leaks during switching.
What to do: Multi-process browsers sometimes render tabs in separate processes. If the cloaking tool targets only the main browser process, child renderers may escape. NoCapture handles this recursively. With free tools, you may need to cloak each tab process individually if the tool supports it.
The Verification Habit
Professional screen sharers build verification into their pre-meeting ritual:
- [ ] Apply routine or manually cloak sensitive apps
- [ ] Snipping Tool spot-check on one cloaked window
- [ ] OBS or Zoom preview check
- [ ] Alt-Tab title check if title masking is enabled
- [ ] Notification test if shielding is active
- [ ] Multi-monitor check if using secondary displays
This takes under 60 seconds. It prevents the leaks that happen when you assume protection is active and it is not.
We wrote about the full checklist for screen sharing here.
The Limitation
These tests verify supported software capture paths. They do not test kernel-level bypasses or physical cameras. No tool can. But the tests do cover the paths used by Zoom, Teams, OBS, Snipping Tool, and the screenshot-hungry AI agents that are now standard on modern desktops.
We wrote about the honest limitations of all WDA-based tools 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.
