1

NX Installation Guide for Windows

December 2024

Introduction ...................................................................................................................................... 4
Conventions ............................................................................................................................................ 4
Basic Windows Techniques ..................................................................................................................... 4
Document Revisions ............................................................................................................................... 5
Media Contents ...................................................................................................................................... 6
Supported Workstations ......................................................................................................................... 6
Licensing NX ............................................................................................................................................ 7
Siemens NX Launcher ............................................................................................................................. 7
Overview of the Installation Process ....................................................................................................... 8
Installation Software Integrity ................................................................................................................ 8
Release Frequency .................................................................................................................................. 8
Functional Product Releases ................................................................................................................... 8
Functional Releases and Associated Monthly Releases .......................................................................... 9
NX Start Menu Changes ........................................................................................................................ 10
Preparing for the Installation............................................................................................................ 11
Licensing Configuration Decisions......................................................................................................... 11
Java Runtime Environment ................................................................................................................... 11
Check File System ................................................................................................................................. 11
Check Disk Space................................................................................................................................... 12
Set Up TCP/IP Network Services ........................................................................................................... 12
Installing NX .......................................................................................................................................... 13
Installation Features Pre-Selected Based On Previously Installed Release ........................................... 13
Installation Features to Cabinet Files Listing ......................................................................................... 13
Changes to Add-On Products Features Default Installation Settings .................................................... 14
Installation Steps................................................................................................................................... 15
Installation Feature Contents................................................................................................................ 18
Using the Maintenance Options ........................................................................................................... 20
Running NX ...................................................................................................................................... 21
Java Runtime Environment ................................................................................................................... 21
Running NX from the Start Menu ......................................................................................................... 21
Running NX by Double-Clicking ............................................................................................................. 21
 2

Running Multiple Versions of NX .......................................................................................................... 21

Automatic Installation of NX ............................................................................................................ 23
Installing NX as an Upgrade .............................................................................................................. 27
Upgrade Installation Using MSI ............................................................................................................. 27
Automatic Installation of NX as an Upgrade Using MSI ........................................................................ 27
Upgrade Installation Using MSP ............................................................................................................ 28
Automatic Installation of NX as an Upgrade Using MSP ....................................................................... 28
Installing NX for Parallel Product Testing .......................................................................................... 29
Administrative (Parallel) Installation ..................................................................................................... 29
Upgrading the Parallel Installation with an MSP file ............................................................................. 29
Running the Parallel Installation (Administrative Install) ...................................................................... 30
Removing the Administrative (Parallel) Installation .............................................................................. 30
Installing Siemens NX Launcher ........................................................................................................ 31
Siemens NX Launcher Installation Steps ............................................................................................... 31
Automatic/Silent Installation of Siemens NX Launcher ......................................................................... 31
Mapped Drive Installation ................................................................................................................ 33
Mapped Drive Installation Steps ........................................................................................................... 33
Automatic/Silent Installation of Siemens NX (Mapped Drive) .............................................................. 34
Additional Topics ............................................................................................................................. 37
Uninstalling NX...................................................................................................................................... 37
Other Uninstall Considerations ....................................................................................................................... 37
Changes ................................................................................................................................................ 38
Kit Consolidation ............................................................................................................................................ 38
UGII_ROOT_DIR obsoleted ............................................................................................................................. 38
NXBIN directory.............................................................................................................................................. 38
Siemens License Server Installation no longer provided on NX Installation Media ........................................... 38

Troubleshooting............................................................................................................................... 39
Windows Diagnostic Tools .................................................................................................................... 39
Launch.exe does not show proper user interface ................................................................................. 39
“Connection to license server machine failed.” during installation ...................................................... 39
Certificate Errors During Installation..................................................................................................... 40
Error writing to file ugshext.dll during update installation ................................................................... 41
Creating Install Log Files........................................................................................................................ 41
Repairing registry entries ...................................................................................................................... 42
NX Won't Start ...................................................................................................................................... 42
Can't Connect to License Server ...................................................................................................................... 42
No Licenses Available ..................................................................................................................................... 42
Error Handling Failed – NX Initialization error ................................................................................................ 45
NX Startup Very Slow ............................................................................................................................ 45
 3

Tools->Spreadsheet does not start Excel .............................................................................................. 46

Part Preview Issues ............................................................................................................................... 46
Proprietary & Restricted Rights Notice ............................................................................................. 48
 4

Introduction
This document explains the installation and running of NX on supported 64-bit Windows workstations. NX
is not supported on any Windows 32-bit platform. See the Release Notes for operating system
requirements.

Conventions
All references to "Windows" in this manual refer to 64-bit versions of Windows.
Our company name is "Siemens", however, some program names, folder names and some product kit
names may still retain the old UGS company name.
All references to "Siemens License Server" in this manual refer to Siemens License Server software.
Windows menu items and commands will be written in bold letters.
When presenting a series of choices from a Windows pull-down menu, an arrow →will be used to
represent the series of submenus, (e.g., Start→All Apps→Windows System→File Explorer). If you do not
have the Symbol font installed, or you browse this document on a non-Windows computer, you may see
the registered trademark symbol (®) in place of the arrows.

Basic Windows Techniques

This document may require you to use some basic Windows techniques to perform certain actions. For
example, you may need to use File Explorer to browse disks and folders, or you may need to use the tools
in the Control Panel to check or change some system settings. You can reach the Control Panel folder
either via your Computer This PC icon, or through Start→All apps→Windows System→Control Panel.
Finally, you may need to use the Windows Task Manager to check that certain programs are running
properly. You can display the Task Manager by right clicking in an unoccupied area of the Taskbar and
then choosing Task Manager. If you are not familiar with these techniques, please consult your Windows
documentation or Help.
 5

Document Revisions
January 2019 Initial Release for NX.
March 2019 Added content for update installations with MSP file.
April 2019 Updated content for MSP file installations.
June 2019 Updated content for functional release information and NX Launcher product.
August 2019 Minor updates and fixes.
December 2019 Updated for 1899 Series
June 2020 Updated for 1926 Series
December 2020 Updated for 1953 Series
February 2021 Added note about bypassing licensing form using 28000@LocalHost on page 12.
June 2021 Updated for 1980 Series
December 2021 Updated for 2007 Series
March 2022 Added note about higher versions of prerequisites installed on page 12. Fixed
typographical error on page 19.
June 2022 Updated for 2206 Series.
December 2022 Updated for 2212 Series.
January 2023 Added note about "/w" (wait) option on setup.exe during MSI and MSP
automatic (silent) upgrades.
June 2023 Updated for 2306 Series.
July 2023 Added missing install features for silent (automatic) installation.
September 2023 Updated Java information text on page 19.
December 2023 Updated for 2312 Series.
February 2024 Added missing information about needing to set FEAT_UGFLEXLM when using
ADDLOCAL for silent/unattended installations.
June 2024 Updated for 2406 Series.
September 2024 Updated Check Disk Space space estimate page 12
December 2024 Updated for 2412 Series.
 6

Media Contents
NX software is provided on DVD media and via download.
Any reference to DVD or media in this document refers to either a physical DVD or a hard drive location
where you have copied or extracted the downloaded installation image files.
The NX media contains the following main items:
README.txt Gives a brief description of the contents of the media, an
official title and version, and any special instructions.
Launch.exe Program to start the installation process and access other
files on the media.
nx This is the main NX "BASE & OPTIONS" kit, which contains
the installation program, optional products and
Translators.
nxlauncher This is the installation folder for the option Siemens NX
Launcher application.
mapped This is the installation folder for the Siemens NX Mapped
Drive installer.
docs Contains installation guide, Release Notes and Fixed PR
information.

Note: NX Documentation is provided on separate media.

Supported Workstations
The NX supported workstations are not listed in this installation manual; the information is frequently
outdated by new vendor offerings and support certifications. For information on NX supported
workstations, consult the Certification link on the Support Center Web site:
https://support.sw.siemens.com/.
 7

Licensing NX
NX can be licensed in one of two ways:

1. NX can communicate with a license server which has had the Siemens License Server software installed
on it. The license server is installed separately by the Siemens License Sever installation program; it is
not part of the main NX installation. It is only required on license server nodes. You obtain the Siemens
License Server installation from Siemens Support Center (https://support.sw.siemens.com/en-
US/product/1586485382).
Note: The current Siemens License daemons support NX versions 5.0 thru current but they are not
backward compatible with NX 4.0. For NX 4.0 and prior releases you will require the old
license daemons supplied in NX 4.0. You may run both the old and new servers at the same
time.
2. NX can acquire licensing information directly from a special node locked license file called a
"Standalone Node-Locked License". In this scenario, no license server is needed, but this does require
access to a file that is encoded to your machine’s Ethernet address. In this case it is not necessary to
install the Siemens License Server product.

Siemens NX Launcher
The Siemens NX Launcher is an optional standalone application that you can use to launch NX. It provides an
interface in which you can select an NX environment and NX application, and set any necessary connection
options.

The Siemens NX Launcher installation is available on the NX product media or download. Instructions for
installation are provided in this document.
 8

Overview of the Installation Process

The basic steps for installing NX are as follows:
1. Log onto your workstation with an Administrator account.
2. Perform pre-installation checks of your Windows system.
3. Install Siemens License Server, if necessary. {Only required on license server(s)}
4. Install NX as a new installation.
5. Install Siemens NX Launcher as a new installation. {Optional product}
The details of this process are described in subsequent sections. If difficulties arise refer to the
Troubleshooting Section at the end of this guide.

Installation Software Integrity

Digital signatures provide for the authenticity of digital content, such as binary files and executables.
Beginning with NX 12, the binary files and executables included with the installation software for
the Siemens software provided for this release have been digitally signed to ensure that the
installation for this product has not been tampered with before delivery.
Verify the digital signatures on files by opening the Properties of a file and noting the Digital Signatures
tab which lists the digital signatures on the file. The details of a signature can be verified by highlighting a
signature in the list and then clicking the Details button. This will allow a verification that the binary files
delivered have digital signatures from Siemens and have not been subject to tampering.
The installation files, executables (*.exe), MSI files (*.msi), cabinet files (*.cab) and MSI transform files
(*.mst), are all digitally signed by Siemens. Some other binary files and executables on the installation
media may be digitally signed by other providers, such as Microsoft.

Release Frequency
Beginning with NX January 2019 release, the frequency of releases will be increased. Most releases after
January 2019 for NX will be distributed as full installations which can be used to install a full, new
installation, or upgrade a previous NX installation (from releases beginning with January 2019).
This installation guide describes the procedure for new installations and upgrade installations. The
upgrade installation will not be available until the next release of NX after the first functional release.

Functional Product Releases

Beginning with the June 2019 release (1872), NX will have functional product releases that will install to a
separate location than the previous functional release (January 2019). Functional releases are releases
where NX Open functionality may change and new prerequisites may be needed to run NX.
Functional releases will be released on a six month cadence and each functional release will have its own
set of monthly release updates for the 5 months following the functional release. Every functional release
will not require new prerequisites if no prerequisite changes are made to allow NX to run properly.
The first functional release of each family will only be released as a full installation on GTAC as there is no
previous release in the same family to which to perform an upgrade only install.
The monthly updates will continue to be released as full installation which can be used to install a full
install without having a previous release of NX installed or an upgrade to an existing NX installation of the
same functional release family (functional release plus its monthly updates). Patch only installations will
also be made available for each monthly release after a functional so that upgrading from an installed NX
 9

to a following monthly release can be done with a smaller download file and a faster installation process.
It is not required to install the first functional release of each functional release family to install a
subsequent monthly version of NX. For example, if you skip the June and July releases of NX, you can
install the August 2019 release as a full installation to begin using NX at the August version. After
installing the August release, you can then use either full September install or the September update only
installation to upgrade your August product version to the September product version.

