Fake Cam Not Showing Up? Work Through These Fixes

You started the virtual camera, opened your conferencing app, and the camera dropdown shows the same devices it always did. This is the most common problem with a fake cam, and it is almost never a broken install — the causes below are ordered by how often they turn out to be the real one.

1. You started the conferencing app first

Zoom, Teams and Discord scan for cameras when they launch and then stop looking. A virtual camera that appears afterwards will not be in the list, no matter how many times you reopen the settings panel.

Quit the conferencing app completely — on Windows it usually keeps running in the system tray after you close the window, and on macOS you need Cmd + Q. Then start the virtual camera, and only then start the conferencing app.

2. The virtual camera app is not actually running

The device exists only while the app driving it is open. If you closed the window, or it quit after a sleep/resume cycle, the camera vanishes from every app's list. Check that it is still open and that the camera is started, not merely loaded — most apps, CamLooper included, have a distinct start control separate from picking the file.

3. Narrow it down with a second app

Before you change anything else, find out whether the problem is the camera or the app asking for it. Open a webcam test page in your browser, or your OS camera app, and look for the device.

• It shows up there but not in Zoom — the camera is fine; the problem is that app's device list. Go back to fix 1.
• It shows up nowhere — the camera is not registered with the OS. Continue below to the platform-specific section.

4. Another app has the camera

On Windows a capture device can usually be opened by only one application at a time. If a browser tab from an earlier test still holds it, or Zoom is running in the background with video on, the next app gets nothing — sometimes a black frame rather than an error. Close everything that touches a camera, then try again.

Windows: the driver may not be registered

A Windows virtual camera is a DirectShow filter registered under a CLSID. If installation could not write that registry entry — an install that was not elevated, or an antivirus tool that blocked it — the app runs but its camera never appears.

Check whether the class is registered, in PowerShell:

Get-ChildItem 'HKLM:\SOFTWARE\Classes\CLSID' | Where-Object { $_.GetValue('') -like '*CamLooper*' }

If nothing comes back, reinstall and accept the elevation prompt. CamLooper also re-registers its driver on first camera use when it finds the entry missing, which fixes this in one step — that is the one UAC prompt you may see the first time you start the camera.

Also worth knowing: 32-bit applications need the 32-bit registration. If the camera appears in some Windows apps but not an older one, this is usually why.

macOS: signing is not optional

Camera extensions on macOS must be signed and notarized by Apple. An unsigned or ad-hoc signed build will launch and look completely healthy while its camera silently never registers — there is no error message to find.

Install from the developer's official download rather than a repackaged copy, and after the first install check System Settings → Privacy & Security for a blocked-software prompt waiting to be allowed. Some apps also need a full logout or restart before the extension loads.

Linux: check the kernel module

Linux virtual cameras go through v4l2loopback. Confirm the module is loaded:

lsmod | grep v4l2loopback

And that the device node exists:

ls -l /dev/video*

If the module is missing, load it with sudo modprobe v4l2loopback. Two things break this repeatedly:

• A kernel update. The DKMS module has to rebuild for the new kernel. If it did not, reinstall the v4l2loopback-dkms package and reboot.
• Secure Boot. Unsigned out-of-tree modules are refused outright. Either enrol a MOK key or turn Secure Boot off.
• Permissions. Your user needs to be in the video group. Check with groups, and log out and back in after adding yourself.

Installing CamLooper from the .deb or .rpm handles the module setup for you, which removes most of this list.

Browser-specific: Meet and other web apps

Meet runs in the browser, so the browser has to allow camera access for the site and has to have picked up the new device. Reload the tab after starting the virtual camera — Chrome in particular caches the device list per page load. If the site permission was previously denied, clear it from the padlock icon in the address bar; a denied permission produces the same empty dropdown as a missing camera.

It appears, but the picture is black

A device that is listed and selected but shows black is a different problem from one that is missing. Usually it is one of: no video file loaded, the camera started but playback paused, another app holding the device, or a resolution the conferencing app will not accept. Try 1280×720 first — it is the resolution every app supports.