VPN, cortafuegos y antivirus: software que bloquea los exámenes supervisados en línea.

Proctoring software fails to install or launch most often because something else on the machine is blocking it: a VPN, endpoint security, antivirus, a firewall, or a tool that holds the camera or the screen. On a personal computer these are all solvable in a few minutes. On a managed work laptop several of them are not solvable by you at all, which is the single strongest argument for testing on a personal device.

Sort this out days ahead, not at your appointment.

VPNs

Disconnect any VPN before launching, and make sure it will not reconnect on its own. Proctoring sessions route traffic to specific services, and a VPN can break that routing, degrade the connection badly, or make your apparent location inconsistent with your registration.

Corporate VPNs are the harder case because they often reconnect automatically on a schedule or when a network change is detected. Quitting the client is not always enough; on a managed device it may restart itself. If you cannot fully disable it, that machine is not a safe choice.

Antivirus and endpoint security

Consumer antivirus most often interferes at installation, quarantining the downloaded application or blocking it from running. Temporarily disabling real-time protection for the installation usually resolves it. Re-enable it afterwards.

Corporate endpoint protection is a different problem. Tools of this class are designed to prevent exactly the behaviour proctoring software exhibits: taking over the screen, blocking input, and monitoring processes. They frequently cannot be disabled by the logged-in user, and attempting to disable them can generate a security alert to your IT team.

Firewalls

A local firewall occasionally blocks the connections the session needs, and allowing the application through resolves it. A corporate or network firewall is more likely to be the real obstacle, since it may block the ports and destinations the proctoring service uses, and you usually cannot change it.

If you are testing from home on your own network, firewalls are rarely the problem. If you are testing on a corporate network, they often are, and the fix is to test from a home network instead.

Software that holds the camera, screen, or input

These prevent launch even on a fully personal machine:

• Video conferencing tools such as Teams, Zoom, Meet, and Skype, including when only running in the background.
• Remote desktop and remote access tools such as TeamViewer, AnyDesk, Chrome Remote Desktop, and built-in remote desktop services.
• Screen recording and streaming software.
• Virtual machine software, which usually blocks the exam regardless of whether a VM is running.
• Cloud sync clients such as OneDrive, Dropbox, Google Drive, and iCloud, which can saturate your upload bandwidth at the worst moment.
• Chat applications such as Slack and Discord, particularly with overlays enabled.
• Gaming overlays from Discord, Steam, and graphics card utilities.
• Clipboard managers, macro tools, and peripheral software for keyboards and mice.

The pattern: anything that watches your screen, injects an overlay, captures input, or holds the camera is a candidate.

Closing them properly

Quitting the window is often not enough, because many of these run in the background.

On Windows, check the system tray including the hidden icons area, then use Task Manager to confirm the process has actually ended. Disable the relevant startup entries so they do not return after a restart.

On macOS, check the menu bar, quit applications explicitly rather than closing their windows, and check login items so they do not relaunch.

Then restart the computer and check again. A restart with startup items disabled is far more reliable than closing things one by one.

The clean-profile approach on Windows

The most effective single trick is to create a second Windows user account with no startup applications, and take the exam from that account. You get a genuinely clean environment without uninstalling anything from your normal profile, and it takes a few minutes to set up.

Do it the day before and log into it once to confirm the camera and microphone work there, since permissions are per-account.

Why work laptops fail

A company-issued machine can fail for several reasons at once:

• No administrator rights to install the application.
• Endpoint protection blocking installation or execution.
• A VPN that reconnects automatically.
• Device management policies restricting camera or microphone access.
• Application allowlisting that prevents unapproved software running at all.
• A corporate firewall blocking required destinations.

If a work machine is genuinely your only option, start a week ahead and involve IT explicitly, explaining that you need to install proctoring software for a certification exam. Some IT teams will grant a temporary exception. Many will not, and finding that out early is the point.

Be aware too that installing unapproved software on a corporate device may breach your own organisation's acceptable use policy, which is a reason to ask rather than to try quietly.

A sequence that works

• A week ahead: decide which machine you will use, and if it is a work device, ask IT now.
• Several days ahead: install and run the system check on that machine, in the room and on the network you will use.
• The night before: disable startup items, disconnect the VPN, close everything, restart, and re-run the check.
• An hour before: restart again, confirm no VPN, confirm nothing has relaunched, and download the proctoring application fresh.

When to stop troubleshooting

If the application still will not install or launch the day before, stop and change something structural rather than continuing to fix. Borrow a personal computer, or reschedule to a test centre.

Rescheduling costs far less than a forfeited exam fee, and a test centre removes this entire category of problem, since the hardware is theirs.

Software compatibility and system requirements change with each proctoring application release. Confirm current requirements against your platform's official documentation and run the system check well before test day.