Functional Releases and Associated Monthly Releases

NX is released as a new functional release every 6 months with update monthly releases each month after
as mentioned in Functional Product Releases above. Below is a chart of the NX functional releases and the
range of numbers identifying the monthly releases for each functional release.

1847 Series December 2019 1851 through 1867

1872 Series June 2020 1876 through 1892

1899 Series December 2020 1903 through 1919

1926 Series June 2020 1930 through 1946

1953 Series December 2020 1957 through 1973

1980 Series June 2021 1984 through 2000

2007 Series December 2021 2011 through 2027

2206 Series June 2022 2206 through 2206.7000

2212 Series December 2022 2212 through 2212.7000

2306 Series June 2023 2306 through 2306.7000

2312 Series December 2023 2312 through 2312.7000

2406 Series June 2024 2406 through 2406.7000

2412 Series December 2024 2412 through 2412.7000

 10

NX Start Menu Changes

Beginning with the June 2019 functional release (1872), the Start Menu for NX will use the same folder name
for every functional release, including the January 2019 release (1847). The new Start Menu starting with the
June 2019 release will have new link names which separates different areas of programs into categories. With
Windows 10, there are no sub-folders in the Start Menu so this change is being done to create a structure that
groups different types of programs together so that they can be located similar to how the sub-folders work in
the Windows 7 Start Menu.

Because the same Start Menu folder will be used for all functional releases, this means that only one version of
NX will have a defined start menu icon for its products. Only one version will have links from the Start Menu
even if multiple versions are installed. The last version installed will take control of the Start Menu links. If you
have an 1872 release or later version installed and afterward you install an 1847 series version, including the
deferred releases for continued support of 1847 series, that version will change the Start Menu links for NX
and other programs to point to the 1847 series.

It is recommended that if you will be installing an older version of NX on a machine with an 1872 or later
version, that you make a copy of the Start Menu links for the current version before installing so that you can
replace them if needed.

The Siemens NX Launcher is as an optional product to use to launch NX applications from any version with the
ability to pre-configure environments. NX Launcher will create its own Start Menu link outside of the NX Start
Menu. More information on the Siemens NX Launcher is available in the NX Help.
 11

Preparing for the Installation

