Skip to content

CyberHive Connect limitations

Where we're aware of a technical limitation, we'll offer guidance and possible workarounds on this page.

Windows requires OpenGL drivers

Running the Connect client for Windows on a device without OpenGL drivers results in an application crash.

A possible workaround is to set QMLSCENE_DEVICE=softwarecontext in the environment.

Tunnelling Connect over Connect

You can't tunnel Connect inside Connect.

For example, if you have your laptop running Connect, tethered to your phone which is running Connect, connectivity won't be established correctly.

To work around this, simply stop Connect on one of your devices.

Microsoft accounts and email aliases

Users registering with a Microsoft account prior to release 3.2 may have encountered problems if they used an email alias which was not the same as their User Principal Name (UPN).

Since release 3.2, Connect uses the UPN as the username, as long as it is an email address.

In cases where the UPN is not an email address, the primary email address supplied by Microsoft during authentication is used instead.

The Connect user interface is not compatible with Windows Server 2012 R2

The Connect user interface component, "connectui.exe", does not start on Windows Server 2012 R2.

This means that configuration settings cannot be made using the graphical user interface, and that authentication is only possible using authentication tokens.

Please see installation instructions for Windows Server 2012 R2 for full details.