You open Teams for a meeting, and your video feed is black — or the camera app says it cannot find your camera at all. On a brand-new Copilot+ PC this feels especially wrong, because the hardware is barely months old. The good news: camera failures on AI PCs are almost never dead hardware. They are driver, privacy, or stream-conflict problems, and they resolve quickly once you find the right layer.
Copilot+ PCs add one wrinkle you will not see on older laptops. Many of them route the camera through the NPU for Windows Studio Effects — background blur, automatic framing, and eye contact correction. If that NPU pipeline stalls, the whole camera feed can freeze even though the sensor itself is fine. A related guide covers what to do when your Copilot+ PC microphone stops working at the same time, since audio and video often break together after the same update.
This guide walks you through every layer in order: privacy toggles, app conflicts, the driver stack, and firmware.
Why this happens
- Camera privacy is switched off: Windows 11 has both a master camera toggle and per-app permissions. One flipped switch silently blocks every app.
- Windows Studio Effects locks the stream: The NPU-powered effects pipeline can crash and hold the camera hostage, so other apps see a black feed. If apps are not using your AI hardware correctly, our guide on NPU not used by apps in Windows 11 explains the underlying cause.
- Driver failed after a Windows update: A feature update can replace your working camera driver with a generic or incompatible one.
- Another app is holding the camera: Zoom, Teams, Discord, or a browser tab can keep an exclusive lock on the device.
- Physical privacy shutter is engaged: Many AI laptops have a hardware shutter or a function-key camera kill switch that software cannot override.
- Camera filter or virtual camera software conflicts: Third-party virtual cameras (OBS, Snap Camera leftovers) intercept the feed and break it.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Check the physical shutter and function keys
Start with the hardware, because no software fix can help if the lens is physically covered. Many Copilot+ PCs ship with a sliding privacy shutter above the display, and some add a dedicated camera kill switch or an Fn key combo that disables the camera at the firmware level.
- Look above the display for a small sliding shutter and make sure it is fully open.
- Check your function keys for a camera icon (often F8 or F9) and press Fn + that key to toggle the camera on.
- On Lenovo models, confirm the ThinkShutter is not slid closed; on HP models, check the physical kill switch on the side.
- Open the built-in Camera app and test again before touching any software settings.
Fix 2: Verify Windows camera privacy settings
Windows 11 can silently block camera access after an update resets privacy toggles. If the master switch is off, every app reports a black or missing camera even though the device is healthy.
- Open Settings > Privacy & security > Camera and turn on “Camera access.”
- Scroll down and enable “Let desktop apps access your camera” as well.
- Confirm Teams, Zoom, and your browser each have their individual toggle enabled.
- Restart the video app and re-test the camera feed.
Fix 3: Close apps holding the camera hostage
Only one app can cleanly own the camera at a time — a background Zoom session or a crashed Studio Effects process can hold the stream open, leaving other apps with a black feed.
- Close Teams, Zoom, Discord, and any browser with video tabs open.
- Open Task Manager, end any leftover processes for those apps, and look for “Windows Camera Frame Server” to restart.
- Open the Camera app — if it works there, the problem was an app conflict, not the driver.
- For a related audio conflict, see our guide on the Copilot+ PC microphone not working and clear both pipelines together.
Fix 4: Restart the Studio Effects pipeline
Windows Studio Effects routes the camera through the NPU. When that pipeline stalls, the feed freezes or goes black across all apps.
- Open Settings > Bluetooth & devices > Cameras and select your built-in camera.
- Turn off all Studio Effects (background blur, eye contact, automatic framing) and test the raw feed.
- If the feed returns, re-enable effects one at a time to find the one that crashes.
- Sign out and back in (or restart) to fully reset the NPU effects pipeline if the freeze persists.
Fix 5: Reinstall the camera driver cleanly
If Device Manager shows the camera with a warning icon, or as an unknown device, the driver is corrupted. A clean reinstall forces Windows to load a fresh copy from the driver store.
- Open Device Manager, expand “Cameras,” right-click your camera, and choose Uninstall device.
- Tick “Attempt to remove the driver for this device” and confirm.
- Restart the laptop — Windows will reinstall a driver automatically.
- If it still fails, download the camera driver from your maker’s support page (for example Dell Support or HP Support ) and install it manually.
Fix 6: Reset the Camera app and check for firmware updates
When the driver is healthy but the Camera app itself misbehaves, a reset clears its corrupted state. Pair this with a firmware check, since several Copilot+ PC makers fixed camera bugs in BIOS updates.
- Go to Settings > Apps > Installed apps > Camera > Advanced options and click Reset.
- Check Settings > Windows Update for pending updates and install them.
- Visit your manufacturer’s support site and apply any camera or BIOS updates listed for your model — Microsoft documents general camera fixes on the Windows support hub .
- As a last resort, roll back the most recent Windows update from Settings > Windows Update > Update history > Uninstall updates.
Closing
Camera failures on Copilot+ PCs look dramatic but are rarely hardware problems. Work from the shutter to privacy to the Studio Effects pipeline to the driver, testing after each step, and you will isolate the fault fast. If nothing here restores video, the camera module itself may have failed — contact your manufacturer’s support while the warranty is active, and mention that you already ruled out software causes. See also our guide to Steam games on ARM laptops for gaming-side driver quirks.
