The technical failures that hit online proctored exams — webcam faults, crashes, internet dropouts — with in-the-moment responses and prevention.
Every technical failure in an online proctored exam falls into one of five families: the secure browser will not launch, the webcam or microphone fails, the internet drops, the exam software freezes or crashes, or the check-in itself rejects you. Knowing which family you are in — and the correct first move for each — is the difference between a five-minute interruption and a forfeited appointment.
This guide is the triage manual: what each problem looks like, what to do in the moment, and how to stop it happening at all. One boundary up front: if your session drops entirely and does not come back, the aftermath — resumption, incident tickets, rebooking — is its own process, covered in what happens if your online exam disconnects. Here we focus on keeping the session alive.
Before the specific fixes: whatever goes wrong, your first and safest channel is the proctor. Platforms such as Pearson VUE's OnVUE monitor you throughout the session via human proctors and assistive tools, and they provide a chat function precisely for session problems. Reporting an issue creates a record and never counts against you; silently improvising — leaving your seat, grabbing your phone, restarting things unannounced — can look like a rule violation even when your intentions are innocent. The behaviours that get sessions revoked are catalogued in online proctored exam rules you should know; do not let a glitch push you into one of them.
When it strikes: almost always before the exam starts, which is why it is the most fixable failure of all.
What it looks like: the download blocked, the application crashing on open, an error about another programme, or a launch that hangs forever.
In the moment: restart the computer and try once more with nothing else running — most launch failures are another process holding the screen, camera or network. If it still refuses, contact the delivery platform's candidate support before your appointment window closes, so the failed attempt is on record.
Prevention: this failure is nearly always caught by the official system test that platforms such as Pearson VUE require in advance — run on the same machine, network and room you will use. Corporate laptops with VPNs and endpoint security are the classic culprits. The full pre-exam shakedown lives in how to prepare your computer for an online exam.
What it looks like: a black square where your video should be, a "camera not found" error at check-in, or the proctor telling you they have lost your feed mid-exam.
In the moment: first check the physical layer — the privacy shutter many laptops and external cameras now have, then the USB plug. If the camera worked at check-in and died later, tell the proctor through chat and follow their instructions rather than rebooting on your own initiative; the feed is their evidence that the session is valid, so they lead the recovery.
Prevention: confirm camera and microphone in an ordinary video call the day before, and close every app that can claim the camera (video-call software left running in the background is the usual thief). Note the bar is low but real: CompTIA's requirements, for example, specify a webcam of at least 640×480 at 10 frames per second — most built-in cameras qualify, but a clean lens matters more than resolution, since your ID must be readable through it.
What it looks like: questions loading slowly, the proctor reporting choppy video, or — the worst case — the session disconnecting outright.
In the moment: if the exam is still running but sluggish, do not refresh or restart anything; message the proctor and let them decide. If the session drops, stay calm and stay at your desk: reconnect and attempt to re-enter through the same application or link you started from, and expect a fresh identity check if you get back in. If you cannot re-enter, the situation graduates from "problem during the exam" to "dropped session," and the recovery-and-rebooking process in the disconnection guide takes over. Be aware that resumption policies are programme-specific — do not assume every provider can restore a broken session.
Prevention: this is the failure most worth over-preparing for. CompTIA's stated minimum is 1 Mbps up and down, but stability beats speed: a wired ethernet connection, a household warned off streaming, paused cloud backups, and a router restarted the day before remove almost all of the risk. Upload matters as much as download — your webcam stream runs the entire session.
What it looks like: a timer that stops moving, a question that will not submit, an unresponsive screen, or the application closing outright.
In the moment: distinguish freeze from crash. For a freeze, wait thirty seconds before touching anything — brief stalls often resolve — then use the proctor chat if it persists. For a crash, reopen the testing application and attempt to rejoin, exactly as with a dropped connection. In both cases, resist the panic move of force-restarting the whole computer unless support tells you to; an orderly re-entry preserves your session where one exists.
Prevention: crashes cluster on machines running background software that fights the secure browser — screen recorders, clipboard tools, virtual machines, pending OS updates that fire mid-session. A fresh restart an hour before check-in, updates installed days earlier, and everything else quit is the whole defence.
What it looks like: ID photos repeatedly refused, a room scan the proctor will not accept, or an onboarding step that loops.
In the moment: treat proctor feedback as instructions, not judgement — retake the photo in better light, remove the flagged item, re-scan the room. Most rejections resolve on the second attempt. ID problems are the stubborn exception: policies such as CompTIA's require the ID name to exactly match the registration name, with photocopies not accepted, and no amount of retaking photos fixes a mismatch. That is a pre-exam admin task — see what identification you need for a certification exam.
Prevention: good lighting, a genuinely clear desk, and a name-match check the week you book. The full walkthrough of what check-in involves is in what to expect during an online proctored exam.
Lay the five families side by side and the same preventions keep reappearing:
Only check-in rejection sits outside the pattern, and it is solved by paperwork, not technology.
There is also a fourth, quieter habit: rehearsal under realistic conditions. Sitting a timed practice-test simulation on your exam machine a few days out both benchmarks your knowledge and gives your setup a dress rehearsal — if anything is going to freeze, better it freezes then.
No — a genuine technical failure is a support case, not a scored attempt. What matters is that it is documented: report problems through the proctor chat or the platform's support channel as they happen, so there is a record if the session cannot be completed.
Not as a first move. Wait briefly, then use the proctor chat; if the application has crashed, try rejoining through the same app first. Restart the machine only when re-entry fails or support tells you to — an orderly re-entry gives you the best chance of resuming where you stopped, where the programme supports resumption at all.
Yes — this is one reason policies such as CompTIA's have your phone nearby but outside the workspace. If the computer is unusable, the delivery platform's candidate support number is the right call, and the phone is your route to it.
Report it exactly the same way and note the time it occurred. Platform-side outages affect many candidates at once and providers handle rebooking through their support process — the aftermath follows the same path described in our guide to dropped sessions.
Candidates who come through technical trouble unscathed share one trait: they respond in order — observe, report, follow instructions — instead of improvising under adrenaline. The five failure families above cover essentially everything that goes wrong in a remote exam, and every one of them has a first move you now know. Prepare the machine, protect the connection, and keep the proctor in the loop, and technology becomes what it should be on exam day: background noise.
Exam facts in this guide were checked against official certification-provider pages on . Fees, exam codes and policies change — confirm on the provider’s own site before you book.
Put it into practice
Reading about an exam only takes you so far. Work through practice questions for your certification and find the gaps before exam day does.
·7 min read
Timing, score benchmarks and review technique for CompTIA practice tests — how to turn A+, Network+ and Security+ practice scores into a genuine pass signal.
Continue reading·8 min read
How to use CISA practice tests properly — when to take them, how to benchmark scores across the five domains, and how to turn wrong answers into study priorities.
Continue reading·8 min read
A practical buyer's checklist for choosing a reliable certification practice test: objective alignment, explanations, simulation features and red flags.
Continue reading
