Resolving WinCC V8 Runtime Startup Freeze at Alarm Logging 28%

Problem Overview

After a Windows 10 Home to Professional in-place upgrade on a workstation hosting a Siemens WinCC V8 (TIA Portal / SIMATIC WinCC) project, the WinCC Explorer runtime activation hangs at approximately 28% with the status text frozen on "Starting Alarm Logging...". The companion Windows service ccAlgrtserver (SIMATIC WinCC Alarm Logging Server) refuses to start or enters a continuous restart loop, and the WinCC RT icon in the system tray never reaches the green "running" state.

This symptom is a classic post-upgrade failure mode caused by:

• Retained registry keys from the previous Windows edition (Home SKU values that are not present or valid in Pro).
• SQL Server instance metadata (WinCC uses a local MS SQL Server for the alarm and tag archive databases) that was bound to a removed SKU identifier.
• Service account permissions that no longer resolve correctly after the SKU change.
• Pending Windows updates that were queued during the in-place upgrade but not finalized.

Affected Software and Versions

Refer to the official release notes for the exact compatibility matrix:

• SIMATIC WinCC V8.0 - System Manual / Readme
• SIMATIC WinCC V8.0 - Operating WinCC
• Compatibility tool for automation and drives (TIA, WinCC, S7)

Root Cause Analysis

The "28% stuck on Alarm Logging" indicator is generated by the WinCC Computer startup sequence. The progress meter advances as each internal subsystem reports ready:

1. Graphics Runtime (0-15%)
2. Tag Management / Channel units (15-22%)
3. Tag Logging initialization (22-26%)
4. Alarm Logging initialization (26-30%) — common hang point
5. Report Services and user archive (30-40%)
6. Redundancy / scripts / final handshake (40-100%)

When the meter is frozen inside the Alarm Logging range, the ccAlgrtserver.exe process has either crashed, is waiting on a non-responsive SQL Server connection, or cannot bind to its configured TCP port (default 4900 for AlarmLogging control).

Why the SKU upgrade triggers the failure

An in-place Windows 10 Home → Pro upgrade preserves installed applications but rewrites significant portions of the registry hive, including:

• HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion — EditionID changes from Core to Professional.
• Group Policy branches that did not exist under Home are now instantiated, changing the default security context for services.
• Some bundled WinCC prerequisites (e.g. the Microsoft Visual C++ runtime, .NET Framework targeting packs) may be re-registered with wrong CLSIDs.

The WinCC internal service configuration reads the original Home-SKU path assumptions and fails the consistency check. The ccAlgrtserver log shows entries such as:

2024-05-12 10:14:33.872  ERROR  ccAlgrtserver  Database connection failed (WINCC_ALG_DB)
2024-05-12 10:14:33.872  ERROR  ccAlgrtserver  State: SQL Server not available / network error
2024-05-12 10:14:34.018  ERROR  ccAlgrtserver  Aborting startup. Exit code -1

Inspecting the failure with the Windows Event Viewer

1. Open Event Viewer → Windows Logs → Application.
2. Filter the source to CCAlgRtServer, CCSqlDrv, and MSSQLSERVER.
3. Look for Event ID 257 (SQL Server cannot bind a named pipe) or Event ID 7024 (service terminated with a service-specific error).
4. Open the WinCC_Sql_<ComputerName>_<Timestamp>.log file in C:\Program Files (x86)\Siemens\Automation\WinCC\Diagnose.

Solution: Clean Platform Approach (Recommended)

Siemens explicitly states that upgrading the Windows edition while WinCC is installed is not supported. The reliable fix is a clean installation of the supported Windows edition followed by a clean installation of WinCC V8. The previously created WinCC project file (.MCP) can be migrated forward.

Prerequisites

• Valid Windows 10 Professional or Enterprise license key.
• Original WinCC V8 installation media or Siemens Online Software Delivery (OSD) download.
• License keys (floating or single) for WinCC RT and, if applicable, the AlarmLogging and TagLogging options.
• Full project backup: copy the entire WinCC project folder (default: C:\Program Files (x86)\Siemens\Automation\WinCC\WinCCProjects\<ProjectName>) to external media.
• User archive and archive database exports (CSV / SQL backup) if you need historical data.

Step 1 - Back up the project

1. Open WinCC Explorer on the broken system while it is still partially functional.
2. Select Project → Backup → Create backup. This produces a compressed .zip archive that includes the .MCP file, graphics, scripts, and database exports.
3. Additionally copy the folder <ProjectName>\<ComputerName>\ to external media. This directory contains the Computer properties, the channel configuration, and the local archive paths.
4. Export the Tag Logging and Alarm Logging archive configuration as XML using the WinCC Configuration Studio (Project menu → Export) so the segment size and time base can be re-imported later.

Step 2 - Clean Windows 10 Professional installation

1. Back up all non-WinCC data from the system drive.
2. Create a Windows 10 Pro USB installer using the Microsoft Media Creation Tool.
3. Boot from the USB drive and select Custom install (do not choose "Keep personal files and apps" — WinCC must be installed on a freshly provisioned OS).
4. Install Windows 10 Pro, apply all current Windows updates, and install manufacturer drivers.
5. Disable Fast Startup (Control Panel → Power Options → Choose what the power buttons do → uncheck "Turn on fast startup"). Fast Startup interferes with service start order and is a frequent contributor to AlarmLogging hangs even on a clean install.
6. Set the regional and language settings to match the original project (decimal separator, thousand separator, system locale) before installing WinCC.

Step 3 - Install WinCC V8 prerequisites

WinCC V8 setup will install the prerequisites automatically if the option "Install prerequisites" is selected. The major prerequisites are:

Step 4 - Install SIMATIC WinCC V8

