Prometric ProProctor: Launch, Check-In and Readiness Fixes

ProProctor is Prometric's remote delivery application, used for nursing, healthcare, accounting and government credentialing exams that also run in Prometric test centers. It is a downloadable application with a live greeter and, unlike some competitors, a fairly strict environment policy — Prometric's remote rules mirror its test-center rules closely.

Run the readiness check first

Prometric publishes a system readiness check that verifies operating system, browser, camera, microphone and bandwidth. Run it on the exact device and network.

Requirements that trip candidates up most: a personal (not employer-issued) computer, administrator rights, no dual monitors, sustained bandwidth in both directions, and an operating system inside the supported range. Tablets and phones are not supported.

The application will not install or open

Download ProProctor only from the launch link in your confirmation email, and install it before exam day so any permission prompts happen early. On Windows, approve the SmartScreen prompt and allow the app through the firewall. On macOS, allow it under Privacy & Security and grant Screen Recording, Camera and Microphone permissions, then relaunch. Corporate laptops with device-management policies frequently block installation entirely — plan for a personal machine.

Check-in: what the proctor will require

Check-in typically opens 30 minutes before the appointment. Expect: an ID scan, a face photo, and a thorough 360-degree environment scan including under the desk, the ceiling area above the workspace, the walls, and sometimes your sleeves, wrists and ears.

Prepare the room: a hard-surfaced desk, no papers, no second screen (unplug and turn it away), no whiteboards on the wall, no bookshelf of notes immediately behind you, no drinks unless permitted, door closed, and nobody else entering for any reason.

ID: unexpired, government-issued, photo-bearing, and the name must match your registration exactly. Prometric enforces this strictly; a mismatch means a forfeited appointment.

Bandwidth drops and freezes

ProProctor streams continuously. Use Ethernet where possible; if using Wi-Fi, sit close to the router on the 5 GHz band and ask the household to stay off high-bandwidth services. Pause cloud backup and system updates for the day. If you freeze, wait — the application often recovers. If it closes, relaunch immediately using the same link and contact support through the on-screen chat; sessions can frequently be resumed with time preserved.

Breaks and rule enforcement

Unscheduled breaks are permitted on some exams and forbidden on others; the candidate handbook for your specific credential is the authority. Where breaks exist, the clock usually keeps running and a fresh security check is required on return. Leaving the camera view without authorization is treated as a serious violation and can void the attempt.

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.