Resolving TIA Portal V11 SP2 Version Error on SP1 Upgrade

Problem Statement

A maintenance engineer attempts to upgrade a development workstation running TIA Portal V11 Basic Service Pack 1 on Windows XP Professional SP3 to V11 Service Pack 2. The installer aborts with a generic version error and refuses to commit the update. Re-launching the SP2 setup with administrator rights produces the same dialog. Because TIA Portal V11 is a multi-package suite (Basic / Professional / a combined multi-CD image), the installer performs a strict version-compatibility check against the installed components, and any mismatch produces the reported fault.

The error manifests under several guises:

• Setup wizard halts immediately after the welcome screen and reports an incompatible installed base.
• Setup proceeds past the prerequisites check, then rolls back silently and reverts to the SP1 state.
• The installer log under %TEMP%\Siemens\Setup.log shows the token 0x80091007 (hash mismatch) or 0x80004005 (unspecified component error).

The root cause is virtually never the SP2 download itself; it is the detection logic that walks the registry keys under HKLM\SOFTWARE\Siemens\Automation\PortalV11\ and the parallel HKLM\SOFTWARE\Wow6432Node\Siemens\Automation hive on 64-bit operating systems. If the original SP1 install was a Basic edition and the user accidentally mounts the Professional upgrade image (or vice-versa), the comparator immediately fails.

TIA Portal V11 Architecture Overview

TIA Portal V11 is engineered as a unified engineering framework for the SIMATIC family. The install media shipped in three coordinated product lines that must never be cross-mixed:

Service Pack 2 was published by Siemens as a hot-fix collection consolidating the engineering improvements listed in the V11 SP2 release notes, including expanded S7-1200 firmware (V4.0), bug fixes for the project comparator, and the first iteration of the SINAMICS Startdrive plug-in. SP2 is a product-line-locked update: the SP2 update for STEP 7 Basic cannot be installed on top of STEP 7 Professional SP1, and vice-versa.

For official catalog and ordering data refer to the Siemens Industry Online Support entry Entry ID 56750498 – TIA Portal V11 SP2 download collection.

Edition Compatibility Matrix

When the upgrade image and the installed base do not match, the setup engine returns the generic error to avoid silently corrupting the registry-driven project database. The diagnostic information written to the log file is the only reliable way to confirm which side is wrong.

Windows XP SP3 Prerequisites

TIA Portal V11 SP2 supports the following operating systems at the time of release:

• Windows XP Professional SP3 (32-bit only)
• Windows 7 Professional / Enterprise / Ultimate SP1 (32-bit and 64-bit)
• Windows Server 2008 R2 (64-bit) for engineering stations

Windows XP Home Edition is not supported and will produce setup errors. On a Windows XP Professional SP3 workstation the engineer must confirm that the following runtime components are installed before launching the SP2 update:

Root Cause Analysis

The "version error" reported by the SP2 setup is a catch-all returned by the Siemens proprietary bootstrapper Siemens.Automation.Portal.Setup.Launcher.exe. After analysis of the supported log files, the failure falls into one of five categories:

1. Edition mismatch (most common). The launcher reads the registry key ProductType under the PortalV11 hive. A value of Basic rejects a Professional update payload and vice-versa. This is what the original reporter was encountering.
2. Incomplete prerequisite chain. One of the redistributables (notably MSVC++ 2005 SP1) is older than what the SP2 build expects. The setup returns a generic version error instead of the explicit dependency failure when the dependency is shared.
3. Corrupted SP2 media. A partial download of the SP2 package (often the result of resumable downloads interrupted by proxy timeouts) leaves a file with a valid filename but a corrupt internal manifest. Re-downloading the missing files (as one engineer reported with "parts of SP2") resolves the hash mismatch.
4. Multi-language contamination. The launcher also reads InstallLanguage. A German SP1 with an English SP2 update is rejected. The full language pack must match across the entire V11 chain.
5. Concurrent antivirus / file-lock conflict. Real-time scanners holding the S7DOS.exe or S7wnasvc.exe processes prevent the in-place replacement of the underlying binaries. The setup therefore rolls back the version commit.

