PCoIP Software Client 3.4 for Windows Release Notes¶

Release Overview¶

PCoIP Software Clients 3.4 introduce new fixes and updates and enable customers to establish a PCoIP session with:

Teradici Cloud Access Software
PCoIP Remote Workstation Card

Teradici has bundled the Windows and Mac clients separately for this release.

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

What's New in This Release¶

Enhanced audio and video synchronization¶

Improved full-screen video playback, including tighter sync between audio and video channels and smoother playback with the software clients.

Simplified bundling of client log files¶

Client log files can now be bundled with the PCoIP Support Bundler Tool and sent to Teradici support for troubleshooting purposes.

Release Downloads¶

PCoIP Software CLient 3.4 for Windows (3.4)

Release History¶

Version/Build	Date	Description
3.4	January 2018	Updated Release

Supported Clients¶

PCoIP Software Client for Windows: PCoIP Software Client for Windows is compatible with the following Windows operating systems: **Note:**PCoIP Software Client for Windows does not operate with Windows Embedded Standard 7 or Windows Embedded Standard 8 systems.

Windows 10
Windows 7 (64-bit)
Windows 7 (32-bit

Supported Hosts: Teradici Cloud Access Software and PCoIP Remote Workstation Card.

Known Issues¶

Incompatibility between PCoIP Software Client for Windows and virtual KVM application Synergy¶

There is a known incompatibility between PCoIP Software Client for Windows and the virtual KVM application Synergy (http://symless.com/synergy). The Synergy application can interfere with the keyboard handling of the PCoIP client and cause sometimes a single or no keypresses to be transmitted to the PCoIP agent. This issue was observed with Synergy 2016 and may be present with other Synergy releases. (52396)

Workaround: Disable Synergy when using the PCoIP client.

Connection > USB Devices client dialog does not list any USB devices¶

At times, after a session starts, the Connection > USB Devices dialog does not list any of the USB devices connected to the client. (42270)

Workaround: Reconnect to the session or physically unplug and reconnect the USB devices connected to the client.

Wacom Intuos Pro and Intuos 5 tablets cannot be bridged¶

These tablets work as a pointing device when a session is not active, and when the tablet is not bridged while a session is active. When the tablet is bridged, the device manager application running on the remote host displays a warning icon next to the tablet and the tablet does not work. (41045)

Workaround: Avoid bridging Intuos Pro and Intuos 5 tablets.

Logitech Touch Mouse does not work when bridged in Windows¶

The Logitech Touch Mouse does not work when the device is bridged. This issue affects Windows PCoIP Software Client. (40960)

Workaround: Do not bridge the device. The device works as expected with the remote host when it is not bridged.

Cancelling large USB file transfer fails¶

Cancelling a large file from being copied to or from a USB flash drive while bridged in PCoIP software client fails to function. The file will continue to copy until finished. (40817)

Workaround: Do not try to cancel large file transfers.

SanDisk Cruzer USB devices do not work if the PCoIP session is disconnected while a file transfer is in progress¶

SanDisk Cruzer USB devices do not successfully re-bridge after the PCoIP session was disconnected during an active file transfer. (40769)

Workaround: If possible, avoid disconnecting the device or the session while file transfers are in progress. If a disconnection does occur while transfers are in progress, physically unplug and reconnect the device to the client. If the device fails to mount as a mass storage device after the previous step:

Find the SanDisk Cruzer in Device Manager.
Right-click on the device and select Uninstall.
After uninstall completes, physically unplug and reconnect the device to the client.

USB keyboards do not work in bridged mode¶

Keyboards do not work when bridged. This affects both Windows and macOS PCoIP Software Client. (40580)

Workaround: Do not bridge the keyboard. Keyboards function correctly when locally terminated.

Reconnecting dialog takes up to one minute to appear from sleep mode¶

The reconnecting dialog on the PCoIP Software Client may take up to one minute to appear after waking up laptop from sleep mode (by opening the lid). Prior to the reconnecting dialog appearing, the client displays the last session content. (36363)

Windows client crashes when IP address is used as broker address¶

The Windows client will crash when an IP address is used as a Host Address (broker address). (32663)

Workaround: Use FQDN instead of IP address as a broker address.

Client window size is not remembered when crossing multiple monitors¶

When stretching the client window across multiple monitors, client window size is not remembered for session reconnects. (32597)

Mouse out of sync due to scaling in dual high-resolution displays¶

Connecting a PCoIP Software Client session with dual high-resolution displays in full-screen mode (2560x1600 for example) to a hard host that does not support high-resolution displays may result in unexpected behavior. For example, one or both displays may be scaled to single link DVI resolutions without the client also scaling, resulting in unsynchronized mouse movement. (29862)

Workaround: Set client desktop to single link DVI resolutions. Alternatively, upgrade host GPU to support dual-link resolutions (Tera2 hosts only)

Audio input in PCoIP Software Client with PCoIP Remote Workstation Card does not work¶

When in session with a PCoIP Remote Workstation Card, PCoIP Software Client supports audio out from the host, but not audio into the host. (26355)

Resolved Issues¶

Fixed security issue in third party package.¶

A third party package has been updated to resolve a security issue. (68271)

Excel clipboard copy and paste now works as expected¶

Previously, redundant transfers of clipboard information between the client and host VM could occur. (68090)