Micro Focus LoadRunner

Software Version: 12.60 to 12.63


Publication date: September 26, 2019

This Readme provides the latest information about LoadRunner 12.60 to 12.63.


What's new in LoadRunner

LoadRunner includes many new features, enhancements, and usability improvements.

You can find information about what's new in the LoadRunner Help Center.

For information about what new functionality for versions previous to 12.60, use the following links.

Back to top

Installation and configuration information

You can find information and components for installation as follows:

Installation permission requirements:

Back to top

Notes and limitations

This section includes pre-installation notes, issues, and workarounds for LoadRunner 12.60 to 12.63.

For additional limitations and workarounds, see the sections on known issues in the Help Centers.

Installation and upgrade

  • Installation path: The default installation path has changed to C:\Program Files (x86)\Micro Focus\LoadRunner.
  • Licenses: Due to changes in LoadRunner licensing starting from version 12.60, you need to replace your current license to enable working with LoadRunner 12.60 and later.

    To obtain and install a new license, see Install LoadRunner Licenses in the LoadRunner Help Center.

  • Community license: Customers who have a valid license for LoadRunner can obtain a LoadRunner Community license without registration. This option is exclusively for a scenario where a LoadRunner Controller machine has no access to the internet. To obtain the license, contact the customer support team.

Virtual environments

The architectures provided by virtualization vendors are rapidly evolving. LoadRunner is expected to function as designed in these changing environments, as long as the third-party vendor guarantees full compatibility of the virtualized environment with the LoadRunner-approved hardware requirements.

If you follow the LoadRunner system requirements and support matrix to create the virtual machine, LoadRunner will work correctly.

Working on top of a virtual machine may require access to the virtualization server hardware/monitoring environment to ensure the virtualization server is not saturated; otherwise, this might obscure the virtual machine's measurements and lead to false results.

Security - CA certificate

LoadRunner 12.60 uses an updated version of OpenSSL, which enforces additional constraints for secure communication.

OpenSSL (from 1.1.x) requires that the basic constraints for a CA certificate include a confirmation that the certificate is a CA certificate.

Upgrade: If you are upgrading, and your CA certificate was created in a previous version of LoadRunner using any of the LoadRunner tools, you can no longer use these certificates because they do not include the required constraints. Use the LoadRunner tools to create and install a new CA certificate and new TLS certificates on each LoadRunner machine. For details, see Secure Communication with TLS (SSL).

Organization's CA: If your CA certificate is provided by your organization, verify that the certificate includes the constraints described above. If the required constraints are not defined, your IT department should provide updated CA and TLS certificates to install on the LoadRunner machines.

To verify:

Check that the constraint is defined for the CA certificate in the Basic Constraints extension, for example, Subject Type=CA or CA:TRUE (the constraint format varies, depending on how the certificate was accessed).

  • On Windows: Double-click the CA certificate and select the Details tab. Select Extensions only from the Show list, then select Basic Constraints and check that the constraint is defined in the properties area.
  • On Linux: Use the following command to view certificate information: openssl x509 -in <CA-filename> -noout -text.

Virtual Table Server (VTS) upgrade

  • To upgrade VTS, first uninstall the version you have, then reinstall the latest version from the Additional Components folder.
  • The default data path for VTS has been updated to C:\ProgramData\Micro Focus\VTS\db\data. To continue using your current data path:

    • When prompted during the installation, redirect the data path to your current data path
    • After installation, update the dbPath value in the VTS configuration file. Then restart VTS service.


  • If you have multiple LoadRunner components installed together on a machine (for example, both VuGen and Analysis, standalone versions), and you uninstall one of the components, run a Repair installation on the remaining components after the uninstall.
  • If you have VuGen standalone and BPM installed together on a single machine, and you uninstall BPM, run a Repair installation on VuGen.


  • A Red Hat Enterprise Linux (RHEL) 7 (or later) OS is required for running JavaScript Web HTTP/HTML scripts.
  • When uninstalling a load generator on a Linux machine, the uninstall process may fail and you may get an error message saying "Cannot restore segment port after reloc: permission denied."

    Resolution: Use the setenforce 0 command to disable SE Linux before uninstalling the load generator. When the uninstall is complete, use the setenforce 1 command to enable SE Linux.

