Selected Topic
Important: If you are unable to access the sign-in link or if the page navigation seems broken, force refresh your browser's cache. From Windows and Linux browsers, use Ctrl+F5. From Mac browsers, use +Shift+R.

PCoIP Graphics Agent 2.9.0 for Windows Release Notes (15134-3151)

Release Overview

PCoIP Graphics Agent 2.9.0 for Windows consolidates a number of new features and updates.

These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.

What's New in This Release

PCoIP Graphics Agent 2.9.0 for Windows includes the following new features and updates:

Preview of AMD FirePro™ GPU optimization

Added a preview of AMD FirePro GPU optimization for AMD FirePro Driver Release 16.60. Be aware that the preview may have stability, compatibility, or other issues.

Simplified license management including ability to review the remaining subscription time

Added the ability to register a license within the PCoIP Control Panel.

You can now query the remaining time in your subscription license through a command line tool.

Improved PCoIP client connection time

The latest release supports a faster establishment of PCoIP connections.

Important Notes and Requirements

  • PCoIP Graphics Agent 2.9.0 for Windows requires a software activation code. If you are a new user, request an activation code for a full evaluation.

  • When reporting issues to Teradici, be sure to run the SupportBundler.exe application and include the output it generates.

Release Downloads

Related Documents and Software

Release History

2.9.0 July 2017 General availability release


For compatibility details, refer to Windows system requirements in the administrators' guide.

Known Issues

Remotely installing PCoIP agent may fail to install Windows dependencies

When running the agent installer using remote commands (for example, remote WMI), the agent installer may fail to install the required components used by the Visual Studio 2015 runtime libraries.The installation failure would leave the host in a bad state. To clean the system, go to the Control Panel to manually uninstall VS 2015 redistributable. (63444)

Workaround: Install Microsoft Windows update KB2999226 on the host machine before running the agent installer.

Initial PCoIP connection on Azure may result in blank display

With PCoIP Graphics Agent on Azure, display may not be properly initialized on the first connection. You may get a blank display. (62483)

Workaround: Disconnect and reconnect, or resize your PCoIP client window.

User may be required to log on twice

Rarely, a user may be presented with the lock screen when connecting via PCoIP. (61632)

Workaround: Authenticate a second time to gain access to the desktop.

GRID licensing fails after disabling then enabling GRID capture.

GRID licensing fails after disabling NVFBEnable -disable then enabling NVFBEnable -enabling GRID capture, resulting in limitations in the number of monitors and resolutions available. (61247)

Workaround: Teradici has included, as part of the PCoIP Graphics Agent install, a reset script to reset the graphics driver to a good state:

C:\Program Files (x86)\Teradici\PCoIP Agent\GRID\reset_grid.bat

You'll need administrator permissions to run the script. Before running the script, close all other applications, especially those that utilize the GPU. Teradici also recommends you disconnect and reconnect once the script has completed.

Virtual USB Hub installation failure can prevent software upgrade

An installation error 'Failed to install Virtual USB Hub: -1' can prevent software upgrade. (61172)


  1. Open Windows Device Manager
  2. Uninstall all USB Stub devices, making sure to check the box 'Delete the driver software for this device'
  3. Reboot the system
  4. Reinstall the PCoIP agent

GRID licensing not enabled after re-allocating an Azure VM with GRID 4.2 (369.95) driver

After starting (re-allocating) a previously stopped (de-allocated) VM in Azure, GRID licensing is not always enabled following VM boot up. This results in PCoIP sessions being limited to a single screen with a maximum resolution of 2560x1600 pixels. (61088)

Workaround: Restart Windows.

Screens may not wake up automatically when system has been sleeping

Occasionally, when logging into a PCoIP Graphics Agent instance, you may be presented with black screens at a lower than native resolution (this can be inferred by a larger-than-usual cursor). This only happens when the machine has been left unattended for an extended period. (59890)

Workaround: Click the mouse or press a key on the keyboard to wake up displays. This may take several seconds. Failing this, reconnect to solve the problem.

Cursor size larger than 64x64 pixels does not display correctly

Display of cursors larger than 64x64 pixels can become truncated and can terminate the PCoIP session. (57721)

PCoIP Graphics Agent upgrade after disconnecting may not work on mapped drives

If you manually download a new version of the PCoIP Graphics Agent and run it from a mapped drive from within a PCoIP session, the update will show an error and plan to continue the update offline while the user is disconnected. If the software installer is located on a mapped drive that the local system account does not have access to, the update will fail. (55408)

Workaround: Copy the installer to a local drive first.

PCoIP Graphics Agent does not support all cursor shapes

The default arrow cursor is shown when an unsupported cursor shape is set by an application. (53310)

Multiple display issue occurs when NVIDIA GRID is not properly licensed

If NVIDIA GRID is not properly licensed, connecting with multiple displays to a remote machine running PCoIP Graphics Agent may result in only one display being optimized with GRID performance. The other displays will work but will not be optimized with GRID, resulting in lower frames per second. (52157)

Workaround: Ensure NVIDIA GRID GPU is properly licensed.

Duplicated screens in-session

If an application sets the displays to 'duplicate', the user will be unable to restore the configuration to extend across multiple displays due to the controls being disabled. (51912)

Workaround: Open the Projector Menu by pressing Windows key + P, then select Extend.

NVIDIA GPUs do not support Windows Sleep and Hibernate system power states (S3/S4 respectively)

A small number of occurrences have been reported where Windows will crash (resulting in BSOD) when resuming from Windows Hibernate, when installed on a virtual machine equipped with NVIDIA GPUs. For details on sleep and hibernate behaviors supported by NVIDIA, contact and visit (51788)