The original post did not include the setup log contents, so the exact category cannot be confirmed without inspecting %ProgramFiles%\Siemens\Automation\Portal V11\Log\Setup.log and the corresponding %TEMP%\SiemensInstaller*.log. The decision tree below is the appropriate diagnostic sequence.

Diagnostic Decision Tree

Pre-Update Preparation

Before any installer is launched, perform the following housekeeping. Skipping these steps is the single largest contributor to the version error and to the post-update performance complaints (PC slow-down, restart prompts) that other engineers have reported.

1. Snapshot the workstation. Use System Restore on Windows XP or a full disk image. SP2 modifies more than 4000 files; the only safe rollback path is a disk-level snapshot or a saved VM state.
2. Archive projects. Close TIA Portal and copy %USERPROFILE%\Documents\Automation and any project libraries to an external volume. TIA Portal V11 projects are backward-compatible but the SP2 save-format introduces minor schema changes that cannot be undone without V11 SP2.
3. Disable antivirus real-time scan. The setup replaces binaries under %ProgramFiles%\Siemens. McAfee, Symantec, and Kaspersky historically flag S7wnasvc.exe and AlmTrace.dll. Either disable real-time scanning or add the Siemens directory to the exclusion list.
4. Stop the S7DOS service. net stop s7dos from an elevated command prompt. This prevents the live PLC routing service from holding files that the setup needs to overwrite.
5. Free at least 8 GB on the system drive. SP2 stores the rollback archive in %ProgramFiles%\Siemens\Automation\Portal V11\Setup\Rollback.
6. Confirm the exact installed base. Open Control Panel → Add or Remove Programs and look for one of the following display strings:

The original poster identifies the installation as "TIA Basic SP1" which corresponds to the first row – STEP 7 Basic V11 SP1. The matching SP2 image is therefore the STEP 7 Basic V11 SP2 Update, not the Professional update.

Step-by-Step Resolution Procedure

The procedure below assumes the installed base is SIMATIC STEP 7 Basic V11.0 SP1 on Windows XP SP3 and the goal is to reach V11 SP2. Adjust paths and product names accordingly for Professional editions.

1. Acquire the correct SP2 image. Log in to the Siemens Industry Online Support portal and navigate to Entry ID 56750498. Filter on STEP 7 Basic V11 SP2. The download is delivered as a 7-zip self-extracting archive, typically 1.4 – 1.9 GB. Use the Siemens download manager so the package integrity hash (SHA-1) is verified client-side.
2. Verify the archive hash. After download, right-click the .exe archive → Properties → Digital Signatures. The signer must be Siemens AG, DI PA. If the signature is invalid or absent, the SP2 installer will produce hash mismatch errors during MSI extraction.
3. Extract locally. Run the self-extractor to D:\Setup\TIAV11_SP2\. Do not extract to a UNC path or a drive with compressed NTFS attribute.
4. Remove residual installer state. Delete the directories %ProgramData%\Siemens\Setup and %TEMP%\SiemensInstaller*. These caches are left over from interrupted SP1 installs and frequently trigger the version comparator to read a stale product type.
5. Open an elevated command prompt. On Windows XP this is runas /user:Administrator cmd. The launcher writes to HKLM and requires administrative privileges.
6. Launch the bootstrapper. Execute D:\Setup\TIAV11_SP2\Start.exe. The welcome screen must identify the installed product as SIMATIC STEP 7 Basic V11.0 SP1. If the product name is blank or shows a different edition, abort and re-check the archive.
7. Accept the license and proceed. Do not change the install path. The TIA Portal V11 architecture stores absolute paths in the registry; changing the directory after SP1 will corrupt the project database.
8. Monitor the file replacement. The SP2 package replaces roughly 4 200 files in %ProgramFiles%\Siemens\Automation. Expect 12 – 25 minutes on a Windows XP workstation with a 5 400 rpm mechanical disk; 4 – 8 minutes on an SSD-equipped Windows 7 fallback machine.
9. Reboot when prompted. The setup requires a single reboot to commit the registry hive and to release file locks on S7wnasvc.exe. After the reboot the V11 SP2 binaries are live.
10. Verify the install. Open SIMATIC Manager → Help → About and confirm the splash screen shows STEP 7 Basic V11.0 SP2 (Build xxxxx).

