Known issues when installing

This section describes troubleshooting and limitations for installing UFT.

Previous UFT versions

  • Ensure that you have the Microsoft update installed before installing UFT.

    If the installation fails, repair the Microsoft C++ 2015 Redistributable installation (found in the <UFT installation directory>/prerequisites folder) and try the UFT installation again.

  • Due to the Help documentation being online, the Help_Documents silent installation parameter is no longer supported. If you have silent installation scripts that use this parameter, remove it from your scripts to ensure UFT installs correctly.

Back to top

Files in use

If the UFT Files in Use dialog box is displayed during the installation process, select Close the application and attempt to restart them.

UFT automatically closes the applications and continues the installation.

If after restarting, the UFT Files in Use dialog box lists Explorer as the open application, do one of the following:

Close the applications and attempt to restart them

Instructs UFT to automatically close the applications that are needed for the installation.

Do not close application.

Instructs UFT to continue the installation. You must restart your computer after the installation if you select this option.

Back to top

Component registration failed

If a message is displayed during installation about component registration failing, do not click OK to continue.

Instead, check the issue in the VC2015Prerequisite_yyyymmdd_XXXXXX.log file in the %TEMP% directory. If the log shows that a service did not start correctly, restart the service manually, and start your installation again.

Back to top

UFT installations and other ADM software


UFT may work unexpectedly after uninstalling LoadRunner version 11.50. If this occurs, perform a repair installation for UFT after uninstalling LoadRunner 11.50.

Additionally, if you install LoadRunner 11.52 Patch 1 after installing UFT12.53, make sure to reboot the computer after installing LoadRunner. Otherwise, you may receive errors referring to the mdrv process.

Sprinter If you are using both UFT and Sprinter on the same computer, and you modify either UFT or Sprinter, you must run a Repair for the installation of the other product.

When an ALM client is installed on the same computer as UFT, uninstalling UFT may remove the association of movie (.fbr) files.

This may prevent you from viewing movies associated with defects in ALM using the Micro Player application.

Workaround: Re-associate the movie files with the Micro Player application from the Windows File Options dialog box.


In the Custom Setup screen, it is possible to select the LeanFT Visual Studio or Eclipse plugins even if you do not have the relevant IDE installed at the time of the installation.

If you install the IDE later, you will not have the LeanFT plugin available.

Workaround: After installing the required IDE, run a Repair for the installation.

Back to top

UFT installations and Microsoft software

Software UFT instructions
Windows 10
  • When installing UFT on a Windows 10 operating system, you must close Cortana and the Action Center before performing the UFT installation.

  • You must have administrative permissions to connect to ALM from UFT on Windows 10.

    Connect to ALM with Administrator permissions immediately after installing UFT.

  • When uninstalling UFT on Windows 10, the UFT4WinRT service is not uninstalled with other UFT files. As a result, a new installation on the same machine will fail.

    Workaround: Restart the computer after uninstalling UFT.

  • If version ofthe pdm.dll is found on your computer, the setup program will recgonize this during installation and will instruct you download the corrected DLL from the Microsoft site.

    For more details, see

  • To debug GUI tests in UFT, ensure that you have the most recent version of the pdm.dll file installed and registered.

    The pdm.dll file is installed and registered with Microsoft Visual Studio and Microsoft Office, and installed (but not registered) with Microsoft Internet Explorer.

    If your currently registered version is lower than 9:

    1. Uninstall the Microsoft Script Debugger (if installed).

    2. Perform a repair installation of Microsoft Visual Studio or Microsoft Office.

      Check the registry for pdm.dll version: HKEY_CLASSES_ROOT\CLSID\{78A51822-51F4-11D0-8F20-00805F2CD064}\InprocServer32

    If you need to use the pdm.dll file installed with Microsoft Internet Explorer, do the following:

    1. Ensure that you have administrator privelgest.
    2. Locate the pdm.dll file, usually located either in c:\program files(x86)\internet explorer\ or c:\program files\internet explorer.
    3. Move the pdm.dll file and the msdbg2.dll file from the same folder to a different location.

    4. Run the following commands:

      regsvr32 <full path to pdm.dll>\pdm.dll

      regsvr32 <full path to pdm.dll>\msdbg2.dll

Microsoft Office 64-bit

