Fixing MTP1500 Unified Comfort Simulation Extended Download Error

1. Problem Overview

After applying a TIA Portal V17 update to a working project that includes both a SIMATIC TP1500 Comfort and a SIMATIC MTP1500 Unified Comfort panel, the Comfort panel simulation continues to operate normally, but the MTP1500 Unified Comfort simulation halts during startup. The Simatic Runtime Manager dialog displays:

• A long-running "Extended Download" phase that never completes.
• A final popup containing "General error during processing."
• The Runtime Manager log may also show entries tied to certificate handling, configuration download, or the Unified configurator when the failure occurs.

This fault is reproducible on Windows 11 Pro 24H2 with TIA Portal V17 engineering software, a CPU 1515-2 PN controller project, and a mixed HMI configuration (TP1500 Comfort + MTP1500 Unified Comfort). The failure is not triggered by the project, the panel selection, or the controller, but by the runtime/engineering version mismatch introduced when the TIA Portal update is applied without updating the paired WinCC Unified PC Runtime.

2. Affected System Configuration

3. Symptoms and Diagnostic Indicators

The failure chain presents a consistent set of indicators. Capture all of them before changing software; they form the fingerprint of a version mismatch.

1. Simatic Runtime Manager status bar: the launch sequence reaches the "Extended Download" step and stalls. The progress bar advances slowly, then freezes, then a dialog reports "General error during processing."
2. Runtime Manager log directory (%ProgramData%\Siemens\Automation\Logfiles\WinCCUnified or the configured RTILtrace location) shows the same timestamp for the stall followed by a generic failure, frequently with the tag UCSM, UMC, or ConfigDownload referenced.
3. TP1500 Comfort simulation continues to start and run, even though it shares the same engineering database. This is because the Comfort panels do not require the WinCC Unified PC Runtime; they use the WinCC flexible / Comfort simulation stack.
4. Browser/Edge never receives a complete runtime configuration; if launched manually, it shows either a missing configuration page or a stub indicating the project failed to deploy.
5. Siemens entry 315848 in the Siemens Industry Online Support describes the identical symptom stack and explicitly identifies the runtime/engineering version skew as the root cause.

4. Root Cause: Engineering / Runtime Version Mismatch

WinCC Unified PC Runtime and the TIA Portal engineering tool share a project schema and a configuration protocol. Siemens' official compatibility statement for WinCC Unified is:

The WinCC Unified PC Runtime must be at the same major version as the TIA Portal used to compile the project. Within a major version, the runtime must be at an update level that is greater than or equal to the engineering update level. A runtime that is older than the engineering will fail to load the compiled configuration, typically during the "Extended Download" phase of startup.

Mechanically, the compiled *.bin project file and the HMI configuration tag map include a build identifier that the runtime validates on load. When the build number of the runtime is lower than the build number embedded in the compiled project, the runtime rejects the configuration mid-download, leaving the Runtime Manager in the Extended Download state and reporting General error during processing to the user.

The TIA Portal V17 update path that triggered this fault is the standard Siemens delivery model:

• One installer updates the TIA Portal engineering (Step 7, WinCC, PLCSIM, Startdrive, etc.).
• A separate installer updates the SIMATIC WinCC Unified PC Runtime and the SIMATIC WinCC Unified PC Simulation.

When only the engineering installer is applied, the runtime on the same machine still reports the previous (lower) version, and the next simulation launch is the first time the conflict is observed.

5. Pre-Repair Diagnostic Checklist

Before installing anything, capture the version state of the system. This both confirms the diagnosis and provides a rollback target if a different fault is uncovered.

1. Open Start → Installed Products (Siemens Automation) and record the exact version, build, and installation date of every entry in the table below. Compare left/right columns for skew.

2. From the project tree in TIA Portal, right-click the MTP1500 → Compile → Software (rebuild all). This forces the project to a build number the runtime will check against.
3. Open Simatic Runtime Manager and remove the cached configuration for the project (right-click the entry → Delete configuration). Restart the Runtime Manager service: net stop "Siemens Runtime Manager" && net start "Siemens Runtime Manager" from an elevated command prompt.
4. Inspect the Unified certificate in the WinCC Unified Certificate Manager. A self-signed, default certificate is acceptable for local simulation. If the certificate is missing or expired, regenerate it before testing the runtime version alignment, because certificate failures produce overlapping error messages.

6. Solution: Align WinCC Unified PC Runtime to the TIA Portal Update Level

The repair is the runtime update that was skipped when TIA Portal was patched. There are three acceptable paths; pick the one that matches your environment.

6.1. In-place repair with the Siemens Update Installer (preferred)

1. Close TIA Portal, Simatic Runtime Manager, and any open Unified browser session.
2. Launch the Siemens Automation Software Update tool from the Siemens program group. This is the same updater used to patch TIA Portal.
3. Check the Installed products tree for the entries SIMATIC WinCC Unified PC Runtime and SIMATIC WinCC Unified PC Simulation.
4. Select both, then click Update selected. The updater will download the matching V17 Update n package and install it.
5. Reboot the workstation. Runtime services do not always restart cleanly without a full reboot after a major runtime patch.

