Stuck on the OnVue Video Streaming Check? Here’s the Fix.
The video streaming check is the most common OnVue exam blocker. We break down exactly why your camera isn't being recognized and how to solve it in five minutes.
Why OnVue Exams Block Your Webcam (And How Sapior Understands It)
The moment you see that spinning wheel on the video streaming check, your exam day anxiety spikes. You’re not alone—a quick search on Reddit reveals countless test-takers staring at the same frozen screen, minutes before a certification attempt. The irony? The check is meant to verify the one piece of hardware you definitely have connected.
Pearson VUE’s system test is a browser‑based diagnostic that expects real, unfiltered access to your camera and microphone. When something sits between the browser and the physical device, the check hangs. At Sapior, we build headful browser environments for exactly this kind of delicate, real‑device interaction. The same principles that debug a video feed in our sandboxes apply directly to your exam setup.
The four real reasons your camera gets rejected
**1. Browser permissions aren’t actually granted**
Chrome and Edge prompt for camera and mic access once—and only once. If you missed that pop‑up, or clicked “Block” in a hurry, the permission stays denied across the entire origin. The OnVue system test page cannot override it. The fix: click the lock icon next to the address bar, and ensure both Camera and Microphone are set to “Allow.”[^1]
**2. Another app holds the camera lock**
Video conferencing tools like Zoom, Teams, or even OBS Studio can claim exclusive access to your webcam. Close every application that might use the camera—including browser tabs that previously streamed video. On Windows, you can verify by opening the Camera app: if it can’t display a picture, something else is in control.
**3. Corporate firewall or security software is hijacking media**
Many enterprise environments deploy Deep Packet Inspection or endpoint protection that strips media device enumeration. If you’re on a work machine, the safest path is to switch to a personal, unmanaged device. If that isn’t possible, temporarily disable the security suite—but only for the duration of the check, and only if your IT policy allows it.
**4. Your browser version is too new (or too old)**
Pearson VUE states that the latest two versions of Chrome and Edge are supported. However, rolling releases sometimes introduce changes to the WebRTC stack. If you’re on a bleeding‑edge build, drop back to the stable channel. Conversely, an outdated browser may lack the required MediaDevices API. Always run the check from Chrome 120+ or Edge 120+.[^2]
A diagnostic flow that actually works
Instead of refreshing the page repeatedly, run through this sequence:
1. **Quit every other app.** Task Manager on Windows, Activity Monitor on macOS. End anything that isn’t the browser.
2. **Open a private window.** Go to the OnVue system test directly—this avoids cached permission state.
3. **Test with the official Camera app.** If the feed shows there, the hardware is fine.
4. **Run the system test.** If it still hangs, note the exact step (camera icon never appears, or feed is black).
When the feed is black despite permissions being correct, the issue is almost always a driver conflict. Sony and Logitech cameras, in particular, have been flagged in user forums for needing a firmware update before they work with OnVue’s WebRTC stream.
How Sapior re‑creates these conditions safely
Our live browser environments give developers a clean, isolated Chrome instance with real webcam and microphone pass‑through. That lets teams at proctoring companies and certification vendors reproduce the exact “stuck at video check” scenario without tying up a physical laptop. You can toggle permission blocklists, inject network latency, and even simulate corporate firewall policies—all from one URL. It’s the same layer of control that lets us pinpoint why a user’s camera works in Google Meet but not in OnVue.
If you’re building or maintaining a test‑taker experience, you shouldn’t have to guess why media devices fail. Drop us a line—we’ll show you how a headful browser sandbox makes webcam validation deterministic.
[^1]: Pearson VUE – OnVue system test guide, https://home.pearsonvue.com/onvue/system-test
[^2]: Google Chrome platform status – MediaDevices API, https://developer.chrome.com/docs/extensions/reference/api/mediaDevices