Resolving Repeated Restart Prompts During SIMATIC PCS 7 Software Installation

In SIMATIC PCS 7, when an installation, service pack, or hotfix setup repeatedly halts with the prompt 'Please restart Windows before installing new programs' despite multiple reboots, the installer is blocked by a persistent registry value. Siemens setup checks for pending system reboot requests in the Windows registry. To resolve this, open Registry Editor, navigate to 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager', delete the 'PendingFileRenameOperations' value without rebooting, and immediately launch 'Setup.exe'.

Executive Summary

During the initial deployment of SIMATIC PCS 7 or when applying updates, service packs, and hotfixes, engineers frequently encounter an installation roadblock: the setup wizard immediately terminates with the warning message: Please restart Windows before installing new programs. However, restarting the operating system does not resolve the condition; upon relaunching the installer, the identical reboot prompt appears.

This recurring prompt occurs because Windows and third-party software installers register pending file rename and deletion operations in the registry key PendingFileRenameOperations. Siemens setup routines inspect this key to ensure the operating system is in a clean state prior to modifying system drivers and COM components. When another Windows background service, antivirus update, or incomplete printer driver installation continuously repopulates this key, a setup deadlock occurs. This guide outlines the registry remediation procedure and temporary file cleanup steps required to proceed with installation.

Architecture and Fundamental Mechanics

The Windows session management subsystem handles file replacement during system startup via designated registry keys:

Purpose of PendingFileRenameOperations:
- When an application or driver update modifies a file currently locked in memory (such as a core DLL or system driver), Windows cannot overwrite the file while the operating system is active.
- The installer writes the source and destination paths to the multi-string registry value PendingFileRenameOperations under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager.
- During the subsequent Windows boot phase, smss.exe (Session Manager Subsystem) processes this list, performs the file renames or deletions, and empties the registry value.
Siemens Setup Pre-Check Mechanism:
- To protect system integrity and prevent version mismatches, SIMATIC PCS 7 Setup.exe checks for the presence of PendingFileRenameOperations before initializing any installation components.
- If the value exists and contains data, Siemens Setup assumes a previous installation is incomplete and aborts with the reboot prompt.
The Deadlock Condition:
- Certain third-party software (e.g., security scanners, hardware management agents, or failed update loops) continuously regenerate entries in PendingFileRenameOperations upon every system startup.
- Because smss.exe executes before user login, the key is immediately repopulated, preventing Siemens Setup from ever seeing a clean state. Deleting the value while Windows is running allows the installer to bypass the pre-check without triggering another reboot cycle.

Step-by-Step Implementation Procedure

Follow these steps to clear the persistent reboot prompt and execute SIMATIC PCS 7 Setup:

Launch the Windows Registry Editor:
- Press Win + R to open the Run dialog.
- Type regedit and press Enter.
- Confirm the User Account Control (UAC) prompt to open the editor with administrative privileges.
Navigate to Session Manager:
- In the left registry tree, expand the path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.
Locate and Delete PendingFileRenameOperations:
- In the right-hand details pane, locate the multi-string value named PendingFileRenameOperations.
- Right-click PendingFileRenameOperations and select 'Delete'.
- Confirm the deletion by clicking 'Yes'.
- (Optional) If a value named PendingFileRenameOperations2 exists, delete it as well.
Execute Siemens Setup Immediately:
- Crucially, do NOT restart Windows after deleting the registry value!
- Immediately navigate to your PCS 7 installation media or extracted setup folder.
- Right-click Setup.exe and select 'Run as administrator'.
- The setup wizard will now initialize without raising the restart prompt.
Clean Up Temporary Installation Directories:
- Large extracted PCS 7 ISO packages can rapidly exhaust disk space in the user's temporary folder.
- Press Win + R, type %temp%, and press Enter.
- Delete orphaned temporary setup extraction folders (often exceeding several gigabytes) to ensure sufficient disk space for installation.
Complete Installation and Perform Final Reboot:
- Proceed through the PCS 7 setup screens, select the required components, and allow installation to finish.
- When setup completes, perform the final system restart requested by the installer to register all COM objects and drivers.

Verification

Launch Setup.exe after deleting the registry value: confirm that the Siemens Installation Wizard progresses directly to the component selection screen.
Confirm that the message 'Please restart Windows before installing new programs' does not appear.
Verify in Windows Services (services.msc) that Siemens automation services (e.g., Automation License Manager Service, S7DOS) install and register correctly.
Complete the installation and verify that SIMATIC Manager launches without licensing or library registration errors.

Limitations and Operational Precautions

Deleting PendingFileRenameOperations clears pending file movements for other applications. Ensure no critical Windows Operating System updates are actively midway through installation before performing this manual registry modification. Always ensure proper engineering licenses and SIMATIC PCS 7 installation media are sourced and verified through an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Why does Windows repeatedly ask for a restart during setup?

Because the registry value PendingFileRenameOperations contains unresolved file rename or deletion requests queued by Windows or background applications.