TIA Portal V15.1 Update 4 Installation Fails: Root Cause and Fix

Problem Overview

TIA Portal V15.1 Update 4 — the cumulative HSP roll-up for the V15.1 engineering platform — refuses to install cleanly on a Windows 7 Professional SP1 64-bit workstation that already hosts TIA Portal V13. The Siemens Installer Assistant (SIA2.exe) trace ends with Intermediate ExitCode after execution queue : 1603 - Installation failed and eight logged errors, even though the TIA Portal overview subsequently reports V15.1 Update 4 as installed. The dual outcome — partial installer failure plus a registry state that looks healthy — is the signature of a half-completed MSI transaction that has rolled the patch files back while leaving registry metadata pointing at the new build.

This article walks an automation engineer through the exact failure mode, the prerequisite matrix that TIA Portal V15.1 Update 4 enforces, and the recovery procedure that avoids a full workstation rebuild. The approach is field-tested against Windows 7 SP1 (build 7601), Windows 10 LTSC 2019, and Windows 10 LTSC 2021 images with mixed V13 / V15.1 / V16 prior installations.

Error Chain Decoded

Two distinct failure signatures appear back-to-back in the trace and both must be cleared for a clean install. The chain is short but every entry matters:

ERROR_INSTALL_SOURCE_ABSENT is Windows Installer error code 1612, documented at Microsoft Learn: MSI Error 1612 and listed in the broader MSI error code reference. The MSI engine raises 1612 when the path embedded in a product or patch manifest cannot be reached through the Win32 file system layer. The seven repeats in the trace come from each SetupUnit in the CHANGES list that was queued for patching — PE_Upd, SIMATIC_Upd, IECPL_Upd, HM_AllEditions_Upd, HM_NoBasic_Upd, ES_Upd, WinCC_TR_Mandatory_Upd, WinCC_TrC_All_Upd, WinCC_TrC_CAP_Upd, HMIRTMV11_Upd, RT_Adv_SIM_Upd — each of which falls back to Skip Patch AddLocal the moment the source resolution fails.

The first failure at 19:14:02 is from the ClassicComponent worker, the legacy Setup Manager wrapper used by older TIA Portal and WinCC products. When its OnWorkerCompleted callback receives "unknown error", the setup rolls the update back even though the manifest reads "Complete" downstream — that is why TIA Portal's Help → About dialog later shows V15.1 Update 4 even though the installer reported failure.

Root Cause

Three conditions converge to produce this symptom. They can occur independently or together, but each must be ruled out before the installer is re-run.

1. Patch source path is unresolved. The bundle path C:\SIMATIC TIAP V15.1 UPD4\InstData referenced in the SIA command line cannot be located by MSI for one of the following reasons: the directory was on a removable drive that was unmounted, the path exceeds the Win32 MAX_PATH limit once MSI temp-folder expansion is applied, the archive was extracted into a deep or permission-restricted folder, or the source folder was deleted before MSI's deferred custom actions fired.
2. Legacy ClassicComponent prerequisites missing. The first ERROR_BLOCK in the log specifically calls out the "Automation Software Updater" ClassicComponent. TIA Portal V15.1 Update 4 ships a refreshed ClassicComponent stub that requires the previous V15.1 base install to be in a state where the legacy Setup Manager can still discover its product database. A side-by-side TIA Portal V13 install splits the product database and can mask the V15.1 base install from the legacy Setup Manager.
3. Pending reboot from a previous failed update. The installer registers files for rename or delete on reboot and then refuses to commit any further patches until that pending rename is processed. A "soft" reboot that only signs out or sleeps does not satisfy the PendingFileRenameOperations registry flag, and the next install silently rolls back.

Prerequisite Verification

Before the installer is run again, validate every prerequisite on the target workstation. TIA Portal V15.1 Update 4 inherits the base prerequisites of the V15.1 release plus the prerequisites of every HSP shipped inside the update manifest.

Resolution Procedure

Work the following steps in order. Do not advance until the current step is verified.

Step 1 — Full Power-Cycle Reboot

A documented workaround for the MSI FileRenameOperations flag is to fully power-cycle the workstation multiple times. Implement it as a clean power-cycle rather than a soft restart.

1. Open cmd.exe as Administrator.
2. Execute shutdown /r /t 0 /f. The /f flag terminates running processes without prompting, which is required for MSI cleanup.
3. After the workstation returns, verify with reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations. A clean machine returns ERROR_FILE_NOT_FOUND.
4. Open Task Manager → Details and confirm no SIA2.exe, Setup.exe, or msiexec.exe instances remain. Kill any that are present with taskkill /F /IM <process>.

Step 2 — Re-Stage the Update on a Local NTFS Volume

