ProctorU Troubleshooting: Connection, Guardian Browser and Proctor Chat Fixes

ProctorU (now delivered under Meazure Learning) is a *live* proctoring service. A human greets you, verifies identity, watches the room scan, and takes temporary remote control to inspect your machine before unlocking the exam. That human element is why ProctorU sessions fail differently from automated platforms: the technology usually works, but the handoff between candidate, software and proctor is where things break.

Guardian Browser will not install or launch

Guardian Browser is a standalone application, not an extension. Corporate and campus-managed laptops routinely block its installation.

Fix path: install Guardian while signed in as a user with administrator rights; on Windows allow it through Defender/SmartScreen when prompted; on macOS approve it under Privacy & Security if it is blocked as an unidentified developer, and grant Screen Recording, Camera and Microphone permissions before the appointment. Test-launch Guardian at least a day early — the first launch triggers the permission prompts, and doing that during your appointment burns your window.

Endless "connecting to a proctor" or long queues

Live proctoring is capacity-bound. If you arrive at a peak time — Sunday evenings, end of term, the final day of a testing window — wait times climb. Log in ten to fifteen minutes early, keep the tab in focus, and do not refresh: refreshing sends you back into the queue. Rescheduling to an off-peak morning slot is the single most effective fix.

Screen sharing or remote control fails

ProctorU proctors use a remote-support tool to inspect and unlock your machine. Failures here are permission failures. On macOS, Screen Recording and Accessibility permissions must both be granted; on Windows, the applet must be allowed through the firewall. Antivirus suites with "remote access protection" — notably some ESET, Kaspersky and Bitdefender configurations — silently block it. Pause web shields for the session.

ID verification keeps rejecting you

The ID scan compares a live photo with your government document.

• Use a physical, unexpired, government-issued photo ID; photos of an ID on a phone screen are rejected.
• Hold the card still, six to eight inches from the lens, and let the camera focus.
• Kill glare — the biggest cause of rejection is a lamp or window reflecting off the laminate. Tilt the card slightly and turn off any light directly behind the camera.
• Remove hats, headphones and glasses if asked; keep hair off the face.

Audio: the proctor cannot hear you

Select the correct input device in Guardian's system check, not just in the operating system. Bluetooth headsets are a frequent culprit because they switch to a low-quality profile when the microphone activates; a wired headset or the built-in microphone is more reliable. Confirm that the microphone is not muted at the hardware level (many external webcams and laptops have a physical mute key).

Bandwidth and disconnects

ProctorU streams two-way video. Target at least 1.5 Mbps upload, ideally wired Ethernet. Ask everyone in the household to stay off 4K streaming and cloud backup for the duration. If you must use a hotspot, place the phone next to the laptop, disable other devices from tethering, and confirm your plan does not throttle after a data threshold.

If you disconnect mid-exam, reconnect immediately using the same Guardian session — do not start a new appointment. Your proctor holds the session open for a short grace period, and reconnecting inside that window usually preserves your progress and your remaining time.

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.