Discord Camera Not Detected 2026 (Windows 11 24H2 Fix)

What is the Discord camera not detected error?

When you open User Settings > Voice & Video in Discord and the Camera dropdown shows "No Video Device", or your webcam is listed but the preview stays black, Discord cannot enumerate or access a working video source. The mic and speakers still work; only the camera path is broken. This surged sharply across Windows 11 24H2 and 25H2 in 2026 because Microsoft tightened the camera privacy permission model and now requires apps to be explicitly granted access through a redesigned Settings page — and Discord no longer trips the legacy auto-prompt.

The other 2026-specific cause is the explosion of virtual cameras (OBS Virtual Camera, NVIDIA Broadcast, Snap Camera, e2eSoft VCam). When two of these are installed, the Windows camera enumeration order is unstable, and Discord locks onto a placeholder device that returns no frames.

When does it occur?

• After upgrading to Windows 11 24H2 or 25H2 (KB5077181 / KB5089549 / KB5074109)
• After installing OBS Studio, Streamlabs, NVIDIA Broadcast, or any virtual camera
• After Discord's auto-update from 1.0.9180 to 1.0.9181+
• After connecting a new USB webcam (Logitech C920, StreamCam, Razer Kiyo, Insta360 Link)
• Immediately after a Teams or Zoom call (camera held by another process)
• On laptops where the camera privacy shutter is physically closed but not recognized by Windows

Common causes

• Windows 11 24H2 Camera Privacy permission revoked or never granted (the new model is opt-in)
• Multiple virtual cameras installed confusing Discord's device enumeration
• Discord overlay holding an exclusive lock on the camera after a previous call
• Outdated USB Video Class (UVC) driver for the webcam
• Discord Stable lagging behind the camera-stack rewrite shipped in PTB/Canary 0.0.620+
• Windows Hello / Face Recognition keeping the IR camera in an exclusive session
• Group Policy or MDM disabling camera access on managed or work laptops
• USB power saving putting the camera into selective suspend mid-call

Step-by-step fixes

1. Fix Windows 11 24H2 camera permissions FIRST — Open Settings > Privacy & security > Camera. Confirm three toggles are ON: Camera access (top), Let apps access your camera, AND Let desktop apps access your camera (scroll to bottom — this last one is the new 24H2 toggle most guides miss). Discord is a desktop app, not a UWP app, so the bottom toggle is the critical one. Restart Discord fully (right-click tray icon > Quit Discord).

1. Reset Discord's camera selection — In Discord: User Settings > Voice & Video > Camera dropdown. Switch to "No Video Device", wait 3 seconds, then switch back to your actual webcam. This rebuilds Discord's MediaFoundation session, fixing cases where Discord cached an old device path that no longer matches the enumerated camera list after a Windows update.

1. Disable conflicting virtual cameras — If you have OBS Virtual Camera, NVIDIA Broadcast, Streamlabs, Snap Camera installed simultaneously, stop all of them (and stop their background services from services.msc). Test Discord with only the physical webcam. To permanently fix: in OBS, never leave Virtual Camera running when not streaming; in NVIDIA Broadcast, set Camera off when idle. Each installed virtual camera adds an entry to HKLM\SOFTWARE\Microsoft\Windows Media Foundation\Platform\VideoDevices, and Discord can latch onto an empty one.

1. Close camera-locking apps — Open Task Manager (Ctrl+Shift+Esc), end any of: Microsoft Teams, Zoom, Skype, OBS, Snap Camera, NVIDIA Broadcast UI, Windows Hello Face. Cameras under MediaFoundation can only have one exclusive owner — if Teams crashed mid-call, it can leave a dangling lock until reboot.

1. Update or roll back webcam driver — Open Device Manager > Cameras (or Imaging devices), right-click your webcam, Update driver > Search automatically. If that doesn't help, Properties > Driver > Roll Back Driver. For Logitech, install Logi Tune instead of the deprecated Logitech Capture. For Razer Kiyo, Razer Synapse 4 ships the current UVC driver.

1. Switch to Discord PTB or Canary — The camera stack rewrite shipped in 0.0.620+ (Canary) and PTB build 1.0.1126+ has a redesigned device enumerator that fixes Windows 11 24H2 detection. Download from [discord.com/download/canary](https://discord.com/download/canary) — Canary can run side-by-side with Stable.

1. Clear Discord cache — Quit Discord fully. Delete %appdata%\discord\Cache, %appdata%\discord\Code Cache, and %appdata%\discord\GPUCache. Relaunch. A corrupted cache from a pre-24H2 install can keep referencing the old camera permission model.

1. Disable USB selective suspend for the webcam port — Open Power Options > Change plan settings > Change advanced power settings > USB Settings > USB selective suspend setting > Disabled (both on battery and plugged in). For external webcams, this prevents Windows from cutting power mid-call and dropping the camera from Discord's device list.

If it still doesn't work

If Discord still shows "No Video Device" after all eight fixes, run [Microsoft's Camera troubleshooter](https://support.microsoft.com/windows/camera-doesn-t-work-32adb016-b29c-a928-0073-53d31da0dad5) (Settings > System > Troubleshoot > Other troubleshooters > Camera) — it can repair a broken MediaFoundation registration that no app can work around manually. On managed/work laptops, check gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > App Privacy > Let Windows apps access the camera — if set to "Force Deny", your IT admin has blocked all camera access regardless of user setting. As a last resort, fully uninstall Discord (and delete %appdata%\discord and %localappdata%\Discord), then reinstall from discord.com — this regenerates the MediaFoundation device cache from scratch, which fixes the rare case where Discord's stored device GUIDs no longer match any device on the system.