Troubleshooting TIA Portal V19 Install Errors: .NET and IIS

Problem Overview: TIA Portal V19 Installation Failures

Symptom: TIA Portal V19 Setup terminates mid-run, the splash dialog disappears, and a Siemens installation report is generated. The dialog usually shows a generic message such as "An error has occurred during installation" or "Setup has failed", with no in-context pointer to the failing module. The installer may also leave behind a partial install footprint that prevents subsequent attempts from succeeding until cleaned.

The TIA Portal V19 product stack is larger than V18 and pulls in more than twenty MSI/MSP packages at install time — including the WinCC Runtime components, the OPC UA gateway stack, the SIMATIC Automation License Manager, several .NET-based engineering services, and the S7-PLCSIM V19 add-on packages. Any one of those sub-installations failing will surface as a generic TIA Portal error from the top-level bootstrap because the wrapper Setup.exe cannot enumerate the underlying cause; it can only state that the chain broke.

Two recovery paths exist for this class of failure:

1. Eliminate host prerequisites before retrying — this resolves the majority of reported cases.
2. Read the long-format Siemens installation report and match the reported HRESULT/feature against the documented fix matrix.

Root Cause Taxonomy

The empirical distribution of failed TIA Portal V19 installs in support tickets clusters into seven categories. The first two account for roughly 70–80% of all reported cases.

Install Microsoft .NET Framework 3.5

TIA Portal V19 retains runtime dependencies on .NET Framework 3.5 for legacy code paths in the HMI engineering tools (WinCC Comfort/Professional parts), even though the newer TIA APIs target .NET Framework 4.8. On Windows 10 1909+ and Windows 11 client SKUs, .NET 3.5 is not present by default; it must be enabled as a Windows Feature on Demand. Windows Server 2019/2022 also ships without it by default.

Enable via DISM (recommended)

Open an elevated command prompt and run:

Substitute D:\sources\sxs for the path to your Windows installation media. If no media is mounted, omit /source and let Windows Update supply the payload:

Enable via PowerShell

(Server SKUs only.)

Verify

Confirm the feature state is Enabled:

Confirm registry presence under HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5 with Install = 1.

Install and Configure IIS

TIA Portal V19 requires Internet Information Services (IIS) as a host for the built-in TIA Portal Help Server, the SIMATIC WinCC WebUX/RT Professional web components, and the OPC UA Gateway services. IIS is optional only on machines dedicated to non-HMI projects; for any install that includes WinCC components (which the V19 media carries as part of the unified installer), IIS is mandatory.

Required IIS role services

• Web Server (IIS) — root role
• Common HTTP Features (static content, default document)
• Application Development: CGI, ISAPI Extensions, ISAPI Filters
• Management Tools: IIS Management Console (optional but recommended for diagnostics)
• Windows Authentication (required for OPC UA gateway integrated auth)

Install via Server Manager (Windows Server)

1. Open Server Manager → Add Roles and Features.
2. Select Web Server (IIS).
3. In the Role Services dialog, ensure CGI, ISAPI Extensions, ISAPI Filters, and Windows Authentication are checked.
4. Confirm and complete the wizard. Restart if prompted.

Install via PowerShell (Server)

Install on Windows 10/11 (client)

1. Open Control Panel → Programs → Turn Windows features on or off.
2. Expand Internet Information Services.
3. Expand World Wide Web Services → Application Development Features; check CGI, ISAPI Extensions, and ISAPI Filters.
4. Check Web Management Tools → IIS Management Console.
5. Click OK and allow Windows to download the optional components.

Verify

Confirm each line returns Install State: Installed. A quick HTTP smoke test: browse to http://localhost/. The default IIS7 splash screen confirms the service is reachable on port 80.

Run the Installer with Administrative Privileges

Even on a member of the local Administrators group, User Account Control (UAC) restricts writes to %ProgramFiles%\Siemens\Automation, %ProgramData%\Siemens, and the registry hives used by the Automation License Manager. The TIA installer marks itself as requiring elevation, but the elevation prompt can be silently dropped when triggered from an installer-launched child process, particularly when the media is mounted from a network share or zip extraction.

Procedural fix

1. Right-click Setup.exe in the mounted media root (do not double-click).
2. Select Run as administrator.
3. Confirm the UAC prompt with Yes.
4. Wait for the installer to fully terminate before opening any TIA Portal instance — do not interrupt the installer mid-package.

Persistent fix (for SCADA/engineering workstations in restricted UAC environments)

1. Create a scheduled task that runs Setup.exe with Run with highest privileges.
2. Configure the task to run only when the user is logged on (interactive).
3. Trigger manually from taskschd.msc when needed.

Capture and Read the TIA Setup Log Files

Every TIA Portal V19 install attempt — successful or not — writes a report into %TEMP%\Siemens (typically C:\Users\<user>\AppData\Local\Temp\Siemens). The report exists in two forms:

Extracting the report for support

1. After a failed install, navigate to %TEMP%\Siemens.
2. Sort by Date modified, newest first.
3. Copy SetupReport.log (long format) and the matching SetupReport.txt into a zip before sending.

What to look for in the long format

Useful grep targets (PowerShell example):

Notable patterns and their meaning:

Step-by-Step Clean Installation Procedure

Use this procedure when the installer has failed two or more times in sequence.

Pre-checks

1. Confirm Windows version is on the TIA Portal V19 supported list (Windows 10 21H2+ or Windows 11 22H2+ for the unified installer; Windows Server 2019/2022 supported).
2. Confirm at least 25 GB free on the system drive.
3. Confirm at least 16 GB RAM (32 GB recommended for projects > 100 PLCs).
4. Verify .NET 3.5 and IIS using the commands above.
5. Temporarily disable real-time AV; add the install media mount point and %ProgramData%\Siemens to exclusions.

Clean-up of failed prior attempts

1. Stop the SIMATIC Automation License Manager service: net stop "SIMATIC Automation License Manager".
2. Stop the S7TraceService if present: net stop "S7TraceService".
3. Remove %ProgramData%\Siemens shared data (preserve any licensed dongle data — move rather than delete).
4. Run the official SIMATIC TIA Portal Clean-Up Tool if one is available; otherwise remove any partially installed SIMATIC entries in apps & features.
5. Re-arm .NET 3.5 detection: net stop wuauserv, net start wuauserv to refresh Windows Update features cache.

Install TIA Portal V19

1. Mount the V19 ISO (or extract zip — extract with 7-Zip, not the Windows built-in zip handler which can corrupt MSI streams).
2. Right-click the mounted drive → Open → right-click Start.exe (preferred) or Setup.exe → Run as administrator.
3. In the product picker, select the components required for your engineering scope. For HMI work, leave the WinCC options at default.
4. Choose an installation directory on a drive with no path containing spaces if possible — some legacy MSI transforms still misbehave on paths with multiple spaces.
5. Allow the installer to restart Windows when prompted mid-session. The installer will resume automatically.
6. After final completion, restart the workstation even if the installer does not prompt for it.

Verification Checklist

Run these checks immediately after the install completes:

1. Open TIA Portal V19 from the Start menu. The splash should report V19.0 in the about dialog (Help → About).
2. Verify that the WinCC components (if licensed) appear under the Portal view's installed products: Help → Installed products should list TIA Portal V19, SIMATIC STEP 7 V19, SIMATIC WinCC V19, and optionally S7-PLCSIM V19.
3. Open Automation License Manager; confirm the service is running: sc query "SIMATIC Automation License Manager" must return STATE: 4 RUNNING.
4. Confirm the IIS-based TIA Help server responds: browse to http://localhost:49880/ (default V19 help port). If 49880 fails, the IIS prerequisite may be present but the application pool may not have been registered — re-run the installer in repair mode.
5. Create a blank project and click Compile → Hardware detection on a default S7-1500 to confirm the engineering services start.

Common Error Patterns and Fixes

Escalation to Siemens Support

When prerequisite verification, log analysis, and clean install all fail, escalate. Siemens Industrial Technical Support accepts support requests through the Siemens Industry Online Support portal.

1. Create a support request citing product TIA Portal V19 and the PS catalog entry for the product family.
2. Attach SetupReport.log (long format), SetupReport.txt (short), and a screenshot of the failure dialog.
3. Attach the output of:
   systeminfo · dism /online /get-featureinfo /featurename:NetFx3 · sc query "SIMATIC Automation License Manager"
4. Quote the MSI HRESULT and the component name from the long log so the case lands on the correct specialist team.

Expect first response within one business day for paying customers under a valid SSA; paid priority contracts shorten this considerably.

Edge Cases and Field-Proven Caveats

• Long-path installations: If the install path contains more than 100 characters or has more than two non-adjacent spaces, several legacy WinCC MSIs revert to MSI 1603. Keep paths short (e.g., C:\Siemens\TIAV19).
• Container / VM usage: Cloned VMs occasionally carry duplicate SIDs for the SIMATIC Automation License Manager service. Reset the service account password and re-register: sc delete "ALM_Service", then re-install ALM.
• OS language: TIA Portal V19 is released in English, German, French, Italian, Spanish, Chinese, Japanese, Korean. Mixed-language hosts (English OS, German media or vice versa) install correctly but may report language pack failures in the long log — these are warnings, not fatal.
• Windows 11 24H2 specific: The "Microsoft Defender SmartScreen blocking unknown publisher" dialog can intercept Start.exe if SmartScreen reputation is not yet established. Click More info → Run anyway in that flow; do not disable SmartScreen globally.
• Simatic Box PC and IPC hosts: Siemens-specific WinAC RTX installations may conflict with TIA V19 — contact Siemens Application Support before installing TIA V19 on an active WinAC host.