Troubleshooting WinCC V6.2 Random Runtime Hangs with SP2 Patch

Problem Overview

WinCC V6.2 installations running the initial release (V6.2.0.1) frequently exhibit random runtime failures: the operator station freezes, the WinCC Runtime process stops responding, and the host PC must be power-cycled to recover the visualization. Because the HMI process is the operator's only window into the plant, even an unscheduled restart of the SCADA node is a production event. The documented remediation path is the cumulative service pack plus hotfix train: SP2, then SP2 Patch 1, then SP2 Patch 3 (urgent update), and finally SP3.

This article documents the procurement channels, the in-place upgrade procedure, the patch order that must be respected, and the verification checks that confirm the service pack has been installed correctly on a SIMATIC WinCC V6.2 SCADA node.

Root Cause Analysis

The V6.2.0.1 baseline shipped with several defects in the WinCC Runtime data manager, the alarm logging service, and the connection to the AS (automation system) layer that were only exposed under sustained runtime load. Symptoms commonly reported in the field:

• Process image freeze with the mouse cursor still active.
• Alarm window stops updating; new alarms no longer appear in the message list.
• Tag connections to S7 PLCs (S7-300, S7-400) drop with internal error entries in the WinCC diagnostic files.
• WinCC Explorer remains responsive while the Runtime process CCWin.exe consumes 100% CPU or has stopped.
• Mandatory reboot to recover; clean exit of Runtime is not possible.

Siemens aggregated the fixes for these issues into the cumulative service packs. Hotfixes (called patches in the WinCC V6.2 nomenclature) were released between full service packs to address specific urgent problems and must be layered in the correct order on top of the parent SP.

Available Updates for WinCC V6.2

Three categories of update exist for the V6.2 branch. They are not interchangeable; the table below summarises the cumulative chain.

Siemens' official entry for the SP3 release is published as the Delivery Release: SIMATIC WinCC V6.2 SP3 and SIMATIC WinCC V6.2 SP3 Asia. That entry states that SP3 can be requested as a free download to the previously available WinCC V6.2 SP2 from the SIMATIC download area.

Procurement Channels

Siemens does not expose a single direct "click and install" download for every intermediate service pack. The procurement model depends on the update you need:

SP2 (free of charge with license)

1. Open the Siemens Industry Online Support portal and search for "Service Pack 2 for WinCC V6.2".
2. Sign in with your Siemens customer account and provide the WinCC V6.2 license number from the Certificate of License / License Key disk.
3. Submit the order. The order is free; Siemens ships a DVD or provides a download link.
4. Typical delivery time is 5–7 business days, depending on region.

SP2 Patch 1 and Patch 3 (hotfixes)

1. Search the Siemens Industry Online Support portal for "WinCC V6.2 SP2 Patch 1" and "WinCC V6.2 SP2 Patch 3".
2. Both files are direct downloads (typically a few hundred MB) and do not require a license key.
3. Save the hotfix installers to a known path; you will execute them on the SCADA node after SP2 has been applied.

SP3 (free download)

1. Open the SP3 delivery release entry.
2. Follow the link to the SIMATIC download area.
3. Register the download against your customer account and save the ISO locally.

Pre-Upgrade Prerequisites

A failed SCADA upgrade is far more costly than a failed engineering workstation upgrade. The prerequisites below must be satisfied before any installer is launched.

Step-by-Step Upgrade Procedure

Apply the updates in the order Siemens documents. Do not skip SP2 to jump directly to SP3 unless the SP3 readme explicitly states it can be applied over V6.2.0.1.

Step 1 – Snapshot the SCADA node

1. Shut down the WinCC Runtime cleanly via WinCC Explorer.
2. Stop the WinCC service: net stop "WinCC" or via the Service Control Manager.
3. Take a full system image (Acronis, Veeam, Windows Server Backup) to a network share.
4. Export the WinCC project: in WinCC Explorer, choose Project → Export and copy the resulting archive to the same network share.

Step 2 – Apply WinCC V6.2 SP2

1. Insert the SP2 DVD (or mount the ISO).
2. Run Setup.exe from the root of the media as a user with local administrator rights.
3. Select Install/Update WinCC. The installer detects the V6.2.0.1 installation and offers an in-place update.
4. Accept the license agreement and provide the SP2 license if prompted. SP2 reuses the existing V6.2 license; no new key is required when you have a valid V6.2 license.
5. Wait for the installer to complete. The WinCC installer typically performs two passes: first it deploys the binaries, then it runs the configuration migration.
6. Reboot when prompted.

Step 3 – Apply SP2 Patch 1

1. Download the SP2 Patch 1 hotfix from the Siemens support portal.
2. Copy the executable to a working directory such as C:\Temp\WinCC62SP2_Patch1\.
3. Stop the WinCC service.
4. Run the hotfix executable. It is a self-extracting installer; follow the on-screen prompts.
5. Reboot when prompted.

Step 4 – Apply SP2 Patch 3 (urgent UPDATE)

1. Download the SP2 Patch 3 hotfix from the Siemens support portal.
2. Patch 3 is the urgent update Siemens shipped to address stability issues that remained after SP2 + Patch 1.
3. Stop the WinCC service.
4. Run the hotfix executable.
5. Reboot when prompted.

