Fix HP monitor or EliteDisplay webcam not working
Get the HP EliteDisplay E221c or similar monitor webcam working: USB detection, privacy permissions, app input, and when the microphone is a separate issue.
What is going wrong
If an HP EliteDisplay with a built-in camera, including the E221c and the similar E240c, shows a picture on the screen but the webcam does not appear, stays black, or is refused by an app, the camera is almost always a USB capture device. The cable that drives the display does not carry webcam video. Until a working USB link exists, the operating system cannot detect the camera, and no app can use it.
Three layers fail in different ways and need different fixes: device detection (the computer does not see a camera), access permission (the computer sees it but the system or browser blocks capture), and active input selection (a camera is allowed, but the app is using another device or cannot open this one). Microphone audio is a separate capture path. A silent mic does not prove the webcam is broken, and a working picture does not prove the mic is selected.
This guide is for a missing, blocked, or failed webcam on these monitors. It does not include official HP driver names, firmware versions, or factory-reset steps; those should come from HP’s documentation for your exact model and operating system before you change firmware or reinstall vendor software.
Checks that narrow the cause
Work through these checks in order. Each one only tests the layer named here. A pass or fail does not prove anything about a layer you have not tested yet.
1. Confirm the USB path, not the picture on screen
A bright, correctly sized desktop only proves the video cable (DisplayPort, DVI, VGA, or HDMI, depending on what you connected) is working. Webcam and monitor-mic data travel over USB. Look for a USB cable from the monitor’s computer-facing USB upstream port to a USB port on the PC or docking station. If that cable is missing, plugged into a charge-only port, or sitting in a dead hub, the camera will not enumerate.
Reseat both ends, try a different USB port on the computer itself, and avoid unpowered hubs for this first test. This check only tests physical USB connectivity and power. It does not prove the camera sensor, the microphone, Windows privacy, or an app’s device list.
2. See whether the operating system detects a camera
On Windows, open Settings, then Bluetooth and devices (or Devices on older builds), and look under Cameras. You can also open Device Manager and look under Cameras or Imaging devices. On macOS, a USB camera that has enumerated typically appears in System Information under USB, and in an app’s camera menu. If no camera device appears after a solid USB connection, the problem is still detection: cable, port, hub, or the monitor’s USB function. If a camera device does appear, detection has succeeded and the next layers are permission and selection.
Device Manager or a camera list only reports what the OS enumerated. A yellow warning or a missing device is not proof the sensor is faulty. An entry that looks healthy is not proof an app can open it.
3. Check for a privacy cover or a blocked lens
Many EliteDisplay webcams sit in the top bezel. If the model has a sliding privacy shutter, or if a sticker, sliding door, or object covers the lens, the OS can still list the camera while every preview is black. Open the shutter fully and confirm the lens is unobstructed. A covered lens explains a black image. It does not explain a missing device in Settings, and it does not explain a muted microphone.
4. Separate permission from selection
On Windows 10 and Windows 11, open Settings, Privacy and security, then Camera. Camera access for the device must be on, and access for desktop apps must be on if you use a classic meeting or recording program. Store apps need their own camera toggle. Browsers need camera permission for that site as well; a browser prompt or the site’s padlock controls are a different switch from the Windows camera privacy page.
On macOS, open System Settings, Privacy and Security, Camera, and allow the app you are testing. A denied system or browser permission produces “camera in use,” “could not start video,” or a blocked icon even when Device Manager lists the camera. This check does not test the USB cable and does not tell you which camera the app actually selected.
5. Confirm the app is using this monitor’s camera
Laptops and docks often expose more than one camera: the built-in notebook camera, an IR login camera, a dock camera, and the EliteDisplay. In the meeting or recording app, open video settings and choose the HP or EliteDisplay camera by name if it is listed. Close other apps that might already hold the device (another browser tab, the Windows Camera app, a background meeting client). Only one program can usually capture a given USB camera at a time.
Choosing the correct device in one app does not change another app. A preview in Windows Camera tests that Windows can open the device. It does not prove a browser has permission, and it does not prove the microphone is the one the meeting app is using.
6. Treat the microphone as its own path
If the picture works and people cannot hear you, stay in audio settings. On Windows, open Settings, System, Sound, and check the input device; also check Privacy and security, Microphone. In the meeting app, select the monitor’s microphone explicitly rather than “Default.” Mute switches in the app, in Windows, and on a headset are independent. A working webcam preview does not test the mic. A selected headset mic will stay silent for the monitor’s array even when the EliteDisplay camera is correct.
What to change, and how you know it worked
Change only what the matching check supported. Start with reversible steps, then retest the original symptom in the same app you care about (preview plus a real call if that is where it failed). Stop if the symptom is gone. If it remains after the steps below, escalate rather than stacking unrelated resets.
If the camera is not detected
- Connect a known-good USB cable from the monitor’s USB upstream port to a USB port on the PC or a powered dock. Unplug display-only adapters from this test; they do not carry the camera.
- Use a different USB port on the computer, preferably USB-A or USB-C that already enumerates other devices.
- Power-cycle the monitor and unplug the USB cable for several seconds, then reconnect so the USB function can re-enumerate.
- Retest: the camera should appear under Cameras (Windows) or as a USB imaging device, and a simple camera app should show a live image with the lens uncovered.
If it still never appears, the remaining causes are a failed USB upstream port on the monitor, a failed port or controller on the PC, or a hardware fault in the camera module. Those need inspection or support for the specific EliteDisplay model. Do not treat a missing device as a privacy-setting problem.
If the camera is detected but apps cannot open it
- Turn on camera access for the device and for desktop apps (Windows) or grant Camera access to the specific app (macOS).
- In the browser, allow camera access for the meeting site and reload the tab.
- Quit other capture apps and extra meeting windows, then choose the EliteDisplay camera in the app’s video device list.
- Open the privacy shutter and confirm the preview is a live room image, not a frozen last frame.
Success is a live preview in the same app that failed, with you moving in frame. If Windows Camera works and only one browser still fails, the remaining issue is that browser’s site permission or an extension blocking getUserMedia; it is not the monitor hardware.
If video is fine and audio is not
- Set the meeting app’s microphone to the EliteDisplay (or to the headset you actually wear), not Default if Default points somewhere else.
- Unmute the app, the system input, and any hardware mute.
- On Windows, allow microphone access for the device and for desktop apps, then retest a short recording or call.
Success is other people hearing a live voice, or a system sound recorder showing input level when you speak. Leave webcam settings unchanged once the picture already works.
If the image is dark, noisy, or badly exposed
Once the correct camera is selected and the lens is open, lighting in front of you matters more than a second round of cable swaps. Face a light source, avoid a bright window behind you, and wipe the lens. App-side beauty filters and automatic exposure can also crush or smear the image; disable them to see the raw camera. These steps test scene lighting and software processing. They do not prove a sensor defect.
Drivers, firmware, and resets
USB cameras on these monitors often use a generic UVC driver that Windows already includes. Reinstalling a random webcam driver from an unrelated pack can replace a working generic driver with the wrong one. If Device Manager shows the camera with an error, note the exact error code and use HP’s software and driver page for your model and OS, or Windows Update, rather than an unofficial bundle.
Firmware or a factory reset of the monitor can affect USB hub behavior, but it can also wipe monitor settings (input, color, power). There is no substitute here for HP’s procedure for the E221c, E240c, or your specific EliteDisplay: follow that document, including any warning that USB devices will disconnect during the update. After any driver or firmware change, retest detection first, then permission, then the original app.
When to stop and escalate
Stop once the original app shows live video (and live audio, if that was the complaint). Escalate to HP or the PC vendor if the camera never enumerates on more than one USB port and cable, if it enumerates then immediately disappears, or if it is detected everywhere but every preview is black with the shutter open. Have the monitor model (for example E221c or E240c), the OS version, and whether the display image itself is normal; that split tells support whether they are looking at a USB capture fault or a video-cable fault.