1. Problem Overview
TIA Portal V19 (also marketed as SIMATIC STEP 7 / WinCC V19, build 19.0.0.x) installation aborts mid-setup with a setup error referencing the URLRewrite2 Microsoft Internet Information Services (IIS) component. The setup log produced by the Siemens Installer Assistant records the failure inside the Setup log folder under C:\ProgramData\Siemens\Automation\Logfiles\Setup, and the graphical installer either rolls back automatically or leaves a partially deployed TIA Portal V19 shell that blocks subsequent reinstalls.
Engineers hit this when the workstation previously hosted older TIA Portal versions (V15.1, V16, V17, V18) and the underlying Windows Server / Windows 10/11 IIS feature set is missing or has been disabled by group policy. Removing TIA V15.1 (because it bundled WinCC Professional) does not enable the IIS features V19 needs - in fact it makes the dependency gap more obvious because V19 reuses the WinCC web components that depend on URL Rewrite.
Symptom signatures:
- Setup terminates during the "Installing SIMATIC components" phase.
- Log file contains entries such as
ERROR: Failed to install URLRewrite2 (x64)orComponent 'IIS_URL_Rewrite' failed with HRESULT 0x80073CF6. - Windows Event Viewer logs
Microsoft-Windows-IIS-W3SVCwarnings because the W3SVC service is not registered. - On retry, the installer reaches the same component and aborts identically, confirming a deterministic dependency issue rather than a transient download fault.
2. Environment and Prerequisites
TIA Portal V19 has hard Windows component dependencies that V16/V18 did not require. Before opening the setup, verify the workstation matches the Siemens TIA Portal V19 readme (Entry ID 109773506) and the installation manual (Entry ID 109817124).
| Component | Required State for TIA V19 | Notes |
|---|---|---|
| OS | Windows 10 IoT Enterprise LTSC 2021 / Windows 11 Pro/Enterprise 22H2+, Windows Server 2019 / 2022 | 32-bit not supported; 64-bit only |
| .NET Framework | 4.8 (built-in on supported OS) | Do not downgrade |
| IIS (World Wide Web Services) | Enabled, with W3SVC running | Common root cause of URLRewrite2 failure |
| URL Rewrite Module 2.x | Installed by setup or by Windows feature | Setup ships the MSI but requires IIS host to register it |
| ASP.NET 4.x | Enabled in IIS | Needed for WinCC WebUX/Server |
| MS Visual C++ Redistributable | 2015-2022 x64 | Both x86 and x64 on 64-bit OS |
| SQL Server | 2019 Express or higher, or bundled instance | TIA installs its own instance by default |
| Free disk | 40 GB+ for full V19 incl. PLCSIM, WinCC, Safety | SSD strongly recommended |
| Administrator account | Local admin or UAC-bypass for setup | Domain admins often lack the IIS policy key |
gpresult /h gpresult.html and inspect Administrative Templates > Windows Components > Internet Information Services to confirm nothing is being forced off.3. Root Cause Analysis
The URLRewrite2 dependency is new in TIA V19 because the WinCC V19 web server runtime, the TIA Help Server, and the new TIA Cloud Connector all sit on top of IIS with URL Rewrite used for HTTPS redirection and reverse-proxy routing. When IIS is not present, the setup calls the rewrite_amd64.msi package shipped under Support\IIS\ in the V19 DVD/ISO, and the package calls iisreset and dism /online /enable-feature /featurename:IIS-WebServerRole under the hood. If those sub-calls fail (because the IIS root feature is disabled), the rewrite MSI returns 0x80073CF6 (ERROR_INSTALL_RESOLVE_DEPENDENCY_FAILED) and the parent TIA setup aborts.
The two scenarios that produce this:
- Fresh Windows 10/11 install where IIS has never been enabled. Default Windows 10 Home/Pro installations ship with IIS off. TIA V16/V17/V18 did not require it; V19 does.
- Previous TIA Portal version was uninstalled in a way that disabled IIS. The TIA uninstaller does not remove IIS, but corporate IT images sometimes strip IIS for security baselines before issuing the laptop, and the V15.1 → V18 upgrades may have masked the missing feature because they only consumed IIS for optional components.
Removing TIA V15.1 (in this case to clear WinCC Professional conflicts) does not change the IIS state. It is the V19 installer's new component graph that exposes the gap.
4. Pre-Installation Cleanup (Required Before Retrying)
Before enabling IIS, kill every residual Siemens process and clear the installer cache. A corrupted previous run will recreate the same error every boot, even after IIS is enabled, because the partial installer loops on the missing component.
4.1 Kill Residual Siemens Processes
Open cmd.exe as Administrator and execute the process terminator:
REM --- SCRIPT 1: Close all Siemens processes ---
taskkill /F /IM s7epa*.exe
taskkill /F /IM TIAP*.exe
taskkill /F /IM Siemens.Automation*.exe
taskkill /F /IM SIA*.exe
taskkill /F /IM Siemens.Simatic*.exe
taskkill /F /IM Framework*.exe
taskkill /F /IM WinCC*.exe
Each taskkill /F /IM with the wildcard terminates every matching process family, including background updaters, the SIA (Siemens Installer Assistant), and the WinCC runtime services. The /F flag forces termination without prompting, which is required because some of these services hold open file handles inside C:\Program Files (x86)\Common Files\Siemens.
4.2 Clear the Siemens Installer Cache and Log Directory
REM --- SCRIPT 2: Clear installer cache and logs ---
rmdir /S /Q "C:\ProgramData\Siemens\Automation\InstallerCache"
rmdir /S /Q "C:\ProgramData\Siemens\Automation\Logfiles\Setup"
mkdir "C:\ProgramData\Siemens\Automation\InstallerCache"
mkdir "C:\ProgramData\Siemens\Automation\Logfiles\Setup"
The /S /Q flags recursively delete without confirmation. Re-creating the empty directories preserves the ACLs Siemens setup expects, avoiding a follow-up Access Denied error when the new setup writes its first log line.
4.3 Delete Corrupted Temporary Installers
The Siemens Installer Assistant extracts the MSI/EXE payload to a staging folder. If the V19 setup was killed mid-extract, a half-written .msi remains there and is auto-launched on the next reboot by a scheduled task:
REM Delete leftover V19 setup payloads
del /F /Q "C:\Program Files (x86)\Common Files\Siemens\Automation\Siemens Installer Assistant\*.*"
Siemens Installer Assistant folder itself; only its contents. The folder contains the registry hooks the TIA updater needs at runtime. Removing the folder breaks the Start Center "Check for Updates" function permanently until TIA is reinstalled cleanly.5. Enable Internet Information Services (IIS)
This is the load-bearing step. TIA V19 cannot install until IIS is registered with Windows.
5.1 GUI Method (Control Panel)
- Open Control Panel → Programs → Programs and Features → Turn Windows features on or off (or run
optionalfeatures.exe). - Locate Internet Information Services in the tree.
- Tick the master checkbox. Expand the subtree and ensure the following sub-features are enabled:
| IIS Sub-Feature | Required by TIA V19 | Purpose |
|---|---|---|
| Web Management Tools → IIS Management Console | Yes | Setup probes inetmgr.exe presence |
| World Wide Web Services → Common HTTP Features → Default Document | Yes | WinCC web default page |
| World Wide Web Services → Common HTTP Features → HTTP Errors | Yes | Diagnostics pages |
| World Wide Web Services → Common HTTP Features → Static Content | Yes | WebUX assets |
| World Wide Web Services → Application Development Features → ASP.NET 4.8 | Yes | WinCC Server / WebUX runtime |
| World Wide Web Services → Application Development Features → ISAPI Extensions / Filters | Yes | PLCSIM web interface |
| World Wide Web Services → Security → Request Filtering | Yes | URL Rewrite uses it for regex rules |
| World Wide Web Services → Security → Windows Authentication | Optional | Needed for SSO into WinCC web |
- Click OK. Windows applies the feature change; this can take 2-8 minutes and may require a reboot.
- After the reboot, verify the W3SVC service is set to Automatic and started: run
services.msc, locate World Wide Web Publishing Service.
5.2 Command-Line Method (Faster, Scriptable)
For repeatable deployments across engineering fleets, use DISM and PowerShell:
REM Enable IIS and the TIA V19 sub-features
DISM /Online /Enable-Feature /FeatureName:IIS-WebServerRole /All
DISM /Online /Enable-Feature /FeatureName:IIS-WebServer /All
DISM /Online /Enable-Feature /FeatureName:IIS-CommonHttpFeatures /All
DISM /Online /Enable-Feature /FeatureName:IIS-ApplicationDevelopment /All
DISM /Online /Enable-Feature /FeatureName:IIS-ASPNET45 /All
DISM /Online /Enable-Feature /FeatureName:IIS-ISAPIExtensions /All
DISM /Online /Enable-Feature /FeatureName:IIS-ISAPIFilter /All
DISM /Online /Enable-Feature /FeatureName:IIS-Security /All
DISM /Online /Enable-Feature /FeatureName:IIS-RequestFiltering /All
DISM /Online /Enable-Feature /FeatureName:IIS-ManagementConsole /All
REM Ensure W3SVC is running
sc config W3SVC start= auto
net start W3SVC
The /All flag enables every child of the named feature. IIS-ASPNET45 covers ASP.NET 4.5/4.6/4.7/4.8 - the package name has not changed since Windows 8. Confirm with DISM /Online /Get-FeatureInfo /FeatureName:IIS-ASPNET45; the State should read Enable Pending or Enabled.
6. Optionally Pre-Install URL Rewrite Module 2
TIA V19 ships rewrite_amd64.msi inside Support\IIS\ on the install media. If the bundled MSI itself is corrupted (visible as a CRC mismatch in the log), install the module manually from the Microsoft URL Rewrite Module 2.1 download before re-running the TIA setup. The MSI is signed by Microsoft and registers the RewriteModule under HKLM\SOFTWARE\Microsoft\IIS Extensions; the TIA setup checks for that key and skips the bundled install.
7. Re-Run the TIA Portal V19 Setup
- Right-click
Start.exeon the V19 DVD/ISO and choose Run as administrator. - The setup detects the new IIS installation and proceeds past the URLRewrite2 component without error.
- When prompted for the product key, enter the Siemens License Key V19 for the active bundles (STEP 7 Professional, WinCC Professional, S7-PLCSIM, Startdrive, Safety). Floating licenses from the Siemens Automation License Manager V6 are checked in automatically.
- Accept the default installation path (
C:\Program Files\Siemens\Automation) unless your project standard dictates otherwise. - Do not interrupt the install. Typical runtime is 25-45 minutes depending on which options are ticked.
C:\Program Files\Siemens\Automation and C:\Program Files (x86)\Common Files\Siemens to the exclusion list before launching setup.8. Verification
After the installer reports success, validate the install with these checks:
| Check | Command / Action | Pass Criteria |
|---|---|---|
| TIA Portal V19 launches | Start → Siemens Automation → TIA Portal V19 | Splash screen, no missing-DLL popup |
| Start Center reports V19 | Help → About | Build string shows 19.0.x.xxxx
|
| IIS hosts TIA Help Server | Open http://localhost/tia-portal-help/
|
HTTP 200, no 500.19 error |
| URL Rewrite registered | Run appcmd list modules /name:RewriteModule in %windir%\system32\inetsrv
|
Module listed as Enabled |
| PLCSIM V19 starts | Project → Start → Start PLCSIM | PLCSIM window opens, instance starts |
| License Manager sees dongle/server | Automation License Manager V6 → Plug-ins | Yellow icon, license available |
Open the TIA Portal log directory and confirm no ERROR-level entries exist for the URLRewrite2 component:
findstr /S /I "URLRewrite" "C:\ProgramData\Siemens\Automation\Logfiles\Setup\*.log"
A clean install returns no output. Any line containing HRESULT 0x80073CF6 means the IIS enablement did not stick - reboot and re-run the DISM commands in section 5.2.
9. Troubleshooting Matrix
| Symptom in Setup Log | Root Cause | Corrective Action |
|---|---|---|
URLRewrite2 installation failed (0x80073CF6) |
IIS root feature disabled | Section 5 - Enable IIS |
Setup rolls back repeatedly at 65% |
Corrupted cached payload | Section 4 - Clean cache + kill SIA |
Error 1402 - Cannot open key HKLM\...\IIS |
Insufficient permissions on IIS registry hive | Run setup from elevated cmd with regedit granting local admin full control on HKLM\SOFTWARE\Microsoft\IIS
|
ASP.NET 4.x not registered with IIS |
aspnet_regiis -i not run after feature enable |
Run %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
|
| Setup hangs on "Configuring SIA service" | Previous SIA service instance still registered | Run sc delete SIA in elevated cmd, then reinstall |
| V16/V18 no longer launch after V19 install | V19 overwrote shared TIA Portal Common Components | Run V18 setup in maintenance mode and choose Repair |
0x800F0922 DISM error enabling IIS |
Pending Windows Update blocks feature change | Install all pending updates, reboot, retry DISM |
| Reboot loop after IIS enablement | Corrupt IIS config from earlier partial install | Boot Safe Mode, run %windir%\system32\inetsrv\appcmd uninstall config, then re-enable IIS |
10. Frequently Asked Questions
Why does TIA Portal V19 require IIS when V18 did not?
V19 ships an embedded WinCC Help Server, WebUX runtime, and the new TIA Cloud Connector, all of which run as IIS-hosted web applications. The TIA V19 setup also relies on the URL Rewrite Module 2 to handle HTTPS redirects inside the SIA (Siemens Installer Assistant) web front end, so IIS with the URL Rewrite feature must be enabled before setup.
Can I install TIA Portal V19 without enabling Internet Information Services?
No. The setup will fail at the URLRewrite2 component with HRESULT 0x80073CF6 and roll back. Enable IIS via Control Panel → Turn Windows features on or off (or via DISM /Online /Enable-Feature /FeatureName:IIS-WebServerRole /All) and retry.
Do I have to uninstall TIA V15.1, V16, and V18 before installing V19?
No. TIA Portal supports parallel installation of V16, V17, V18, and V19 on the same workstation because each major release uses its own isolated directory. Uninstall V15.1 only if you need to free the WinCC Professional seat, as V15.1 bundles the full WinCC Prof. package while V19 uses modular licensing.
What happens to my V18 projects after installing V19?
V19 opens V18 project files and offers an in-place upgrade. The V18 installation remains intact and continues to function, but the TIA Portal Common Components (Help Server, automation license manager hooks) are upgraded to V19 first; this can break V18 launches until you run a Repair on the V18 installation via its maintenance installer.
Where do I find the TIA Portal V19 setup log when installation fails?
Setup logs are written to C:\ProgramData\Siemens\Automation\Logfiles\Setup. The latest run is always Setup_<timestamp>.log. Run findstr /S /I "error" "C:\ProgramData\Siemens\Automation\Logfiles\Setup\*.log" to extract every error line across the active log set before contacting Siemens Industry Online Support.