Troubleshooting TIA Portal V12 Install Failure on Windows XP SP3

1. Problem Definition: TIA Portal V12 Setup Fails on Windows XP SP3

When launching the TIA Portal V12 Professional setup on a Dell laptop running Windows XP Professional SP3, the installer halts with a "Failed Prerequisite" dialog before the welcome screen appears. The user typically confirms that the laptop appears to satisfy every published requirement, has administrative rights, and passes the Windows Installer version check, yet the prerequisite routine refuses to advance. This article documents the root causes, the diagnostic procedure to identify the exact failing check, and the resolution paths available on XP SP3 versus the more durable migration to a supported operating system.

The Failed Prerequisite message is generated by the Siemens Setup.exe bootstrapper, not by Windows Installer itself. The bootstrapper runs a pre-flight pass against a manifest file (PrerequisiteCheck.xml or equivalent *.cab payload on the installation media) and blocks the main MSI if any single check returns FAIL. The dialog rarely identifies the specific check, so the technician must isolate it manually.

2. TIA Portal V12 System Requirements (Reference Matrix)

The following table summarizes the published hardware and software requirements for TIA Portal V12 / V12 SP1 Professional. Cross-check the host against each row before assuming a missing redistributable is to blame.

3. Root Cause Analysis

The "Failed Prerequisite" symptom on Windows XP SP3 typically traces to one of the following root causes, in order of frequency:

1. Unsupported operating system family. The bootstrapper rejects Windows XP outright. This is the most common cause and produces the message even when every visible check appears to pass.
2. Insufficient User Account Control (UAC) elevation. Although XP does not have UAC in the Vista/7 sense, the setup requires that the active account be a member of the local Administrators group with the "Allow programs to run as administrator" right intact.
3. Missing or downlevel Windows Installer. XP SP3 ships with Windows Installer 4.5 in many OEM images, but earlier 3.x versions will trigger the prerequisite check. MSI 4.5 redistributable WindowsInstaller-KB942288-v4-x86.exe must be installed manually.
4. Missing .NET Framework 4.0 redistributable. The full-profile dotNetFx40_Full_x86.exe must be present before TIA Portal setup is launched.
5. Corrupted installation media. Damaged sectors or interrupted download produce a partially extracted PrerequisiteCheck manifest. Verify by comparing SHA-1 of Setup.exe against the value printed in the DVD readme.
6. Third-party security software intercepting the bootstrapper. Some antivirus suites quarantine Setup.exe silently. Check quarantine logs.

4. Decoding the "Failed Prerequisite" Dialog

To identify the exact check that failed without re-architecting the installer, extract a verbose setup log:

1. Open cmd.exe with administrative rights.
2. Change to the DVD root or extracted setup directory.
3. Execute the following command:

   Setup.exe /debug "C:\Temp\TIA_Portal_V12_Install.log" /silent

4. Open the resulting log in Notepad and search for the token PREREQ_FAILED or OSCheck.

The log will reveal one of the following lines, which uniquely identifies the failing check:

5. Pre-Installation Checklist

Before invoking Setup.exe, confirm each item on the host:

1. Operating system: winver.exe returns "Windows XP Service Pack 3".
2. User account: Open lusrmgr.msc, expand Groups, open Administrators, confirm the current user is a member.
3. Windows Installer version: Run msiexec /?. Line 2 reports the internal version; V12 requires 4.5 or higher.
4. .NET Framework versions installed: Inspect %WINDIR%\Microsoft.NET\Framework. Look for v4.0.30319 directory.
5. Free disk space: dir C:\ /-c reports bytes free; require at least 15 GB to accommodate extraction.
6. Temp directory writable: echo test > %TEMP%\test.txt returns without error.
7. DVD integrity: Right-click DVD drive → Properties → Tools → Check Now with both options enabled.
8. Antivirus: Temporarily disable real-time scanning or add an exclusion for the DVD root and C:\Temp.

6. Step-by-Step Resolution Procedure

The following sequence resolves the symptom in approximately 90% of field cases. Run the steps in order, re-launching Setup.exe after each major item until the welcome screen appears.

Step 1 - Verify Administrative Context

1. Log in with the local Administrator account or a domain account that is a member of the local Administrators group.
2. Open cmd.exe and type net localgroup administrators to confirm membership.
3. If running from a standard user account, use Run as... (hold Shift, right-click Setup.exe, select Run as different user) and supply Administrator credentials.

Step 2 - Install Windows Installer 4.5

1. Download WindowsInstaller-KB942288-v4-x86.exe from the Microsoft Update Catalog.
2. Execute the package; it self-installs and prompts for reboot.
3. Reboot and verify with msiexec /? that version 4.5 is reported.

Step 3 - Install .NET Framework 4.0

