WinCC Flexible 2008 Runtime on Windows 8: Migrate to TIA V14 SP1

Siemens HMI software has undergone three major generational shifts since the WinCC Flexible 2008 era: the move into the Totally Integrated Automation Portal (TIA Portal) with WinCC Advanced RT V12, the consolidation to TIA Portal V14 in 2016, and the formal Windows 10 enablement delivered by TIA Portal V14 SP1. Engineers who still operate WinCC Flexible 2008 Runtime on Windows XP or Windows 7 face a hard retirement question when the host PC must be replaced with Windows 8, Windows 8.1, or Windows 10 hardware. This reference consolidates the runtime/OS compatibility matrix, the documented PG/PC interface network-card detection fault, and the migration ladder that takes a WinCC Flexible 2008 SP4 project all the way to TIA Portal V14 SP1 without losing HMI tags, screens, or alarms.

1. Runtime/OS Compatibility Matrix

The single most common point of failure when moving WinCC Flexible 2008 Runtime (RT) onto a newer PC is the unsupported host operating system. The table below summarizes the runtime edition against the host operating systems for which the corresponding service pack was validated. Service packs are mandatory: WinCC Flexible 2008 without SP4 is not equivalent to WinCC Flexible 2008 SP4 and the OS support differs.

Siemens formally ended mainstream support for WinCC Flexible 2008 with the last delivered service pack (SP4) and the upgrade path was progressively redirected to TIA Portal. Operators that need to keep a WinCC Flexible 2008 SP4 project running on Windows 8 must either accept the functional caveats listed below or migrate the project forward through the TIA Portal upgrade wizard.

2. Why WinCC Flexible 2008 RT Behaves Anomalously on Windows 8

The Windows 8 kernel exposes a substantially different driver stack than Windows 7. The two integration points that consistently trip up WinCC Flexible 2008 Runtime are:

1. PG/PC Interface enumeration. The legacy Set PG/PC Interface tool, which ships with SIMATIC NET and is used by WinCC Flexible to bind to PROFINET, MPI, PROFIBUS, or TCP/IP back-channels, calls a Windows API that changed between Windows 7 and Windows 8. The tool may install cleanly but list zero network cards.
2. Signed-driver enforcement. Windows 8 enforces driver signature verification by default. SIMATIC NET components released against WinCC Flexible 2008 predate Windows 8 and therefore require either a test-mode boot or an updated SIMATIC NET redistributable that supplies signed drivers.
3. UAC and Start Screen replacement. WinCC Flexible 2008 RT depends on classic Win32 services that, when launched from a non-elevated token on Windows 8, cannot register the HMI runtime as a system service. This shows up as RT not starting, or as RT starting but HMI tags staying at initial value.

The Microsoft look and feel question raised in the original field report (whether a Simatic Touch Panel PC running Windows 8 can be styled like Windows XP) is largely cosmetic. The functional issue is always at the OS/runtime boundary described above. Microsoft's documentation on down-level UI shells is summarized in Can I make Windows 8 look and feel like Windows XP?, but those shell replacements do not change the kernel driver model that WinCC Flexible 2008 depends on.

3. The PG/PC Interface Network Card Detection Fault

3.1 Symptom

After installing WinCC Flexible 2008 Runtime on a clean Windows 8 host, the Set PG/PC Interface control-panel applet (under Control Panel → All Control Panel Items → Set PG/PC Interface) shows an empty Interface Parameter Assignment Used drop-down. The two physical NICs detected by Windows are absent. Any S7 / PROFINET transfer fails with:

Error: Cannot establish a connection to the PLC.
Error code: 0x000003E7 (connection path invalid)

3.2 Root Cause

The 2008-era Set PG/PC Interface tool enumerates network adapters through a deprecated NDIS 5.x API path. Windows 8 prefers NDIS 6.x drivers and, when no NDIS 5.x binding is registered, returns an empty adapter list. The underlying network stack is healthy (ping and TCP/IP work), but the legacy enumeration fails.

3.3 Solution

1. Install the latest SIMATIC NET PC software that ships with WinCC Flexible 2008 SP4 or newer. The redistributable provides an updated s7onlinx.dll that re-registers the NDIS binding.
2. If SIMATIC NET is not available, force the legacy enumerator by importing the registry key:
   HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\S7ONLINE\SetPGPCInterface\ForceLegacyEnum = 1 (DWORD)
