Resolving TIA Portal V15 Installation Failure on Windows 10 1903

1. Problem Summary

Fresh installations of Siemens TIA Portal V15 (and V15.1) on a clean Windows 10 version 1903 (May 2019 Update, OS build 18362.x) build can fail with an unspecific abort after a few seconds, or with the spurious message "You need a valid license to install the selected software". The error appears even on machines that have no license-related issue and is encountered before the normal license transfer screen is reached. The same TIA Portal media install without issue on Windows 10 1809, and in-place upgrades from 1809 to 1903 typically retain the working installation, which confirms the failure is specific to a clean 1903 image and not the TIA Portal media itself.

This article documents the root cause, the diagnostic procedure to capture the TIA Portal setup log, and the verified remediation sequence that restores the installer behaviour on Windows 10 1903. The same procedure applies to the closely related TIA Portal V15.1 media when installed on a 1903 image that has not been updated with the required Windows cumulative update set.

2. Affected Environment Matrix

3. Symptoms and Error Messages

Three distinct failure modes have been reported in the field on a clean Windows 10 1903 image:

1. Silent abort. The TIA Portal setup launches, displays the splash for several seconds, then closes without any error dialog and rolls the partially extracted package back. No log entry is shown in the installer UI.
2. License transfer dialog shown as an error. When the installer is re-launched as Administrator, the dialog that should appear after successful product installation appears during the install attempt and reads "You need a valid license to install the selected software." This dialog is normally only presented once the TIA Portal software has been fully installed; its appearance during install indicates the Automation License Manager (ALM) service is not registered correctly or the ALM RPC endpoint cannot be reached.
3. Windows Installer MSI error 1603. Embedded MSI packages inside the TIA Portal bundle fail with generic error 1603 (Fatal error during installation). The MSI log file shows a return code of 3 from a custom action named CheckLicense or ALMCheck.

The root cause for all three symptoms is the same: the ALM service cannot be reached by the TIA Portal setup on a fresh Windows 10 1903 image. In-place upgrades retain the existing ALM service registration and therefore succeed; a clean 1903 image lacks the prerequisites that ALM expects to find.

4. Root Cause Analysis

Windows 10 1903 introduced several changes to the Service Host (svchost) infrastructure, the RPC endpoint mapper defaults, and the .NET Framework servicing model. Each of these can break the TIA Portal V15 installer in isolation, and they compound when present together on a fresh 1903 RTM image.

• ALM service registration timing. The Automation License Manager installs its Windows service during the very first step of the TIA Portal setup. On 1903 RTM, the SCM (Service Control Manager) can return ERROR_SERVICE_NOT_ACTIVE (Win32 1062) when queried within the same process that just started it, causing the setup's ALMCheck custom action to report "no license service present" and abort with the license error.
• Missing .NET Framework 4.7.2 / 4.8 servicing baseline. TIA Portal V15 prerequisites include .NET 4.7.2; the 1903 RTM image ships with the .NET 4.8 inbox version that is binary-compatible but not always recognized as a valid prerequisite by the TIA setup bootstrapper, producing a non-zero custom action return.
• Pending reboot from previous Windows update. A clean 1903 image frequently has one or more pending cumulative updates queued. The TIA setup honors the Windows Installer "pending reboot" flag and rolls back, which is reported as an unspecific abort.
• Long path support (MAX_PATH) regression. 1903 enabled Win32 long path support by default in some configurations; the TIA V15 setup uses legacy MAX_PATH-bound MSI paths, and the resulting path conversion can fail when the temp directory sits more than 90 characters deep (common with C:\Users\<longname>\AppData\Local\Temp\Siemens\Setup\).

5. Diagnostic Procedure: Capturing Installation Logs

Before applying any fix, capture the TIA Portal setup log. The installer is silent on aborts by design, so the log is the only authoritative source for the failure cause.

1. Open an elevated Command Prompt (right-click Command Prompt → Run as administrator).
2. Create a working directory for the logs:

   mkdir C:\Temp\TIA_Install_Log
   set TIALOG=C:\Temp\TIA_Install_Log