Coexistence with Unified Functional Testing (UFT) and LeanFT

  • It is not recommended to install LoadRunner and LeanFT on the same machine. Doing so may cause issues when invoking the Analysis API from an external code or plugin (for example, Jenkins), with recording and code generation for Java protocols, with Network Virtualization replay, TruClient functionality, and other issues. If you try to continue to work while these issues exist, it may cause LoadRunner to malfunction.

    Possible workaround: Before proceeding, make sure that LeanFT is excluded from the PATH environment variable on the machine. For more information, see this Knowledge Base article.

  • If you install or uninstall LoadRunner on a machine where UFT is installed, at the end of the process a warning message is displayed: "Cannot load resource file <somepath>/mdrv_res.e2 (<somepath>/mdrv_res.j2)." Ignore this message.

  • If you install LoadRunner and UFT on the same machine, and then uninstall one of them, the remaining software program may not function correctly.

    Resolution: Run a Repair of the software program you want to use on the machine.

  • A machine with LoadRunner and UFT, on which UFT was installed after LoadRunner, may not allow the recording of certain protocols.

    Resolution: Uninstall UFT and run a Repair on the LoadRunner installation.

  • If you install UFT on a load generator machine when the load generator agent is running, the remote Controller may not be able to run UFT scripts on the load generator machine.

    Resolution: After installing UFT, restart the load generator agent using the Agent Configuration utility, or alternatively reboot the machine.


Windows 10 and Windows Server 2016

  • When working with Windows 10 or 2016, we recommend using Internet Explorer (IE) 11 as the default browser; using the Edge browser interferes with some of the advanced functionality.

  • Use IE as the default browser with Windows 10 to prevent issues with proxy recording and certificate settings.

Java over HTTP

Version 12.60-12.61: Recording Java over HTTP applications with Oracle 64-bit JRE is not supported on Windows 10.

Version 12.62 and later: The above issue is fixed.


  • When recording mstsc.exe on Windows 10, if the RDP server side enables FIPS, the default recording will produce the following error: "Because of an error in data encryption, this session will end. Please try connecting to the remote computer again."

    Resolution: Turn off FIPS on the server side, or perform the following procedure to enable recording using the SSL mode:

    1. Open mstsc, enter the IP address of the RDP server, click Show Options to expand the dialog box, and then click Save As to save the configuration to a file. Name the file RDPConfig.RDP.
    2. Open RDPConfig.RDP with Notepad, add enablecredsspsupport:i:0 at the bottom. Search for authentication level in the same file, make sure this line is authentication level:i:2.
    3. Go to <LoadRunner root>\dat\, open rdp_ro.ini with Wordpad or Notepad++ (do not use Notepad because of the new line characters issue), add SupportSSL=1 at the bottom.
    4. In VuGen, click Start Recording. In the Remote Desktop Connection dialog box, click Show Options. Click Open, and choose the RDPConfig.RDP file that you saved above. Then click Connect.


  • Where applicable, we recommend using TruClient Browser or Chromium on Windows 10 and Windows 2016.
  • (Windows 10 + IE) TruClient script conversion to Web - HTTP/HTML is not supported on Windows 10 using the IE browser.
  • (Windows 10 + IE) The TC.setProxy API does not work on Windows 10 when both Automatically detect settings and Use automatic configuration script (ie, PAC proxy settings) are configured in the LAN settings for the IE browser.


(Windows 10 + IE) WinINet recording mode is not supported on Windows 10. An empty script will be generated.

Windows Sockets (WinSock)

Recording on Microsoft Edge browser is not supported.



VuGen and protocols





General LoadRunner

Help and PDFs

Non-English operating systems


Back to Notes and Limitations

Back to top

Deprecated features, protocols, and technologies

This section provides information about features, protocols, and technologies whose support was partially or fully discontinued, or will be discontinued in future versions of LoadRunner and Performance Center.

This section includes:

Removed features

The following features have been removed from LoadRunner:

Note: In version 12.53, the Mobile Application - HTTP/HTML protocol was unified with the Web - HTTP/HTML protocol. All functionality for generating Vuser scripts for mobile applications is now provided with the Web - HTTP/HTML protocol. For details, see Web - HTTP/HTML - Recording Methods for Mobile Applications in the LoadRunner Help Center.


Removed support for technologies

From version 12.62, LoadRunner no longer supports these product technology versions:

Operating System or Protocol Product Versions
OS Red Hat Enterprise Linux 6.4, 6.5, 6.6, 7.1 and 7.2
OS Windows 10 1511 (November)
Citrix ICA Citrix XenApp and XenDesktop 5.x, 6.x, and 7.0 to 7.13
JMeter Apache JMeter 2.13 and 3.1
JUnit JUnit 4.0 to 4.6
NUnit NUnit 3.2
Oracle 2-Tier Oracle Database 9i R2, 10g and 11g R1
Oracle NCA Oracle Forms and 6i+
Selenium Selenium 2.24.1 to 3.11.0
Siebel Web Oracle Siebel CRM 7.5.2, 7.5.3, 7.7 and 7.8
Teradici PCoIP Teradici PCoIP Agent 2.7 to 2.11
Teradici PCoIP Connection Manager 1.5 to 1.8.0
Teradici PCoIP Security Gateway 1.11 to 1.13


From version 12.63, LoadRunner no longer supports these product technology versions:

Operating System or Protocol Product Versions
.NET .NET Framework 4.5, 4.5.1
Java Java 6, 9, 10
Eclipse Eclipse IDE Neon, Mars, Luna, Oxygen, Photon
JMeter Apache JMeter 3.2, 3.3, 4.0
JUnit JUnit 4.7 to 4.9.1
MAPI Microsoft Messaging Application Programming Interface (MAPI) 2007


Protocols supported for replay only

If a protocol is supported for replay only, you can no longer create scripts based on that protocol.

Protocol Supported for replay only

Ajax Click & Script

From version 12.60

Tip: Migrate your existing Ajax Click & Script scripts to another Web protocol such as TruClient - Web or Web - HTTP/HTML

COM/DCOM From version 12.60
EJB (Enterprise Java Beans) From version 12.00
Java Record Replay with CORBA From version 12.60
JavaScript Vuser From version 12.00
MMS (Media Player) From version 12.53
MMS (Multimedia messaging service) From version 12.53
Silverlight From version 12.55
VBScript Vuser From version 12.00
Web - Click and Script From version 12.00


Fully removed protocol support

There is no record or replay support for the following protocols:

Protocol Supported for replay only No support
DB2 CLI From version 11.00 From version 12.55
i-mode From version 11.00 From version 12.55
Informix From version 11.00 From version 12.55
PeopleSoft Enterprise From version 12.00 From version 12.55
PeopleSoft -Tuxedo From version 12.00 From version 12.55
Real From version 11.50 From version 12.55
SAP - Click & Script From version 12.53 From version 12.55
Siebel - DB2 CLI From version 11.00 From version 12.55
Siebel MSSQL -- From version 12.55
Siebel Oracle -- From version 12.55
SQL Server From version 11.50 From version 12.55
Sybase Ctlib From version 11.00 From version 12.55
Sybase Dblib From version 11.00 From version 12.55
Tuxedo From version 12.00 From version 12.55
VB Vuser -- From version 11.50
VoiceXML (VXML) From version 11.00 From version 12.55
WAP From version 11.50 From version 12.55


Planned future removal of technologies

The following product technology versions are no longer supported by their vendors. To align with this, LoadRunner will discontinue support for these technologies in a future LoadRunner version:

Operating System or Protocol Product Versions
OS Red Hat Enterprise Linux 6.7, 6.10, 7.3 and 7.4
OS Windows Server 2008 R2 All versions
OS Windows 7 All versions
OS Windows 10 1703 (Creators)
Citrix Citrix XenApp and XenDesktop 7.18
Flex Adobe LiveCycle Data Services ES2 3.1 and ES4 4.7
NUnit NUnit 3.4
SAP GUI SAP GUI Client 7.50
Teradici PCoIP Teradici PCoIP Teradici Agent for Windows 2.12 to 2.13
Teradici PCoIP - VMware Horizon 6.2.1


Planned future removal of LoadRunner functionality

The following information provides advance notice of functionality that will be removed in an upcoming LoadRunner version.

Back to Deprecated features and protocols

Back to top

Beta and tech preview features

This product includes limited functionality entitlements – these can be either “beta” or “tech preview” features (as indicated in the What’s New). This means that these beta or tech preview features may be undergoing further testing before their full capabilities are released. These features, including their capabilities and content, are provided on an “as is” basis. Micro Focus disclaims all other warranties. Micro Focus shall not be responsible for any loss or damage suffered by any customer as a result of their use of any beta or tech preview feature.

Micro Focus reserves the right to change or remove a beta or tech preview feature at any time, without further notice. These features, which include basic capabilities, are currently offered as embedded features accompanying the product license. In the future, Micro Focus may offer advanced capabilities for the same features at a separate cost.

Should you encounter any bugs, glitches, lack of functionality, or other problems with any beta or tech preview feature, please let us know immediately. Your help in this regard is greatly appreciated.

Send your feedback to

Back to top

Additional resources

The Usage Hub enables you to view license information and usage for all Micro Focus Software products and solutions that are installed in your environment. The Usage Hub is a central server that runs in the background. It collects, maintains, and provides a centralized view of software deployments, license assets, and the product features.

In addition, follow these links to learn more about LoadRunner and other Micro Focus products.

Back to top

Legal Notices


Certain versions of software and/or documents (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company.  As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company.  Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.


The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Restricted Rights Legend

Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Comodo Code Signing Certificate

The code signing certificate for LoadRunner was changed from Verisign to Comodo starting on January 1, 2017.

If you are installing this product on a computer with an older version of Windows, or on a computer without automatic Windows updates, the Comodo root certificate may not automatically be included as a trusted root certificate.

In such cases, we recommend manually configuring Comodo as a trusted root certificate.

For more details, see:

Copyright Notice

© Copyright 1994-2019 Micro Focus or one of its affiliates

Send documentation feedback