WinCC v14 on Windows 10: Troubleshooting HMI Placeholder Icons

1. Problem Overview

When migrating a TIA Portal V14 WinCC Runtime (RT) project from Windows 7 to a Windows 10 workstation, the most frequently reported symptom is that all lamp-type HMI objects (bit-field tags from the PLC) stop displaying their configured graphic and instead show a stock desert scene containing a cactus and a sun. The underlying PLC connection is verified end-to-end:

• Ethernet interface on the new PC is configured with the same static IPv4 address as the previous unit.
• The new PC can ping the PLC CPU's IP address successfully.
• No firewall or Windows Defender prompt blocks the connection.

Despite reachability, the HMI mimics a "no graphic available" state across every faceplate. This is rarely a single failure mode; in production environments, three independent root causes are typically found:

1. OS compatibility miss: WinCC RT V14 is not released for Windows 10. Only V14 SP1 (or later) is supported, and only on Windows 10 1607 LTSB / Enterprise / Professional.
2. Tag-address regression: HMI tags silently switch from absolute addressing to symbolic addressing, decoupling them from the PLC's data block layout.
3. Display scaling mismatch: Different DPI settings between the engineering station (ES) where the project was last saved and the runtime station (RT) cause the HMI to refuse to render certain graphics.

Each of the three failure modes produces a visually identical "desert placeholder" icon, which is why field engineers often misdiagnose the issue as a firewall or NIC problem when, in reality, the OS, the project file, and the display subsystem are all conspiring.

2. Symptom Identification: The Desert Placeholder

The desert scene with a cactus and a sun is a built-in TIA Portal placeholder. It is rendered by WinCC RT whenever one of the following conditions is met:

3. Root Cause #1: Windows 10 Compatibility

Siemens product support for the TIA Portal V14 generation follows a strict OS matrix:

Critical: V14 without SP1 is not released for any Windows 10 edition. The installer may succeed, the RT may start, and the project may load, but HMI graphics rendering, alarm logging, and recipe services exhibit undefined behavior. Always confirm the WinCC RT version before the OS migration.

Use the official Siemens Compatibility Tool to verify the matrix for the specific RT build, HMI panel firmware, and PLC firmware combination in use. The tool accepts TIA Portal versions, WinCC versions, and PLC firmware versions as input filters.

Recommended remediation path when V14 base is installed on Windows 10:

1. Capture a full TIA Portal project backup (.zap14 archive).
2. Install TIA Portal V14 SP1 (or later) on the engineering station.
3. Open the project, accept the upgrade prompts, and recompile both the HMI and PLC sides.
4. Re-download the runtime image to the RT PC.

4. Root Cause #2: HMI Tag → PLC Variable Decoupling

The most common cause of the desert placeholder after an ES/RT swap is a silent addressing-mode change. In TIA Portal V14, HMI tags referencing PLC variables can be configured in two modes:

• Absolute addressing: Direct memory area, e.g. %DB5.DBX0.0 or %MW10.
• Symbolic addressing: Reference to a named tag in the PLC's data block, e.g. "HMI_Control".Lamp_Run.

When the HMI project is opened on a workstation with a different TIA Portal installation (different language, different update level, or a fresh PC), the project may upgrade the tag list and convert absolute addresses to symbolic. If the PLC has not been re-compiled and downloaded, the symbolic name does not resolve to a live address, and the HMI sees an unlinked tag — triggering the placeholder bitmap.

4.1 Diagnosing Tag Decoupling

1. Open the affected project in TIA Portal on the engineering station.
2. Navigate to HMI Tags in the project tree.
3. Right-click the tag table and choose Show all columns.
4. Inspect the Connection, Address, and Symbolic access columns:

4.2 Repairing Tag Decoupling

1. In TIA Portal, switch the project's HMI tags back to absolute addressing (or to the mode the PLC DB was last compiled with).
2. Open the PLC's Program blocks → DB in cross-reference and confirm the tag name, type, and offset.
3. Recompile the PLC software (full rebuild) and download it to the CPU.
4. Recompile the HMI software (full rebuild) and download the RT image.
5. Cycle the WinCC RT process: Stop Runtime → Start Runtime or restart the CCRtHmiObjMgt service.

5. Root Cause #3: DPI / Display Scaling Mismatch

TIA Portal V14 records the DPI scaling used by the engineering station at the time the project was last saved. WinCC RT enforces the same scaling at runtime; if the two values differ, the renderer drops back to the placeholder graphic for any object whose bounding box was clipped by the scale change. This is documented in Siemens KB article 13899072.

5.1 Required DPI Settings

5.2 Setting the Runtime DPI

1. Right-click the Windows 10 desktop → Display settings.
2. Set Scale to the same percentage used on the engineering station.
3. Click Advanced scaling settings and verify the override is unchecked.
4. Log off and back on (DPI changes do not apply to running processes).
5. Restart the WinCC RT service.

6. Diagnostic Procedure (Sequential)

Apply the following sequence on the Windows 10 RT PC. It is ordered from least-invasive (no project changes) to most-invasive (full project rebuild).

1. Verify OS compatibility: winver → confirm build 1607 (14393) or the build certified by Siemens for your RT version. Cross-check with the Siemens Compatibility Tool.
2. Verify network reachability: From a CMD prompt on the RT, run ping <PLC IP> and telnet <PLC IP> 102. Both must succeed.
3. Verify WinCC RT version: In TIA Portal, Project tree → Runtime settings → General, or on the RT PC open Help → About.
4. Check the HMI tag status online: With RT running, open TIA Portal → HMI Tags → Tag Status (or use the HmiTagMonitor tool). Tags must show "Good" quality, not "Bad".
5. Check DPI parity: Settings → Display → Scale and Layout. Compare with the ES.
6. Rebuild the RT image: In TIA Portal, HMI device → Compile → Software (rebuild all), then Download to device → Software (all).
7. Rebuild the PLC: PLC → Compile → Software (rebuild all), then download to the CPU.
8. Cycle the RT: Stop and restart the WinCC Runtime service.

7. Firewall and Windows Service Configuration

Although the placeholder icon is rarely firewall-induced, the Windows 10 default firewall profile is more aggressive than Windows 7. Configure the following to rule out a parallel network failure:

Quick command-line verification on the RT PC:

netsh advfirewall firewall add rule name="S7COMM" dir=in action=allow protocol=TCP localport=102
netsh advfirewall firewall add rule name="WinCC-RT" dir=in action=allow program="C:\Program Files\Siemens\Automation\WinCC RT\bin\CCRtHmiObjMgt.exe"

8. Verification

After applying the corrective steps, confirm the fix with the following checklist:

• All HMI lamps display their configured graphics (not the desert placeholder).
• TIA Portal Tag Status view shows quality code 0xC0 for all lamp tags.
• The HMI alarm window populates within two polling cycles of an acknowledged alarm.
• The WinCC RT system log contains no entry matching the pattern Graphic 0x0[0-9A-F] missing.
• A PLC-to-HMI value change is reflected on the screen within the configured update cycle (default 1 s for non-cyclic tags, 100 ms for cyclic tags).
• A power-cycle of the RT PC (cold start) leaves the configuration intact and the screens rendered correctly without manual intervention.

9. Prevention and Best Practices

• Standardize the ES image: Deploy the same TIA Portal version (V14 SP1 update level), the same Windows 10 build, and the same DPI scale on every engineering workstation.
• Version-pin the HMI tags: Always re-compile both the PLC and HMI sides together; never upgrade one without the other.
• Document the OS matrix: Maintain a one-page matrix of "RT version × Windows build × Panel firmware × PLC firmware" at the commissioning station.
• Use the compatibility tool at design time: Run the Siemens Compatibility Tool on every migration, including minor Win10 build changes (e.g., 1607 → 1709).
• Archive the project before any migration: Use Project → Archive (.zap14) and store the archive with the configuration change ticket.
• Keep the firewall rules scripted: Maintain a PowerShell or netsh script that re-applies the S7COMM and WinCC RT rules after any Windows 10 feature update.

10. Troubleshooting Matrix (Symptom → Cause → Fix)

11. Frequently Asked Questions