SecureClient for Windows troubleshooting

SecureClient is a delivery app with offline test support and built-in protections against internet and device failure. For general information on SecureClient and the Surpass test driver, see the Test Delivery section of the Surpass Help Site.

This article will provide information on some of the common troubleshooting issues that may be encountered using SecureClient for Windows and provides advice on how they can be fixed.

If you have tried the steps outlined in this article and are still having issues with SecureClient, or you are encountering any issues with SecureClient not listed here, contact support@surpass.com.

Table of Contents
TIP: It is recommended that SecureClient is always installed with administrative permissions on Windows devices. For information on installing SecureClient, read Installing SecureClient.

Antivirus software

If you are experiencing general test performance issues, particularly concerning files being opened during a test (for example, opening a PDF file), this may be due to interference from antivirus software installed on your device.

The following instructions detail how you can whitelist SecureClient to be excluded from antivirus protection.

CefSharp.Core.dll error

If SecureClient does not open or closes after checking for updates then you may be encountering a ‘CefSharp.Core.dll’ error. This is caused by the Microsoft Visual C++ x86 redistributable package being absent from SecureClient’s config files.

To identify if it is a CefSharp.Core.dll error you are encountering, follow these steps to check the log file:

  1. Navigate to (C:\Users\Public\Surpass\SecureClient\configfiles).
  2. Open the Log XML file.
  3. Check for the following line in the document: MainError : Could not load file or assembly ‘CefSharp.Core.Runtime.dll’ or one of its dependencies. The specified module could not be found.

Error 821: SecureClient core

When an Error 821 message is shown it means there was an error trying to decrypt an item for the current question.

This is caused by an on-access virus scan preventing SecureClient from reading or writing files.

Error 827: Error validating keycode

When a candidate enters a keycode for an online test, they may encounter an Error: 827 message:

  • Error: 827 Secure Client Core – OFFLINE – There was an error validating the keycode

This means SecureClient is being forced into an offline state where it cannot communicate with the database and validate the keycode.

Error 8008: Source material does not open in SecureClient

If your device’s settings are improperly configured, you may see an Error: 8008 message when attempting to open source material in SecureClient.

This error is caused by an incompatibility with the Trusted Documents setting in Microsoft Office.

Error 8051: Unable to Launch SecureClient (Windows Text Suggestions)

SecureClient cannot be launched if Windows text suggestions are enabled.

Navigate to Settings > Time & language > Typing and ensure the Show text suggestions when typing on the physical keyboard,  Multilingual text suggestions, Autocorrect misspelt words, and Highlight misspelt words settings are disabled.

NOTE: In Windows 10, these settings can be found in Settings > Devices > Typing.

Error 8052: Unable to Launch SecureClient (Open Applications)

Some applications, such as Grammarly, prevent SecureClient from opening.

Close the applications listed in the error dialog before trying to relaunch SecureClient. You may need to access Windows Task Manager via Ctrl + Alt + Del to ensure it is not running in the background.

In Progress/User disconnected tests

After a candidate has taken a test, tests appear as In Progress/User disconnected in the Invigilate screen despite the tests actually having been completed.

This is caused by a lost or slow internet connection when the test was submitted by the candidate.

Installing SecureClient on a locked-down laptop

When trying to download SecureClient, issues may be encountered where test centres have restricted permissions on laptops.

SecureClient Update Loop

When SecureClient is launched it can get stuck in an update loop.

Unhandled exception

An unhandled exception error may occur after SecureClient is launched if there were any issues during installation.

Close SecureClient, uninstall it, and reinstall it from an account with administrator permissions.

Updates are invalid

When SecureClient is launched, it initially checks the Surpass server for any updates made to the software. If the error message Updates are invalid appears, this means SecureClient has tried to check for updates but has been prevented from doing so.

The most common cause of this block is a proxy server. Alternatively, updates may have been found, but there are not enough local user permissions on the PC to write to this directory.

NOTE: This form is to provide feedback to help improve the Surpass Help documentation only. If you need live support, contact support@surpass.com.