Resolving 'Active Applications Still Running' and Reboot Blockers During SIMATIC PCS 7 V8.2 Installation

When upgrading or installing SIMATIC PCS 7 V8.2 over an existing V8.1 system, setup initialization failures displaying 'Applications are still running' or demanding an endless loop of system reboots are caused by active background Siemens services, running SQL Server instances, or a persistent Windows registry flag located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations. To resolve this installation blocker, engineers must close all SIMATIC applications, stop lingering background services (such as Automation License Manager, SQL Server, and CCArchiveManager), delete the 'PendingFileRenameOperations' registry key value, and execute the PCS 7 setup using administrative privileges immediately after a clean reboot.

Root Cause Analysis of PCS 7 Setup Initialization Blockers

The SIMATIC PCS 7 installation suite (Setup.exe) executes an extensive pre-installation system readiness check before allowing software components to install or update. This check inspects running Windows tasks, open file handles, database service locks, and pending operating system operations.

When attempting to upgrade from PCS 7 V8.1 to V8.2, setup frequently flags that 'applications are still running' even though all visible desktop windows are closed. This condition is triggered when background communication daemons (e.g., s7oiehsx.exe, almsrvx.exe) or Microsoft SQL Server instances remain active in memory, preventing the installer from overwriting shared dynamic link libraries (DLLs) and system drivers.

Background Services and Lingering Database Engines

Even when SIMATIC Manager and WinCC Explorer are closed, several critical automation services remain permanently active in the background:

Automation License Manager (ALM): Runs as Windows service almsrvx.exe, locking license storage files.
SIMATIC Security Control / S7DOS: Communication layers (s7oiehsx.exe, s7epatsx.exe) that govern CP 1623 and network card drivers.
WinCC SQL Server Instances: Instances WINCC and WINCCPROT maintain active memory allocations and file locks on database templates in C:\Program Files (x86)\Siemens\WinCC.
Station Configuration Editor: The local PC Station manager (s7basomx.exe) locks virtual rack configurations.

The Windows PendingFileRenameOperations Registry Blocker

The most notorious installation roadblock across all Siemens industrial software installations is the Windows operating system registry value PendingFileRenameOperations:

Registry Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Mechanism: When any third-party program or Windows update replaces a file that is currently in use, Windows queues the rename/delete operation to execute on the next system reboot and records it in this Multi-String registry value.
Siemens Installer Check: The Siemens setup inspects this key. If the key contains ANY file entries, the installer assumes a system reboot is outstanding and halts installation. If a background driver continuously repopulates this key upon reboot, an endless reboot loop occurs.

Step-by-Step Procedure to Clear Setup Locks and Upgrade to V8.2

To eliminate setup blockers and complete the upgrade to PCS 7 V8.2:

Gracefully Close Applications: Ensure SIMATIC Manager, WinCC, PLCSIM, and ALM are closed.
Stop Background Services: Open Windows Services (services.msc) and manually stop:
- Automation License Manager Service
- SQL Server (WINCC)
- SIMATIC Workstation Service
Clear the Registry Blocker:
- Press Win + R, type regedit, and press Enter.
- Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
- Locate the value named PendingFileRenameOperations.
- Right-click and select Delete (or double-click and clear all text content).
- Do NOT restart the computer after deleting this key; immediately proceed to the next step.
Launch PCS 7 Setup: Right-click Setup.exe on the PCS 7 V8.2 installation media and select Run as Administrator.
Select Upgrade / Package: Proceed through the installer wizard to upgrade the system cleanly.

Comparison of In-Place Upgrade vs Clean Operating System Installation

The following table compares performing an in-place upgrade over an existing PCS 7 installation versus executing a clean operating system installation:

Deployment ParameterIn-Place Upgrade (Over V8.1)Clean OS ReinstallationInstallation DurationFast (1 - 2 hours)Longer (4 - 8 hours including OS setup)Legacy Registry ClutterRetained; prone to service conflictsZero clutter; pristine clean registrySQL Server Upgrade RiskHigh risk of SQL instance version conflictsZero risk; fresh automated SQL installationRecommended EnvironmentTest benches and non-critical ES stationsProduction ES, Redundant OS Servers, and Batch ServersSoftware License HandlingExisting ALM licenses remain intactRequires restoring ALM license keys from USB

Verification

Verify successful installation and environment readiness:
1. Launch the PCS 7 V8.2 installer; verify that the pre-check passes all system prerequisites with green checkmarks and no blocking dialogues.
2. Complete the installation wizard; allow the required system restart at the conclusion of setup.
3. Open SIMATIC Manager; navigate to Help > About > Installed Software and confirm that all software components (Step 7, CFC, SFC, WinCC, APL) report version V8.2.
4. Open Automation License Manager; confirm that installed PCS 7 V8.2 engineering and runtime licenses are recognized and valid.

Limitations and Operational Precautions

While in-place upgrades are supported between close minor versions (such as V8.1 to V8.2), Siemens strongly advises performing a clean operating system reinstallation for major version hops (e.g., V8.x to V9.0) or when switching OS architectures (Windows 7 to Windows 10 / Server 2016). Always create a complete disk image backup of the Engineering Station using backup tools (such as SIMATIC Image & Partition Creator) before starting any software upgrade.

Engineer FAQ

Why does 'PendingFileRenameOperations' reappear even after I delete it?

Certain antivirus agents, Windows auto-updates, or print spoolers continuously queue file operations upon startup. Deleting the registry value and immediately launching the Siemens installer without rebooting bypasses this repopulation cycle.

Can I install PCS 7 V8.2 on Windows 10?

PCS 7 V8.2 was designed and validated for Windows 7 SP1 (64-bit) and Windows Server 2008 R2 SP1. Windows 10 and Windows Server 2016 support was officially introduced with SIMATIC PCS 7 V9.0.