PCoIP Host Software for Windows 4.3.1 Release Notes

Release Overview

PCoIP Host Software for Windows enables Windows operating systems (OS) to interact with PCoIP Remote Workstation Cards installed in host computers, and a PCoIP client connected to the host.

PCoIP Host Software for Windows 4.3.1 includes stability fixes. These release notes provide a summary of key feature additions and compatibility notes for this firmware release.

What's New in This Release

Added Windows 10 support

PCoIP Host Software for Windows now supports Windows 10 64-bit.

Windows 10 signed drivers

Remote Workstation Card drivers for Windows 10 are now properly signed by Microsoft.

Important Notes and Requirements

  • PCoIP Host Software for Windows 4.3.1 only runs on Windows 7 64-bit and Windows 10 64-bit. The installer will generate an error if it is executed on any other Windows OS.
  • Should you like to run with another Windows OS, including XP, Vista, Windows 7 32-bit and Windows 8.1 64-bit, use PCoIP Host Software for Windows 4.2.2.

Release Downloads

Release Documents and Software

Release History

Version/Build Date Description
4.3.1 December 2016 Windows 10 support, stability fixes

Compatibility

Host Software Release Recommended Remote Workstation Card Firmware Releases Compatible Firmware Releases Supported Operating Systems
4.3.1 4.9 4.9.x - Windows 10 64-bit
- Windows 7 64-bit
4.2.2 4.2.0 4.2.x - Windows 10 64-bit
- Windows 8.1 64-bit
- Windows 7, 32-bit and 64-bit
Windows Vista, 32-bit and 64-bit
Windows XP SP2, 32-bit and 64-bit.

Resolved Issues

Multiple virtual display adaptors no longer cause PCoIP Host Software for Windows to crash

Previously, PCoIP Host Software for Windows would crash when there were more than four virtual display adaptors detected in the operating system. This issue is now fixed. (47164)

Topology settings are now enforced in the Windows login screen

Previously, changing topology settings from the user tray application would not cause the settings to take effect in the Windows login screen. This issue is now fixed. (41021)