TIA Portal V15.1 Crash When Adding HMI Buttons: Root Cause and Fix

STEP 7 / WinCC inside TIA Portal V15.1 can terminate unexpectedly with an unhandled exception the moment an HMI button (or any configured HMI object with the same object factory path) is dragged into a panel screen. The application closes, the Just-In-Time debugger offers to attach, and a Siemens crash report is generated. This article documents the engineering root cause, the environment assumptions, the official Siemens knowledge base references, and the validated fix path. The same V15.1 line also produces a separate, related crash inside the Cross-reference Editor on S7-1200 CPUs; both faults share the V15.1 maintenance branch and are documented separately by Siemens Support.

1. Problem Description

Symptom: TIA Portal V15.1 is running normally. A new HMI button is dropped from the Toolbox onto an HMI screen of any of the following device families:

• SINAMICS TP / Comfort Panels (TP700 Comfort, TP900 Comfort, TP1200 Comfort, TP1500 Comfort, TP1900 Comfort, TP2200 Comfort)
• SIMATIC Basic Panels (KTP400 Basic, KTP700 Basic, KTP900 Basic, KTP1200 Basic)
• SIMATIC Mobile Panels (KTP700 Mobile, KTP900 Mobile, KTP1000 Mobile, KTP1200 Mobile)
• WinCC Runtime Advanced / Professional targets embedded in the TIA project

Within 1-3 seconds, the integrated engineering environment disappears. The Windows Event Viewer records a .NET runtime exception raised from Siemens.Automation.Hmi.Controls.dll or Siemens.Engineering.Hmi.dll. The Siemens Error Reporting tool (SRT) opens and prompts the user to forward a ZIP bundle to Siemens. No project data is lost if the most recent save is recent.

2. Affected Versions and Environment

Siemens does not list Windows 11 in the released operating-system matrix for TIA Portal V15.1. The compatibility matrix that ships with the installation media lists Windows 7 SP1, Windows 10 (versions 1607 to 1909 for the base V15.1 release; later updates for incremental TIA updates where explicitly released), and Windows Server 2012 R2 / 2016 / 2019. The user's confirmation in the engineering discussion that V15 was running on Windows 11 is technically an unsupported configuration. Windows 11's tightened UIPI (User Interface Privilege Isolation) rules and the new .NET CLR activation changes are sufficient to convert a soft V15.1 issue into a hard process termination.

3. Root Cause Analysis

Two independent causes can produce the symptom. Diagnose both before assuming a single fix path.

3.1 Cause A — Missing Project Language

The HMI object factory in TIA Portal V15.1 attempts to enumerate the translation matrix for the new object across every active project language. If the only project language is a non-installer language (for example, Spanish, French, Italian, Portuguese, Chinese-Simplified, Japanese, Korean, Turkish, Polish, Czech, Russian), the localization table for that object contains a null key in the resource bundle. The first object-property access path that consumes the null key raises an unhandled System.Resources.MissingManifestResourceException in the HMI Designer subsystem. The exception is not caught by the V15.1 fault barrier; the JIT debugger hooks the process and the application terminates.

The fix is to enable English (United States) or German (Germany) as a project language. Either one of those two languages ships as a built-in resource in the TIA Portal V15.1 installer and is the minimum guaranteed fallback for every HMI object factory in this release line.

3.2 Cause B — Unsupported Windows 11 Host

Windows 11 enforces strict activation context checks for COM components and modifies the way the TIA Portal V15.1 shell loads XAML resource dictionaries. The activation context that V15.1 ships with does not declare Windows 10 21H2/22H2 nor Windows 11 compatibility GUIDs. The shell's fault barrier cannot recover from a Win32-level STATUS_DLL_NOT_FOUND raised deep inside the HMI object activation, so the entire S7TIA.exe process is torn down.

4. Related V15.1 Update 2 Crash: Cross-Reference Editor with S7-1200

Siemens Support entry ID 109768712 documents a separate, but version-adjacent, V15.1 crash. The symptom, the affected branch, and the engineering mitigation are listed below for completeness because field engineers routinely encounter both defects in the same project.

• Symptom: Opening the Cross-reference Editor while a project contains an S7-1200 CPU causes STEP 7 (TIA Portal) V15.1 Update 2 to crash.
• Affected: STEP 7 V15.1 Update 2 with S7-1200 CPUs (any firmware; the defect is in the engineering tool, not the CPU firmware).
• Resolution path: Apply the update identified in the Siemens Support entry or migrate to the successor TIA Portal version (V16 or later) that contains the corrected Cross-reference Editor build.

Reference: Why does STEP 7 (TIA Portal) V15.1 crash when you are looking for cross-references with the S7-1200 CPU?

5. Diagnostic Procedure

Run the following ordered checks before applying any fix. The order is chosen to surface the most likely cause first and to avoid masking the second cause with the first fix.

1. Open the Siemens Error Reporting tool output (the ZIP generated when TIA Portal closes). Extract the .dmp file. Confirm the faulting module is one of: Siemens.Automation.Hmi.Controls.dll, Siemens.Engineering.Hmi.dll, or HmiDesigner.dll. If a different module is at the top of the stack, this article does not apply.
2. In TIA Portal, open the project, right-click the project node, choose Properties > Project languages. Record every active language. The most common failing configuration is a single language that is not English (United States) or German (Germany).
3. On the engineering host, press Win+R, type winver, and confirm the Windows version. Anything that reports as Windows 11 is out of the V15.1 support envelope.
4. Launch TIA Portal with verbose logging by setting the environment variable SIEMENS_TIA_LOGLEVEL=4 before invoking S7TIA.exe. Reproduce the crash and inspect the log for entries containing MissingManifestResourceException (Cause A) or STATUS_DLL_NOT_FOUND (Cause B).
5. Open the Windows Event Viewer, navigate to Windows Logs > Application, and locate the .NET Runtime error. The Application Error event typically lists the faulting module and the exception code 0xC0000005 or 0xE0434352.

