Webcam Not Working for Proctorio or ProctorU? Run This Checklist Before Your Exam
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Webcam TestIf your webcam is not working for Proctorio or ProctorU, the cause is almost always one of three things: a Chrome permission block at the OS level, a USB controller bandwidth conflict from too many devices on one hub, or a stale INF driver entry that reports the camera as available when it is physically disconnected from the enumeration chain. Proctorio and ProctorU both run permission checks inside a Chrome extension sandbox, which means they cannot override a system-level camera block the way a native app sometimes can. The extension sees a denied device handle and reports no camera found, even though Device Manager shows the hardware as healthy.
Run a Baseline Camera Check First
Before you touch any settings, confirm the camera actually outputs a signal. Open the Webcam Test in Chrome and click Allow when the browser asks for camera access. If you see a live image there, the sensor and lens assembly are functional and the problem is isolated to how Proctorio or ProctorU is reading the permission state. If the webcam test also fails, you have a hardware or driver problem that needs to be solved at the OS level before the proctoring software will ever work.
Note which resolution the test reports. Proctorio requires a minimum of 640x480 at a stable frame rate. Several budget USB cameras, particularly ones using the SunplusIT SPCA series chipset, will enumerate at 640x480 in their descriptor but silently drop to a partial frame when USB bandwidth is constrained, which causes the extension's frame validation to time out.
Fix Chrome and OS-Level Permission Blocks
This is the most common reason webcam not working for Proctorio errors appear on otherwise healthy machines. Chrome maintains its own permission layer on top of the OS, and both have to be open simultaneously.
- In Chrome, go to chrome://settings/content/camera. Under the Allowed section, confirm the proctoring site domain is listed. If it is under Blocked, click the trash icon and reload the exam page to re-trigger the permission prompt.
- On Windows 11 or 10, go to Settings > Privacy & Security > Camera. Toggle Camera access to On, then scroll down and confirm that the toggle for Google Chrome is also On. A Windows update in late 2022 reset these toggles silently on many machines.
- On macOS, go to System Settings > Privacy & Security > Camera. Google Chrome must have a checkmark. If it is greyed out, you need to unlock the pane with your admin password first.
- After changing any OS toggle, fully quit Chrome using chrome://quit rather than just closing the window. Background processes keep the old permission state cached until the full process tree exits.
If you changed a macOS privacy toggle and Chrome still reports no camera, open Terminal and run tccutil reset Camera com.google.Chrome. This wipes Chrome's TCC database entry and forces a clean permission prompt on next launch.
Resolve USB Bandwidth and Hub Conflicts
USB 2.0 controllers allocate 480 Mbps of bandwidth across all devices sharing that controller. A 1080p30 webcam using uncompressed YUY2 output needs roughly 148 Mbps on its own. If you have a USB headset, an external hard drive, or a USB hub with multiple devices all sitting on the same controller, the camera negotiates a lower bandwidth allocation and the driver may fail to open the stream entirely.
- Plug the webcam directly into a rear motherboard USB port, not a front-panel header or a hub. Rear ports are typically wired directly to the chipset controller.
- On Windows, open Device Manager, expand Universal Serial Bus Controllers, and look for multiple entries of the same hub. Right-click each USB Root Hub entry, go to Properties, then the Power Management tab, and uncheck Allow the computer to turn off this device to save power. Do this for every root hub listed.
- If you have a USB 3.0 port free, use it. Even though most webcams are USB 2.0 devices, plugging into a USB 3.0 port puts the camera on a separate xHCI controller with dedicated bandwidth headroom.
External webcams like the Logitech C920 and C922 use the UVC (USB Video Class) driver stack and are particularly sensitive to bandwidth contention because they send raw MJPEG or YUY2 streams without hardware compression negotiation at the OS level.
Driver, Firmware, and Extension-Specific Fixes
If the Webcam Test passes but webcam not working proctoru or Proctorio errors persist, the conflict is between the extension and either a virtual camera driver or a conflicting media process.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Camera works in Zoom, fails in Proctorio | Virtual camera driver (OBS, ManyCam) intercepting device handle | Uninstall virtual camera software, reboot, retest |
| Camera detected, black screen in exam | Privacy shutter closed or IR filter stuck on integrated laptop cam | Check physical shutter slider; update OEM firmware via manufacturer utility |
| Webcam not working proctorio exam after Windows update | Inbox UVC driver replaced OEM driver with generic fallback | Roll back driver in Device Manager under Imaging Devices |
| ProctorU guard app says no camera found | Guard app running as different user context than camera permission grant | Right-click guard app, run as the same user account, not as administrator |
| Intermittent disconnects during exam | USB selective suspend cutting power to camera | Disable USB selective suspend in Power Options > Advanced > USB Settings |
Virtual camera drivers are the single most overlooked cause of webcam not working proctorio exam failures. Proctorio's extension explicitly checks the device string reported by the UVC descriptor. OBS Virtual Camera reports itself as a virtual device, and Proctorio flags it as a non-physical camera and refuses to proceed. Uninstalling is not enough if the virtual audio/video driver service is still registered. Open services.msc and confirm no OBS or ManyCam service entries are running.
Also check your mic while you are in here. ProctorU requires both camera and microphone access simultaneously. Use the Mic Test to confirm your microphone is outputting signal before the exam session starts. A failed mic check causes the same "hardware not detected" error screen as a camera failure, and the two are easy to conflate.
Frequently Asked Questions
Why does Proctorio say my webcam is not detected even though it works in other apps?
Proctorio's Chrome extension requests the camera handle through the browser's getUserMedia API. If another application, including a background video conferencing app or a virtual camera driver, already holds an exclusive lock on the device, Chrome cannot open a second stream. Close all other apps that use the camera, then reload the exam page.
Can I use a phone as a webcam for Proctorio or ProctorU?
Proctorio does not support phone-based virtual webcam apps like DroidCam or EpocCam because they register as virtual UVC devices, which Proctorio blocks. ProctorU's secondary device feature is a separate mobile app running on your phone as a room-scan camera, not a replacement for the primary desktop webcam.
My webcam works on the webcam test page but fails when I launch the Proctorio extension. What changed?
The Proctorio extension runs in a locked Chrome profile context that re-evaluates camera permissions independently of your normal browsing session. Go to chrome://extensions, find Proctorio, click Details, and confirm that the extension has Site access set to On all sites. Then revisit chrome://settings/content/camera and make sure no wildcard block rule is overriding the site-specific allow entry.
Does using a USB hub cause webcam problems for online exams?
Yes, frequently. Unpowered USB hubs split the 500mA power budget of a single USB 2.0 port across every connected device. A webcam that needs 400mA during active streaming will brown out on an unpowered hub shared with a keyboard and mouse. Use a powered hub rated at least 2.1A per port, or plug the camera directly into the computer.
ProctorU's system check passes but the live exam session says no camera. Why?
ProctorU's pre-check tool uses a lightweight WebRTC probe that does not fully replicate the permissions the guard application requests during a live session. The guard app opens the camera at a higher resolution and frame rate than the check tool. If your camera's UVC firmware does not correctly report its supported format list, the guard app's format negotiation fails silently. Update your webcam firmware through the manufacturer's utility and rerun the full system check.
Should I update or roll back my webcam driver before an exam?
Roll back only if a recent Windows Update broke a previously working setup. Otherwise, leave the driver alone within 48 hours of an exam. Driver installations require a reboot and occasionally leave the device in a reset state where it does not enumerate correctly until a second reboot. If you need to change drivers, do it at least two days before the exam and verify with the Webcam Test after each reboot.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Webcam Test