App-Specific Video & Camera Conflicts
How to Force Close Background Services Locking Your Laptop Camera
The two most common hidden background service locks on a laptop camera are Windows' Camera Frame Server and macOS's VDCAssistant process — both covered in their own dedicated guides elsewhere on this site, and both can be forcibly restarted through a genuinely simple, safe command or menu action, without needing a full system restart in most cases.
Locating Hidden Media Service Locks
Unlike a visible application you can simply close through its normal window, these are background system services running invisibly, managing camera hardware access on behalf of whatever app currently needs it. When one of these services itself gets stuck — most commonly after a sleep/wake cycle or an app crashing while the camera was active — it can hold a stale lock that persists even after every visible application appears closed.
Windows and macOS handle this at a genuinely different architectural level, which is why each platform has its own specific service and its own specific restart method — there's no single universal command that works identically across both operating systems for this particular fix.
Commands and Methods to Terminate Camera Services
Step 1: Open the Start menu, search "Services," and find "Windows Camera Frame Server."
Step 2: Right-click it and select "Restart."
If it's not currently running, "Start" instead.
Step 1: Open Terminal
(Cmd + Space, type "Terminal").
Step 2: Run
sudo killall VDCAssistant and enter your admin password when prompted.
Step 3: Reopen whichever app needs the camera.
Both platforms automatically start a fresh instance of the relevant service the next time an app requests the camera. ↑ Test with the widget above.
If restarting the specific service doesn't resolve it, a full system restart remains a reliable fallback, since it clears every running process and service state regardless of which one was actually responsible for the original lock.
When to Use This vs. a Full Restart
Restarting the specific service directly, rather than your entire computer, is worth doing first simply because it's faster and preserves whatever else you currently have open and running — other applications, unsaved work, and your general session all stay intact, unlike a full restart which closes everything.
That said, there's no real downside to simply restarting your computer if you'd rather not deal with Services or Terminal commands at all — it accomplishes the same underlying goal of clearing a stuck lock, just less surgically and at the cost of closing everything else you had open at the time.
If you find yourself needing this fix frequently, that recurring pattern is worth noting — an occasional stuck service after an unusual event like a crash is normal, but a service that reliably locks up after every single sleep cycle points toward a deeper driver or OS-update-related issue worth investigating further, rather than just repeating the same manual restart indefinitely.
Keeping your operating system fully updated is a reasonable baseline precaution here too, since both Microsoft and Apple periodically refine exactly how these background camera-management services handle sleep and wake transitions, and a system running an older build may simply be more prone to this specific class of stuck-service issue than a current one.
A Few More Things to Check on Windows
How do I reset the Windows Camera app itself?
Go to Settings → Apps → Installed apps, find Camera, open its three-dot menu, and choose Advanced options → Reset. This clears the built-in Camera app’s own cache and settings without uninstalling it, which can fix a stuck, frozen, or permanently black preview even when the underlying device and driver are both working correctly. It only resets that one app — not your camera driver, and not other applications that use the camera.
Could my antivirus be silently blocking my camera?
Many third-party security suites — Bitdefender, Kaspersky, Norton, and ESET among others — include their own webcam-protection feature that runs independently of Windows’ own privacy settings. That means Windows can show camera access as fully permitted while the antivirus software blocks it anyway, at a layer Windows has no visibility into. Check the antivirus program’s own settings, usually under a Privacy, Webcam Protection, or similarly named section, and confirm your browser or conferencing app is on its allow-list.
How do I re-enable my camera in Device Manager if it's disabled?
Right-click the Start button → Device Manager, expand Cameras or Imaging devices, and look for a greyed-out icon or a small down-arrow badge. Right-click that entry and choose Enable device. This is a different action from updating a driver — a disabled device won’t respond to any other fix until it’s explicitly re-enabled here first, so it’s worth checking before assuming the problem is a driver or a permission.
Is Windows' own camera privacy toggle blocking access, separately from anything else?
Windows keeps a system-level camera permission at Settings → Privacy & security → Camera, completely separate from Device Manager, the Camera app, and any antivirus software. This one screen has a master Camera access switch plus a per-app list beneath it — both need to be on. It’s worth checking directly, since a camera can show as fully enabled and working in Device Manager while this toggle silently blocks every app from reaching it.
For a full check of resolution, frame rate, and audio together, not just this one issue, the free webcam test covers all of it in one place.