Resolving WinCC V7.0 SP2 Installation Failure on Windows Server 2008 R2 SP1

Problem Summary

Engineers deploying SIMATIC WinCC V7.0 SP2 on Windows Server 2008 R2 SP1 encounter a hard block at the WinCC Setup splash screen: the installer refuses to continue, citing an unsupported operating system. The platform message reads as a simple "No" dialog and the user is left to determine the underlying cause. This article documents the root cause of the rejection, the official Siemens compatibility matrix, the supported Microsoft downgrade path, and the field-tested workarounds that allow a WinCC V7.0 SP2 runtime to be brought up on a 64-bit Server 2008 R2 host.

Root Cause Analysis

The WinCC V7.0 SP2 setup program runs an early OS compatibility check that examines the registry keys under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion for ProductName, CurrentVersion, and CurrentBuildNumber. The matching logic is hard-coded against the entries listed in support entry 21927773 of the Siemens Industry Online Support. Two facts combine to cause the rejection:

1. WinCC V7.0 SP2 is a 32-bit application line. Even when installed on 64-bit Windows, the underlying runtime services, the SQL Server host instance, the WinCC Explorer, and the alarm / logging DLLs are compiled for x86. Siemens did not certify the line for 64-bit Windows until a service pack later in the V7 lifecycle.
2. Windows Server 2008 R2 reports CurrentVersion = 6.1 and ProductName = Windows Server 2008 R2. The WinCC V7.0 SP2 matcher accepts Windows Server 2008 with CurrentVersion = 6.0 and Service Pack 2 only. The R2 SKU has a different major version, so the matcher fails before the user can choose an installation mode.

This is not a bug - it is a deliberate support boundary. The install log written to %TEMP%\Siemens\WinCC\Setup.log contains a diagnostic string of the form OS check failed: ProductName='Windows Server 2008 R2' CurrentVersion=6.1 - not in allow-list (the exact wording varies between setup builds). The check is identical on both the x86 and x64 bootstrapper, which is why simply re-running setup from a 32-bit command prompt does not help.

Supported Operating Systems for WinCC V7.0 SP2

The certified matrix at this service-pack level is reproduced below. The list is exhaustive - any OS not appearing here is rejected by the setup guard.

Three operational facts follow from this matrix:

• There is no supported path for Windows 7 64-bit, Windows Server 2008 R2, or Windows Server 2008 64-bit on the V7.0 SP2 code line.
• Windows Vista is not on the matrix at all, so Vista-based servers are equally unsupported.
• Server role is only permitted for the Server 2003 family and the 32-bit Server 2008 SP2 SKU. Client and Single-User roles are the only options on Windows 7 / XP.

Why Windows Server 2008 R2 Differs from Windows Server 2008

The naming overlap is the single largest source of confusion in V7.0 deployments. Although Microsoft released both products in the 2008-2009 window, they are not service packs of one another - they are distinct releases that share branding.

From a WinCC V7.0 SP2 perspective, the decisive rows are the internal NT version and the architectures shipped. Server 2008 R2 is 64-bit-only, so the V7.0 SP2 setup, which is 32-bit-only, cannot complete its prerequisites check; the matching routine inspects architecture as well as version.

Pre-Installation Verification

Before applying any workaround, capture the actual OS identity the WinCC setup will see. Run the following from an elevated command prompt on the target server:

reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ProductName
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentVersion
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildNumber
wmic os get OSArchitecture, Caption, ServicePackMajorVersion, Version
systeminfo | findstr /B /C:"OS Name" /C:"OS Version" /C:"System Type"

Document the output. If the value of CurrentVersion is 6.1 and ProductName contains R2, the V7.0 SP2 setup will fail at the OS check. Save the output to C:\install\precheck.txt for the change-log. If a downgrade is the chosen path, this becomes the before-snapshot.

Also verify that no partial WinCC install is present:

sc query "CCAgent"
sc query "CCEServer"
sc query "SQLBrowser"
dir /s "C:\Program Files\Siemens"

Any leftover services from a previous attempt must be removed with sc delete and any orphaned directories under %ProgramFiles%\Siemens must be deleted before the new install begins. A partial state will produce Error 1920: Service 'CCAgent' (CCAgent) failed to start or Error 1603: Fatal error during installation in the MSI log even after the OS issue is fixed.

Solution Path A - Microsoft Downgrade Rights to Windows Server 2008 SP2 (32-bit)

This is the officially supported approach. The Windows Server 2008 R2 license grants the holder downgrade rights to the prior version - that is, the original Windows Server 2008 - provided the downgrade is performed on the same machine and the same license key is reused.

Step-by-step downgrade

1. Back up the entire system image. A bare-metal backup is preferred because the downgrade replaces the OS partition completely.
2. Download the Windows Server 2008 with Service Pack 2 (32-bit) media. The published file name is 6001.18000.080118-1840_x86fre_Server_en-us-KRMSFRE_EN_DVD.iso, available from the Microsoft Volume Licensing / Download Center, and the matching download record is Microsoft Download id=5023.
3. Burn the ISO to DVD or attach it via an iLO / iDRAC virtual media.
4. Boot from the media and choose Custom (advanced) install. The setup will refuse to upgrade in place; you must install to a formatted partition. Accept the warning that Windows cannot be downgraded in place and that data on the partition will be erased.
5. After the base install, apply Windows Server 2008 Service Pack 2 if the integrated media does not include it. The SP2 standalone package is available at Microsoft Download id=16468.
6. Install the hardware drivers and re-join the domain. Re-apply the same product key used for the R2 license. Microsoft recognizes the downgrade through the licensing channel; no separate key is required.
7. Run the WinCC V7.0 SP2 setup. The OS check should now report Windows Server 2008 with CurrentVersion = 6.0 and pass.