1. Download dotNetFx40_Full_x86.exe from the official Microsoft Download Center.
2. Run the installer elevated.
3. Confirm installation by checking %WINDIR%\Microsoft.NET\Framework\v4.0.30319\clr.dll exists and reports version 4.0.x.

Step 4 - Re-launch the Bootstrapper Elevated

1. Right-click Setup.exe on the DVD.
2. Select Run as... (XP) or use Shift+right-click → Run as different user.
3. Supply Administrator credentials.
4. Wait for the bootstrapper to extract prerequisite CABs into %TEMP%; this can take 3 to 5 minutes on XP-class hardware.

Step 5 - Enable Compatibility Mode (Conditional Workaround)

If the OS check still fails on XP even after admin elevation, force the bootstrapper to evaluate as Windows 7 by setting the NT compatibility shim:

1. Right-click Setup.exe → Properties → Compatibility tab.
2. Enable Run this program in compatibility mode for: and select Windows 7.
3. Check Run as administrator (this option exists on XP when the compatibility tab is invoked; the underlying token is still standard XP elevation).
4. Click Apply and re-launch.

7. Manual Prerequisite Verification Commands

Use these one-liners in cmd.exe on Windows XP SP3 to validate each prerequisite individually before re-running the Siemens setup:

REM --- Windows version ---
ver

REM --- Windows Installer version ---
msiexec /? | findstr /i "version"

REM --- .NET versions installed ---
dir /b /ad "%WINDIR%\Microsoft.NET\Framework"

REM --- Administrator group membership ---
net localgroup administrators

REM --- Free disk space on C: ---
dir C:\ | findstr /i "bytes free"

REM --- System root writable ---
echo test > "%WINDIR%\test_write.tmp" && del "%WINDIR%\test_write.tmp" && echo OK

REM --- Required DCOM and RPC services ---
sc query RpcSs | findstr STATE
sc query DCOMLaunch | findstr STATE

Each command should return a positive indication. If any single command reports failure, address it before re-attempting the Siemens installer.

8. Administrator Rights Deep Dive on Windows XP

Windows XP does not include User Account Control in the same form as Windows Vista and later, but it does enforce a related concept via the Secondary Logon service and the RunAs capability. The Run as administrator option seen on later operating systems is replaced on XP by the Run as... context menu item, which appears only when the seclogon service is started and the user is not the built-in Administrator.

To confirm that the active token has administrative privilege at the level required by the Siemens bootstrapper:

1. Open cmd.exe.
2. Execute whoami /groups | findstr /i "S-1-5-32-544". The S-1-5-32-544 SID is the BUILTIN\Administrators alias. A match in the Enabled column confirms full membership.
3. If the SID is listed only as Disabled, the user is part of the group but lacks the active privilege. Log off and log back in, or use Run as... to elevate.

The Siemens bootstrapper calls IsUserAnAdmin(), which returns TRUE only when the active token has the Administrators group enabled. A user who is a member but currently running with a filtered token (a state possible on XP when Fast User Switching or RunAs is involved) will receive a FALSE and the prerequisite check will fail.

9. Windows Installer Repair and Reset

If the prerequisite check fails with a msi subsystem error after the bootstrapper advances, perform a clean reset of the Windows Installer service on XP:

1. Stop the service: net stop MSIServer
2. Reregister the binaries:

   msiexec /unreg
   msiexec /regserver

3. Restart the service: net start MSIServer
4. Delete the %TEMP% contents to clear any cached MSI transform.
5. Re-launch the Siemens setup.

10. Verification and Post-Install Checks

After the install completes successfully, perform the following functional verifications to confirm the platform is healthy:

1. Launch TIA Portal V12 from Start → Siemens Automation → TIA Portal V12. The Portal view must load within 30 seconds on a Core i3 class machine.
2. Open Project → New and create a test project. The system should accept the project path and create the .ap12 file without warnings.
3. Add an S7-300 device and confirm that the device catalog populates. This validates the GSD/EDD cache is intact.
4. Start the Online → Accessible nodes scan to validate the S7-Online interface initialized.
5. Close the application and check Event Viewer → Application for any Siemens-sourced errors during startup.

11. Migration Path: When to Abandon Windows XP

If after applying all the steps above the prerequisite check still reports failure, the operating system is the only remaining cause. Windows XP SP3 is below the supported OS floor for TIA Portal V12, and no shim or registry hack can make the engineering environment stable. Plan a migration to one of the following:

For long-term support, deploy the engineering station on Windows 7 SP1 64-bit with the latest Siemens automation license manager and at least 8 GB of RAM. Reserve Windows XP SP3 hosts for legacy programming of pre-V11 SIMATIC projects using the legacy STEP 7 V5.5 toolchain.

12. Troubleshooting Matrix

FAQ