Step 5 – Verify or skip to SP3

At this point, three choices exist:

• Option A – Remain on SP2 + Patch 1 + Patch 3. Use this when SP3 is not yet available locally or when the SP3 readme lists a regression that affects your configuration.
• Option B – Move to SP3 from SP2 + Patch 1 + Patch 3. SP3 is cumulative; the SP2 hotfixes are included in the SP3 build. Run the SP3 installer over the patched SP2 installation.
• Option C – Move to SP3 from V6.2.0.1 directly. This is supported per the Siemens SP3 delivery release. Apply SP3 over the unpatched V6.2.0.1 base. Useful when hotfix installers are not available.

Step 6 – Apply WinCC V6.2 SP3 (if chosen)

1. Download the SP3 ISO from the Siemens Industry Online Support portal per the SP3 delivery release entry.
2. Run the SP3 setup as Administrator.
3. The installer detects the existing V6.2 (V6.2.0.1 or SP2 + patches) installation and performs an in-place update.
4. Reboot when prompted.

Patch Order and Dependencies

The hotfixes are not independent. Each Patch assumes the binaries installed by its parent. Installing a patch out of order or over the wrong base installation produces a WinCC installation that reports the new version in About but still contains the unpatched DLLs.

Post-Upgrade Validation

Validation must confirm three things: the binaries are updated, the project loads, and the connections to the automation system are healthy.

Verify the installed build

1. Open WinCC Explorer.
2. Choose Help → About.
3. Confirm the build string contains the expected SP keyword (for example, SIMATIC WinCC V6.2 SP3).

For a deeper check, query the Windows registry: the entry HKLM\SOFTWARE\Siemens\WinCC\Setup\Version records the WinCC version. The value should match the build string shown in About.

Verify the patch level

1. Open the Windows Control Panel → Programs and Features (or Add/Remove Programs on Windows XP / Server 2003).
2. Locate the WinCC entries; SP2/SP3 and the patches are listed as separate entries with their own version numbers.
3. Cross-check that Patch 1 and Patch 3 are present when you stopped at the SP2 + patches level.

Functional validation

1. Start the WinCC Runtime in test mode (no operator graphics active): WinCC Explorer → Computer → Start Runtime.
2. Watch the diagnostic window for the first 30 minutes. Look for repeated entries of the same tag or alarm.
3. Force a tag read on every configured connection: open the Tag Management, right-click a tag, and choose Update. A healthy connection returns the current value within 1–2 seconds.
4. Trigger an alarm from the AS to confirm the message frame is delivered and archived.
5. Run the WinCC project for 24 hours before handing back to operations.

Compatibility and Co-Existence

When the SCADA node is part of a multi-server or redundant configuration, additional rules apply:

• Redundant server pair. Both servers must be on the same SP/patch level. A mixed pair (one server on SP2, the partner on SP3) is not supported. Plan a maintenance window long enough to upgrade both.
• Clients. WinCC clients on V6.2 can connect to a server on SP3 only if the client is also upgraded to the matching SP level. The WinCC installer provides a "client only" install option.
• AS side. The S7-300 / S7-400 firmware versions are independent of the WinCC service pack. No PLC change is required.
• OPC. If the WinCC node is the OPC DA server, the OPC client must be retested. Some WinCC OPC fixes changed the namespace structure.
• WinCC options. Options such as WinCC/Web Navigator, WinCC/DataMonitor, WinCC/Connectivity Pack, and WinCC/User Archives have their own compatibility matrix. Verify that the installed option version supports the target SP. In many cases the option must be reinstalled.

Troubleshooting Matrix

Rollback Strategy

If post-upgrade validation fails and you cannot resolve within the maintenance window, the only reliable rollback path is the full image taken in Step 1. The service pack installers do not provide a clean uninstall that preserves the project. The rollback sequence:

1. Stop all WinCC services.
2. Restore the system image to a clean state.
3. Restore the WinCC project export.
4. Verify the WinCC version in Help → About matches V6.2.0.1.
5. Open a follow-up ticket with Siemens to analyse the upgrade failure before the next attempt.

Operational Notes

A few items that surface in the field and rarely appear in the readme files:

• Antivirus exclusion. Exclude the WinCC project directory, the \Siemens\Automation\WinCC directory, and the CCArchiveManager archive paths from real-time AV scanning. The runtime freezes documented in V6.2.0.1 are aggravated by AV scanners that lock archive files mid-write.
• Time service. The WinCC Runtime depends on a stable system clock for alarm timestamping. Use the same NTP source on the SCADA node that the AS uses, and confirm the Windows Time service is set to start automatically.
• Page file. On 32-bit Windows installations, set a fixed page file of at least 4096 MB. The default dynamic page file is too small for sustained runtime and contributes to WinCC Explorer crashes.
• Network. If the SCADA node connects to S7 PLCs over Industrial Ethernet, verify the SIMATIC NET version is on the V6.2 SP compatibility list. Mixing an old SIMATIC NET with a new WinCC SP is a frequent cause of channel-down alarms.

FAQ