Solution Path B - Wait for the Next WinCC Service Pack

Siemens announced that a WinCC V7 service pack scheduled for release later in the V7 lifecycle would extend the certified matrix to include 64-bit Windows editions. That subsequent service pack update was the practical resolution for the majority of integrators who did not want to disturb an existing R2 deployment. Track the support entry 21927773 for change notifications.

Operational guidance while waiting:

• Reserve the 64-bit R2 hardware but provision a temporary 32-bit Server 2008 SP2 box (physical or virtual) to host the SCADA server until the supported service pack is released.
• Use a separate engineering station (Windows 7 32-bit) for project development and the WinCC Configuration Studio. This is allowed because WinCC V7.0 SP2 supports Windows 7 32-bit as a Single-User / Client role.
• Document the OS check failure in the change log so the eventual service-pack upgrade is captured in the project's history.

Solution Path C - Virtualize the WinCC Server

If the production fleet is committed to Server 2008 R2 hardware and an OS downgrade is not acceptable, run a 32-bit Windows Server 2008 SP2 guest as a virtual machine on the R2 host using Hyper-V (built into Server 2008 R2). This isolates the OS restriction from the physical hardware.

1. Enable the Hyper-V role on the Server 2008 R2 host. Reboot when prompted.
2. Create a Generation 1 virtual machine (Generation 2 VMs do not support 32-bit Windows Server 2008). Allocate at least 2 vCPUs, 4 GB RAM (8 GB recommended for a WinCC server with redundancy), and a 100 GB dynamic VHDX.
3. Attach the 32-bit Server 2008 SP2 ISO and complete the guest install.
4. Inside the guest, install WinCC V7.0 SP2. The OS check now sees a 32-bit Server 2008 SP2 and passes.
5. Bridge the virtual switch to the production network so the SCADA clients can reach the VM. Tag VLANs and configure firewall rules as required.

The virtualization layer is transparent to WinCC - the application sees only its guest OS. The trade-off is real-time latency: if WinCC is driving a high-density tag archive or a fast cyclic interrupt, the hypervisor's timer resolution becomes a bottleneck. For HMI / SCADA workloads (typical cycle times of 250-1000 ms) the overhead is negligible.

SQL Server, .NET, and Other Prerequisite Components

Regardless of which solution path is chosen, the WinCC V7.0 SP2 server requires a stack of supporting components that must be installed in the documented order. Skip one of them and the setup will silently mark the prerequisite as failed and abort with MSI error 1719 - Windows Installer service could not be accessed or Error 1925 - You do not have sufficient privileges.

Install SQL Server before WinCC so the WinCC setup can attach to the named instance. If WinCC installs its own SQL Server, you cannot later promote that instance to a clustered SQL Server without re-running the WinCC setup in repair mode.

Post-Installation Verification

After the install completes, run the following sanity checks before commissioning the runtime.

1. Verify all WinCC services are started: CCAgent, CCEServer, CCAlgRtServer, CCArchiveManager, CCSysDiag, and the redundancy service if used.
2. Open WinCC Explorer and confirm the project loads without error.
3. Activate the project. Watch the Diagnostics view for tag connection state. Every configured tag should reach Connected within 5 seconds of activation on a healthy network.
4. Trigger a test alarm and confirm it appears in the Alarm Logging view and is written to the archive database.
5. On a remote WinCC client (Windows 7 32-bit), launch the WinCC Client and connect. Confirm the picture tree, tag values, and alarm list all update.

Capture the verification screenshots and the contents of C:\Program Files\Siemens\Automation\WinCC\Diagnose\DiagMonitor.log in the commissioning report. This is the evidence the operations team will need when the system is handed over.

Field-Proven Pitfalls and Lessons

• Active Directory domain functional level. If the R2 server is a domain controller, the downgrade path requires demotion to a member server first. Plan a separate Server 2008 R2 DC if the domain is to remain online during the work.
• Anti-virus exclusions. WinCC's cyclic tag polling is sensitive to file-system antivirus scans. Exclude C:\Program Files\Siemens\Automation and the SQL data directories from the real-time scanner before the first project activation.
• Time synchronization. The WinCC archive uses the local clock for timestamp indexing. Use the same NTP source for the SCADA server and the PLCs; drift greater than 1 second breaks sequence-of-events reconstruction.
• Firewall rules. WinCC uses dynamic port allocation for redundancy. Open the WinCC server in the firewall by allowing the CCAgent.exe and CCEServer.exe executables, not by opening fixed TCP ports. Fixed-port configurations break when redundancy fails over.
• Power management. Disable sleep, hibernation, and USB selective suspend on the SCADA server. Windows Server 2008 SP2 is the last server OS to honour these settings by default; they cause intermittent tag timeouts in the archive logs.
• Windows Updates and the OS check. After install, lock the server to manual updates and review each patch. A service pack slipstream that re-introduces a non-allow-listed kernel can re-trigger the original guard.

Troubleshooting Matrix

FAQ