1. Insert the WinCC V8 DVD or mount the ISO.
2. Right-click Setup.exe → Run as administrator.
3. Follow the dialog. On the Package Installation page, select at minimum:
   • WinCC Runtime
   • WinCC Configuration
   • Alarm Logging
   • Tag Logging
   • SQL Server instance for WinCC
4. Accept the SQL Server service account as Local System unless your plant policy requires a dedicated domain account. If a domain account is used, ensure the account has Log on as a service rights and is a member of the local SQLServerMSSQLUser$ groups.
5. Complete the installation and do not restart the system immediately; finish all pending Windows updates first.

Step 5 - Restore the project

1. Open WinCC Explorer and choose Project → Restore → Restore from backup.
2. Point to the .zip created in Step 1.
3. WinCC will re-link the project to the new computer, recreate the Alarm and Tag Logging databases in the fresh SQL instance, and re-attach the user archive.
4. Re-apply your license using the Automation License Manager.

Step 6 - Repair the ccAlgrtserver service

1. Open Services (services.msc).
2. Locate SIMATIC WinCC AlarmLogging Server (display name) / ccAlgrtserver (service name).
3. Confirm the Log On tab uses either the Local System account or the domain account configured during setup, and that the password is correct.
4. Confirm the Dependencies tab lists SQL Server (WINCC) with a check mark. If it does not, the SQL Server instance failed to install; rerun the WinCC setup and select Modify → Repair.
5. Set the Startup type to Automatic (Delayed Start). The 60-second delay prevents the AlarmLogging service from trying to start before the SQL Server has finished recovery.
6. Start the service manually. Within a few seconds the Event Viewer should show a Started successfully entry.

Workaround: In-Place Repair (Without Clean OS Install)

If a clean OS install is not feasible in the short term (e.g. the operator station cannot be taken offline), the following repair sequence can be attempted. It addresses the most common post-upgrade symptoms without reinstalling Windows.

Step-by-step

1. Open Control Panel → Programs and Features.
2. Locate SIMATIC WinCC V8.0 (or appropriate version).
3. Select it and click Change → Repair. This re-registers COM components, refreshes the WinCC SQL instance, and re-issues service credentials.
4. When the repair completes, reboot.
5. Verify the ccAlgrtserver starts cleanly.

If the repair fails or the runtime still hangs at 28%:

6. Open SQL Server Configuration Manager → SQL Server Network Configuration → Protocols for WINCC.
7. Enable Named Pipes and TCP/IP. Set the TCP/IP listen port to 1433 for the default instance, or verify the dynamic port is not blocked by Windows Firewall.
8. In Computer Management → Local Users and Groups, confirm the group SQLServerMSSQLUser$<ComputerName>$WINCC exists. If it does not, the in-place upgrade stripped it; recreate the group and add the SYSTEM account plus the WinCC service account.
9. Run regedit as administrator. Verify the registry key HKLM\SOFTWARE\Siemens\WinCC\SQL\<InstanceName> exists and points to the correct SQL Server instance name. If absent, repair of WinCC should re-create it.
10. Delete the contents of C:\Program Files (x86)\Siemens\Automation\WinCC\Diagnose (logs only, not configuration) and try to start runtime again. The new log will contain a clean trace that can be sent to Siemens Technical Support if the issue persists.

Verification

1. Open WinCC Explorer.
2. Right-click the Computer → Properties. Confirm the Startup tab lists all four services (Graphics, AlarmLogging, TagLogging, Report Services) with Automatic startup type.
3. Click the Activate button in the toolbar.
4. Watch the progress meter. The bar must reach 100% within 60-90 seconds on a typical workstation. The system tray icon turns green.
5. Trigger a test alarm by setting a tag to a defined alarm state in the tag simulator (WinCC Explorer → Tools → Tag Simulation).
6. Open the Alarm Logging runtime window and confirm the test alarm appears with the correct timestamp, priority, and acknowledgement state.
7. Check the Status of the WinCC Services dialog (right-click the system tray icon → Status) and confirm all services report OK.
8. Open Task Manager → Details and confirm the following processes are running:
   • CCExplorer.exe
   • CCAlgRtServer.exe
   • CCTlgRtServer.exe
   • sqlservr.exe (instance WINCC)

Advanced Diagnostics

If the runtime still fails after the repair and the verification steps, gather the following evidence before opening a Siemens support ticket:

Troubleshooting Matrix

Preventive Best Practices

• Always confirm the Windows edition on the WinCC DVD label or in the SIMATIC WinCC installation guidelines before commissioning.
• Create a system image (e.g. with Disk2vhd or a vendor tool) immediately after a successful WinCC installation. This image becomes the recovery baseline.
• Schedule Back up WinCC project as a scheduled task nightly, exporting to a network share.
• Never perform a Windows edition in-place upgrade on a machine that hosts WinCC. Always plan a clean OS install.
• Use the Apdiag tool as a pre-flight check after any OS patch or service pack installation.

Field-Proven Notes

Engineers who have resolved this issue in production report three recurring patterns:

1. The 28% hang almost always points to AlarmLogging, but in 10-15% of cases it is actually a TagLogging symptom (the bar position is approximate). Always check both services.
2. When the SQL Server instance name was changed (e.g. from WINCC to WINCC2) the ccAlgrtserver configuration stored in the project file still references the old name. The fix is to either rename the instance back, or to use the WinCC Installation Manager to repoint the project.
3. Virtual machines tend to mask this issue at first because VSS snapshots restore the registry hive intact. Once a re-IP, re-activation, or checkpoint consolidation happens, the latent corruption surfaces. Always provision WinCC on physical hardware or on dedicated VMs with no prior WinCC image.