Resolving 'Reboot Required' and System Restart Popups Across ES, OS Servers, and Clients in SIMATIC PCS 7

In SIMATIC PCS 7, persistent 'Reboot required' or 'System restart pending' popups appearing across the Engineering Station (ES), OS Servers, and OS Clients are caused by pending Windows file rename operations (PendingFileRenameOperations registry key), uncoordinated Windows Update automated reboot policies, or unresolved SIMATIC Security Control settings. In industrial environments, automated reboots threaten process safety and SCADA availability. To resolve this, clear the pending file rename registry flag, configure Windows Group Policies (GPO) to prevent automatic reboots during active sessions, and execute 'Repeat Settings' in SIMATIC Security Control.

Pending Reboot Mechanisms in Windows and SIMATIC Software

In industrial control systems running Windows Server and Windows 7/10:
* PendingFileRenameOperations: When software packages, service packs, or security updates install system files that are currently locked by running processes, Windows registers them in the registry to be renamed upon the next reboot.
* SIMATIC Setup Guard: Siemens software installers and runtime services query this registry value. If it contains pending entries, setup programs abort with 'Please perform a restart before installing' or display periodic restart warning prompts.
* Windows Update Auto-Reboot: Default Windows update policies force a system restart when security patches are downloaded, which can unexpectedly shut down live SCADA servers and operator stations.

Root Causes of Simultaneous Restart Prompts Across Stations

When an entire plant facility (ES, Servers, Clients) prompts for a reboot concurrently:
1. Domain Group Policy (GPO) Push: Corporate IT pushed a Windows Update patch or policy change via Active Directory Domain Services (AD DS). All domain-joined PCS 7 stations ingested the update simultaneously and initiated countdown timers.
2. Coordinated Antivirus Engine Update: Enterprise endpoint security software (such as Symantec Endpoint Protection or McAfee) updated its kernel filter drivers across all nodes, flagging an obligatory system restart.
3. Pending File Rename Deadlock: Even after rebooting, certain third-party software or unclosed installers fail to clear the PendingFileRenameOperations registry string, leaving workstations in a perpetual 'reboot required' loop.

Remediation Procedure - Clearing Registry Flags and Suppressing Forced Reboots

Follow this procedure to eliminate persistent reboot loops and prevent automated restarts:

[Phase 1: Clear the Pending File Rename Registry Flag]
   │  • Press Win + R -> Type "regedit" -> Press Enter
   │  • Navigate to:
   │    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
   │  • In the right pane, locate: "PendingFileRenameOperations"
   │  • Right-click -> Select "Delete" (or double-click and clear all text contents)
   │  • (Do not reboot immediately; launch the Siemens installer or application)
   │
[Phase 2: Disable Automatic Windows Update Reboots via Group Policy]
   │  • Press Win + R -> Type "gpedit.msc" -> Press Enter
   │  • Navigate to: Computer Configuration -> Administrative Templates ->
   │      Windows Components -> Windows Update
   │  • Enable the policy:
   │      "No auto-restart with logged on users for scheduled automatic updates"
   │  • Set: "Configure Automatic Updates" -> "3 - Auto download and notify for install"
   │
[Phase 3: Synchronize SIMATIC Security Control]
   │  • Open: Start -> Siemens Automation -> SIMATIC Security Control
   │  • Click: "Repeat Settings"
   │  • Confirms firewall, DCOM, and security permissions across the station

Industrial Restart Policy and Registry Configuration Matrix

Verify and enforce the following registry and policy settings across all industrial nodes:

Subsystem / PolicyDefault Corporate IT SettingMandatory PCS 7 SettingOperational Consequence of DefaultWindows Auto-RestartEnabled (Reboot at 3:00 AM)Disabled (Notify Only)Unexpected SCADA server shutdown; loss of plant view.Pending File Rename StringPersists until rebootClear via Registry EditorSiemens installers and runtime tools blocked.Windows Update ServiceAutomatic Download & InstallManual / WSUS StagedUncoordinated driver overwrites on Terminal Bus NICs.SIMATIC Security ControlUnconfiguredRepeat Settings ExecutedDCOM communication dropouts between ES and OS.

Verification

To confirm that persistent reboot prompts are resolved:
1. In Windows Registry Editor, verify that PendingFileRenameOperations under Session Manager is clear.
2. Launch a Siemens software setup or WinCC Explorer; confirm that no restart warning dialogs appear.
3. In Local Group Policy Editor (gpedit.msc), verify that 'No auto-restart with logged on users' is active.
4. Review Windows Event Viewer (System log); confirm that no pending restart requests from Windows Update Client (Event ID 19 or 20) are pending.

Limitations and Operational Precautions

Never allow automated patch deployment tools (such as Microsoft WSUS or SCCM) to push unverified security updates directly to production PCS 7 servers without prior testing in an offline staging environment. Always schedule industrial server reboots during planned plant maintenance windows, ensuring redundant partner servers remain operational to maintain continuous supervisory control.

Engineer FAQ

Why does 'PendingFileRenameOperations' reappear after I delete it?

If an unclosed installer or background updater (e.g. print spooler, antivirus, or hardware driver utility) is running, it will re-write the registry key. Terminate the offending installer before clearing the key.

Can clearing PendingFileRenameOperations damage the operating system?

No. It simply removes temporary file replacement instructions for uninstalled or updated files, allowing pending applications to proceed without rebooting.

How do I prevent domain group policies from overriding PCS 7 settings?

Place all PCS 7 computers (ES, OS, Historian) into a dedicated Organizational Unit (OU) in Active Directory and block inheritance of corporate workstation power and reboot policies.

Why does SIMATIC Setup refuse to install even after multiple reboots?

A locked file or stuck third-party service is continuously populating the Session Manager registry key. Manually deleting the value immediately before running setup resolves this.