Licensing Configuration Decisions
Use the following criteria to help decide if you need to install the Siemens License Server product on your
local machine.
The Siemens License Server installation is needed for the following configurations:
• The local machine will be a license server on your network. It will provide (serve) licenses to itself or
other machines on your network.
• The local machine is a standalone machine (such as a laptop) that can not receive licenses from another
machine on your network and must serve its own licenses.
The Siemens License Server installation is not needed for the following configurations:
• The local machine receives licenses from another machine on your network (i.e. another machine is the
server and the local machine is a license client).
• The local machine will use “Standalone Licensing” in which NX will acquire licenses directly from a
special “Standalone Node-Locked License” file.
Caution: The “Standalone Node-Locked License” file is a special type of license file that is node
locked to your machine’s Physical address (a.k.a. MAC address, Ethernet address. It is not
the same type of file used by License Servers. A server license file can not be used for
Standalone Licensing.
The latest Siemens License Server server can be installed with the separate Siemens License Server
installation that is obtained from Siemens Support Center (https://support.sw.siemens.com/en-
US/product/1586485382). One license server can serve licenses to many workstations running NX. The
Standalone Node-Locked License file will only provide licenses to your local machine running NX.
NX uses the SPLM_LICENSE_SERVER environment variable. NX versions 5.0 thru 8.5, all use the
UGS_LICENSE_SERVER environment variable. NX 4.0 and earlier versions use UGII_LICENSE_FILE variable.
All three variables may exist on systems running concurrent versions. The default TCP socket for
SPLM_LICENSE_SERVER and UGS_LICENSE_SERVER is 28000, instead of 27000 as previously used in NX 4.0
and earlier releases. Beginning with NX 2212, the default TCP socket for SPLM_LICENSE_SERVER is 29000.
For further information on the licensing installation see the guide Siemens Digital Industries Software
License Server Installation Instructions from the Siemens Support Center Documentation section of the
link above.

Java Runtime Environment

NX is certified to use 64-bit Java Runtime Environment (JRE) 11. The Java Runtime Environment (JRE) is not shipped
with NX. See the Release Notes for a list of products that use Java.
While many Java releases are available from several providers, we recommend that you use only the Long Term
Support (LTS) releases, such as JRE 11, 14, and 17. Any version of Java should work as long as it is equal to or higher
than the certified version. The Java version can be obtained from any Java provider.

Check File System

Window NTFS file system is required for NX and all related products. NX will not work correctly on an old
FAT file system. Please consult your Windows documentation or Help for questions on file systems and
disk partitions.
 12

Check Disk Space

A complete installation of every module of NX requires approximately 38 GB of free space on your disk.
When you run the installation program, it will provide an accurate estimate of the space required and
check that you have the required amount of free space on the target disk.
As the product is updated monthly the size can increase so it is recommended that you estimate an
additional 2 to 3 GB of disk space needed beyond the initial product size estimate above to account for
any potential size increase over time.
If you wish to check that there is enough free space on the target disk before starting the installation, run
File Explorer and right-click on the disk letter that you wish to use and select Properties.

Set Up TCP/IP Network Services

TCP/IP services must be set up and configured for your system. To check this, click on Start→All
apps→Windows System→Control Panel→Network and Internet→Network and Sharing Center→Change
Adapter Settings→Right-click Ethernet→Properties. TCP/IP should be displayed as one of the installed
protocols.
NX uses the TCP/IP network protocol to communicate with the license server. Even if the Siemens License
Server is running on the same computer, TCP/IP is still used.
If your computer does not have an Ethernet Card configured, you must install the Microsoft Loopback
Adapter, which is a "virtual" network adapter that will allow your computer to "talk to itself" via TCP/IP.
You may use the ping utility to check that your TCP/IP connection is operational. On the computer where
you will be running NX, open a Command Prompt window, and type
ping <hostname>
where <hostname> is the name of the computer you will be using as your License Server. If the network
connection is working correctly, several lines of diagnostic output will be displayed, indicating the time
required to transmit packets of data.
If the network connection is not working, you will receive an error message. You must be able to ping
your License Server (and vice versa) in order to run NX. For help with the ping utility, please consult your
Windows documentation or Help.
 13

Installing NX
Please complete all of the pre-installation procedures from the previous sections before starting the
installation.

Installation Features Pre-Selected Based On Previously Installed Release

Starting at NX 2007 when installing with the installer user interface, if you already have a release of NX
installed on your system the installation user interface will automatically pre-select the same installation
features you installed with the previous release. Any new installation features which did not exist in the
previous release will also be selected for installation. If you do not install all features, this will make it
easier for re-selecting the same features from release to release. You will see the new features selected
so you only need to make an install decision on those features if you want to have the same installation
selections as your previous release installation. You can still select and deselect features in the user
interface even if those features are not pre-selected.
Note: This function of the installation only pre-selects based on release of NX 1926 or newer series. If
you have NX 1926 or a later series installed, the installation will pre-select to the newest version
of the previous release installed (e.g. if you have 1926 and 1980 installed, the pre-selections will
be done against what is installed with 1980). This change does not pre-select from installed
releases prior to NX 1926. In the case of having an older release than NX 1926 and no newer
release installed, the features selected in this release will be the default of all features.

Installation Features to Cabinet Files Listing

A listing of the cabinet files needed to install each installation feature is provided in the file
“docs\NX_2412_Features_Cabinet_Files.txt” in the full installation folder after extracting the zip file.
 14

Changes to Add-On Products Features Default Installation Settings

Starting in NX 2212, the Add-On Products default installation settings, whether they will install or not
install by default, have been changed for some add-on product features.
Localization files have been separated from all product features and merged into per-language add-on
optional features for each language. This allows you to install only the language files for NX for the
languages your site will use and reduces the size of the product be not installing language files which
you will not use at your site. The default setting for this is all languages (except English, which is not an
optional language) is to not install. You will need to use the feature selection dialog and choose
languages to install.
The Simcenter Nastran and Programming Tools install features will be set to not install by default if you
do not have a previous version of NX installed on the machine. A previous version installed will
preselect these features based on the install setting for that version. See Installation Features Pre-
Selected Based On Previously Installed Release above for information.

The following NX product functions will not be available when the 3 install features are left off by
default.
1. Functionalities dependent on Simcenter Nastran feature
- NX stress and vibration wizards
- NX Design Simulation
- Simcenter Structures
2. NX cannot be launched in non-english language unless a specific Localization feature is installed
3. Compilation of NXOpen applications may not work as expected when Programming Tools feature is not installed
4. NXOpen Wizards will not be available when Programming Tools feature is not installed

Starting at 2306, Model Based Part Manufacturing is a new feature which does not install by default.

Starting at 2312, the following additional features are not installed by default:
Simcenter 3D Acoustics Solvers
Additive Manufacturing Simulation
Ship Building
Greater China Tools
NX VR

Starting at 2412, the following additional features are not installed by default:
Samcef Solver
Simcenter 3D Thermal Flow
Meshing Services
CFD Designer
 15

Installation Steps
Please use the following instructions to perform the installation:
1. Log onto your workstation, using an account with Administrator privileges.
2. Place the NX DVD into the DVD drive on your system. When the DVD mounts, it will automatically run
the launch program and present the launch screen.
If this "autorun" feature is turned off for your DVD drive, follow the next two steps to start the
launch program.
In File Explorer click on the icon for your DVD drive.
In the top level folder, double-click on the program Launch.exe.
3. Select Install NX from the media Launch screen (if available). {A media launch screen may not be
available, or may be disabled on your system}
OR
Using File Explorer, navigate directly to the nx folder on the DVD drive, and double-click on setup.exe
to start the setup program.
4. Select the language in which to run the setup.exe program. This will be the user interface language for
the installation program and does not determine the runtime language of NX.
The setup.exe program, in addition to starting the NX installation, will install prerequisite software
products if the local machine does not already have them or a newer version installed:
- Microsoft Visual C++ 2015-2022 runtime redistributable (14.40.33810.0)
- Microsoft .NET 4.8 Framework (4.8.4115.00)
- Microsoft .NET Windows desktop runtime 6.0.35 (6.0.35.34113)
- Microsoft .NET Windows desktop runtime 8.0.11 (8.0.11.34221)
- Microsoft ASP.NET Core runtime 6.0.35 (6.0.35.24462)
- Microsoft ASP.NET Core runtime 8.0.11 (8.0.11.24521)
If the machine already has all of these software products, the NX installation will start immediately
when running setup.exe.
If the local machine does not have one or any of the prerequisite software products, the setup.exe will
run their installation program(s) from Microsoft to attempt to silently install the products to the
machine. However, depending on your UAC settings, the installers for these products may pop-up a
request to install on the system. You should accept the request so that the prerequisite software is
installed.
Note: If your machine has a higher version of any of the prerequisites already installed, the setup.exe
will not attempt to install the older prerequisite. The prerequisites supplied are the minimum
required, newer versions already installed on machines will be used if they already exist.
If you prefer to install the prerequisite software separately before installing NX, you will find the .NET
4.8 Framework installer (ndp48-x86-x64-allos-enu.exe), .NET Windows desktop runtime 6.0.35
(windowsdesktop-runtime-6.0.35-win-x64.exe), .NET Windows desktop runtime 8.0.11
(windowsdesktop-runtime-8.0.11-win-x64.exe), ASP.NET Core runtime 6.0.35 (aspnetcore-runtime-
6.0.35-win-x64.exe), ASP.NET Core runtime 8.0.11 (aspnetcore-runtime-8.0.11-win-x64.exe) and Visual
C++ redistributable installer (VC_redist.x64.exe) in the nx folder with the setup.exe program.
 16

5. At the Welcome dialog, click Next to continue. Clicking on the Cancel button at any time during the
installation will discontinue (and roll back) the installation.
6. Custom Setup – By default, if you do not have a previous version of NX installed, all install features
are selected for installation to local hard drive, which is the same as the Typical setup from
previous releases. If you have a previous release as mentioned in the section above, Installation
Features Pre-Selected Based On Previously Installed Version, the features selected will match
your previous version installed features plus any new features that did not exist previously. The
NX Platform feature (and the Model-Based Definition feature in NX 2007) is/are required and can
not be changed to not install. Any of the other Add-on products can be set to install or not install
to local disk based on the feature selection drop down to the left of the feature name in the
scrolling box. Click on the drop down and you will be given three options:

1. Will be installed on local hard drive – select this to install the feature to the destination
path.
2. Entire feature will be installed on local hard drive – same as “Will be installed on local
hard drive” except for the Add-on products selection. For Add-on products, this will allow you
to select all subfeatures to install to local disk without having the set each feature separately.
3. Entire feature will be unavailable – sets the feature to not install to disk. During
maintenance mode, changing from “Will be installed on local hard drive” to “Entire feature will
be unavailable” will remove files for the feature from your hard drive. Selecting “Entire feature
will be unavailable” on the Add-on products feature will set all subfeatures to be unavailable on
hard drive.
Click the Browse button to change the destination location or accept the default directory path
provided. The installation will create the directory if it does not exist.
7. Licensing - Enter the name of a license server, a list of license servers or a path to a single
“Standalone Node-Locked License” file. The installation will only support (1) of these options.
• Server name(s) are machine(s) that supply licensing information for running NX. This may or
may not include the hostname of your local node (the computer running this installation). The
hostname(s) of the license server(s) should be entered in the form "<port>@<hostname>"
(where <port> is the TCP port on which the Siemens License Server service runs on the license
server; usually this will be 29000).
• License file is a path to a single “Standalone Node-Locked License” file that NX will read to
acquire license information. A “Standalone Node-Locked License” file is a special license file
that is node locked to your machine’s physical address. It is not the same type of file used by
License Servers. The installation dialog provides a “Browse” button to allow users to navigate
to their license file.
The answer to this dialog will be used to set the SPLM_LICENSE_SERVER environment variable on your
system. This environment variable may be changed at any time by the Administrator.
Note: If you are installing before your license server is set up or you are off the network and there is
no connection to the license server, you can bypass this form by entering “29000@LocalHost” as the
license server and then change the SPLM_LICENSE_SERVER environment variable manually after you
have installed NX and your license server is set up and running.
8. Software Configuration - Select the runtime language for NX. In the language selection screen you
may choose the language to be used by NX at runtime, to present menus and text. This selection
will set the UGII_LANG environment variable which may be easily changed at a later time or set
differently for different users.
(New starting with 2312) If you select Programming Tools to install and you have a supported
 17

Visual Studio version installed on the same machine, there will be a check box shown on the
Software Configuration dialog to allow for the selection to install the NX Open Visual Studio
extensions during the installation of NX. Leave the check box unchecked if you do not want the
extensions to install, check the box to install the extensions. If you do not see this option on the
dialog it means you either did not select Programming Tools to install or you do not have a
supported version of Visual Studio installed. If you choose not to install the extensions during
installation you can run the extensions VSIX installers manually after installation from the
UGOPEN\NXOpenWizard subfolders. Double-click the vsix file in each subfolder to install the
extensions.
9. Ready to Install - The final dialog is the Setup Confirmation screen. Verify your installation selections
before proceeding to the file copy sequence. To change any settings, use the Back button to navigate
back to the appropriate installation dialog. Click Install to begin the installation.

Upon the completion of the file copy process, the installation procedure will configure NX to run on this
machine. At the conclusion of the installation, NX will be ready to run and selectable from the Start Menu
(shown as Siemens NX->NX in the Start Menu).

The installation automatically generates a log file in the %TEMP% folder. The file is named MSI*.LOG
where * is a series of numbers and characters which make the filename unique in the %TEMP% folder.
After installation, you can view this log file by selecting the “Show the Windows Log” check box before
closing the installation program or opening the file in the %TEMP% folder.
 18

Installation Feature Contents

Installation features are a combination of different NX folders required for running the product. Some
features have common NX folders. These folders are only installed once and will exist on the system as
long as one of the install features are installed. The Install Feature is the name of the feature you would
use during automated installation. The Displayed Name is the name (will be translated for some
languages) of the install feature that is displayed in the installation program
The NXBIN directory, is created on all platforms at the %UGII_BASE_DIR%\nxbin location during the NX
installation. Executables and libraries from the user selected installed kits are consolidated into the NXBIN
directory during the installation. NXBIN is not listed below as it is a combination of many install folders.
The folders included in each installation feature are listed below.
In this table the features with ** next to their names are not installed by default in a new installation. All other
features are set to be installed by default.
Install Feature Displayed Name NX Folders
Required feature(s):
FEAT_NXPLATFORM NX Platform INSTALL, CLOUDDM, DIAGRAMCORE,
LOCALIZATION, NXASSEMBLY,
NXHUMAN, NXPARTS, NXPLOT, NXVR,
PVTRANS, REL_INFO, RULE, UGFLEXLM
(moved in 2312), UGII, UGMANAGER,
UGTIPS, UGWEB, AUTOMATIC_UPDATE,
BLOCK_STYLER, MBD, TDP (moved in
2212)
FEAT_UGFLEXLM (hidden) – not displayed UGFLEXLM (new in 2312)
FEAT_MODEL_BASED_DEFINITION Model Based Definition MBD, TDP (moved to
(required beginning with NX 2007) FEAT_NXPLATFORM in 2212)
(merged with FEAT_NXPLATFORM in NX
2212, will not appear on dialog in 2212
and should not be used for silent
installation ADDLOCAL option (error
2711 will occur))
Optional install features (Add-on products):
FEAT_ADDMANSIM ** Additive Manufacturing AM_SIMULATION, COMPOSITES,
Simulation MACH, NXCAE_EXTRAS, SIMULATION,
UGSTRUCTURES, DESIGN_TOOLS
FEAT_AUTOMATED_TESTING_STUDIO Automated Testing Studio AUTOMATED_TESTING
FEAT_AUTOMOTIVE Automotive UGAUTOMOTIVE, UGWELD,
MOLDWIZARD, STAMPING_TOOLS,
NXREPORTS, TOOLING_BASE,
DESIGN_TOOLS, VDV, VDA
FEAT_CFDD ** CFD Designer CFD_DESIGNER
FEAT_COMPOSITES Composites COMPOSITES, DXFDWG
FEAT_DIAGRAMMING Diagramming DIAGRAMMING
FEAT_DRAFTING Drafting DRAFTING, NX2DEDIT
FEAT_ECLASS_NX_AUTHOR NX Author for ECLASS ECLASS_STANDARD
FEAT_FABRICMODELER Fabric Modeler FABRICMODELER
FEAT_GREATERCHINATOOLS ** Greater China Tools GCTOOLKIT
FEAT_IMMERSIVE Immersive IMMERSIVEEXPERIENCE
 19

FEAT_INDUSTRIAL_ELECTRICAL_DESIGN Industrial Electrial Design AUTOMATION_DESIGNER

(was Automation
Designer)
FEAT_MANUFACTURING Manufacturing CMM_INSPECTION, MACH, MBD,
NX_VSA, POSTBUILD, PSTUDIO,
STAGE_MODEL, UNFOLD
FEAT_MANUFACTURING_PLANNING Manufacturing Planning MANUFACTURING_PLANNING
FEAT_MECHATRONICS Mechatronics Concept MECHATRONICS
Designer
FEAT_MESHINGSRV ** Meshing Services MESHING_SERVICES
FEAT_MODEL_BASED_DEFINITION Model Based Definition MBD, TDP
(optional prior to NX 2007, no longer an
install feature, do not use after 2007)
FEAT_MODELBASEDPARTMANUFACTURING Model Based Part PARTMFG, DOCUMENT,
** Manufacturing DIAGRAMMING
FEAT_MOLDED_PART_DESIGN Molded Part Design PLASTIC_DESIGNER
FEAT_NXACOUSTICS ** Simcenter 3D Acoustics ACOUSTICS
Solvers
FEAT_NXNASTRAN ** Simcenter Nastran NXNASTRAN
FEAT_NXREPORTING NX Reporting MENDIXREPORTING
FEAT_NXTMG ** Simcenter 3D Thermal THERMALFLOW
Flow
FEAT_NXVR ** (no longer an install NX VR NXVR
feature starting at 2406)
FEAT_OPTIMIZATION_TOOLS Optimization Tools DESIGNSPACEEXPLORER
FEAT_PROGRAMMING_TOOLS ** Programming Tools UGOPEN, UGOPENPP, UGALLIANCE
FEAT_ROUTING Routing ROUTING, CAPITALINTEGRATION
FEAT_SAMCEF ** Samcef Solver SAMCEF_SOLVER
FEAT_SHIP_BUILDING ** Ship Building NXSHIP, NXCABLEROUTER
FEAT_SIMULATION Simulation SIMULATION, MECH, MOLDCOOLING,
NXCAE_EXTRAS, SAFETY,
UGSTRUCTURES, UGPCBXCHANGE,
UGPCBX, UGFPCD, COMPOSITES
FEAT_STUDIO_RENDER Studio Render UGSTUDIO, UGPHOTO
FEAT_TOOLING_DESIGN Tooling Design UGAUTOMOTIVE, UGWELD,
MOLDWIZARD, STAMPING_TOOLS,
TOOLING_BASE, NXREPORTS,
DESIGN_TOOLS, NXJOIN,
NXSTRUCTUREDESIGN, NXCOATINGS,
NXAECDESIGN
FEAT_TRANSLATORS Translators CATIAV5, DXFDWG, IGES, NXPROE,
NXCREO, STEP203UG, STEP214UG,
UGCATIA, UGTO2D, UGIMW,
TRANSLATORS
FEAT_VALIDATION Validation NXREPORTS, DESIGN_TOOLS, MPA
 20

Using the Maintenance Options

After completing an installation, any subsequent executions of setup.exe will present the ‘Maintenance’
screen. This prompt will offer the option to ‘Change’, ‘Repair’ or ‘Remove’ the installation of the product.
The Change option will allow the installer to add or remove installed features of the NX release. For
example if you wish to add a product that was not previously installed, use the Change option to add the
product. The Change option will also allow the installer to change the license server or runtime language
settings
Note: This option will also uninstall products that are not selected. Any previously installed products
you do not wish to remove must all be re-selected for installation. If they are already installed,
they will not be reinstalled. However, if they are not selected, they will be uninstalled.

The Repair option will attempt to reinstall or correct any files that do not match the original installation.
Note: This option compares checksums for thousands of NX files so it takes a very long time to
complete.
The Remove option will uninstall the product completely.
 21

Running NX
Java Runtime Environment
The Java Runtime Environment (JRE) is not shipped with NX, but NX does require JRE for certain products. Please
see the NX Release Notes for more information about which Java implementations and versions are
supported for use with NX.

Running NX from the Start Menu

The NX installation program creates a new item in the Programs section of your Start Menu:
To run NX, choose:
Start→All apps→Siemens NX→NX
The NX splash screen will appear, followed by the NX window. Startup should take somewhere between a
few seconds and a couple of minutes, depending on the speed of your computer and your network. If it
takes longer than this, you should consult Troubleshooting to try to diagnose the problem.

Running NX by Double-Clicking
You can also run NX by double-clicking on an NX part (.prt) file.
The NX installation option will establish a filename association between part files and the latest version of
NX installed. Double-clicking a .prt file should work correctly unless the association has been changed by
other applications or removed by an uninstallation of (another version of) NX. The cleanest and fastest
way to reestablish this filename association is to:
1. Uninstall desired version of NX
2. Reinstall desired version of NX

Running Multiple Versions of NX

The following section no longer applies to NX as a requirement to have two functional releases side-by-side as
functional releases will be released having separate installation locations. This information describes how to
run the administrative installation of the product to set up a separate installation environment.
This information can still be used to install a monthly release to a functional release in a separate location for
testing, if desired, before installing the monthly release as an upgrade to the existing functional release series.
Running multiple versions of NX with the following method is supported for versions prior to January 2019 and
one version of each functional release series of NX after January 2019. To run multiple versions of NX within a
functional release series released after January 2019, see the Installing NX for Parallel Product Testing section.
To provide the ability to run several versions of NX on a single system, do the following:
1. Install all of the desired NX versions on the system, using instructions in the Installation Guide for
the appropriate version. The install procedures will create a different entry on your Start Menu
for each version. You should install multiple versions in the order of oldest to latest. For
instance; install the oldest Base & Options, then any Maintenance Release (a.k.a. MR) for that
base release. Then install the next higher version in that order, finally ending with the latest
release or last MR.
2. If you are running multiple versions of NX, which include versions prior to NX 5.0, you will require
both the NX 4.0 and the current NX versions of the license file and service. The license file and
 22

service installed with NX support 5.0 through current, but they are not backward compatible with
NX 4.0 and earlier versions.

Note: To run NX 4.0 or earlier, you must continue to run the NX 4.0 (uglmd) service.
 23

Automatic Installation of NX
The installation of NX can also be accomplished by an automatic, unattended install. This feature may aid
those System Administrators with a large number of site installations.
Caution: Use of this type of installation is intended for experienced installers only.
The setup.exe program installs the two prerequisite software products for NX prior to installing NX. It is
recommended that the setup.exe program be used to run the automatic installation to install the prerequisite
software or install the prerequisite software using their installation programs prior to performing the
automatic installation of NX.
The setup.exe program is used to launch the unattended installation in addition to running unattended
installations of the prerequisite software. Command line switches for setup.exe are used to pass values to
the msiexec.exe program.
The unattended installation is controlled by the Windows system component, msiexec.exe. In order to
install silently you must pass switches and NX specific configurable properties to msiexec.exe on the
command line. The msiexec.exe program has several command line switches. For full documentation on
these switches, see the Microsoft help documentation “Help and Support” for msiexec.
There are a few command line switches for the setup.exe program which can be used:
/h – setup.exe help, lists available switches.
/s – run setup.exe silently without any dialogs.
/a – perform an administrative installation.
/w – setup.exe waits for the msiexec.exe command to complete before closing.
Use the /w option on setup.exe when running the program from inside a script or when using an software
configuration management system, like SCCM. This option causes the program to wait until the
msiexec.exe process completes before exiting the setup.exe and proceeding to the next step in the
script/software configuration process. This option will not cause setup.exe to wait in a regular command
prompt, it will only wait when setup.exe is called from inside another script or software configuration
management system.
/v – pass parameters to the msiexec.exe program.
Parameters for msiexec.exe must be immediately following /v and may be optionally wrapped in quotes.
You can pass multiple parameters with one /v option. If any parameters passed require spaces, e.g.
C:\Program Files, you must pass the parameter with escaped quotation marks, e.g. \"C:\Program Files\".
The parameters passed with the /v option are set to the msiexec.exe program as command line switches.
A few of the commonly used msiexec.exe command line switches are:
/h – msiexec help, will list available switches.
/q – specifies the UI level. /qn+ specifies no dialogs except for the ending "install done" dialog
{recommended}. /qn specifies a silent installation with no dialogs. If this option is used there is no
indication when the install completes, you must use the Task manager to monitor the "msiexec.exe".
/L – specifies a logfile to be created, and the level of the messages to be written to the logfile {e.g.
msiexec /L*v "logfile"}. This example gives the most verbose log file; see msiexec switches for various log
switch options.
/i - specifies the msi file use for installation {e.g., msiexec.exe /i SiemensNX.msi}.
/x- specifies the msi file use for uninstallation {e.g., msiexec.exe /x SiemensNX.msi}.
 24

The configurable properties for the NX install are:

LICENSESERVER This property sets the value of the NX license server. It will default to the
value of the SPLM_LICENSE_SERVER environment variable (if it is set from a
previous installation) or 29000@<localhost> where <localhost> is your
workstation name.
LANGUAGE This property sets the value of the user interface language for NX. Valid
choices are german, french, spanish, english, italian, japanese, korean,
russian, simpl_chinese, trad_chinese, braz_portuguese, czech and polish.
The default value of this property is english (all lowercase). Beginning in
2212, this also sets an additional language to install along with English.
INSTALLDIR This property sets the directory where NX will be installed. If not specified
this will default to "C:\Program Files\Siemens\NX[series]". [series] is the first
release number of the NX series which is being installed.
ADDLOCAL This property selects the features to be installed. Using ADDLOCAL=ALL will
install all the features.

TRANSFORMS This property sets the installation user interface language transform (.mst)
and the language used to create the Start Menu links. Valid choices are cs-
cz.mst, de-de.mst, es-es.mst, fr-fr.mst, it-it.mst, ja-jp.mst, ko-kr.mst, pl-
pl.mst, pt-br.mst, ru-ru.mst, zh-cn.mst, zh-tw.mst.
TARGETDIR This property sets the directory where an NX administrative installation will
be placed. This property is for administrative installations only. See
Installing NX for Parallel Product Testing for more information.
NXOPEN_EXTENSIONS This property is new beginning wth 2312. This property works in conjunction
with the installation of the FEAT_PROGRAMMING_TOOLS feature. If you
install the Programming Tools and you have a supported Visual Studio
version installed, this property defines whether the installation program will
install the NX Open VSIX extensions to Visual Studio on the installation
system. Set this property to 1 (NXOPEN_EXTENSIONS=1) if you want the
installation automatically install the VSIX extension to Visual Studio (if it is
installed) and do not set the property if you do not want VSIX extensions to
be installed during installation.
If you are doing a full installation then you must specify ADDLOCAL=ALL. If ADDLOCAL is not specified on
the command, it is the same as ADDLOCAL="FEAT_NXPLATFORM" only.
("FEAT_NXPLATFORM,FEAT_MODEL_BASED_DEFINITION" prior to NX 2212)
Starting in NX 2312**, FEAT_NXPLATFORM does not include FEAT_UGFLEXLM, you need to include both
FEAT_NXPLATFORM and FEAT_UGFLEXLM in ADDLOCAL if not using ADDLOCAL=ALL. Use
ADDLOCAL=”FEAT_NXPLATFORM,FEAT_UGFLEXLM”.
** Note: The need to include FEAT_UGFLEXLM with FEAT_NXPLATFORM is no longer needed starting in
2406. ADDLOCAL=”FEAT_NXPLATFORM” will install both FEAT_NXPLATFORM and FEAT_UGFLEXLM
beginning in 2406.
The remaining selectable install features for a custom install are:

FEAT_ADDMANSIM FEAT_MODELBASEDPARTMANUFACTURING
FEAT_AUTOMATED_TESTING_STUDIO FEAT_MOLDED_PART_DESIGN
FEAT_AUTOMOTIVE FEAT_NXACOUSTICS
FEAT_CFDD FEAT_NXREPORTING
FEAT_COMPOSITES FEAT_NXNASTRAN
 25

FEAT_DIAGRAMMING FEAT_NXTMG
FEAT_DRAFTING FEAT_OPTIMIZATION_TOOLS
FEAT_ECLASS_NX_AUTHOR FEAT_PROGRAMMING_TOOLS
FEAT_FABRICMODELER FEAT_ROUTING
FEAT_GREATERCHINATOOLS FEAT_SAMCEF
FEAT_IMMERSIVE FEAT_SHIP_BUILDING
FEAT_INDUSTRIAL_ELECTRICAL_DESIGN FEAT_SIMULATION
FEAT_MANUFACTURING FEAT_STUDIO_RENDER
FEAT_MANUFACTURING_PLANNING FEAT_TOOLING_DESIGN
FEAT_MECHATRONICS FEAT_TRANSLATORS
FEAT_MESHINGSRV FEAT_VALIDATION
The following install language files for each language:

FEAT_BRAZ_PORTUGUESE FEAT_KOREAN
FEAT_CZECH FEAT_POLISH
FEAT_FRENCH FEAT_RUSSIAN
FEAT_GERMAN FEAT_SIMPL_CHINESE
FEAT_ITALIAN FEAT_SPANISH
FEAT_JAPANESE FEAT_TRAD_CHINESE

The following are examples of silent installations of NX.

Caution: The setup.exe examples below may appear on multiple lines because of document
formatting but they must be entered on your computer as one line. Arguments with
embedded spaces must be quoted.
This first example installs NX silently, using a full installation, selecting the runtime language to be French,
setting the license server to 29000@myserver, setting the Start Menu language to French (fr-fr.mst), and
using the installation location of F:\Program Files\Siemens\NX. No dialogs are displayed.
setup.exe /s /v"/qn ADDLOCAL=ALL LANGUAGE=french INSTALLDIR=\"F:\Program
Files\Siemens\NX\" LICENSESERVER=29000@myserver TRANSFORMS=fr-fr.mst"
This next example installs NX silently selecting five features to be installed. The installation is done to
E:\Program Files\Siemens\NX, the runtime language is defaulted to English, and the license server is
specifically set to 29000@xyz. No dialogs are displayed.
setup.exe /s /v"/qn ADDLOCAL=\"FEAT_NXPLATFORM,FEAT_AUTOMOTIVE,
FEAT_TRANSLATORS,FEAT_DRAFTING\" INSTALLDIR=\"E:\Program Files\Siemens\NX\"
LICENSESERVER=29000@xyz"
This example installs NX silently. The installation is done to E:\Program Files\Siemens\NX, the runtime
language is defaulted to English, and the license server is specifically set to 29000@xyz. In addition a
verbose (*v) log file is generated to C:\temp\install.log. The "/qn+" switch will cause an ending message
dialog to appear.
setup.exe /s /v"/qn+ /L*v C:\temp\install.log ADDLOCAL=ALL
INSTALLDIR=\"E:\Program Files\Siemens\NX\" LICENSESERVER=29000@xyz"
 26

This example installs NX silently. The installation is done to E:\ Siemens\NX, the runtime language is set
to Japanese, and the license server is specifically set to 29000@abc. The setup.exe wait switch (/w) is
used to keep the setup.exe from closing until the msiexec.exe program completes the installation. Use
the /w option when putting commands in a script where you need to wait until the installation is
complete before performing the next command. At a command prompt, the setup.exe will return to the
command prompt. In a batch script, running setup.exe /w will wait until setup.exe exits before the next
batch command is executed.
setup.exe /s /w /v"/qn ADDLOCAL=ALL LANGUAGE=japanese INSTALLDIR=E:\Siemens\NX
LICENSESERVER=29000@abc"
This example installs NX silently selecting four features to be installed. The installation is done to E:\
Siemens\NX, the runtime language is set to Japanese, the Japanese language files are installed for the four
features selected, and the license server is specifically set to 29000@abc. The setup.exe wait switch (/w)
is used to keep the setup.exe from closing until the msiexec.exe program completes the installation. Use
the /w option when putting commands in a script where you need to wait until the installation is
complete before performing the next command. At a command prompt, the setup.exe will return to the
command prompt. In a batch script, running setup.exe /w will wait until setup.exe exits before the next
batch command is executed.
setup.exe /s /w /v"/qn
ADDLOCAL=\"FEAT_NXPLATFORM,FEAT_AUTOMATED_TESTING_STUDIO,
FEAT_TRANSLATORS,FEAT_DRAFTING\" LANGUAGE=japanese INSTALLDIR=E:\Siemens\NX
LICENSESERVER=29000@abc"
This next example installs NX silently selecting five features and two additional language features (French
and German) to be installed. The installation is done to E:\Program Files\Siemens\NX, the runtime
language is defaulted to English, and the license server is specifically set to 29000@xyz. No dialogs are
displayed.
setup.exe /s /v"/qn ADDLOCAL=\"FEAT_NXPLATFORM,FEAT_AUTOMATED_TESTING_STUDIO,
FEAT_TRANSLATORS,FEAT_DRAFTING,FEAT_FRENCH,FEAT_GERMAN\"
INSTALLDIR=\"E:\Program Files\Siemens\NX\" LICENSESERVER=29000@xyz"
This example installs NX silently selecting all features which installs all features including all language
features. In addition, the NXOPEN_EXTENSIONS property is set to 1 to have the install run the VSIX
installations for the NX Open extensions to Visual Studio (if Visual Studio is installed). The installation is
done to E:\apps\Siemens\NX, the runtime language is defaulted to Japanese, and the license server is
specifically set to 29000@xyz. No dialogs are displayed.
setup.exe /s /v"/qn ADDLOCAL=ALL NXOPEN_EXTENSIONS=1
INSTALLDIR=\"E:\apps\Siemens\NX\" LANGUAGE=japanese LICENSESERVER=29000@xyz"
This last example performs a silent administrative installation of NX to the D:\Admin folder. The
administrative installation requires the TARGETDIR property and not the INSTALLDIR property. No other
properties are used by the administrative installation. See Installing NX for Parallel Product Testing for
more information about using an administrative installation.
setup.exe /s /a /v"/qn TARGETDIR=\"D:\Admin\""
 27

Installing NX as an Upgrade
The following section applies to monthly updates after the first functional release has been installed. For
example, if you install the June 2022 functional release, then the monthly update in July to that version can be
done as an upgrade installation as shown in this section.

Upgrade Installation Using MSI

To install NX as an upgrade to a previous NX version using the full MSI installation, follow these steps:
1. Log onto your workstation, using an account with Administrator privileges.
2. Place the NX DVD into the DVD drive on your system. When the DVD mounts, it will automatically run
the launch program and present the launch screen.
If this "autorun" feature is turned off for your DVD drive, follow the next two steps to start the
launch program.
In File Explorer click on the icon for your DVD drive.
In the top level folder, right-click on the program Launch.exe.
3. Select Install NX from the media Launch screen (if available). {A media launch screen may not be
available, or may be disabled on your system}
OR

Using File Explorer, navigate directly to the nx folder on the DVD drive, and right-click on setup.exe
to start the setup program.
4. A dialog stating: “This setup will perform an upgrade of ‘Siemens NX’ Do you want to continue?” will
be shown. Click Yes.
5. At the Welcome dialog, click Next to continue.
6. Click Install to begin to upgrade NX. Clicking on the Cancel button at any time during the installation
will discontinue (and roll back) the installation.

Automatic Installation of NX as an Upgrade Using MSI

The MSI installation of NX as an upgrade can also be accomplished by an automatic, unattended install.
This feature may aid those System Administrators with a large number of site installations.
Caution: Use of this type of installation is intended for experienced installers only.
Performing an unattended upgrade installation can be done with the command line:
setup.exe /s /v"/qn /L*v C:\temp\upgrade.log REINSTALL=ALL REINSTALLMODE=vomus"
This will update installed files in the NX environment to the new NX version of the files.
Note: if putting the command into a script for running, add a “/w” option to the setup.exe command to cause
the command to wait for completion before exiting.
setup.exe /s /w /v"/qn /L*v C:\temp\upgrade.log REINSTALL=ALL
REINSTALLMODE=vomus"
 28

Upgrade Installation Using MSP

To install NX as an upgrade to a previous NX version using the patch MSP installation, follow these steps:
1. Log onto your workstation, using an account with Administrator privileges.
2. In File Explorer locate the location to which you saved the downloaded upgrade MSP zip file from GTAC.
3. Extract the MSP zip file.
4. Double-click on the program setup.exe program in the extracted location to begin the installation.
5. A dialog stating: “This setup will perform an upgrade of ‘Siemens NX’ Do you want to continue?” will
be shown. Click Yes.
Note: Prior to 1980 Series, the following two steps were part of the update process with MSP. From
1980 Series and after, these steps are no longer used. For 1980 and later, the install of the update
will begin immediately after selecting Yes to upgrade the software. This change eliminates two
extra button presses.
6. On the Welcome screen, click Next.
7. Click Update to begin to upgrade NX.

Clicking on the Cancel button at any time during the installation will discontinue (and roll back) the
installation.

Automatic Installation of NX as an Upgrade Using MSP

The MSP installation of NX as an upgrade can also be accomplished by an automatic, unattended install.
This feature may aid those System Administrators with a large number of site installations.
Caution: Use of this type of installation is intended for experienced installers only.
Performing an unattended upgrade installation can be done with the command line:
setup.exe /s /v"/qn /L*v C:\temp\upgrade.log"
setup.exe in this command is the setup.exe included with the msp files in the downloaded zip file.
Note: if putting the command into a script for running, add a “/w” option to the setup.exe command to cause
the command to wait for completion before exiting.
setup.exe /s /w /v"/qn /L*v C:\temp\upgrade.log"
This will update installed files in the NX environment to the new NX version of the files.
 29

Installing NX for Parallel Product Testing

Because the NX installation will upgrade any previously installed version of NX (January 2019 and newer)
you must perform an administrative installation to put a newer version of NX on the system without
upgrading your existing installation.
Note: This type of installation will not configure NX for execution. It will not modify or add registry
entries or change the SPLM_LICENSE_SERVER and UGII_LANG environment variables.
Installing the administrative installation will allow you to run NX using the same environment
variables as your existing installation but does not affect the settings of the existing
installation.
Note: This type of installation can not be done into the %SystemDrive%:\Program Files folder.

Administrative (Parallel) Installation

To install NX for parallel product testing follow these steps:

1. Log onto your workstation, using an account with Administrator privileges.
2. Place the NX DVD into the DVD drive on your system. When the DVD mounts, it will automatically run
the launch program and present the launch screen.
If this "autorun" feature is turned off for your DVD drive, follow the next two steps to start the
setup.exe program.
Exit the Launch.exe program if it starts.
3. Using a Command Prompt window, change folder directly to the nx folder on the DVD drive, and run
setup.exe with the command:
setup.exe /a
4. At the Welcome dialog, click Next to continue. Clicking on the Cancel button at any time during the
installation will discontinue (and roll back) the installation.
5. Network Location – Set the location to put the administrative installation of NX for use in parallel
product testing. Enter a network location in the field or click Change… to select a location.
Click Install to begin the installation.
NX will be put in the following folder structure under the location defined as the network location:
Siemens\NX\[kits] – this is the installed location of the parallel NX on the system
System64 – contains files which would be installed to the system folders if this were a standard
installation, these can be ignored in this environment as these files were previously installed with the
prior complete installation of NX.
The system environment variables UGII_LANG and SPLM_LICENSE_SERVER will remain the same values as they
were when NX was previously installed for the version which is managed by MSI and available on Start menu.
This version can use those same variables when running. The UGII_BASE_DIR environment variable is set to
point to the existing version of NX and not this administrative install version. You MUST set the
UGII_BASE_DIR to point to this administrative version of NX when running.

Upgrading the Parallel Installation with an MSP file

 30

The MSP files provided as an upgrade only installation can be used to update the parallel installation location
with updated files.

Note: The parallel installation must be in the same format that it was originally dumped to disk with the
SiemensNX.msi file at the top level and the Siemens\NX folder still existing. E.g. E:\Parallel was the
original installation location and E:\Parallel\SiemensNX.msi and E:\Parallel\Siemens\NX exist.

To update a parallel installation (administrative install) location with an MSP file, do the following:

1. Log onto your workstation, using an account with Administrator privileges.

2. Open a Command Prompt window and change the folder to the location to where you extracted the
downloaded MSP zip file from GTAC.
3. Update the parallel installation location with the following command. In this example, the parallel
installation is in E:\Parallel and the extracted MSP files are in D:\Downloads. The below command line
is all one line, not separate lines.
Note: The names of the MSP files will be the names created during the extraction of the zip file.
msiexec.exe /a E:\Parallel\SiemensNX.msi /p
D:\Downloads\SiemensNX1.msp;D:\Downloads\SiemensNX2.msp;D:\Downloads\SiemensN
X3.msp
Look in the folder where the MSP files were extract and include all of the MSP file names in the folder in
order of numbers, separated by semi-colons, on the command line.
This will update any changed existing files, add new files, and convert removed files to empty files in the
parallel installation location. This will allow NX to run like it would in a regular installation.

Running the Parallel Installation (Administrative Install)

To run the parallel installation, you must use a command prompt and run NX at the command line.
1. Open a Command Prompt window.
2. Set the UGII_BASE_DIR variable to point to NX. If the network location of the parallel install was
E:\Parallel, then set UGII_BASE_DIR to E:\Parallel\Siemens\NX.
set UGII_BASE_DIR=E:\Parallel\Siemens\NX
3. Verify the UGII_LANG and SPLM_LICENSE_SERVER variables are as expected.
4. Use set UGII_LANG and set SPLM_LICENSE_SERVER to check the values. Set to new values if needed.
5. Run NX:
"%UGII_BASE_DIR%\nxbin\ugraf.exe" –nx

Removing the Administrative (Parallel) Installation

Since the administrative installation does not create any registry entries or modify environment variables,
to remove the administrative installation you only need to delete the files and folders from the workstation.
Use Windows Explorer and remove all the files and folders under the location used to install the
administrative installation.
 31

Installing Siemens NX Launcher

The Siemens NX Launcher installation is on a separate button on the Launch.exe program.

Siemens NX Launcher Installation Steps

Please use the following instructions to perform the installation:
1. Log onto your workstation, using an account with Administrator privileges.
2. Place the NX DVD into the DVD drive on your system. When the DVD mounts, it will automatically run
the launch program and present the launch screen.
If this "autorun" feature is turned off for your DVD drive, follow the next two steps to start the
launch program.
In File Explorer click on the icon for your DVD drive.
In the top level folder, right-click on the program Launch.exe.
3. Select Install NX Launcher from the media Launch screen (if available). {A media launch screen may
not be available, or may be disabled on your system}
OR
Using File Explorer, navigate directly to the nxlauncher folder on the DVD drive, and right-click on
setup.exe to start the setup program.
4. At the Welcome dialog, click Next to continue. Clicking on the Cancel button at any time during the
installation will discontinue (and roll back) the installation.
5. Destination Folder – Enter in or use the Change…. Button to select a location on your workstation
to install the NX Launcher program. Click Next to continue.
6. Ready to Install - The final dialog is the Setup Confirmation screen. Verify your installation location
before proceeding to the file copy sequence. To change the installation location, use the Back button
to navigate back to the appropriate installation dialog. Click Install to begin the installation.
Upon the completion of the file copy process, the installation procedure will configure NX Launcher to run on
this machine. At the conclusion of the installation, NX Launcher will be ready to run and selectable from the
Start Menu (shown as Siemens NX Launcher in the Start Menu).
See the product help document, PDF format, in the doc folder in the NX Launcher installation location for
information on configuring NX Launcher to use multiple programs and environments.

Automatic/Silent Installation of Siemens NX Launcher

The installation of NX Launcher can also be accomplished by an automatic, unattended install. This
feature may aid those System Administrators with a large number of site installations.
Caution: Use of this type of installation is intended for experienced installers only.
The setup.exe program is used to launch the unattended installation. Command line switches for
setup.exe are used to pass values to the msiexec.exe program.
The unattended installation is controlled by the Windows system component, msiexec.exe. In order to
install silently you must pass switches and NX Launcher specific configurable properties to msiexec.exe on
the command line. The msiexec.exe program has several command line switches. For full documentation
on these switches, see the Microsoft help documentation “Help and Support” for msiexec.
There are a few command line switches for the setup.exe program which can be used:
 32

/h – setup.exe help, lists available switches.

/s – run setup.exe silently without any dialogs.
/a – perform an administrative installation.
/w – setup.exe waits for the msiexec.exe command to complete before closing.
Use the /w option on setup.exe when running the program from inside a script or when using an software
configuration management system, like SCCM. This option causes the program to wait until the
msiexec.exe process completes before exiting the setup.exe and proceeding to the next step in the
script/software configuration process. This option will not cause setup.exe to wait in a regular command
prompt, it will only wait when setup.exe is called from inside another script or software configuration
management system./v – pass parameters to the msiexec.exe program.
Parameters for msiexec.exe must be immediately following /v and may be optionally wrapped in quotes.
You can pass multiple parameters with one /v option. If any parameters passed require spaces, e.g.
C:\Program Files, you must pass the parameter with escaped quotation marks, e.g. \”C:\Program Files\”.
The parameters passed with the /v option are set to the msiexec.exe program as command line switches.
A few of the commonly used msiexec.exe command line switches are:
/h – msiexec help, will list available switches.
/q – specifies the UI level. /qn+ specifies no dialogs except for the ending “install done” dialog
{recommended}. /qn specifies a silent installation with no dialogs. If this option is used there is no
indication when the install completes, you must use the Task manager to monitor the “msiexec.exe”.
/L – specifies a logfile to be created, and the level of the messages to be written to the logfile {e.g.
msiexec /L*v “logfile”}. This example gives the most verbose log file; see msiexec switches for various log
switch options.
/i - specifies the msi file use for installation {e.g., msiexec.exe /i SiemensNXLauncher.msi}.
/x- specifies the msi file use for uninstallation {e.g., msiexec.exe /x SiemensNXLauncher.msi}.
The only configurable property for the NX Launcher installation is INSTALLDIR. This property sets the
directory where NX Launcher will be installed. If not specified this will default to “C:\Program
Files\Siemens\NXLauncher”.
This first example installs NX Launcher silently using the installation location of
D:\applications\Siemens\NXLauncher. No dialogs are displayed.
setup.exe /s /v"/qn INSTALLDIR=\"D:\applications\Siemens\NXLauncher"\"
This second example installs NX Launcher silently, setting the Start Menu language to French (fr-fr.mst),
using the installation location of D:\application\Siemens\NXLauncher and creates a log file named
nxlauncher_install.log in C:\scratch. No dialogs are displayed.
setup.exe /s /v"/qn INSTALLDIR=\"D:\applications\Siemens\NXLauncher\"
TRANSFORMS=fr-fr.mst /L*v C:\scratch\nxlauncher_install.log"
 33

Mapped Drive Installation

The mapped drive installation has been moved to a separate installation program. The mapped drive
installation is used if you have NX installed on a remote disk on your network and you want to configure your
local machine to run the network mapped NX via the Start menu. Mapped drive installation installs the NX
required fonts; configures the registry settings needed for file associations and registered DLLs; creates the
NX environment variables and creates Start menu shortcuts to run NX. You can not create a mapped drive
installation on the same machine that has NX locally installed except for local administrative installations.

Mapped Drive Installation Steps

Please use the following instructions to perform the installation:
1. Log onto your workstation, using an account with Administrator privileges.
2. Place the NX DVD into the DVD drive on your system. When the DVD mounts, it will automatically run
the launch program and present the launch screen.
If this "autorun" feature is turned off for your DVD drive, follow the next two steps to start the
launch program.
In File Explorer click on the icon for your DVD drive.
In the top level folder, right-click on the program Launch.exe.
3. Select Mapped Drive Installation from the media Launch screen (if available). {A media launch screen
may not be available, or may be disabled on your system}
OR
Using File Explorer, navigate directly to the mapped folder on the DVD drive, and right-click on
setup.exe to start the setup program.
4. Select the language in which to run the setup.exe program. This will be the user interface language for
the installation program and does not determine the runtime language of NX.
The setup.exe program, in addition to starting the NX installation, will install prerequisite software
products if the local machine does not already have them or a newer version installed:
- Microsoft Visual C++ 2015-2022 runtime redistributable (14.40.33810.0)
- Microsoft .NET 4.8 Framework (4.8.4115.00)
- Microsoft .NET Windows desktop runtime 6.0.35 (6.0.35.34113)
- Microsoft .NET Windows desktop runtime 8.0.11 (8.0.11.34221)
- Microsoft ASP.NET Core runtime 6.0.35 (6.0.35.24462)
- Microsoft ASP.NET Core runtime 8.0.11 (8.0.11.24521)
If the machine already has these software products, the NX installation will start immediately when
running setup.exe.
If the local machine does not have one of the prerequisite software products, the setup.exe will run
their installation program(s) from Microsoft to attempt to silently install the products to the machine.
However, depending on your UAC settings, the installers for these products may pop-up a request to
install on the system. You should accept the request so that the prerequisite software is installed.
If you prefer to install the prerequisite software separately before installing NX, you will find the .NET
4.8 Framework installer (ndp48-x86-x64-allos-enu.exe), .NET Windows desktop runtime 6.0.35
 34

(windowsdesktop-runtime-6.0.35-win-x64.exe), .NET Windows desktop runtime 8.0.11

(windowsdesktop-runtime-8.0.11-win-x64.exe), ASP.NET Core runtime 6.0.35 (aspnetcore-runtime-
6.0.35-win-x64.exe), ASP.NET Core runtime 8.0.11 (aspnetcore-runtime-8.0.11-win-x64.exe) and Visual
C++ redistributable installer (VC_redist.x64.exe) in the nx folder with the setup.exe program.
5. At the Welcome dialog, click Next to continue. Clicking on the Cancel button at any time during the
installation will discontinue (and roll back) the installation.
6. Reference Folder – Enter the directory path of the network mapped NX installation
(%UGII_BASE_DIR% folder location). The installation must exist to use it as a reference folder. Click
the Change button to change the reference location.
7. Licensing - Enter the name of a license server, a list of license servers or a path to a single
“Standalone Node-Locked License” file. The installation will only support (1) of these options.
• Server name(s) are machine(s) that supply licensing information for running NX. This may or
may not include the hostname of your local node (the computer running this installation). The
hostname(s) of the license server(s) should be entered in the form "<port>@<hostname>"
(where <port> is the TCP port on which the Siemens License Server service runs on the license
server; usually this will be 29000).
• License file is a path to a single “Standalone Node-Locked License” file that NX will read to
acquire license information. A “Standalone Node-Locked License” file is a special license file
that is node locked to your ethernet address. It is not the same type of file used by License
Servers. The installation dialog provides a “Browse” button to allow users to navigate to their
license file.
The answer to this dialog will be used to set the SPLM_LICENSE_SERVER environment variable on your
system. This environment variable may be changed at any time by the Administrator.
8. Language Selection - Select the runtime language for NX. In the language selection screen you may
choose the language to be used by NX at runtime, to present menus and text. This selection will set
the UGII_LANG environment variable which may be easily changed at a later time or set differently for
different users.
9. Ready to Install - The final dialog is the Setup Confirmation screen. Verify your installation selections
before proceeding to the file copy sequence. To change any settings, use the Back button to navigate
back to the appropriate installation dialog. Click Install to begin the installation.
Upon the completion of the file copy process, the installation procedure will configure NX to run on this
machine. At the conclusion of the installation, the mapped drive NX will be ready to run and selectable
from the Start Menu (shown as Siemens NX (Mapped Drive)->NX in the Start Menu).
The installation automatically generates a log file in the %TEMP% folder. The file is named MSI*.LOG
where * is a series of numbers and characters which make the filename unique in the %TEMP% folder.
After installation, you can view this log file by selecting the “Show the Windows Log” check box before
closing the installation program or opening the file in the %TEMP% folder.
The mapped drive installation is named Siemens NX (Mapped Drive) on the local workstation. To
uninstall, remove the Siemens NX (Mapped Drive) product.

Automatic/Silent Installation of Siemens NX (Mapped Drive)

The installation of NX (Mapped Drive) can also be accomplished by an automatic, unattended install. This
feature may aid those System Administrators with a large number of site installations.
Caution: Use of this type of installation is intended for experienced installers only.
The setup.exe program is used to launch the unattended installation. Command line switches for
setup.exe are used to pass values to the msiexec.exe program.
 35

The unattended installation is controlled by the Windows system component, msiexec.exe. In order to
install silently you must pass switches and NX (Mapped Drive) specific configurable properties to
msiexec.exe on the command line. The msiexec.exe program has several command line switches. For full
documentation on these switches, see the Microsoft help documentation “Help and Support” for msiexec.
There are a few command line switches for the setup.exe program which can be used:
/h – setup.exe help, lists available switches.
/s – run setup.exe silently without any dialogs.
/a – perform an administrative installation.
/w – setup.exe waits for the msiexec.exe command to complete before closing.
Use the /w option on setup.exe when running the program from inside a script or when using an software
configuration management system, like SCCM. This option causes the program to wait until the
msiexec.exe process completes before exiting the setup.exe and proceeding to the next step in the
script/software configuration process. This option will not cause setup.exe to wait in a regular command
prompt, it will only wait when setup.exe is called from inside another script or software configuration
management system.
/v – pass parameters to the msiexec.exe program.

Parameters for msiexec.exe must be immediately following /v and may be optionally wrapped in quotes.
You can pass multiple parameters with one /v option. If any parameters passed require spaces, e.g.
C:\Program Files, you must pass the parameter with escaped quotation marks, e.g. \”C:\Program Files\”.
The parameters passed with the /v option are set to the msiexec.exe program as command line switches.
A few of the commonly used msiexec.exe command line switches are:
/h – msiexec help, will list available switches.
/q – specifies the UI level. /qn+ specifies no dialogs except for the ending “install done” dialog
{recommended}. /qn specifies a silent installation with no dialogs. If this option is used there is no
indication when the install completes, you must use the Task manager to monitor the “msiexec.exe”.
/L – specifies a logfile to be created, and the level of the messages to be written to the logfile {e.g.
msiexec /L*v “logfile”}. This example gives the most verbose log file; see msiexec switches for various log
switch options.
/i - specifies the msi file use for installation {e.g., msiexec.exe /i SiemensNX.msi}.
/x- specifies the msi file use for uninstallation {e.g., msiexec.exe /x SiemensNX.msi}.
The only required configurable property for NX (Mapped Drive) installation is the TARGETDIR setting
which points to the already installed version of NX on a network or mapped drive. All other options will
default to pre-defined values.
The first example installs NX (Mapped Drive) silently to set the UGII_LANG variable to french, install the
local files for Mapped Drive to F:\Program files\Siemens\NX, set the SPLM_LICENSE_SERVER variable to
29000@myserver, set the Start Menu to be in French (fr-fr.mst transform) and reference the NX software
already installed in N:\network\NX. No dialogs are displayed during installation.
setup.exe /s /v"/qn ADDLOCAL=ALL LANGUAGE=french INSTALLFOLDER=\"F:\Program
Files\Siemens\NX\" LICENSESERVER=29000@myserver TRANSFORMS=fr-fr.mst
TARGETDIR=N:\network\NX"
This next example installs NX (Mapped Drive) silently to the default location installation location
(INSTALLFOLDER not set to another location), the SPLM_LICENSE_SERVER is set to 29000@xyz,
 36

referencing the NX software already installed in N:\network\NX and both Start Menu and UGII_LANG is in
the default English. No dialogs are displayed.
setup.exe /s /v"/qn ADDLOCAL=ALL TARGETDIR=\"N:\network\NX\"
LICENSESERVER=29000@xyz"
 37

Additional Topics
Uninstalling NX
To remove the NX product:
Note: Beginning at NX 2212, the product version string (2212) is being added to the Siemens NX product
name on the Add/Remove and Apps & Features product listings to make it easier to find the current
version of the installed software.
Windows 10 & 11:
1. Open the Start menu.
2. Click Settings.
3. Click System on the Settings menu.
4. Select Apps & features from the left pane.
5. Select Siemens NX 2412 and then click the Uninstall option.
6. Click the Uninstall pop-up button to confirm.
Note: You can also use the Classic Control Panel and use Add/Remove Programs as in Windows 7/8.

Other Uninstall Considerations

• You may also re-run the NX setup program which will offer the option to Remove the installation (i.e.
uninstall).
• You may also use msiexec install option "/x" to uninstall NX.
a. Uninstall using msi file: msiexec /x "SiemensNX.msi"
b. Uninstall using Product GUID:
i. NX 1847 Series: msiexec /x {1C9E84F3-2EE4-44C1-B2E8-769B797BA18C}
ii. NX 1872 Series: msiexec /x {26973E5A-B9DD-474A-9B0D-106149218DDF}
iii. NX 1899 Series: msiexec /x {C94DF496-AA30-4B1C-9D50-AD2ED5550E14}
iv. NX 1926 Series: msiexec /x {8A2AFCB8-E5E2-48D4-952A-8BA3D0725D2B}
v. NX 1953 Series: msiexec /x {DA3E3F18-6E40-492E-9EDD-49D7C2A0F0BD}
vi. NX 1980 Series: msiexec /x {1A1E2BB0-351E-4D8B-8842-785561DAEE3A}
vii. NX 2007 Series: msiexec /x {D2D0FD15-3214-4A5E-8432-FCDE47B2145F}
viii. NX 2206 Series: msiexec /x {C0C625C8-F0D7-4FFB-965B-A600F8933159}
ix. NX 2212 Series: msiexec /x {1779F785-2F19-48E2-ABBC-98F358D7441C}
x. NX 2306 Series: msiexec /x {0A3E2EAA-10D0-432F-9F36-DDB672A17894}
xi. NX 2312 Series: msiexec /x {BC25F476-AA6E-41ED-BBA3-F7CA7DE8EB92}
xii. NX 2406 Series: msiexec /x {A3B2FFEE-2245-47AB-967C-DB473C4DE3D1}
xiii. NX 2412 Series: msiexec /x {F56493C9-7EDE-4664-8675-203572276A2A}

• There is no separate "uninstall" program or uninstall shortcut for NX.

• It is not necessary to reboot after uninstalling NX.
• The Siemens License Server service supplied by the installation of the Siemens License Server or from
a remote server will not be removed by uninstalling NX.
 38

Changes
This topic provides an overview of significant changes in the installation kits for this release.

Kit Consolidation
Beginning in NX 11, to simplify kit selection at installation time, many kits have been combined into larger
selectable groups in the “Custom” installation selection menu. At the conclusion of the installation the
folder structure will be similar to previous NX versions. For example, a single “Translators” kit selection
now includes all the translators that were previously selectable in prior NX installation.

UGII_ROOT_DIR obsoleted
In NX 11, the %UGII_ROOT_DIR% environment variable was retired.
To find executables and libraries, a central runtime directory called NXBIN is now used.

NXBIN directory
The NXBIN directory, is created on all platforms at the %UGII_BASE_DIR%\nxbin location during the NX
installation. Executables and libraries from the user selected installed kits are consolidated into the NXBIN
directory during the installation.
Configuration and script files that used to be found under %UGII_ROOT_DIR% will now be in
%UGII_BASE_DIR%\ugii. Executables, libraries and jar files that used to be found under
%UGII_ROOT_DIR% will now be in %UGII_BASE_DIR%\nxbin.
While the NX installation no longer sets the UGII_ROOT_DIR variable, the definition on the system will
remain to support earlier releases. If your code or scripts rely on %UGII_ROOT_DIR%, modify them to
ensure they work in NX.

Siemens License Server Installation no longer provided on NX Installation Media

The installation program for the Siemens License Server has been removed from the NX installation media beginning
with NX 2206 series. Due to continuous changes to the Siemens License Server it is recommended that you obtain the
newest version of the Siemens License Server from Siemens Support Center at https://support.sw.siemens.com/en-
US/product/1586485382. Siemens NX supports the newest version for license support.
 39

Troubleshooting
Windows Diagnostic Tools
Windows provides a variety of tools that you can use to understand how your computer is working and
diagnose problems. Some examples are:
Windows System Info Can be found via Start→All apps→Windows Administrative Tools→System
Information. It provides information about your system, and allows you to print this
information, or save it in a file. You can also run Windows Diagnostics by typing
msinfo32 in a Command Prompt window.

Event Viewer Provides you with a log showing various low-level events that have occurred while
your system has been running. Again, you can typically access this utility via Start→
All apps→Windows System→Control Panel→Administrative Tools.

System Properties The System Properties item in Control Panel lets you check and modify the values of
environment variables that affect the behavior of your system. Variables are located
under Start→ All apps→Windows System→Control Panel→ System→Advanced
system settings→Advanced tab→Environment Variables.

Net Commands Windows provides a wide variety of commands for diagnosing networking problems,
which can affect the system’s ability to communicate with the Siemens License
Server daemons. For more information, you might start by looking up the ping and
netstat utilities in Windows Help, or type net help in a Command Prompt window.
If you need help with any of these tools, please consult your Windows documentation or Help.

Launch.exe does not show proper user interface

The installation Launch.exe runs HTA files which are HTML Application files to present the user interface
for the Launch.exe program and to run the commands to launch other programs or view documents. If
the Launch.exe opens a text viewer which shows the source of the Launch.hta or brings up a pop-up
asking for which program to run, this can be fixed by setting the .hta file type to open the Microsoft HTML
Application Host.
To fix the problem, highlight the Launch.hta file and use click the right mouse button (RMB) and then
select “Open with >”. On the “Open with >” selection list select “Choose another app”. On the “Choose
another app” form, turn on the toggle for “Always use this app to open .hta files” and then select
“Microsoft (R) HTML Application host” as the application to use to open .hta files. This will reset the HTA
file type to properly open the “Microsoft HTML Application host” application. Running Launch.exe now
will open the proper user interface defined by the HTA files.

“Connection to license server machine failed.” during installation

If you receive a pop-up error of “Connection to license server machine failed.” when entering the license
file or port@host on the Licensing dialog of the installation this may mean that your license server is not
configured at the time of installation or you are the network and there is no connection to the license
server.
You can bypass this dialog by entering “29000@LocalHost” as the license server and then change the
SPLM_LICENSE_SERVER environment variable manually after you have installed NX and your license
server is set up and running.
 40

Certificate Errors During Installation

On machines which are not connected to the internet, you may run in to issues installing because the systems
root certificates are not up-to-date causing certificate errors during the installation on cabinet files. To
attempt to fix this problem you will need to manually update the root certificates on machines not connected
to the internet.
Follow the steps below to get the updated certificates from a machine on the internet and transfer them to
the machine not on the internet.
On a machine with internet access
1. Open a cmd prompt as admin
2. Navigate to a folder somewhere, i.e C:\Temp
3. Type: CertUtil –generateSSTFromWU Rootstore.sst
4. Current root certificates updates will download and write to the file “Rootstore.sst”
5. Copy the .sst file from the path in Step 2 to the machine(s) which does not have internet access

On the machine without internet access

1. Click Start->Run. Alternatively click windows keyboard button + R
2. Type: certmgr.msc - this opens the certificate manager
3. Right click on the item “Trusted Root Certification Authorities”
4. Select All Tasks>Import
5. Click Next
6. Click “Browse”, change the file type in the lower right selection drop-down to “All Files”
7. Navigate to the location .sst file obtained from the previous set of steps and select the file
8. Click Next
9. Specify the radio item “Place all certificates in the following store.”
“Trusted Root Certification Authorities” should be specified
10. Click Next, Click Finish - Note: It is necessary to click “Yes” for every certificate which resides in the .sst file
11. Click Start->Run. Alternatively click windows keyboard button + R
12. Type: certmgr.msc - this opens the certificate manager
13. Right click on the item “Trusted Publishers”
14. Select All Tasks>Import
15. Click Next
16. Click “Browse”, change the file type in the lower right selection drop-down to “All Files”
17. Navigate to the location .sst file obtained from the previous set of steps and select the file
18. Click Next
19. Specify the radio item “Place all certificates in the following store.”
“Trusted Publishers” should be specified
20. Click Next, Click Finish - Note: It is necessary to click "Yes" for every certificate which resides in the .sst file
 41

Error writing to file ugshext.dll during update installation

The ugshext.dll file in NX is a Windows Explorer extension. If you receive an error during an update
installation this means that the ugshext.dll is locked by Windows Explorer and the installation can not
proceed until the file is unlocked.
To unlock the file, first close all open Windows Explorer windows on the system and then use the “Retry”
button on the pop-up error dialog.
If this does not allow the installation to proceed, you will need to stop the installation, log out and log
back in to the machine, then run the installation without opening any Windows Explorer windows.
Again, if this does not allow the installation to proceed past the ugshext.dll file, then a reboot of the
system will be necessary to clear any file locks on the ugshext.dll file and you will again need to log in
without opening any Windows Explorer windows while running the update installation.

Creating Install Log Files

If the installation does not complete successfully, error logs of the installation may provide helpful
information. By default an installation log file MSI*.log will be created in your user %TEMP% folder. If you
wish to create the file elsewhere during installation, in a command prompt window enter:
setup.exe /v"/L*v C:\LogFile2.txt"
{where LogFile2 is the full path to your log file. Note: there is no space after the “/v” switch. This example
shows using “setup.exe” to start the log. Setup actually passes these switches to msiexec.exe}
Note: The msiexec.exe program supports many levels of log file information from terse start/stop
messages to the very verbose log example shown above. See “Help and Support” on msiexec for
information on the levels of logging available.
 42

Repairing registry entries

It is possible due to install/uninstall processes for the registry entries which define the file associations
and system-wide product defintions to get out of sync with the version of NX you are running.
To repair registry entries associated with NX, when NX files do not need to be repaired, use the msiexec
command without running the UI for repair, as would occur when using Repair in the install or on
Add/Remove programs. Using the command line, non-UI repair will be much quicker to update the
registry.
Command to run:
msiexec /fms <ProductCodeGUID>

Where the command for each series would be:

NX 1847 Series: msiexec /fms {1C9E84F3-2EE4-44C1-B2E8-769B797BA18C}

NX 1872 Series: msiexec /fms {26973E5A-B9DD-474A-9B0D-106149218DDF}
NX 1899 Series: msiexec /fms {C94DF496-AA30-4B1C-9D50-AD2ED5550E14}
NX 1926 Series: msiexec /fms {8A2AFCB8-E5E2-48D4-952A-8BA3D0725D2B}
NX 1953 Series: msiexec /fms {DA3E3F18-6E40-492E-9EDD-49D7C2A0F0BD}
NX 1980 Series: msiexec /fms {1A1E2BB0-351E-4D8B-8842-785561DAEE3A}
NX 2007 Series: msiexec /fms {D2D0FD15-3214-4A5E-8432-FCDE47B2145F}
NX 2206 Series: msiexec /fms {C0C625C8-F0D7-4FFB-965B-A600F8933159}
NX 2212 Series: msiexec /fms {1779F785-2F19-48E2-ABBC-98F358D7441C}
NX 2306 Series: msiexec /fms {0A3E2EAA-10D0-432F-9F36-DDB672A17894}
NX 2312 Series: msiexec /fms {BC25F476-AA6E-41ED-BBA3-F7CA7DE8EB92}
NX 2406 Series: msiexec /fms {A3B2FFEE-2245-47AB-967C-DB473C4DE3D1}
NX 2412 Series: msiexec /fms {F56493C9-7EDE-4664-8675-203572276A2A}

NX Won't Start
If NX fails to start, a window will display the reason for the failure.
Can't Connect to License Server
Check that the Siemens License Server is available. Open a Command Prompt window, change to the
%UGII_BASE_DIR%\UGFLEXLM directory and enter the command:
lmutil lmstat –c 29000@<hostname>
{where 29000 is the port number and <hostname> is the hostname of the Siemens license server}
For example:
cd /d C:\Program Files\Siemens\NX\UGFLEXLM {default location}
lmutil lmstat -c 29000@<hostname>
{where 29000 is the port number and <hostname> is the hostname of the Siemens license server}
Diagnostic messages will appear telling you some possible sources of your problem.
No Licenses Available
Using the Licensing Tool to Select Bundles
Note: Prior to NX 9.0, License Options was used to set persistent or default bundle selections via the
UGS_LICENSE_BUNDLE variable that it created. As of NX 9.0, Licensing Tool does not create a
 43

variable but instead, stores the bundle selections in the Registry.

All licenses for module "gateway" are already in use or no bundles have been selected. Your license file
may contain Suite Packages, otherwise known as Bundles and Portfolio Bundles. To use a bundle, it must
be preset prior to running NX. If bundles are preselected, the application will attempt to check out a
bundled feature before trying to check out the floating feature.
Licensing Tool is an interactive user interface that aids in setting persistent or default bundle selections in
the user accessible registry entry:
HKEY_CURRENT_USER\Software\Siemens_PLM_Software\Common_Licensing\NX_BUNDLES
To set the bundle(s) in the registry:
Click on Start→All apps→Siemens NX→Licensing Tool
Caution: Customers using Bundle/Portfolio licenses must either set the bundle selection(s) via the
'UGS_LICENSE_BUNDLE' variable or the ‘NX_BUNDLES’ registry entry with the package
name(s) of the bundle(s) before attempting to run NX. Licensing Tool honors the bundle
selections set by the variable but once Licensing Tool is used to apply a bundle, the
UGS_LICENSE_BUNDLE variable is no longer honored nor effective. If the ‘NX_BUNDLES’
registry entry exists (even if the value is ‘blank’), it would have to be deleted in order to
make the bundle selections effective for the UGS_LICENSE_BUNDLE variable if set.
 44

Checking the Siemens License Server Service {on the server}

Check that the Siemens License Server service is running, either using Task Manager or Control
Panel→Administrative Tools→Services. In Task Manager, you should see entries for lmgrd.exe and
ugslmd.exe. Using Control Panel→Administrative Tools→Services, you should see Siemens License Server
with a status of "Started".
If the service is present, but not running, you should start it manually. Control Panel→Administrative
Tools→Services. Right-click the service name "Siemens License Server", and click Start.
If the Siemens License Server service is unable to start, there may be other problems. Choose Start→All
apps→Siemens License Server→lmtools. In the Service/License File section, select "Configuration using
Services". Click on the "Config Services" tab. The "Siemens License Server" service should appear in the
Service Name field. Verify that all "path to" entries are valid.
These entries displayed on the lmtools screen should not be blank. If these entries are blank, enter the
correct service name as shown above. Use the browse button to search the drive for the location of the
installed license program (lmgrd.exe). Browse for the correct license file. The default location for the
Debug Log File should be set to C:\Program Files\Siemens\PLMLicenseServer\splm_ugslmd.log, provided
that the directory path is where you installed Siemens License Server. Use the browse button to update
this field. Make sure the two checkboxes, “Start Server at Power Up” and “Use Services”, are both
checked (after checking “Use Services”, “Start Server at Power Up” will become available). Click the “Save
Service” button.
To start the license service from lmtools, open the Start/Stop/Reread tab. Click the Start button.
Note: The graphically-oriented license administration utility lmtools is also available on the Siemens
Licensing client if installed. For example:
Click on Start→All apps→Siemens NX→Lmtools
The utility lmutil is a command line license administration tool similar to the graphically-oriented
LMTOOLS utility. Open a Command Prompt window to use this utility and change directory to the
appropriate FLEXlm directory. Run the command:
lmutil lmstat -c 29000@<hostname> –a
{where 29000 is the port number and <hostname> is the hostname of the Siemens license server}
from the server machine to verify that the vendor daemon is alive. Run the same command from a client
machine to verify the connection across the network from client to vendor daemon. Other information
may be extracted using different switches or options; these are documented in the License Administration
Guide.
For example:
cd /d C:\Program Files\Siemens\NX\UGFLEXLM {on a client}
cd /d C:\Program Files\Siemens\License Server {on a server}
lmutil lmstat -c 29000@<hostname> –a
{where 29000 is the default port number and <hostname> is the hostname of the Siemens license
server}
Diagnostic messages will appear telling you some possible sources of your problem.
Some typical responses are:
 45

License File Could Not If you are receiving your license data file via e-mail, you need to save it in text format.
Be Read Some users using MSWord as their reader may receive garbage in the license file (e.g.
License_Ugslmd.txt) when it is received in e-mail.

See saltd.log When the Siemens License Server service is started, the log file saltd.log is created.
The log file can give you the best information on the state of the license server. This
file can be opened with the Notepad editor, and it will give some indication as to what
went wrong. Errors may be a result of a corrupted license file, the lmhostid not
matching the license file, or networking problems involving TCP/IP or DNS
configuration. Use the instructions given earlier to check that there is a working
TCP/IP network connection to your Siemens License Server. This file is located by
default at:
C:\ProgramData\Siemens\License Server\saltd.log
This can only be performed from the license server.

Error Handling Failed – NX Initialization error

This error may occur due to several reasons:
Check that the real hostname of the license server is on the SERVER line of the license file. The license file
is electronically provided by Siemens Software with 'YourHostname' or 'this_host' on the SERVER line as a
placeholder for the real hostname of the license server. The Siemens License Server installation will edit
the license file to automatically change "YourHostname" or "this_host" keyword to the actual hostname of
the license server. However, this field must be edited manually for any subsequent updates of the license
file and for redundant server configurations (i.e. license files containing 3 SERVER lines).
Check that the SPLM_LICENSE_SERVER environment variable is set to a valid Standalone Node-Locked
License file or '<port>@<hostname>', where the port and hostname come from the SERVER line in the
license file. The SPLM_LICENSE_SERVER variable is normally set during the installation of NX but can be
manually set using the Control Panel→System→Advanced system settings→Advanced
tab→Environment Variables... button user interface.
This error may also be caused by selecting too few colors in Control Panel→Display→Settings tab. NX will
not run if the color palette is only set to 256 colors or if the resolution is below 1024x768.
Check the NX syslog file in your %TEMP% directory for other possible errors.

NX Startup Very Slow

Slow startup of NX can be caused by a slow network connection between the client(s) and license server.
If NX and the Siemens License Server are running on the same computer, then slow startup may also be a
result of a missing entry in your hosts file.
To correct this, find the “hosts” file in your Windows folder and edit it to add a new entry that consists of
an IP address (of the form xxx.xxx.xxx.xxx) and the computer’s hostname . For example: 198.168.0.1
mycomputer.
The hosts file is located at:
C:\WINDOWS\system32\drivers\etc\hosts
 46

Tools->Spreadsheet does not start Excel

To start Excel, the spreadsheet tool uses DLLs which are registered on the local workstation during the installation
process (regular or mapped drive installations). If Excel does not start when you use the spreadsheet tool, verify that
the DLLs are registered on the local workstation.
In regedit, the DLLs are registered in the registry hives:
HKEY_CLASSES_ROOT\CLSID\{D99CD578-9510-4014-9161-F01778698159}
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{D99CD578-9510-4014-9161-F01778698159}
If these hives don’t exist you can register the DLLs using a script in the INSTALL kit of the installation. Run the
INSTALL\register_splm_files.bat script to register the DLLs.
Note: These DLLs use the .NET 4.8 Framework so that version or a newer one is required to be installed on
the local workstation to register the DLLs. The .NET 4.8 Framework is installed by the setup.exe
program if it, or a newer version, doesn’t exist on the local workstation during product installation.

Part Preview Issues

Part file preview in Windows Explorer and the ability to launch NX by double-clicking on a part file are
managed by ugshext.dll. Registry entries are created during regular and mapped drive installations to allow
the part icon to appear in Windows Explorer and for double-click open in NX to function after installation.
If you experience errors during Windows Explorer part file preview, part file preview doesn’t appear, or
double-clicking a part file does not start NX, you may need to fix the registration of the ugshext.dll by
unregistering and re-registering ugshext.dll.
Before unregistering and re-registering ugshext.dll, check that you do not have the Folder Options, View
setting “Always show icons, never use thumbnails” turned on which would prevent a properly registered dll
from displaying part previews.
Note: The file location stored in the registry will be for the last version of ugshext.dll registered. If an older
version of NX is installed and the older ugshext.dll is registered after a newer version, the older version
ugshext.dll will be used for part file preview. Due to differences in the DLL functionality between
versions, this could mean the part preview on newer parts may not work properly when an older
version of ugshext.dll is registered.

To register the ugshext.dll, do the following:

1. Log onto your workstation, using an account with Administrator privileges.
2. Open a command prompt window and move to the %UGII_BASE_DIR%\NXBIN folder:
cd /d %UGII_BASE_DIR%\NXBIN
3. Use regsvr32 to register the DLL:
regsvr32 ugshext.dll
Because of the ability to install multiple older versions of NX on a system, it is possible when a version is
uninstalled that it will remove settings for the ugshext.dll in the registry. If you remove the last or only version
of NX installed on the machine and you have manually registered the ugshext.dll or if you remove one version
of NX and the remaining version was not the one registered you will want to unregister and then, if still
needed, re-register the appropriate ugshext.dll version for continued Windows Explorer extensions support.
 47

To unregister ugshext.dll, do the following:

1. Log onto your workstation, using an account with Administrator privileges.
2. Open a command prompt window and move to the %UGII_BASE_DIR%\NXBIN folder:
cd /d %UGII_BASE_DIR%\NXBIN
3. Use regsvr32 to unregister the DLL:
regsvr32 /u ugshext.dll

Note: The DLL location stored in the registry will be for the last version of ugshext.dll registered. If an older
version of ugshext.dll is registered after a newer version, the older version ugshext.dll will be used for
part preview. Due to differences in the DLL functionality between versions, this could mean the part
preview on newer parts may not work properly when an older version of ugshext.dll is registered.
 48

Proprietary & Restricted Rights Notice

This software and related documentation are proprietary to Siemens.
Unpublished work. © 2024 Siemens Industry Software Inc.
Siemens, the Siemens logo and SIMATIC IT are registered trademarks of Siemens AG. Camstar, DCubed,
Femap, Fibersim, Geolus, I-deas, JT, NX, Omneo, Parasolid, Solid Edge, Syncrofit, Teamcenter and
Tecnomatix are trademarks or registered trademarks of Siemens Industry Software Inc. or its subsidiaries
in the United States and in other countries. All other trademarks, registered trademarks or service marks
belong to their respective holders.