6. Resolution Path A — Enable English or German as a Project Language

This is the validated fix for the HMI button crash when the engineering host is a supported Windows version and the only project language is a non-installer language.

1. Close all open TIA Portal instances.
2. Open the project. In the Project Tree, right-click the project node and select Properties.
3. Select the Project languages tab.
4. Click Add and select English (United States) or German (Germany) from the language list. Either language is sufficient. Adding both is harmless and is recommended for multi-region engineering teams.
5. Click OK to close the Properties dialog.
6. Save the project (Ctrl+S) and commit to the engineering repository if applicable.
7. Open any HMI screen and drag a new Button object from the Toolbox onto the screen.
8. Verify the Button is placed without crash, then drag a Switch, a Symbolic IO field, and a Rectangle to confirm the object factory has been fully initialized.

7. Resolution Path B — Replace the Unsupported Windows 11 Host

If the engineering host is Windows 11, the correct engineering remediation is one of the following, in order of preference:

1. Run TIA Portal V15.1 inside a Windows 10 (1909 or 1809 LTSC) virtual machine on a Windows 11 host. The VM must be 64-bit, must enable nested paging, and must have at least 16 GB of RAM assigned.
2. Dual-boot the engineering workstation into Windows 10. Siemens' released compatibility matrix is the governing reference; engineering hosts running outside that matrix are not eligible for standard support.
3. Migrate the project to a successor TIA Portal version that lists Windows 11 in its compatibility matrix. As of the V15.1 maintenance timeline, V17 and later list Windows 10 (1909, 21H2) and Windows 11. The project can be upgraded using TIA Portal's Project > Migrate project wizard. Verify hardware catalog support for every device in the project before committing to a migration; not every S7-1200 / S7-1500 / Comfort Panel firmware is supported in every TIA version.

8. Forwarding the Project to Siemens Support

If Cause A and Cause B are both eliminated and the crash still reproduces, the project itself contains the trigger. The engineering team should escalate as follows:

1. Open the Siemens Industry Online Support portal: https://support.industry.siemens.com.
2. Submit a Support Request with the project name, the V15.1 Update level, the Windows version, the affected device (PLC type and HMI type with order numbers), and the crash log ZIP.
3. Attach the project (or a minimized reproduction) only after removing any sensitive PLC program logic. The Siemens SRT (Siemens Report Tool) can package the project automatically when the user accepts the prompt at the time of the crash.
4. Reference the support request in the engineering change log so the fix is traceable when the corrected TIA Portal update is released.

9. Workarounds That Buy Time

10. Verification Checklist

After applying the fix, run the following verification to confirm the engineering environment is healthy.

1. Open the project. TIA Portal should load the project in under 60 seconds for a typical single-CPU + single-HMI project. If load time exceeds 5 minutes, the SQL Server instance is degraded; restart the Siemens TIA Portal Agent service and re-test.
2. Open the HMI screen where the crash previously occurred. Drag a Button from the Toolbox onto the screen. The button must appear in the layout within 1 second.
3. Configure an event on the button (for example, Press → SetBit on a tag in the connected PLC). Compile the HMI. The compile must complete without warnings about missing language resources.
4. Right-click the project node, choose Compile > Software (rebuild all). The compile must finish without the HmiRTm error code 13:0x0000000D (HMI object factory resource miss).
5. Open the Cross-reference Editor for the S7-1200 CPU. Per Siemens Support entry 109768712, if the V15.1 Update level is 2, the editor will still crash until the V15.1 successor update is applied.
6. Save the project and close TIA Portal. Re-open the project and confirm the HMI button created in step 2 is present and configured.

11. Prevention Checklist for Future Projects

• Always include English (United States) and the operator's native language as project languages when starting a new TIA Portal V15.1 project. Two languages is the recommended minimum.
• Keep the engineering host OS inside the released Siemens compatibility matrix. If the host is Windows 11, run TIA Portal in a Windows 10 VM.
• Apply TIA Portal V15.1 updates only after reviewing the Siemens Support release notes. Each update lists the defects it addresses.
• Document the TIA Portal Update level and the Windows version in the project cover sheet so that any engineer opening the project later has the same engineering context.
• Forward reproducer projects to Siemens Support via Support Request. A reproducer allows Siemens engineering to issue a fix in the next maintenance update.

12. Related Engineering Constraints

When this defect is present in a project, the engineering team should not:

• Schedule a factory acceptance test (FAT) on the affected V15.1 environment without first applying the fix. An HMI crash during a customer-witnessed test creates a contractual escalation.
• Assume the Comfort Panel firmware is the cause. Firmware from V14.0.0.0 to V15.1.0.0 is unaffected; the defect is in the engineering tool, not the panel runtime.
• Roll the PLC CPU firmware back in an attempt to clear the cross-reference Editor crash. The PLC firmware does not influence the engineering tool's Cross-reference Editor build.