Pass Any Exam & Pay After Pass.
You must disconnect every display except the one you are testing on. Proctoring software reads how many displays your operating system reports, and a second monitor that is switched off but still plugged in is usually still reported. The exam will refuse to launch, and if a display connects partway through a session, that is treated as a serious violation rather than an oversight.
This is the single most common launch failure among IT professionals, for the obvious reason that multi-monitor setups are normal in this line of work.
Powering a monitor off changes nothing from the operating system's perspective. The display is still enumerated, still has a resolution, and still appears in display settings. The check is looking at that list, not at which screens are illuminated.
The same applies to extending or duplicating displays in software, and to setting a second screen to show nothing. The connection is what matters.
Disconnect the cable at one end. That is the fix.
That last one is worth checking because it does not involve any physical hardware. Quit remote access tools entirely rather than just closing their windows.
The reliable sequence, if you hit trouble, is to unplug everything first and then restart, rather than unplugging while the machine is running. Some display configurations persist until a restart clears them, and a restart also takes care of the background software that can create virtual displays.
Do this well before your appointment rather than during check-in.
If the software detects a new display appearing during a session, that reads as a deliberate act. Unlike a failure at launch, which is simply a blocked start, this typically results in the session being terminated and recorded as a violation.
This is worth knowing because it can happen accidentally. A dock waking up, a cable making contact again, or a tablet reconnecting over a wireless display feature can all trigger it. The protection is to disconnect physically and switch off the relevant features, not merely to avoid touching anything.
A few less obvious causes:
Run the system check at least a day ahead specifically so that you have time to work through these.
If you normally work on several screens, decide in advance which one you will test on and how you will disconnect the rest. Practical points:
That final point is a small refinement that avoids an entirely separate problem.
System requirements and display-detection behaviour change with each software release. Confirm current requirements against your proctoring platform's official documentation and run the system check before test day.




Copyright © 2026 - Tous droits réservés.