3. Reboot and re-open Set PG/PC Interface. Both NICs should now appear.
4. Assign the correct access point (typically S7ONLINE) to the desired NIC and confirm the assignment by clicking Diagnostics. A successful Read PLC round-trip confirms the fix.

3.4 Verification

1. Open WinCC Flexible 2008 → Transfer → Transfer Settings.
2. Select "Ethernet" mode and choose the correct NIC.
3. Click "Search" — the target PLC station should appear within 3 s.

4. The Clean Migration Path: WinCC Flexible 2008 RT to WinCC Advanced RT V12

When the WinCC Flexible 2008 Runtime on Windows 8 is unstable, the recommended path documented by Siemens is a project migration to WinCC Advanced RT V12, which sits on TIA Portal V12 and is formally validated for Windows 8.

4.1 Prerequisites

• Original WinCC Flexible 2008 SP4 source project (.hmi or .log archive).
• TIA Portal V12 SP1 or later installed on a Windows 7 / Windows 8 engineering station.
• Matching TIA Portal V12 license key for WinCC Advanced (single-station or floating).
• S7-300 / S7-400 / S7-1200 / S7-1500 PLC program (the HMI migration does not touch PLC code).

4.2 Step-by-Step Migration

1. Archive the WinCC Flexible 2008 project. In the source engineering tool choose Project → Archive. The result is a single .zip that contains the .hmi file plus all referenced graphics.
2. Open TIA Portal V12 and create a new project. Select the device family that matches the original panel (e.g., SIMATIC Comfort Panel KTP1200).
3. Run the migration wizard. Project → Migrate project. Browse to the archived .zip. The wizard will report an estimated migration time and a list of objects that cannot be carried forward automatically (typically custom ActiveX controls and third-party VB scripts).
4. Resolve migration warnings. Open the Migration Log pane. Each warning must be either accepted (with a manual fix later) or remediated by editing the equivalent TIA Portal object. The most common warning category is Cross-reference broken, caused by renumbered tag addresses.
5. Recompile the HMI runtime. Press F7 (Compile → Software (rebuild all)). The output is a .fwx runtime file deployed to the panel or to a WinCC Advanced Runtime station.
6. Deploy the runtime. On the Windows 8 target PC, install WinCC Advanced RT V12 using the SIMATIC WinCC Advanced RT V12 setup. Start the AutoStart configurator and select the migrated .fwx.

4.3 Verification

- Boot the Windows 8 PC and confirm the WinCC Advanced RT icon appears in the system tray.
- Start the runtime. The opening screen should match the migrated Flex 2008 layout.
- Force a tag write from the PLC and verify the value updates on the HMI within one polling cycle.
- Disconnect the Ethernet cable — the runtime should log a "connection lost" alarm and reconnect automatically when the cable is reinserted.

5. TIA Portal V14 and Windows 10

The base release of TIA Portal V14 (released September 2016) shipped with a Windows 10 compatibility statement that was, in practice, incomplete. Specifically, the WinCC Advanced Runtime component was not formally certified for Windows 10 in the V14 GA build; the engineering portions (STEP 7 V14, WinCC V14) installed but the runtime would refuse to start on a clean Windows 10 host with:

HMI Runtime error 130004:
"Operating system version not supported."

This matches the field report that the V14 base release "is not compatible with Win10". Siemens communicated this through the Siemens Industry Online Support portal and through the TIA Portal installation log.

6. TIA Portal V14 SP1 — Windows 10 Enablement

The first TIA Portal V14 service pack (V14 SP1) delivered the missing Windows 10 support. It re-signed the runtime binaries against the Windows 10 driver signature database, updated the installation manifest to recognize Windows 10 build 1607 (Anniversary Update) and later, and added the corresponding registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Automation\WinCC\RT\SupportedOSWin10 = 1 (DWORD)

Engineers who have a valid TIA Portal V14 Software Update Service (SUS) contract receive V14 SP1 through the Automation License Manager automatically. Those without SUS must purchase the upgrade.

7. Simatic Touch Panel PC — Choosing the Runtime Platform