3. Mount the TIA Portal V15 ISO and change to the setup directory. Launch the installer with logging enabled:

   E:\Setup\Setup.exe /log "%TIALOG%\TIA_Setup_%date:~-4%%date:~3,2%%date:~0,2%.log" /silent

   Use /log alone for an interactive install; use /silent only if you intend a fully unattended run for diagnostic purposes.

4. If the install aborts, inspect the log in this order:

   findstr /i /c:"error" /c:"failed" /c:"return value 3" /c:"ALMCheck" "%TIALOG%\TIA_Setup_*.log"

5. Cross-reference any hex error code found with the table below before applying the fix.

Additional Microsoft-side guidance on collecting the relevant log evidence from a Windows install perspective is documented at Problems installing TIA Portal V15.1.

6. Step-by-Step Remediation

Apply the steps in the order listed. Stop and re-verify at each gate; do not skip ahead.

6.1 Pre-flight Checks (Before Launching the Installer)

1. Apply all pending Windows updates. Open Settings → Windows Update, click Check for updates, install every optional and cumulative update, and reboot. Do this at least twice until the system reports "You're up to date". The 1903 image must reach at least the September 2019 cumulative update (OS build 18362.357) for the ALM service registration to be reliable.
2. Disable third-party antivirus and endpoint protection for the duration of the install. Real-time scanning of MSI custom actions is a documented cause of 1603 errors. Re-enable AV after the install completes.
3. Confirm the user account. Use a local Administrator account whose username is ≤ 12 characters and contains no spaces, dots, or non-ASCII characters. The TIA setup's MSI custom actions still traverse the legacy %USERPROFILE% path during extraction, and a 30-character username on a fresh 1903 image can push the working path beyond MAX_PATH even with long-path support enabled.
4. Clean the installer cache.

   rd /s /q "%TEMP%\Siemens"
   rd /s /q "%LOCALAPPDATA%\Siemens"
   rd /s /q "%PROGRAMDATA%\Siemens\Automation\

   Stale entries from a previous aborted install are a frequent source of the unspecific abort on retry.

6.2 Bootstrapper Order: Install ALM First

The TIA Portal V15 media ships the Automation License Manager as a separate, independent installer in the Support directory of the DVD/ISO. Install it before launching the TIA Portal setup:

1. Mount or insert the TIA Portal V15 media.
2. Navigate to <media>\Support\Automation_License_Manager\ (or the equivalent folder name for V15.1).
3. Right-click Setup.exe and choose Run as administrator.
4. Complete the ALM install, accept the license agreement, and reboot when prompted.
5. Verify the ALM service is installed and running:

   sc query "ALM""
   tasklist /fi "imagename eq alm.exe""

   The first command must return STATE: 4 RUNNING for a service whose name contains ALM or Siemens Automation License Manager. The second should list alm.exe in the console session.

Only after the ALM service is confirmed running should the TIA Portal setup be launched. This sequence alone resolves the majority of field-reported 1903 install failures.

6.3 Launch the TIA Portal V15 Setup

1. Right-click the TIA Portal V15 Setup.exe in the root of the installation media and select Run as administrator. Do not double-click or launch from a mapped network drive; copy the media locally first.
2. If Windows SmartScreen warns that the publisher is unknown, choose More info → Run anyway. SmartScreen blocking produces the same silent-abort behavior as a true installer crash.
3. Proceed through the setup dialogs. The license transfer screen that previously appeared prematurely should now appear only at the end of a successful install, as designed.

7. License Manager Service Recovery

If Section 6.2 was skipped or the ALM service still fails to register, recover it manually.

1. Open services.msc as Administrator.
2. Locate Siemens Automation License Manager (display name; service name ALM or ALMSrv depending on the bundled version).
3. Right-click → Properties. Set Startup type to Automatic. Confirm the Log On account is Local System account; if it is Local Service, change it to Local System, click Apply, then Start.
4. If the service fails to start with error "Windows could not start the service on Local Computer. Error 1067: The process terminated unexpectedly", re-register the service binaries from the install media:

   cd "C:\Program Files (x86)\Siemens\Automation\License Manager\Bin"
   ALMService.exe -uninstall
   ALMService.exe -install
   net start ALM

5. Verify the RPC endpoint is reachable:

   netstat -ano | findstr :4410
   netsh rpc filter show state

   ALM listens on TCP/4410 by default. If port 4410 is not listed, the service is registered but not listening — re-install per step 4.

6. Re-launch the TIA Portal V15 setup as administrator.

8. Windows 10 1903 Specific Configuration

The following OS-level adjustments are required on a fresh 1903 image, regardless of whether TIA V15 or V15.1 is being installed. They are independent of the TIA version and are documented here as a single block.

8.1 .NET Framework Servicing

1. Open Programs and Features (appwiz.cpl).
2. Confirm Microsoft .NET Framework 4.7.2 or later is present. If not, install the standalone .NET Framework 4.7.2 offline package from the Windows 10 media's \Installers\ folder, reboot, and retry.
3. Repair the .NET installation from an elevated command prompt:

   dism /online /enable-feature /featurename:NetFx4ServerFeatures /all
   dism /online /enable-feature /featurename:NetFx4ClientFeatures /all

8.2 Long Path and Temp Directory

1. Override the system temp to a short path before running the installer:

   set TEMP=C:\Temp
   set TMP=C:\Temp
   mkdir C:\Temp

2. Disable long path awareness for the TIA setup if it cannot be set via Group Policy by setting the environment variable:

   set COMPLUS_DisableLongPath=1

8.3 Windows Installer Service Health

1. Stop and re-register the Windows Installer service:

   net stop msiserver
   msiexec /unregister
   msiexec /regserver
   net start msiserver

2. Re-launch the TIA setup with full logging (Section 5, step 3).

8.4 Group Policy / Security Mitigations

Windows 10 1903 enabled CVE-2019-0841-related tightening on Windows Installer child processes. On a domain-joined machine, this manifests as 1603 with the "The installer has encountered an unexpected error installing this package" text. If Group Policy Computer Configuration → Administrative Templates → Windows Components → Windows Installer → Turn off Windows Installer → Never is set, change it to Not Configured, run gpupdate /force, and retry.

9. Verification Procedure

After applying the remediation, verify the install is fully functional — not merely that the setup completes.

1. Confirm the TIA Portal shortcut launches from the Start menu without error.
2. In TIA Portal, open Help → Installed software and verify the version string reads V15.0.0.0 (or V15.1.0.0 for V15.1 media) and the build number matches the media.
3. Open the TIA Portal License dialog (Project → Properties → Protection or Online → License Management). Confirm the Automation License Manager dialog opens and lists the locally attached USB license or the network license server.
4. Create a new project, add an S7-1500 PLC device, compile the hardware configuration, and download it to a test PLC (or to PLCSIM) to exercise the full TIA toolchain end-to-end.
5. Re-enable the antivirus that was disabled in step 6.1.2 and verify that the TIA Portal continues to operate normally with the AV in active scanning mode. If a specific AV rule blocks TIA components, add a process exclusion for C:\Program Files\Siemens\Automation\ and C:\Program Files (x86)\Siemens\Automation\.
6. Reboot the workstation, sign back in, and confirm TIA Portal launches on a cold start. This is the definitive test that the ALM service registration survived the reboot — the most common failure mode for fix attempts that appear to work in-session but regress on next boot.

10. Troubleshooting Matrix

11. Prevention and Best Practices

• Maintain a single OS image validated against the TIA Portal version in use. Once that combination is verified, capture the image (e.g., with dism /capture-image) and use it for every subsequent deployment in the engineering fleet.
• Install the Automation License Manager as part of the image's software baseline, before TIA Portal, and confirm the service is set to Automatic startup.
• Apply Windows updates on a controlled schedule, not automatically. A cumulative update that lands between image capture and TIA installation is a common trigger of the symptoms described above.
• Keep a copy of the TIA setup log directory after every install attempt. The 1903-specific root cause is identified from ALMCheck return values; without a log, diagnosis becomes guesswork.
• Document the TIA Portal media version (V15, V15.1, V15.1 Update 2, etc.) in the engineering workstation asset record. TIA Portal V15.1 Update 2 and later are recommended for 1903 and later Windows 10 builds where supported by the readme.
• If the clean-install failure persists after applying every step in this article, the practical fallback is to use Windows 10 1809 (LTSC or SAC) for the engineering workstation. The 1809 build is the last Windows 10 release where the TIA Portal V15 and V15.1 installers complete without the remediation sequence described in Sections 6 through 8.

FAQ