UVC webcam not working

What is going wrong

A USB 2.0 HD IR UVC webcam is a USB Video Class camera. UVC is a standard, so Windows, macOS, and typical Linux setups already ship a class driver. When this device does not work, the usual cause is one of four separate problems: the computer never detects the camera, the operating system or browser has blocked camera access, the app has selected the infrared sensor instead of the color sensor, or another program already has the camera open.

The IR part of the name changes the diagnosis. Many laptops and some USB cameras expose two video devices with similar labels: a color HD camera for calls and recording, and an infrared camera for face unlock. An app that opens the IR device often shows a black, purple, or very dark picture, or reports that the camera failed to start. That is expected for the IR sensor in a normal video call; it is not proof that the color camera is broken.

Treat the microphone as a separate path. Video capture and audio capture are different streams. A UVC webcam’s microphone is typically a USB audio device. Color video with no sound, or sound with no video, points to permission or input selection for that stream, not a single failed “webcam” unit. The same split applies to device detection, access permission, and which input the app is using: a camera can be plugged in, still blocked, and still the wrong device in the app’s camera menu.

Match the symptom to the layer that failed

What you see	Layer to check first
The camera does not appear in the system camera list or Device Manager / imaging devices	Detection: USB connection, port, cable, or class driver
The camera is listed, but the OS, browser, or app says access is blocked	Permission: system privacy settings, then app or browser camera access
The camera is listed and allowed, but the picture is black, dark, or “in use”	Selection or occupancy: IR versus color camera, privacy shutter, or another app holding the device
Video works and the microphone does not, or the reverse	Separate audio or video input: wrong mic, muted capture, or audio permission

Generic names such as USB2.0 HD IR UVC Webcam, USB2.0 HD UVC Webcam, and USB2.0 VGA UVC Webcam are class labels, not a single product. They appear on many laptops, including some ASUS models, and on external USB cameras. VGA in the name means a lower-resolution color sensor, not a different troubleshooting method. Without the exact operating system, error text, and whether the unit is built-in or external, later steps stay general.

Confirm the computer can see the camera

If the device is missing from the system camera list, fix detection before changing app settings. For an external camera, use a direct USB port on the computer, try a second USB 2.0-capable port, and reseat the cable. An unpowered hub that already carries other devices can prevent a USB 2.0 webcam from starting because the camera and hub share the same bus bandwidth. A built-in camera that vanished after a BIOS, firmware, or Windows update may be disabled in firmware or by a function-key camera toggle; those controls vary by manufacturer and model, so use the laptop’s hardware documentation for the exact key or firmware screen.

On Windows, look under Cameras or Imaging devices for the UVC name. A yellow warning or a missing device there is a detection or driver problem. The built-in UVC class driver is the normal driver for this device; a missing Microsoft USB Video Device or USB Video Class entry is more useful than installing a random third-party package. On macOS, check System Settings for the camera in the app’s device list and in Privacy & Security. On Linux, the usual kernel module is uvcvideo; the camera should appear as one or more /dev/video nodes. Multiple nodes are common when the hardware exposes both a color device and an IR or metadata device.

Unblock access, then choose the color camera

Once the device is listed, the next failure is permission. Windows has a system camera privacy switch and per-app camera permission. macOS has Privacy & Security camera permission per app. Chromium-based browsers and Firefox have their own site camera permission on top of the OS switch. An allowed OS camera with a blocked browser site still produces a failed preview. Microphone permission is independent: granting camera access does not grant microphone access.

If access is allowed and the preview is still wrong, open the app’s camera menu and select the color HD device, not the IR device. Names overlap, so pick the entry that produces a normal color image. Leave the IR camera for face unlock. Also close other apps that capture video, including meeting tools, browser tabs, camera utilities, and Windows Hello setup if it has the IR device open. Only one client normally gets exclusive access to a given UVC node. On laptops, confirm the privacy shutter or LED cover is open; a closed shutter looks like a dead sensor.

Check the microphone only if audio is the problem

If you need the webcam mic, select that microphone as the recording or call input. OS sound settings, the meeting app, and the browser can each point at a different device, such as a headset or the laptop’s built-in array. Mute switches, per-app microphone permission, and exclusive-mode audio can silence a mic that the system has already detected. Do not replace the UVC video driver to fix a silent microphone; that is a different device class.

What this guide cannot pin down from the query alone

• The operating system, app, and exact error text were not specified, so menu names above are the usual places to look rather than a guaranteed path on every build.
• Whether the unit is a laptop module or an external USB camera changes the USB-port and shutter checks.
• Which of the two UVC nodes is the color camera cannot be read from the generic device name; that is confirmed only in a live preview.
• No test result, resolution, frame-rate, or ASUS-model compatibility claim is included here because none was supplied.