Installing Older TIA Portal Versions Alongside V15.1

Overview

When engineering teams need to support multiple generations of Siemens automation projects, the requirement to keep more than one TIA Portal installation on a single workstation is common. TIA Portal V15.1 remains widely deployed in plants that also maintain legacy projects authored in V14 SP1, V13 SP2, or in the classic SIMATIC Manager (STEP 7 V5.5 / V5.6). Installing these older toolchains on top of an existing V15.1 installation typically fails with installer errors and corrupted log files because the Siemens setup framework shares components between versions.

This reference covers the root cause of the failure, the correct ascending-order installation sequence when coexistence is required, and the official support boundaries published by Siemens. It also documents the alternate virtual-machine deployment that eliminates the conflict entirely.

Root Cause: Why Older TIA Versions Fail to Install Over V15.1

The TIA Portal setup is a multi-package installer that drops shared components into common directories. Components reused across versions and frequently causing install conflicts include:

• Automation License Manager (ALM) — service and key container reused by every TIA Portal release.
• Siemens Security Framework (SSF) — certificate, signing, and activation components.
• SQL Server instances — V14 onward creates dedicated SQL Server instances (e.g., SIEMENS\TIAP15, SIEMENS\TIAP15_1) used by project libraries and team engineering.
• TIA Administrator and Startdrive plug-ins.
• .NET Framework and Visual C++ redistributables — version-specific runtime dependencies.
• TIA Portal Help System and WinCC Help System — common help content servers.

When V15.1 is already installed, its setup has registered newer versions of these shared components. The V14 or V15 setup detects that the on-disk version is higher than what it intends to install and aborts with the message:

Setup is unable to install the requested product because one or more
required components are already installed at a newer version.

The installer writes detailed logs to:

• C:\Users\<user>\AppData\Local\Temp\Siemens\Setup.log
• C:\ProgramData\Siemens\Automation\Logfiles\

Typical log entries reference error codes 0x80004005, 0x80070643, or 0x800736B3 (component-not-found / version-mismatch). Deleting the log files does not resolve the underlying version conflict; only re-installing in the correct sequence does.

Supported Coexistence: What Siemens Officially Allows

Siemens does not guarantee that every combination of TIA Portal versions runs side-by-side on a single operating system. According to the official compatibility documentation at TIA Portal Compatibility Between Versions, project-level upgrade paths are strictly forward: a project created in V14 must be upgraded to V15.1 before it can be edited, and the reverse is not permitted. The installer mirrors this forward-only model and assumes the version on disk is the highest version in use.

Coexistence Matrix (Single Windows Workstation)

The only supported combination that solves the source scenario — legacy SIMATIC Manager + V14 project files + active V15.1 — is the multi-VM deployment, or alternatively, migrating the V14 project forward to V15.1 through the project upgrade wizard.

Prerequisites

Before touching the workstation:

1. Administrator account on Windows. The setup must run with elevated privileges.
2. Supported Windows version. TIA Portal V15.1 supports Windows 7 SP1 (64-bit), Windows Server 2012 R2, Windows 10 Version 1607 or later, and Windows Server 2016. Newer builds (Windows 11) install but are not listed in the V15.1 release notes.
3. Disk space ≥ 80 GB free. A complete TIA Portal installation occupies 30–45 GB per version.
4. Pending reboot cleared. Run shutdown /r /t 0 if a previous TIA Portal uninstall left pending file operations.
5. External backup. Use an external USB drive or a cloned disk image so the system can be restored if the downgrade corrupts the environment.
6. Original installation media (mounted ISO) for V14 SP1, V15, V15.1, and SIMATIC Manager V5.x.
7. Siemens Automation License Manager installer matching each TIA Portal version (each ships its own ALM installer).
8. TIA Portal Selection Tool shipped on the DVD image — confirm the offline-compatible packages.

Step-by-Step Installation Procedure

The order in which TIA Portal versions are installed is critical. The Siemens setup expects each version to be the newest version on the system at the moment of its installation. The only reliable sequence for installing V14 SP1, V15, and V15.1 on a single workstation is ascending version order.

Step 1 — Create Restore Points and Backups

1. Open System Protection in Windows.
2. Click Create and name the restore point Pre_TIA_Install_<date>.
3. Attach an external USB drive and run a full system-image backup using Windows Backup or a third-party tool.
4. Export TIA Portal settings: open V15.1 and use Settings → Export to save a .tiasettings file.

Step 2 — Uninstall TIA Portal V15.1

This is the action the original poster explicitly wanted to avoid. However, until Siemens ships an installer that supports side-by-side coexistence for V15.1 and V14, the only clean approach is a controlled downgrade.

1. Open Control Panel → Programs and Features.
2. Locate Siemens Totally Integrated Automation Portal V15.1 and all associated add-ins (Startdrive, TIA Administrator, Teamcenter Gateway, Energy Suite).
3. Right-click → Uninstall and follow prompts.
4. When prompted, retain user data and project archives.
5. Restart the PC even if not prompted.

Step 3 — Delete Residual Log Files and Caches

1. Delete the contents of:
   • C:\ProgramData\Siemens\Automation\Logfiles\
   • C:\ProgramData\Siemens\Automation\Siemens\Logfiles\
   • C:\Users\<user>\AppData\Local\Temp\Siemens\
   • C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Siemens Automation\
2. Remove orphaned SQL Server instances:
   • Open SQL Server Configuration Manager.
   • Stop and remove instances named TIAP15 and TIAP15_1 if present.
3. Back up the registry, then remove:
   • HKLM\SOFTWARE\Siemens\Automation\
   • HKLM\SOFTWARE\WOW6432Node\Siemens\Automation\
4. Restart the PC.

Step 4 — Install SIMATIC Manager V5.5 SPx / V5.6

SIMATIC Manager (Step 7 Classic) is installed first because it predates TIA Portal and uses an independent registry tree.

1. Insert or mount the SIMATIC Manager DVD.
2. Run setup.exe as Administrator.
3. Accept the license agreement.
4. Select User-Defined installation for explicit control over S7-PLCSIM, S7-GRAPH, and S7-SCL packages.
5. Restart when prompted.
6. Verify: open SIMATIC Manager and confirm File → Open lists a project. A blank dialog without errors confirms a healthy install.

Step 5 — Install TIA Portal V14 SP1

1. Mount the V14 SP1 ISO.
2. Run Start.exe from the DVD root.
3. The TIA Portal Installation Wizard launches.
4. Accept the license terms.
5. Select packages: STEP 7 Basic V14 SP1, WinCC Basic V14 SP1, Startdrive V14 SP1 (optional).
6. Accept the default installation directory C:\Program Files\Siemens\Automation\.
7. Wait for installation (45–90 minutes).
8. Restart.
9. Open TIA Portal V14 SP1 and create a dummy project to verify the editor loads.

Step 6 — Install TIA Portal V15

1. Mount the V15 ISO.
2. Run Start.exe.
3. The installer detects the existing V14 SP1 prerequisite and proceeds.
4. Select STEP 7 Professional V15 and WinCC Professional V15.
5. Complete installation.
6. Restart.
7. Verify by opening TIA Portal V15 and checking Help → About.

Step 7 — Install TIA Portal V15.1

1. Mount the V15.1 ISO.
2. Run Start.exe.
3. The installer detects V15 and performs the in-place upgrade to V15.1.
4. Select the same packages installed for V15.
5. The installer creates a new SQL Server instance TIAP15_1.
6. Wait for completion and restart.

After this sequence the workstation holds SIMATIC Manager + V14 SP1 + V15 + V15.1 in the correct order, with SQL Server instances and ALM versions consistent with the newest release.

Alternate Approach: Virtual Machine Isolation

For production engineering workstations, isolating legacy toolchains in a VM is more reliable than fighting the Siemens installer.

Recommended Hypervisor and Host Configuration

Workflow

1. Create a VM with Windows 10 1809 LTSC (closest supported OS for V14 SP1 / V15).
2. Install SIMATIC Manager and the older TIA Portal versions in ascending order inside the VM.
3. Share the project archive folder via a network share or shared folder.
4. Use TIA Project-Server Multiuser or simple file copies to move projects between VM and host.
5. Snapshot the VM before any update to enable instant rollback.

This avoids the entire coexistence problem and provides a snapshot-based rollback path for any future version regression.

Common Errors and Recovery

Verification Checklist

After installation, confirm the engineering environment is fully functional:

1. Open SIMATIC Manager → create a new S7-300 project → online → accessible node test passes.
2. Open TIA Portal V14 SP1 → create an S7-1500 project → compile and download to a PLCSIM instance.
3. Open TIA Portal V15 → open the same project (must be upgraded — accept the prompt).
4. Open TIA Portal V15.1 → verify it opens the upgraded project without error.
5. Open Automation License Manager → confirm all three TIA Portal licenses and the SIMATIC Manager license are visible.
6. Open Services (services.msc) → confirm ALM, S7TraceServiceSvr, and TIA Portal Server services start automatically.
7. Run a project backup via TIA Portal → Project → Archive → confirm the .zap15 file is generated.
8. Run sfc /scannow in an elevated command prompt to verify Windows component integrity.

Field-Proven Caveats

• Project upgrade is one-way. Once a V14 project is upgraded to V15.1 it cannot be opened in V14 again. Keep an exported archive of every legacy project before opening it in a newer version.
• Hardware support catalogs differ per version. A V14 SP1 catalog does not contain firmware images for S7-1500 CPUs released after 2017. Use the HSP (Hardware Support Package) that ships with each TIA Portal version.
• WinCC Comfort/Advanced projects require matching WinCC versions on the HMI panel. A V15.1 engineering station cannot deploy a V14 project to a panel whose runtime version differs.
• Startdrive mismatches between V14 SP1 and V15.1 cause SINAMICS G120 parameter downloads to fail silently. Always pair Startdrive with its parent TIA Portal version.
• License Server redundancy across VMs: configure ALM as a network license server in one VM only and point the other VMs to it as \<host>\Siemens\Licenses.

Notes on Future-Proofing

If the requirement to support multiple TIA Portal versions is permanent:

• Adopt a VM-per-version standard. Each VM is a self-contained engineering environment with a dedicated license.
• Track the TIA Portal version matrix published in the Siemens Support Knowledge Base for new release announcements and discontinued support dates.
• Centralize project storage in TIA Project Server (multi-user) or in a version-controlled repository using the Openness API.
• Schedule a monthly V15.1 backup verification — project archives older than six months frequently contain references to deleted HSP versions.

FAQ