You cannot install Microsoft Office 64-bit on a machine with UFT. Instead:

  1. Uninstall the Microsofte Access database engine. This is installed together with UFT.

  2. Install Microsoft Office 64-bit.

  3. Reinstall the Mcrosoft Office Access database engine from the prerequisites\msade2010 folder of the UFT setup directory using the following command:

    <UFT root directory>\prerequisites\msade2016\AccessDatabaseEngine.exe /quiet

Windows 8.x or higher / Windows Server 2012 R2

When using UFT on Windows 8.X or higher or Windows Server 2012 R2, if you want to use API tests and components, make sure that you have MSU (Microsoft Update) KB2887595 installed.

Back to top

UFT installations and the Functional Testing Agent (browser support)

Browser UFT instructions
Google Chrome

If you are testing applications in Google Chrome version 31 or later, Chrome automatically downloads and installs the Functional Testing Agent for Google Chrome the first time you open Chrome after UFT is installed.

In the following cases, you must manually enable the Functional Testing Agent for Google Chrome extension:

  • You have no Internet connection.

  • You have not enabled the automatic updates for Google Chrome.

  • You are using Google Chrome version 30 or earlier.

For details on manually enabling the extension, see the task on How to Enable the Functional Testing Agent for Google Chrome Extension in the Web section of the Unified Functional Testing Add-ins Guide.

Mozilla Firefox

Firefox versions 33 or later

If you are testing applications in Firefox version 33 or later, accept the prompt for install Functional Testing Agent for Firefox the first time you open Firefox after UFT is installed.

Firefox versions 32 or earlier

If you testing applications in Firefox version 32 and earlier, do the following:

  1. Open the <UFT installation folder>\Installations\Firefox folder.
  2. From the Firefox folder, drag the AgentLegacy.xpi file into Firefox.
  3. In Firefox, open the browser menu.
  4. In the menu, click Add-ons.
  5. In the Add-ons Manager tab, select the Extensions node.
  6. In the Functional Testing Extension row, disable the Functional Testing Agent extension and enable the extension you added to Firefox.

Java applets

If you are testing Java applets, you must use the legacy Functional Testing Agent for Firefox.

Legacy Functional Testing Agent for Firefox

The legacy Functional Testing Agent for Firefox is supported only for Firefox versions 39 and earlier.

Note: If you are using a version of the Functional Testing Agent for Google Chrome from UFT version 12.00 or earlier, you must enable the downloaded extension and remove the previous version of the Functional Testing Agent extension.

Back to top

UFT installations and 64-bit applications

Installing with administrator privileges

UFT loses support for 64-bt appliations if a user with administrator priveleges installs the Unified Functional Testing Add-in for ALM, or performs a Repair operation on the Run Results Viewer, and the a user runs UFT on that same computer without adminsitrator priveleges.

Workaround: Log in as an administrator and do one of the following and Repair UFT or run <UFTinstallation>\bin64\Mediator64.exe.

32-bit and 64-bit applications

If your computer has two versions of an application, where one is 32-bit and the other is 64-bit, UFT always opens the 32-bit version.

This occurs when the operating system performs a redirect from the Program Files folder to the Program Files (x86) folder, and from the System32 folder to the SysWow64 folder.

Workaround: To specify a 64-bit version, make sure that the step explicitly states the path to the 64-bit application.

.NET / WPF Add-in extensibility When working with .NET or WPF Add-in extensibility for a 64-bit Windows Forms process, the custom server DLLs must be built using the Any CPU option.

Back to top

UFT installations and Java

When re-installing or upgrading the JRE on a machine with UFT installed, you might encounter error 1603 preventing the JRE installation to complete.

This can be caused by an interference between the UFT Java environment variables and the Java installer.

To successfully complete the installation, rename the UFT Java environment variables, perform the JRE installation and restore the variable names.

To temporarily rename the UFT Java environment variables: 

  1. On your Windows Desktop, right-click My Computer or This PC and select Properties.

  2. Select the Advanced tab.

  3. Click the Environment Variables... button.

  4. Look for the following environment variables both under the user variable list and the system variables list and edit their names:


    • Java_Tool_Options

    • IBM_Java_Options

  5. Install the JRE.

  6. Once the installation is completed, change the environment variables names back to their original names.

Back to top

See also: