Installing Multiple TIA Portal Versions V16 and V17 Compatibility

Problem Description: TIA Portal V16 and V17 Coexistence Error

When attempting to install TIA Portal V17 on a workstation that already has TIA Portal V16, the Setup.exe wizard returns the blocking error: "A more recent version of TIA Portal is already installed. The existing version must be uninstalled before installation can continue." The exact symptom reported on Siemens Support entry 109784440 is a hard installer stop that refuses to proceed with the V17 setup when V16 components of the same product line are detected in %ProgramFiles%\Siemens\Automation.

The dialog does not differentiate between the two main product stacks (STEP 7 vs. WinCC), so the engineer must understand the underlying edition architecture before deciding which TIA components can coexist and which must be uninstalled, virtualized, or moved to a separate workstation.

Root Cause: MSI Shared Components and Edition Lock

TIA Portal is not a single installer. It is a family of MSI packages that share common runtime DLLs, SQL Server instances, SIMATIC Help Server components, and license manager services. Each major product line uses a unique UpgradeCode GUID:

• STEP 7 Basic / S7-1200/1500 toolset
• STEP 7 Professional (includes STEP 7 Basic)
• WinCC Comfort / Advanced (HMI engineering for Comfort Panels and Runtime Advanced)
• WinCC Professional (SCADA configuration for WinCC Runtime Professional)
• PLCSIM, Startdrive, S7-PCT, Safety (optional add-ins)

The Windows Installer engine treats packages sharing an UpgradeCode as mutually exclusive major upgrades. When the V17 Setup reads the UpgradeCode of the already-installed V16 STEP 7 Professional product, it concludes a major version upgrade is required and aborts with the conflict message.

WinCC Professional has an additional constraint: it bundles a full SQL Server instance and WinCC Runtime libraries that are bound to the major TIA version. Only one WinCC Professional edition may exist on a system at a time, regardless of TIA version (V16 or V17).

TIA Portal Edition Architecture

Before selecting an installation strategy, identify which product stack you need. The diagram below summarizes the installable components and their coexistence behavior on Windows 10/11 64-bit or Windows Server 2019/2022.

Coexistence Matrix: Which TIA Versions Live Together?

The matrix below summarizes the supported combinations of TIA Portal major versions on a single physical host. Versions not listed are mutually exclusive.

Project Server Coexistence: An Important Distinction

Beginning with V14, Siemens introduced the TIA Portal Project Server as a centralized multi-user engineering backend. Per the official installation documentation, "Up to TIA Portal V18, it is possible for several versions of the project server that use different project versions of TIA Portal to be installed on the same computer." This applies only to the project server service, not to the TIA Portal client.

Therefore, if your requirement is multi-user engineering across V16 and V17 projects, you can install the project server components from both versions side-by-side on the same server host (for example, Windows Server 2019 Standard), but the engineering client workstations still need to follow the coexistence matrix above. Reference: Installing a TIA Project Server (Siemens Docs).

Solution Path 1: Sequential Install (Single Edition Strategy)

The simplest path is to keep only one TIA Portal major version on the workstation and migrate projects forward. Use this when:

• You have one primary project version and will retire the older version.
• The hardware budget does not allow multiple VMs or workstations.
• SQL Server (instance WINCCINSTANCE) and license server (Automation License Manager) are already configured for one version.

Steps:

1. Open Control Panel → Programs and Features and uninstall all V16 entries beginning with Siemens Automation.
2. Stop the service S7TraceServiceSx and Siemens PLCSim Service via services.msc if present.
3. Delete residual folders: %ProgramFiles%\Siemens\Automation\V16 and %ProgramData\Siemens\Automation V16 entries.
4. Reboot to clear pending file locks.
5. Insert/mount TIA V17 media (or use the online installer from Siemens Support 109784440) and run Start.exe → Setup.
6. Select the appropriate product stack (STEP 7 Professional, WinCC Advanced, etc.).
7. Reboot when prompted; TIA V17 will now operate standalone.

Solution Path 2: Split Edition Strategy (V16 + V17 HMI Coexistence)

Many commissioning engineers need STEP 7 V16 (for legacy V16 project files) and WinCC V17 on the same machine to update HMI screens without migrating the PLC code. This is fully supported because STEP 7 and WinCC are different MSI families.

1. Confirm V16 STEP 7 Professional is already installed.
2. Run the TIA V17 Setup.exe and select only WinCC Comfort or WinCC Advanced (NOT WinCC Professional).
3. The installer will detect STEP 7 V16 but will not block because the HMI product stack has a different UpgradeCode.
4. After installation, the TIA Portal start menu shows two entries: TIA Portal V16 (STEP 7) and TIA Portal V17 (WinCC). Each opens a separate portal instance.
5. Verify both by creating a test project: V16 S7-1500 program compiles, V17 Comfort Panel screen downloads to a TP900.

Solution Path 3: Virtual Machine Deployment

When the project absolutely requires two full TIA Portal installations of different major versions on engineer-accessible machines, deploy a Windows VM.

Recommended VM template:

1. Allocate a fixed-size virtual disk (do not use dynamic expansion — TIA Setup writes large temporary blocks that fragment dynamic VHDs).
2. Enable nested virtualization if running PLCSIM Advanced inside the VM.
3. Snapshot the VM immediately after Windows updates complete, before TIA installation — this gives a clean rollback point per TIA version.
4. Map the Automation License Manager USB dongle through USB passthrough; do not rely on network licensing across multiple TIA versions in the same VM.
5. Install only one TIA major version per VM. Cloning the VM and upgrading the clone is safer than in-place version changes.

Solution Path 4: Project Server Multi-Version Setup

For team environments with mixed V16 and V17 projects, set up a TIA Project Server host that supports both versions per the official TIA Project Server installation guide:

1. Install Windows Server 2019/2022 Standard or Datacenter.
2. Install SQL Server 2019 Standard (project server backend). Note: SQL Server Express is sufficient for ≤ 10 GB project databases.
3. Mount the TIA V16 media and run Setup → select Project Server.
4. Reboot and mount the TIA V17 media and run Setup → select Project Server.
5. Both project server services (TIAProjectServerV16 and TIAProjectServerV17) will be present; each listens on a different TCP port (default 8888 vs. 8889).
6. Connect V16 client workstations to the V16 server backend and V17 clients to the V17 server backend.

Disk Space and System Requirements

Verification Procedure After Resolution

After applying any of the solutions above, run this checklist to confirm the installation is healthy:

1. Open TIA Portal V16 from the Start menu. Create a new project, add an S7-1500 CPU, write a small STL/FBD program, and compile. Result: Compilation completed without errors.
2. Open TIA Portal V17 from the Start menu. Create a new WinCC Comfort project, add a KTP700 panel, configure a tag, and run the simulation via Start Runtime. Result: HMI simulator launches and the tag updates.
3. Open Automation License Manager and confirm both V16 and V17 license keys are visible in the search results.
4. Open Control Panel → Programs and Features and verify both versions are listed under separate Siemens Automation entries.
5. Reboot the workstation and re-launch both TIA versions to confirm services start cleanly.
6. Check Windows Event Viewer → Application log for any Siemens-source errors during startup.

Troubleshooting Matrix

Best-Practice Recommendations

• Standardize on one major version per workstation for routine engineering; use VMs only for legacy project migration windows.
• Document the TIA version matrix on your team wiki so commissioning engineers do not waste hours debugging the install rather than the plant.
• Keep the Automation License Manager as the single source of license truth; avoid copying license keys between versions.
• Snapshot VMs before TIA version upgrades; a V17-to-V18 in-place upgrade frequently fails and the cleanest rollback is a VM snapshot.
• Use the project server multi-version pattern when you have > 5 engineers needing concurrent V16/V17 access — it is cheaper and faster than provisioning individual VMs per engineer.
• Avoid WinCC Professional mix: if your work touches WinCC Professional, commit to one version per workstation because the SQL Server instance is bound to the major TIA version.