Windows 11: What an Interview App Can Record

On Windows 11 you cannot approve or revoke screen recording for an individual desktop application. Microsoft's own support documentation states that "Camera privacy settings for desktop apps can't be changed at an individual desktop app level," and warns that desktop apps "might still be able to access your camera or microphone even when these settings are turned off" (Microsoft, Manage app permissions for a camera in Windows). For screen capture there is not even a desktop-app toggle to turn off.

What Windows gives you instead is an audit trail: a list of executables that have already touched the camera or microphone, plus live indicators while they are in use. That is a different kind of protection from the one macOS offers, and it changes what is worth checking before you install an interview or assessment application. Facts here are current as of 25 October 2026 and are drawn from Microsoft and Apple documentation.

What Windows gates per app, and what it does not

Windows 11 splits applications into two groups for privacy purposes. Packaged apps from the Microsoft Store appear individually under Settings > Privacy & security > Camera and Microphone, each with its own switch. Everything else — anything installed from an installer you downloaded, a USB drive, or an IT administrator — is a "desktop app" and is governed by a single device-wide toggle that applies to all of them at once. Microsoft notes that "If an app isn't in the list, it might not be a Microsoft Store app. Instead, it might be a desktop app," and that the desktop-app setting is what browsers and video conferencing clients such as Microsoft Teams rely on (Microsoft, Manage app permissions for a camera in Windows).

Assessment and proctoring desktop clients are almost always in that second group. So the practical choice on a stable Windows 11 install is not "allow this proctoring app the camera"; it is "allow every desktop app the camera, including this one," or break Teams, Zoom, and your browser along with it.

Screen capture is a packaged-app permission

Screen recording is governed separately, and more narrowly. The Windows policy that controls it, LetAppsAccessGraphicsCaptureProgrammatic, "specifies whether Windows apps can take screenshots of various windows or displays," and its per-app form works by "specifying a Package Family Name," which Microsoft tells administrators to retrieve with the Get-AppPackage PowerShell cmdlet. It is supported from Windows 11 version 21H2 onward (Microsoft, Privacy Policy CSP).

A Package Family Name is an identifier that packaged applications carry. An unpackaged desktop installer does not have one, which suggests that the per-app form of this permission cannot address it — the documentation describes the mechanism, not the gap, so treat that as inference rather than a documented statement. Either way, the user-facing Screenshots and screen recording page in Windows privacy settings is not the place where a conventional desktop proctoring client asks you for capture consent, because on Windows it does not have to ask at all.

This is the most consequential difference between the two desktop platforms for anyone taking a remote assessment, and it applies to any unpackaged desktop software — including the assessment clients covered in what changes when the coding assessment is an application rather than a website.

How macOS handles the same question

Apple's model is a per-application allow list. In macOS Tahoe 26, System Settings > Privacy & Security > Screen & System Audio Recording lists each app and lets you switch it on or off, and Apple describes the choice as granular: "You can allow apps to record both your screen and audio, or just your audio" (Apple, Control access to screen and system audio recording on Mac).

That list is also a disclosure mechanism. An application that wants to see your screen has to appear in it. On Windows there is no equivalent roster to read, which is why the Windows audit steps below are observational rather than permission-based. For the Mac side of this, see the companion walkthrough on auditing what an interview app can record on macOS.

The per-app change in testing does not cover screen capture

Microsoft is narrowing the gap, partially. Windows 11 Insider Experimental build 26340.9233, released 21 August 2026, added per-app permissions for desktop applications: "Windows Insiders can now manage camera, microphone, and location permissions for individual desktop apps. Previously, access for traditional desktop applications was managed through a single device-wide setting." Apps that have not yet used a resource "prompt for permission the first time access is requested," and existing decisions are preserved (Microsoft, Windows 11 Insider Experimental Preview Build 26340.9233). Microsoft also published an IT Pro Blog post on the change, Giving you more control over camera, microphone, and location, last modified 23 September 2026.

Three limits matter for an interview:

• The change covers camera, microphone, and location. Screen capture and screenshots are not among them in any of the announcements above.
• It was introduced in the Experimental Insider channel. Microsoft's stable consumer documentation still says desktop-app camera settings cannot be changed per app, and the Insider build announcements published through 23 October 2026 do not announce general availability — that is an observation from reading those posts, not a statement from Microsoft about shipping plans.
• Enterprise policy still governs managed machines. The release notes say "Existing enterprise policies continue to function as designed," so on a company-managed device the decision may not be yours at all.

If the interview is on a work machine, the device-management layer matters more than any of these settings, which is the subject of what IT can see when you interview on a work laptop.

What you can actually verify before an interview

Read the device list for camera and microphone

Open Settings > Privacy & security > Camera, then Microphone. Microsoft describes what you will find there: "Here you will find the list of desktop apps that Windows has detected which have interacted with the camera or microphone." Selecting an entry shows details including the file that accessed the device, and where a Windows component acted on an app's behalf, the component is listed instead (Microsoft, Windows camera, microphone, and privacy).

That file path is the useful part. After you install an assessment client and complete its setup check, the executable that opened your camera should be one you can account for.

Watch the live indicators

Microsoft documents three signals: "If your device has a camera light, the light turns on when the camera is active"; if there is no light, "Windows shows a notification when the camera turns on or off"; and "A microphone icon appears in the notification area of the taskbar when an app is using the microphone" (Microsoft, Windows camera, microphone, and privacy).

Know what these steps do not show

Neither the device list nor the indicators covers screen capture. There is no documented taskbar indicator for an application reading your display, and no per-desktop-app roster to inspect. Microsoft also cautions that desktop apps "may not always appear in the list of apps available on the Camera and Microphone settings pages," so absence from the list is weak evidence. If you need to know what a particular platform records, the platform's own documentation and your assessment invitation are better sources than the operating system.

Windows Recall is a separate consideration on machines where it is enabled, because it writes its own record of what was on screen; that is addressed in what Windows Recall saves during your interview.

One Teams case that catches candidates out

If your interview runs in a Microsoft Teams meeting with the Teams Premium screen-capture prevention option enabled, platform support decides your experience. Microsoft documents that screenshots on Teams for Windows desktop "show a black rectangle over the meeting window," while attendees on Teams for macOS desktop, Teams on the web, virtual desktop, Cloud Video Interop, and Teams Rooms on Android "will join an audio-only experience." In meetings above 1,000 attendees, anyone joining after the first 1,000 also gets audio only (Microsoft, Prevent screen captures in Microsoft Teams meetings).

The organizer enables it, it is off by default, and turning it on mid-meeting only applies "after everyone leaves and rejoins." Worth knowing if you plan to join a technical interview from a Mac or a browser and expect to see a shared screen.

The asymmetry cuts in both directions

The same gap means Windows does not surface a desktop assistant per application either. Control is a desktop application for Windows and macOS, and its pricing page states it was tested against current Zoom desktop releases, the HackerRank desktop app, and browser-based screen recording as of October 2026 — a vendor statement about specific tested configurations, not a general property of every meeting client, operating system version, or proctoring stack. Platform behavior changes, and a capability verified against one release is not a guarantee about the next.

Separately, most employers and assessment platforms prohibit outside assistance during an interview or test. Understanding what a tool can do is not the same as being permitted to use it, and the rules for a specific assessment are stated in its instructions.

What to take away

On Windows 11, treat the operating system as a witness rather than a gatekeeper. You can confirm after the fact which executable used your camera or microphone, and you can see live indicators while they are in use. You cannot, on a stable install today, grant one desktop app camera access and deny another, and you cannot approve screen capture app by app the way macOS asks you to. Decide what to install on that basis, read the assessment's own disclosures for what it records, and if you need per-app control over capture, a Mac currently gives you more of it.

If you want to see how a desktop overlay behaves against focus and capture checks before an interview rather than during one, Control's focus test runs those checks in your own browser.