Pearson VUE OnVUE: System Test, Check-In and Session Errors Fixed

OnVUE is Pearson VUE's online-proctored delivery platform, used for CompTIA, Microsoft, AWS, Cisco, NCLEX-adjacent programs, state licensure and hundreds of other credentials. Check-in opens 30 minutes before your appointment and closes 15 minutes after the scheduled start. Miss that window and the exam is forfeited, usually with the full fee. Almost every OnVUE horror story is a check-in story.

Run the system test — from the right place

Pearson provides a system test that must be run on the same computer, in the same room, on the same network you will use. It measures camera, microphone, speakers and bandwidth, and it also uploads a test photo. Run it a week out and again the day before.

If the test fails: switch off VPN and corporate networks entirely (many enterprise networks block OnVUE and IT cannot always fix it in time), use a personal laptop rather than a work-issued one, and prefer wired Ethernet.

Check-in photo and ID uploads keep failing

Check-in requires four photos: your face, your ID front, your ID back, and four photos of the testing room, usually taken with your phone through a texted link.

• Use a physical government-issued ID whose name exactly matches your registration name. A mismatch — a maiden name, a missing middle initial — is a common rejection.
• Kill glare on the ID; angle the card away from lights.
• Take the room photos in good light showing the desk, the surface underneath, and the walls.
• If the phone link never arrives, check spam, confirm the mobile number on your Pearson profile, and use the on-screen alternative upload.

"Waiting for a greeter" for a long time

After uploading, you wait for a proctor. Delays of fifteen minutes or more happen at peak times. Do not close the application; closing it cancels the session. Stay in the chair — leaving the frame while waiting can void the session before it starts.

The secure browser will not launch or closes immediately

OnVUE downloads a small application at check-in. It requires the ability to run downloaded executables and to close blocked processes. Before starting, quit every other application, especially conferencing and remote-access tools, and disable antivirus real-time web protection for the session. On macOS grant Screen Recording, Camera and Microphone to the OnVUE app. Reboot before check-in so no stale process is holding the camera.

Rules that end sessions early

Pearson's online rules are stricter than most: no talking or reading aloud, no leaving your seat for any reason (there are no breaks on most exams), no phones, no watches, no headphones, no second monitor connected — unplug it, no notes or scratch paper unless the program specifically allows an approved whiteboard, no food, and no one else in the room at any point.

If you are disconnected mid-exam

Reconnect immediately using the same session; OnVUE holds it briefly. If you cannot, phone Pearson VUE support right away and get a case number. Reinstatement is handled between Pearson and the credential owner and depends on a documented, promptly reported incident.

The universal pre-exam checklist

Roughly nine out of ten proctoring incidents trace back to the same five conditions. Run this list the day before, not fifteen minutes before.

• Use the same machine, browser and network you will test on. A system check passed on a laptop at home does not certify the desktop at work.
• Reboot fully. A cold restart releases the camera handle that Zoom, Teams, Discord, OBS, Snap Camera or Windows Camera quietly kept open.
• Update the browser and the secure application. Version mismatch is the single most common launch failure.
• Test upload, not download. Live proctoring streams video *out*. You need a stable 1.5–3 Mbps upload; a 500 Mbps download does not help if upload collapses.
• Disable VPNs, proxies, corporate firewalls, parental filters and antivirus web shields. Managed work or school devices block the ports proctoring platforms use, and administrators cannot always unblock them in time.

Fast diagnostic sequence when something breaks

1. Note the exact error code or message and screenshot it — support resolves coded errors in minutes and vague descriptions in hours.

2. Check whether the failure is *device*, *network* or *account*. Device: the check fails offline too. Network: it fails only on this connection. Account: it fails on every device.

3. Switch one variable at a time: hotspot instead of Wi-Fi, Chrome instead of Edge, second machine, guest OS profile.

4. Re-run the vendor system check and save the report ID.

5. Contact live support *before* the appointment window closes — most vendors will not reinstate a session once you have exceeded the launch grace period.

What to do if the session is lost anyway

If the exam terminates, do three things immediately, in this order: screenshot the error, open the vendor's live chat and get an incident or case number, and email your institution or licensing board the same day with that number attached. Reinstatement decisions almost always hinge on documented, timestamped evidence created during or immediately after the incident — not on a request filed a week later.

Then use the retake window deliberately. Rehearse the launch flow on the exact machine, run one full-length timed practice test under the same conditions, and treat the technical setup as part of your study plan rather than an afterthought.