Siemens' SIMATIC IPC line (IPC227G, IPC277G, IPC477G, IPC677G) ships with a pre-installed Windows Embedded Standard 7 or Windows 10 IoT Enterprise image. These images strip the consumer shell and present a deterministic Win32 desktop suitable for a long-lifecycle HMI station. When the panel must show a Windows 8 look and feel, the realistic options are:

For a Windows 8 look and feel on a SIMATIC Touch Panel PC, the original Microsoft Surface Pro suggestion in the source thread is feasible only if the device carries a non-Embedded Windows 8 / 8.1 Pro license and the runtime is migrated forward to at least WinCC Advanced RT V12. The Modern UI shell (formerly Metro) cannot be fully disabled without third-party utilities such as StartIsBack or the Windows 8.1 Show the Apps view automatically group-policy setting.

8. Pre-Migration Checklist

Run through this list before starting any project migration. Each item reduces the risk of a mid-migration rollback.

1. Inventory the panels. Capture the Siemens MLFB (order number) of every panel in the field. Comfort Panels (TP700 / TP900 / TP1200 / TP1500 / TP1900 / TP2200) and Mobile Panels (KTP400 / KTP700 / KTP900) each map to a specific TIA Portal device version.
2. Audit the project files. List every .hmi, every graphic library, every script library, and every third-party ActiveX control. The TIA Portal migration wizard cannot recover deleted dependencies.
3. Capture the PLC tag interface. Export the STEP 7 symbol table to .sdf or .xlsx. The TIA Portal HMI tag generator will re-import this file and rebuild the HMI tag database.
4. Document alarms. Export the WinCC Flexible alarm log to .csv. The alarm classes (Errors, Warnings, System) need to be re-mapped in the TIA Portal HMI Alarms editor.
5. Verify the engineering licenses. A valid TIA Portal license key is required on every engineering station that opens the migrated project.
6. Stage the target PC. Install WinCC Advanced RT V12 (or V14 SP1, if Windows 10) on the target PC before deploying the migrated project. Confirm the AutoStart configurator registers the runtime as a Windows service.

9. Troubleshooting Matrix

10. Field-Proven Caveats

• Driver signing on Windows 8. WinCC Flexible 2008 SP4 was the last Flex edition, but the SIMATIC NET CD shipped with that SP4 was signed against the Windows 7 driver database. On Windows 8, install SIMATIC NET V13 SP1 or later alongside the Flex 2008 SP4 runtime to obtain signed drivers.
• UAC and AutoStart. On Windows 8, the WinCC Flexible 2008 AutoStart configurator writes a per-user registry key. If the runtime is configured to run from a non-elevated user, the runtime service is silently dropped at log-off. Always use the dedicated HMIUser local account.
• Project size limit. TIA Portal V12 and V13 enforce a project archive size of 2 GB. Very large WinCC Flexible 2008 projects with hundreds of screens and embedded graphics can exceed this on first archive and must be split into sub-projects.
• Multi-user engineering. WinCC Flexible 2008 supported Team Edition multi-user check-in/check-out through the SIMATIC Logon service. TIA Portal V12+ replaces this with a multi-user server. Plan for a transition window where both engineering tools run in parallel.
• Windows 10 long-term servicing. The 2016 LTSB branch of Windows 10 IoT Enterprise was the first branch validated for TIA V14 SP1. The 2019 LTSC branch is validated for TIA V15.1 and later; do not mix branches without re-verifying.

11. Step-by-Step Verification After Migration

1. Cold-boot the target PC. Power off, wait 30 s, power on. Confirm the Windows login screen appears and that the HMIUser auto-logs in.
2. Confirm the runtime started. The WinCC Advanced RT tray icon should appear within 30 s of login. Hovering the icon must show the project name and the active PLC connection.
3. Trigger a forced tag refresh. From the PLC, write a known value to a tag that is displayed on the opening screen. The value must update within one polling cycle (typically 250 ms to 1 s, configurable).
4. Exercise every alarm class. Force an Error, Warning, and System alarm from the PLC. Each must display in the correct color and must clear automatically when the PLC bit is reset.
5. Disconnect and reconnect the network. Pull the Ethernet cable for 30 s, then reinsert. The runtime must log a Connection interrupted alarm and clear it without operator intervention.
6. Power-fail recovery. Hard-reset the PC. The runtime must auto-start and reload the last project state.

12. FAQ