Workaround: Avoid sleeping and hibernating PCoIP Graphics Agent that is configured to utilize NVIDIA GPUs.

Cursor pointer shadow is not supported with Windows 10

'Enable pointer shadow' is not supported in a PCoIP session to Windows 10 PCoIP Graphics Agent. (45095)

System volume set to maximum after agent upgrade

When upgrading to the latest PCoIP agent, audio volume is automatically set to maximum. (42226)

Workaround: Manually set the audio to the desired volume after upgrading. Once set manually, the audio volume is maintained. The change in audio volume only happens at upgrade.

GRID capture fails with K520 card using VBIOS 80.04.ED.00.07

NVIDIA K520 cards with Video BIOS (VBIOS) 80.04.ED.00.07 are known to cause a GRID capture failure resulting in the PCoIP Graphics Agent falling back to BitBLT capture. The VBIOS version currently installed on the NVIDIA card can be found via the NVIDIA Control Panel under System Information. (42099)

Workaround: Update the VBIOS on the K520 card to the latest version. VBIOS 80.04.D4.00.03 is known to work.

PCoIP agent fails to connect when host has multiple NICs

When a host computer has more than one network adapter, the system must be configured to inform which adapter to use for inbound PCoIP connections. You can do so by populating the PCoIPConnectionAddress registry value with your desired network interface.

Some software applications such as Npcap can create a virtual network adapter that will present additional Ethernet adapters. These configurations also require populating the PCoIPConnectionAddress registry value with your desired network interface. (40825)

Workaround: In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Teradici\PCoIPAgent, set the PCoIPConnectionAddress registry value:


Where a.b.c.d is your desired network interface).The type of the reg key is a string value: REG_SZ.

Agent installation may take a long time

Teradici installs Microsoft Visual Studio 2013 C/C++ runtimes as part of the agent installation. Runtime installers create a system restore point which, on systems such as Windows 8, can take over 15 minutes. If the installer appears to be stalled when installing the C/C++ runtimes, it may simply be the runtime installers creating a system restore point. (22702)

Mouse pointer shadow is missing

The mouse pointer shadow, which gives the mouse pointer a 3D appearance, is not available during PCoIP sessions. (1870)

Resolved Issues

Memory leak in the PCoIP server now fixed

Keeping a PCoIP session active for prolonged periods no longer consumes excessive memory. (62898)

CPU usage no longer increases with video content

Previously, PCoIP server process consumed an increased amount of CPU when the screen content contained video or other frequently changing content. This issue has been fixed. (62507)

Invisible cursor now displayed

Previously, some cursor shapes were rendered invisible. This is now fixed. (62312)

Using '.' as the domain for user authentication no longer fails to logon

Previously, user authentication with '.' as the Windows domain would fail to sign on the user. This issue is now fixed. (59734)

High-resolution monitors are no longer treated as analog displays

Previously, the extended EDID information passed by the displays of high-resolution monitors such as 4K UHD was handled incorrectly, resulting in monitor display being set as analog. This limited available resolutions, causing issues such as black bars small windows, and impacted PCoIP performance. This issue is now fixed. (59517)

Monitor topology changes on Azure NV instances now behave as expected

Use PCoIP Graphics Agent with NVIDIA GRID 4.2 (369.95) driver to ensure promptness of changing monitor topologies on Azure NV instances. (59445)

GPUs are now GRID capture ready following re-allocation of Azure NV instances

Use PCoIP Graphics Agent 2.8 with NVIDIA GRID 4.2 (369.95) driver to ensure newly allocated GPUs are correctly configured for GRID capture. (59045)

Switching from windowed mode to full-screen mode no longer crashes the VM on Azure NV-Series

This issue was specific to Microsoft Azure NV-series VM, running Windows Server 2016 with latest NVIDIA drivers installed (369.71). Previously, while connected from a PCoIP Software Client in windowed mode, changing the view to 'Show full-screen' mode could cause an error in the NVIDIA driver and cause a Windows crash, resulting in a BSOD. This issue is now fixed. (58346)

Logoff no longer required before upgrading to latest PCoIP Graphics Agent on Windows 10 and Server 2016

Previously, on Windows 10 or Server 2016 systems that have applied the latest OS update (Microsoft KB3200970), users would need to log off before upgrading to the latest Cloud Access Software version (agent). Failure to log off these users would cause installation process to hang and prevent a clean reboot of the system. User would have to log off and re-log in via RDP to perform the upgrade. This issue is now fixed. (57680)

PCoIP sessions on NVIDIA GPU now behave as expected even if other video adapters are enabled

Previously, with new installations of the PCoIP Graphics Agent, PCoIP sessions might fail to connect with GRID capture if other video adapters were enabled. You would have to disable any non-GRID video adapters (via RDP) and reconnect the PCoIP session. Once the PCoIP session was established with GRID, you could re-enable non-GRID video adapters. This issue is now fixed. (57525)

GPUs no longer become disabled when installing the PCoIP Graphics Agent

Previously, installing the PCoIP Graphics Agent on systems with more than one GPU might result in one or more GPUs being disabled. The PCoIP Graphics Agent enabled GRID capture during installation but this might take longer than expected on systems with more than one GPU, leaving some GPUs in a disabled state. This issue is now fixed. (56499)

Unicode license server names are now supported

Previously, license server names with non-ASCII characters could not be reached to get a license. This issue is now resolved. (37625)

Was this answer helpful?YesNo

Knowledge Base

Topic Information
  • Topic #: 15134-3151
  • Date Created: 05/08/2017
  • Last Modified Since: 08/15/2017
  • Viewed: 376