Alternative Recovery – Clean Reinstall

If the SP2 update continues to fail after two attempts, the cleanest path is a full reinstall on a freshly imaged Windows XP partition. This avoids the registry corruption that engineers reported in the form of repeated "restart or close" prompts.

1. Use the V11 SP1 installation media to perform a clean install of STEP 7 Basic V11 SP1.
2. Apply the V11 SP2 update immediately while no project files exist and no antivirus real-time scanning is active.
3. Restore the project archive to %USERPROFILE%\Documents\Automation.
4. Open one project as a smoke test, perform a download to a PLC simulator (PLCSIM V11 is not part of Basic; use a real S7-1200 or the integrated simulation in WinCC Basic), and confirm the version label on the device.

Engineers who reported PC slow-down after a partial SP2 install were typically suffering from a corrupted .NET assembly cache (%WINDIR%\assembly on Windows XP). The remediation is %WINDIR%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i followed by a clean install of the SP2 package.

Known Issues and Limitations

SP2 was an interim release; the issues documented by Siemens in the release notes include:

Engineers anticipating SP3 were indeed correct: Siemens published TIA Portal V11 SP3 in 2013, and later the major release V12, which obsoletes the Windows XP code path entirely. V12 requires Windows 7 SP1 or later. The direct upgrade path from V11 SP2 to V13 (or later) is supported by the Siemens migration tool documented in Entry ID 82116931 – Migrating TIA Portal projects.

Post-Update Verification

1. Open TIA Portal and create a new S7-1200 station. The default firmware target must be V4.0 (introduced in SP2). Older firmware targets (V1.0, V2.0, V3.0) remain selectable for backward compatibility.
2. Compile a sample program and confirm that the build completes in less than 10 seconds on the workstation.
3. Connect to a physical S7-1200 CPU 1214C DC/DC/DC (6ES7214-1AG40-0XB0) over PROFINET and download the project. The "Download to device" wizard should now show the SP2 build identifier in the device diagnostics.
4. Open the project comparator against a known-good V11 SP1 reference and confirm the comparator recognizes the schema change without flagging false differences.
5. Check that Start → Programs → Siemens Automation → License Management still reports the active license. V11 used a node-locked license; SP2 does not re-prompt for activation but does re-write the license cache.

For engineering stations that need to communicate with SIMATIC HMI Basic Panels (KTP400, KTP600, KTP1000) the WinCC Basic component is updated in lockstep. Confirm the panel image version under HMI → Panel → Diagnostics → Version matches the expected V11 SP2 build.

Migration Path Beyond V11 SP2

Windows XP reached end-of-life in April 2014. Microsoft security patches are no longer issued, and Siemens ceased support for the TIA Portal V11 line on the same schedule. Engineers maintaining SP2 installations today face a forced migration. The recommended sequence is:

1. Upgrade the engineering station to Windows 10 IoT LTSC 2019 (32-bit is no longer required).
2. Install TIA Portal V16 (the last version supporting direct migration of V11 SP2 projects).
3. Use the migration tool to convert V11 SP2 projects. Expect renaming of certain SCL keywords (notably STR became STRING in V14) and the automatic conversion of old-style data blocks to the optimized DB format.
4. Perform a full FAT on the migrated project before commissioning on a live process.

For older S7-300 / S7-400 programs created in V11, the migration must go through V13 or V14 first; V16 cannot read pre-V11 projects directly.

FAQ