Fix TIA Portal V15 Installation Restart Error on Windows 10

1. Problem Overview

The TIA Portal V15 (and V15.1) installation occasionally terminates immediately after the setup splash screen appears, displaying a dialog that requests an operating system restart. After reboot, the same message reappears on every launch of Setup.exe, and the installer never advances to the product selection or prerequisites stage. The dialog text typically reads:

• "A restart of the computer is required before continuing the installation. Please restart the computer and run setup again."
• "The operating system is not in a state to continue the installation. A pending file rename or delete operation exists."

Affected platforms: Windows 10 (build 1607 through 22H2), Windows 10 Enterprise, Windows 10 Pro, Windows 10 Education. Both first-time installs and re-installs after a successful prior deployment (including a previously working installation on the same laptop that was uninstalled) reproduce the fault. The error is independent of target installation directory, file system (NTFS), disk space, and most background software.

2. TIA Portal V15 System Requirements and Compatibility Matrix

Before troubleshooting the restart loop, verify that the target workstation meets the minimum and recommended hardware/software requirements published by Siemens for STEP 7 / TIA Portal V15. A non-conforming OS build can mask itself as a restart-pending error because the bootstrapper exits before logging a clear cause.

Reference: Siemens Entry ID 109751459 - System requirements for STEP 7 / TIA Portal V15 and V15.1.

3. Root Cause Analysis: Why the Restart Loop Persists

The TIA Portal setup invokes the Microsoft Windows Installer service (msiexec.exe) for each component package. Windows Installer refuses to begin a new transaction when it detects unresolved file-rename operations queued by a prior install, an incomplete Windows Update, or a crash. The pending operations are recorded in:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager
   Value: PendingFileRenameOperations
   Type:  REG_MULTI_SZ

Each entry is a \??\C:\path\oldname → \??\C:\path\newname pair. Windows clears the value only after the rename succeeds during boot. When the user reboots in response to the TIA Portal prompt, Windows does not always process the queue (for example, when an entry points to a file held open by a service). The value persists, the next launch of Setup.exe re-detects it, and the loop continues indefinitely.

Common origins of the stale value:

1. Partial uninstall of a prior TIA Portal / STEP 7 / WinCC version.
2. Pending Windows cumulative update that requires a second boot.
3. Antivirus or backup software that renames files during a real-time scan.
4. Driver installer (NVIDIA, Intel ME, audio) that scheduled a DLL rename.
5. Corrupted %WINDIR%\WinSxS store preventing rename completion.

The same mechanism is documented for Visual Studio (see Troubleshoot Visual Studio installation and upgrade issues) and Autodesk products (see An operating system restart is pending when trying to install AutoCAD 2024), confirming it is a Windows Installer behavior, not a Siemens-specific defect.

4. Pre-Installation Diagnostics

Run the following checks before modifying the registry. Document each result so you can roll back changes if the install still fails.

4.1 Confirm pending rename operations

1. Open regedit.exe as Administrator.
2. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager.
3. Look for PendingFileRenameOperations. If the value exists, right-click it and select Export to back it up (e.g., PendingFileRenameOperations_backup.reg).
4. Double-click the value to inspect the multi-string contents. Count the entries and note any paths.

4.2 Confirm pending reboot from Windows Update

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired"
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending"

If either returns a 0x1 entry, Windows has not finished a servicing operation. The most reliable remedy is to allow Windows Update to complete its cycle, not to suppress the TIA Portal prompt.

4.3 Capture the setup log

Launch Setup.exe from an elevated command prompt with logging enabled:

cd /d "D:\Siemens_Install\TIA_Portal_V15"
Setup.exe /log "%USERPROFILE%\Desktop\TIA_V15_install.log"

The log is written to %USERPROFILE%\AppData\Local\Temp by default if /log is omitted. Search for the strings ERROR, PendingFileRename, and 1638. Error 1638 is the MSI code for "Another installation is already in progress" and is frequently logged alongside the restart loop.

4.4 Verify .NET and Visual C++ runtimes

reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release

Release value must be 461308 (4.7.1) or higher. If the key is missing or below 461308, install .NET Framework 4.7.2 before continuing.

5. Resolution Method 1: Clear PendingFileRenameOperations Safely

1. Reboot the laptop once to give Windows a chance to process the queue. Watch the boot log (%WINDIR%\setupact.log) for the line "Pending file rename operations have been processed".
2. Boot into Safe Mode with Networking: msconfig → Boot tab → check Safe boot → Minimal. In Safe Mode, third-party services (antivirus, backup) that may be holding the queued files are stopped.
3. Open regedit.exe as Administrator.
4. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager.
5. Right-click PendingFileRenameOperations and select Delete. If a PendingFileRenameOperations2 sibling value exists, delete it too.
6. Close regedit. Reboot normally.
7. Run Setup.exe as Administrator from the V15 distribution media.

If the value is repopulated on the next reboot, the queued rename is being re-injected by an active service. The originating service is usually identifiable by running:

Get-WinEvent -LogName Application -MaxEvents 200 | Where-Object {$_.Message -match "rename"} | Format-List TimeCreated,ProviderName,Message

6. Resolution Method 2: Run Setup with Full Administrator Privileges

UAC elevation is mandatory for TIA Portal V15. A standard Run as administrator click is not equivalent if User Account Control is configured to deny elevation prompts or if the user account is missing the SeDebugPrivilege token. Verify and remediate as follows:

1. Open secpol.msc → Local Policies → Security Options.
2. Set User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode to Prompt for consent.
3. Set User Account Control: Detect application installations and prompt for elevation to Enabled.
4. Disable or temporarily uninstall any anti-malware product that hooks CreateProcess (Symantec Endpoint, McAfee ENS, Sophos Intercept X are known offenders).
5. From an elevated cmd.exe window, run whoami /groups | findstr /i "S-1-16-12288" - the result must show High Mandatory Level. If it does not, the shell was not elevated correctly.
6. Launch the setup from the elevated shell with the full path: "D:\Inst\TIA_V15\Setup.exe".

7. Resolution Method 3: User Profile, Locale, and Language Configuration

Siemens setup queries Windows for the default user language and refuses to install non-English languages whose locale is not configured in the active profile. On Danish / Danish-region installations, the bootstrapper has been observed to misreport system capabilities and trigger a false restart-pending error.

1. Open intl.cpl → Administrative tab → Change system locale…
2. Set Current system locale to English (United States). Cancel any prompt to reboot for now.
3. Open control /name Microsoft.RegionAndLanguage → Region → Additional date, time, and regional settings → Language → Windows display language: English.
4. Create a new local user: net user tiauser "P@ssw0rd!" /add and add it to Administrators: net localgroup Administrators tiauser /add.
5. Log out and log in as tiauser.
6. Install the English-only variant of TIA Portal V15. Do not select any other language during the initial deployment.
7. After the install succeeds, log back in to the original user and run Setup.exe again. Choose Modify / Upgrade and add the Danish language pack.

Repeat the procedure for V15.1 if both versions are required.

8. Resolution Method 4: Repair the Windows Installer and SxS Store

If the registry value keeps reappearing even after a clean boot, the WinSxS component store may be corrupted. Run the following from an elevated command prompt:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

After DISM and sfc report no integrity violations, re-register the Windows Installer service:

msiexec /unregister
msiexec /regserver
net stop msiserver
net start msiserver

Re-run the setup.

9. Clean Installation Procedure (Nuclear Option)

Use this procedure when all methods above fail and the install must succeed. Document the original state for rollback.

1. Disable Windows Update service temporarily: net stop wuauserv and net stop bits.
2. Stop the Windows Installer service: net stop msiserver.
3. Delete the following folders if they exist: C:\Program Files\Siemens\Automation, C:\Program Files (x86)\Siemens, %PROGRAMDATA%\Siemens, %APPDATA%\Siemens, %LOCALAPPDATA%\Siemens.
4. Delete residual registry keys: HKLM\SOFTWARE\Siemens\Automation, HKLM\SOFTWARE\WOW6432Node\Siemens, HKCU\SOFTWARE\Siemens.
5. Clear the PendingFileRenameOperations value per Section 5.
6. Run Disk Cleanup with the option Windows Update Cleanup enabled.
7. Re-enable Windows Update: net start wuauserv and net start bits. Let it complete any pending updates and reboot twice.
8. Run Setup.exe as Administrator.

10. Verification Steps

After the install completes, confirm the deployment is functional:

1. Open TIA Portal V15 from the Start menu. The splash screen should display BUILD 15.0.0.0 or higher.
2. Launch the software and create a new project. The license dialog should appear (or the 21-day trial starts) without errors.
3. Add an S7-1500 device and verify the device catalog loads.
4. Check Help → About: confirm the product variants installed (STEP 7 Professional, WinCC Professional, S7-PLCSIM).
5. Verify the following services are present and Started:

   sc query "S7TraceService"
   sc query "SiemensS7TIAV15"
   sc query "TeamCenterGateway"
   

6. Open %WINDIR%\System32\drivers\etc\hosts and confirm no Siemens-related entries are blocked by an AV that hooked the file.
7. Reboot the laptop. Re-launch TIA Portal. It should start without the restart prompt.

11. Troubleshooting Matrix

12. Reporting the Issue to Siemens Support

If the problem cannot be resolved with the methods above, file a support request with Siemens Industrial Online Support. Include:

1. Output of msinfo32 report (File → Export).
2. The full TIA Portal setup log (%USERPROFILE%\AppData\Local\Temp\Siemens\Setup.log or path specified in /log).
3. A screenshot of the restart dialog.
4. The exported PendingFileRenameOperations backup .reg file.
5. Confirmation that the install succeeds on another machine using the same media (this isolates the problem to the laptop, not the installer).

Reference: Siemens Industrial Online Support and Entry ID 109751459.