6.2. Manual download from Siemens Industry Online Support

Use this path when the updater is unavailable (offline workstation, restricted internet access, controlled update window). Reference the official entries:

• SIMATIC WinCC V17 Runtime (TIA Portal) - update overview, entry 109792166
• SIMATIC WinCC V17 Runtime (TIA Portal) - delivery release, entry 109793105
• Siemens PDF: Simulation of WinCC Unified and Controllers V2 (entry 109748099)

1. Open the entry that corresponds to the TIA Portal update you installed (for example, V17 Update 4 → entry 109792166 or the matching successor entry).
2. Download the WinCC Unified PC Runtime package and the WinCC Unified PC Simulation package at the same update level.
3. Run both installers in elevated mode. Order does not matter for the simulation package relative to the runtime package, but the runtime must be installed first if the simulation installer is a child of it.
4. Reboot.

6.3. Direct installation of the latest V19 runtime (workaround)

If the operator cannot downgrade TIA Portal but can install a newer runtime, the runtime can be a major version ahead of the engineering and still simulate correctly, because the Unified runtime carries forward-compatibility for older engineering major versions. This is the path taken in the originating case: V19 WinCC Unified PC Runtime was installed against V19 engineering to clear the failure. It is a workaround, not a baseline. The recommended steady state is "engineering and runtime at the same major and update level".

7. Step-by-Step Recovery Procedure

The following ordered procedure is the most reliable field workflow. It assumes the diagnostic checklist in section 5 has been completed.

1. Open TIA Portal V17 with the affected project.
2. Select the MTP1500 in the project tree. Confirm in the Inspector window that the panel type is MTP1500 Unified Comfort (15" Unified Comfort) and not a TP1500 Comfort.
3. Compile the HMI: right-click MTP1500 → Compile → Software (rebuild all). Address any compile errors before proceeding.
4. Start the simulation: in the function bar, click Start simulation. TIA Portal will launch the WinCC Unified PC Simulation host. The Comfort panel can be simulated from the same project using the equivalent Comfort simulation entry point; this is documented in the Siemens "Migrating to WinCC Unified" guide (4.1 Simulating Operator Panels).
5. Watch the Simatic Runtime Manager. The expected state is Running within 30 to 90 seconds. The Extended Download phase should complete cleanly. The browser (Edge) should open to the runtime home page of the MTP1500.
6. If the failure repeats, re-check the Installed Products page; the runtime and the simulation must show the same major and update number. Mismatches at the second decimal (for example, V17 Update 3 runtime with V17 Update 4 engineering) are sufficient to break simulation.

8. Certificate and Unified Configurator Considerations

The Unified runtime relies on TLS for browser-hosted content. Local simulation uses a self-signed certificate generated by the WinCC Unified Certificate Manager or the Unified Configurator. Certificate problems overlap with version-mismatch problems in the user-visible symptoms, so they must be ruled in or out before the runtime update is declared the fix.

If any of the above checks fail, regenerate the certificate from the Certificate Manager before running the simulation again, even if the runtime version is now aligned. A stale certificate keeps the runtime in a startup retry loop and produces errors that look like version-mismatch errors.

9. Verification Checklist

Use this matrix to confirm the repair and to certify the workstation as "simulation-ready".

10. Preventive Maintenance and Best Practices

• Patch engineering and runtime together. The single largest contributor to this fault is patching TIA Portal without patching WinCC Unified PC Runtime. Adopt a one-step procedure: Siemens Automation Software Update on the same maintenance window, with all products selected.
• Track major versions explicitly. Maintain a workstation inventory of TIA Portal major version (V16, V17, V18, V19, …) and the matching WinCC Unified PC Runtime major version. The two columns must match in steady state; deviations are intentional and time-boxed.
• Avoid running the runtime as a newer major than the engineering in steady state. The reverse skew is supported, but it complicates certificate reuse and project migration. Use it as a temporary bridge only.
• Use the same engineering installation on all engineering workstations, the same runtime installation on all runtime/simulation workstations. A common pitfall is the runtime is updated on the engineer's laptop (which doubles as the simulation host) and the changes do not propagate to the office simulation host.
• Reboot after any runtime patch. The Unified runtime consists of several Windows services; a clean reboot is the cheapest way to guarantee the new build is loaded.
• Keep certificates current. Run the Unified Configurator after any hostname change, after any major runtime upgrade, and at least once per year.
• Document the simulation stack. Capture the Installed Products view as a baseline PDF in the project folder. New team members can diff their environment against the baseline in seconds.

11. Related Siemens References

• SIMATIC WinCC V17 Runtime (TIA Portal) - update overview, entry 109792166
• SIMATIC WinCC V17 Runtime (TIA Portal) - delivery release, entry 109793105
• Siemens PDF: Simulation of WinCC Unified and Controllers V2 (entry 109748099)
• Siemens TIA docs: 4.1 Simulating Operator Panels - Guide for Migrating to WinCC Unified