Release Notes
Client SDK for Windows 25.03.1
Important Notes and Requirements
-
Use of Anyware Client SDK requires a separate agreement with HP Anwyare.
-
The SDK is intended for use cases where client customizations are required and when Anyware Software Clients, PCoIP Zero Clients, and PCoIP Mobile Clients are not sufficient.
-
The SDK is intended for customers with software development skills and knowledge, as well as a sound understanding of virtualization systems.
Version 25.03.1 of the Anyware Client SDK for Windows fixes known issues, bugs and provides stability enhancements for a better user experience and seamless support.
Previous Releases in this Version
25.03
Changes to Windows OS Support
Version 25.03 of the Client SDK for Windows and later will no longer support Windows 10, version 21H2.
Connection Failed when Broker Certificate Serial Number Was 0
While using Anyware Clients version 25.03, brokered connections failed if the broker certificate included serial number zero (0). This issue has now been fixed.
Collaboration Does Not Work on Anyware Client on Windows for ARM with PCoIP Ultra Set to CPU Offload or Auto Offload
Anyware Client running on Windows for ARM is unable to connect to collaboration sessions initiated on Standard agents if PCoIP Ultra is set to CPU Offload or {}Auto Offload{}. This is because the Windows Prism emulator does not support AVX2 instructions necessary for Ultra CPU Offload.
This issue is not observed when PCoIP Ultra is set to {}GPU Offload{}. Note that this capability is available only on Graphics Agents.
- If using a Graphics Agent, set PCoIP Ultra to GPU Offload prior to establishing a collaboration session.
- Use an Anyware Client that supports CPU Offload on a Standard Agents, or CPU Offload or Auto Offload modes on a Graphics Agent.
Client on Windows for ARM - PCoIP Ultra CPU Offload not supported
Anyware Client on Windows for ARM is unable to use PCoIP Ultra CPU Offload. This is because the Windows Prism emulator does not support AVX2 instructions necessary for Ultra CPU Offload.
When connecting to an Anyware Agent with PCoIP Ultra set to GPU Offload , the client will connect with standard PCoIP, and will not support PCoIP Ultra features such as Collaboration.
When connecting to an Anyware Agent with PCoIP Ultra set to {}Auto Offload{}, the client will always connect using in the GPU Offload mode, and will never use CPU Offload.
Client on Windows for ARM does not support USB Peripherals
The Anyware USB Driver for Windows Client is not compatible with Windows for ARM. There is no support for remoting USB devices in-session when running the client on Windows for ARM.
If USB Peripheral remoting is required, use a client that supports USB remoting. This includes Anyware Clients running on Windows x86/x64, Linux x86/x64 or MacOS, and Anyware Trusted Zero Clients.
Caps Lock and Kana state can go out-of-sync when a Japanese keyboard is used
When a Japanese keyboard is used on the client side in a PCoIP session, the Caps Lock state can be out-of-sync on the host side if the Caps Lock key is pressed outside of the PCoIP client window.
On the client machine, set the input language to non-Japanese when a Japanese keyboard is used.
Do not press the Caps Lock key outside of the PCoIP client window when a Japanese keyboard is used.
If the Caps Lock state is out-of-sync inside a PCoIP session, disconnect and reconnect to the host.
Microphone Does not Function with Kaspersky Anti-Virus
On Windows Client running on a desktop with Kaspersky Anti-Virus installed, forwarding of a local microphone to the remote desktop may be blocked. If this happens, the microphone cannot be used in the PCoIP session and Kaspersky Anti-Virus displays the following message: Receiving the audio stream for the application is blocked.
The PCoIP Client must be whitelisted in Kaspersky Anti-Virus in order to allow the audio stream for the application to be forwarded. Refer to Kaspersky for instructions on how to whitelist an application for audio stream access.
The name of network shown in Anyware Health Monitor does not change during a session
In Anyware Health Monitor, the name of network shown will not change during a session even if the actual network changes.
For example, if an ethernet cable is pulled out and the system switches to WiFi, the name of network will not change in the Anyware Health Monitor display until the session is disconnected and reconnected.
Intel UHD driver causes Windows memory leak
Intel UHD driver version 30.0.101.2079 causes a memory leak with PCoIP Software Client for Windows. When this occurs, the client system will slow significantly and may require a restart to recover.
This issue impacts Intel Integrated GPUs when used with 4k (UHD) monitors.
Other driver versions may also have this issue.
To avoid this issue, install an Intel UHD driver that is not affected:
- Version 30.0.101.1069 or earlier, or
- version 31.0.101.3729 or later.
Updating the driver to a version that is not affected resolves the issue.
Audio Input from microphone may stop after a long period of inactivity.
The microphone for a remote session may stop working if not used for a long period of time.
Audio output may stop working when switching devices
After switching to a different audio output device while connected to a remote desktop, audio output from the PCoIP client may stop.
Disconnect and reconnect the session after switching audio devices.
Audio disappears when audio-in is enabled
Audio output to speakers or a headset would stop after using audio input from a microphone.
Audio output may randomly stop
While connected to a remote desktop the audio output on the PCoIP client may stop.
Disconnect and reconnect the session after switching audio devices.
PCoIP Client in window mode can be limited to 30 fps
For high resolution displays with dimensions larger than 3840x1600 the maximum fps will be limited to 30.
To enable up to 60 fps either set the client in full screen mode or reduce the window size to dimensions less than 1600 pixels.
USB driver conflicts with NoMachine software
The USB driver installed with the PCoIP Software Client for Windows has a driver conflict with the USB driver used by the NoMachine remoting software.
Remove the NoMachine software before installing the PCoIP client.
Display arrangement appears different on remote hosts in DPI-unaware application
Windows applications that are DPI-unaware are presented with a scaled display resolution if the display has text and icon scaling enabled. This may result in display arrangements on the remote host appearing in different positions.
Windows remaps the display positions fixing the top left corner of a display at the same position if possible. If the reduced size of the display results disconnected displays, the display positions will be shifted so the displays remain connected.
Leave the client SDK configured as a DPI-aware application.
Using an invalid or corrupt branding package crashes client
If the branding package does not match the hash value specified for the branding package, the session client will terminate.
Replace the corrupt branding file or use the correct hash value.
Bridged USB devices disconnected when switching to Windowed Mode
When the client has more than one monitor, switching from Full-screen to Windowed mode will disconnect all bridged USB devices.
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.
Allow operations on USB devices to complete prior to disconnecting the session.
USB keyboards do not work in bridged mode
Keyboards do not work when bridged. This affects both Windows and macOS PCoIP Software Client.
Do not bridge the keyboard. Keyboards function correctly when locally terminated.
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.