Share via

Release Notes for HPC Pack 2019 Update 3

These release notes address late-breaking issues and information for the high-performance computing (HPC) cluster administrator about Microsoft HPC Pack 2019 Update 3.

Important

Before updating existing HPC Pack 2019 Update 2 and earlier clusters, including Windows-only clusters, to Update 3 or later, users must refer to Manage Linux authentication key for HPC Pack to set a Linux authentication key to address the critical vulnerability CVE-2025-21198.

Download and install Microsoft HPC Pack 2019 Update 3

Microsoft HPC Pack 2019 Update 3 is available for download (Cluster Install & Client Utilities) from the Microsoft Download Center. After the download, please save the installation files to your local machine (or machines) that will be set up as a cluster head node.

Known issues

  • There was a scheduler regression for jobs with node preparation and/or release tasks in the previous Update 3 build 8.3.8310. Such jobs would fail with a validation error "The property 'GroupId' may not be set for tasks of type 'NodePrep'". Please reinstall the cluster with the refreshed Update 3 build 8.3.8328.
  • Windows Server 2022 is supported for head node role with .Net Framework 4.8 cumulative update August 9, 2022-KB5015733 or later applied to all cluster nodes and clients that are on Windows Server 2022. If the updates are not available, you may need to disable TLS 1.3 on Windows Server 2022 before installing the head node as a workaround.
  • Upgrading could be stuck if certian HPC services (e.g., HpcBroker) are in a Pausing or Stopping state. To proceed, stop the corresponding process (e.g., HpcBroker.exe).
  • When using Windows Server 2022 as the head nodes OS, the Linux compute nodes deployed will be in error state. This is due to Windows Server 2022 by default supports TLS 1.3 which the Linux node agent currently does not support. The mitigation is to disable TLS 1.3 on the head node by importing the following registry keys and restart the server.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Client]
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.3\Server]
"Enabled"=dword:00000000