1. Download the TIA Portal V15.1 Update 4 package from Siemens Support entry 109763890 if the original archive is not already present.
2. Verify the integrity of the archive before extracting — compare the SHA-256 hash against the value published on the Siemens Support entry. A truncated download silently produces the same ERROR_INSTALL_SOURCE_ABSENT the next time SIA runs.
3. Copy the contents to a folder on a fixed NTFS volume: not a network share, not a USB drive, and not a OneDrive/SharePoint-synced folder. Acceptable targets: C:\TEMP_TIA\UPD4, D:\Install\TIAP_UPD4. Unacceptable: a path deeper than ~80 characters or any path containing spaces in the parent directory.

Step 3 — Clear Residual Patch Markers with Repair

Failed MSI transactions leave the product in a "source resolver points to non-existent path" state. Use the installer itself to clean this state, not manual registry edits.

1. Open appwiz.cpl from the Run dialog.
2. Locate every entry that begins with SIMATIC or Siemens.
3. Right-click → Repair (not Uninstall). The Repair operation re-resolves the source path against the staged update folder from Step 2.
4. If Repair prompts for a source, point it at C:\TEMP_TIA\UPD4\InstData — not the InstData\... subfolder, not the original archive location.

Step 4 — Disable Antivirus Real-Time Scanning for the Installer

Several AV products quarantine or rename the temporary *.tmp and *.msp files that SIA creates inside %LOCALAPPDATA%\Temp during the patch phase. When that happens, the patch phase cannot find its source files and reports ERROR_INSTALL_SOURCE_ABSENT even though the files were originally present. Windows Defender, McAfee Endpoint Security, and Trend Micro OfficeScan have all been observed to produce this behaviour.

1. Open the AV product console.
2. Add an exclusion for the staging folder from Step 2 and for %LOCALAPPDATA%\Temp.
3. Suspend real-time scanning for the duration of the install — typically 10 to 25 minutes for a full V15.1 Update 4 transaction on a workstation with SSD storage.
4. Re-enable real-time scanning only after the TIA Portal Help → About dialog confirms the new build.

Step 5 — Re-Run the Installer as Administrator

1. Right-click Start.exe (or Setup.exe) in C:\TEMP_TIA\UPD4.
2. Choose "Run as administrator".
3. When prompted for the install language, select the same language that was used for the V15.1 base install — the installer enforces language consistency across patch levels.
4. Accept the default install path C:\Program Files\Siemens\Automation.
5. Wait for the installer to reach the "SetupSummary" stage. A clean install returns ExitCode 0.

Step 6 — Read the New Trace

The new SIA2.exe trace lives at %LOCALAPPDATA%\Siemens\Automation\Siemens Installer Assistant\Logs. Search the file for ERROR or FAIL!. A clean install shows:

• Every SetupUnit ends with Complete — including the previously failing Automation Software Updater.
• The final Intermediate ExitCode after execution queue reads 0 or is omitted because the installer exits through the normal success branch.
• No HspInstallWorker::ApplyUpdates entries referencing ERROR_INSTALL_SOURCE_ABSENT.

Side-by-Side V13 and V15.1 Considerations

Running TIA Portal V13 and V15.1 in parallel on the same Windows image is supported by Siemens with documented constraints. The installer enforces these by reading HKLM\SOFTWARE\Siemens\Automation\InstalledSoftware\TIA Portal and the per-product UpdateLevel registry values:

If the workstation has accumulated partial installs (for example, V13 + V15.1 base + V15.1 Update 4 failures repeated three times in a row), the safest recovery path is: uninstall TIA Portal V13 first through appwiz.cpl, then uninstall V15.1, then reboot, then install V15.1 Update 4 directly on a clean Windows image.

Virtualization as a Long-Term Strategy

TIA Portal V15.1, V15.1 Update 4, V16, V17, and V18 each install their own ClassicComponent, MSO, and SQL Server instances. Side-by-side upgrades on a physical workstation accumulate over time and eventually break the patch chain. Siemens supports running each major release in a dedicated virtual machine. The reference configuration:

Take a clean snapshot immediately after the first successful install and a second snapshot immediately after Update 4. Future updates either succeed against the snapshot or fail safely without corrupting the base workstation. Pass-through USB for the Siemens CP5711 or CP5512 programming adapter is supported in all three hypervisors above with documented driver assignments.

Verification

1. Open TIA Portal.
2. Help → About → confirm "TIA Portal V15.1 Update 4" is shown.
3. Project → New → confirm the device catalog loads without the "Catalog cannot be loaded" warning.
4. Open an existing project that uses an S7-1500 CPU. Confirm the online → "Go online" operation completes without the "The firmware version of the connected device does not match the project" error.
5. Check reg query "HKLM\SOFTWARE\Siemens\Automation\InstalledSoftware\TIAP\V15.1" /v UpdateLevel — it should read 4.
6. Validate the new trace ends with ExitCode 0 and contains no ERROR entries.

FAQ