
A capture card or webcam that suddenly isn't recognized on a new laptop is almost never a dead device — it's a permission, driver, or power problem. On macOS, a fresh install or OS update quietly blocks camera access until you approve it in System Settings, and most people never see the prompt because it doesn't always appear the first time you open OBS. On Windows, a laptop bought in a different region can load a generic USB driver instead of the manufacturer's, which shows the device in Device Manager but not inside any capture app. And on USB-C-only laptops, capture cards and some webcams draw more power than a single port or a cheap hub can deliver, so the device connects, disconnects, and reconnects in a loop. Working through permissions, then drivers, then power, in that order, finds the actual cause in a few minutes.
Every app that wants to use a camera or capture device on macOS — OBS, Zoom, QuickTime, Elgato's own software — needs explicit permission granted in System Settings > Privacy & Security > Camera. On a brand new laptop, or one that's had a clean macOS reinstall, nothing has been pre-approved. The catch is that macOS doesn't always show the permission prompt reliably the first time you launch OBS, especially if OBS was installed via a method that doesn't trigger the standard first-run dialog — so the app just silently shows no video source, with no error explaining why.
Go directly to System Settings > Privacy & Security > Camera and check whether OBS (or whatever capture software you're using) is listed and toggled on. If it isn't listed at all, quitting and relaunching the app usually forces the prompt to appear. For capture card workflows that also record screen content, check Screen Recording permissions in the same section — a surprising number of "webcam not detected" reports are actually a Screen Recording permission blocking a related capture feature.
Laptops sold in different regions sometimes ship with different default driver packages, and Windows Update will often auto-install a generic UVC (USB Video Class) driver for a webcam or capture card the moment it's plugged in. That generic driver is frequently enough to make the device show up in the basic Windows Camera app, which makes it confusing when Elgato's 4K Capture Utility or a similar proprietary tool still reports no device found — proprietary capture software usually needs the manufacturer's own driver, not the generic one Windows substituted.
Open Device Manager and look under "Cameras" or "Sound, video and game controllers" for a yellow warning icon, or for an entry with a generic name like "USB Video Device" instead of the actual product name. If you see the generic entry, uninstall it (check "delete the driver software" if prompted), then download and install the manufacturer's driver directly from Elgato's or Magewell's official site rather than letting Windows Update reinstall its own version.
Capture cards like the Elgato HD60 X and most Magewell USB models draw meaningfully more power than a typical peripheral, and on a laptop with only USB-C ports and no powered USB-A, a single port — especially if it's also handling charging or a hub with several other devices — often can't supply enough current. The symptom isn't usually a clean "not detected"; it's the device connecting, working for a few seconds or minutes, then dropping out and reconnecting in a loop, sometimes with a Windows or macOS notification about a USB device drawing too much power.
The fix is a powered USB-C hub — one with its own external power adapter, not a passive multiport adapter — so the capture card gets dedicated power instead of sharing whatever the laptop's port can spare. This is the same root cause behind USB drives failing to mount reliably on USB-C-only laptops; see our USB drive not recognized guide for the equivalent issue with storage devices.
Rather than guessing, work through this in order, because each step isolates a different category of problem. First, test the device in a completely different app — Photo Booth or QuickTime on macOS, the built-in Camera app on Windows — to determine whether it's an OS/permission-level problem or specific to OBS. If it shows up there but not in OBS, it's almost always a permissions issue.
Second, if it doesn't show up anywhere, try a different USB port and, separately, a different cable — capture cards are sensitive to USB-C cables that don't support enough power or data bandwidth, and "charge only" cables are a common silent culprit. Third, if you have access to another computer, even briefly, plug the device into it; if it works there, you've confirmed the laptop (driver or power) is the issue, not the device itself. Only after ruling out all three should you suspect actual hardware failure.
Getting your capture card or webcam recognized solves the hardware side, but it's a separate problem from whether your stream actually holds up once you go live. If OBS sees your video source fine but your broadcast is still lagging, buffering, or dropping frames, that's almost always an upload bandwidth issue rather than anything to do with the capture device itself — see our livestream lag and dropped frames guide for that half of the problem.
It's worth testing both independently: confirm your video source is stable locally (recording to disk without issue) before troubleshooting network-side streaming problems, so you're not chasing a bandwidth fix for what's actually still a hardware or driver issue, or vice versa.
If you've been through permissions, drivers, and cables and your capture card or webcam is still invisible, it's faster to have someone walk through it with you directly than keep guessing.
We'll walk through permissions, drivers, and power delivery with you live and get your gear recognized again — no fix no fee, 50% refund if we can't.
Book a remote fix — $149.99That usually means Windows is using a generic UVC driver instead of the manufacturer's driver. Uninstall the generic entry in Device Manager and install the official driver from Elgato's or Magewell's site directly.
Yes — macOS permissions are per-app, so OBS, Zoom, and any other capture software each need to be individually approved under System Settings > Privacy & Security > Camera, even if you've already approved a different app.
Yes, if it's an unpowered or passive hub. Capture cards draw more current than the hub or laptop port can reliably supply alongside other devices, which causes the connect-disconnect loop. A powered hub with its own adapter solves this.
Almost never — this is very rarely a hardware failure. Work through permissions, drivers, and power delivery first; see our new device setup guide for general first-boot configuration steps on a replacement laptop.
Different laptops, especially ones bought in different regions or running a different OS version, ship with different default drivers and permission states. The webcam itself hasn't changed — the new machine's configuration has.
Test the device on a second computer if you have any access to one. If it works there, the problem is your laptop's driver, permissions, or power delivery, not the capture card or webcam itself.