Resolving TIA Portal V11 WinCC Menu & Toolbar Unexpected Error

The TIA Portal V11 SP2 engineering environment ships with a known defect that affects the WinCC Professional (and to a lesser degree WinCC Comfort/Advanced) runtime editor. When the user opens Menu & Toolbar configuration under an HMI device or global screen, the TIA Portal host process raises an unhandled exception, displays a generic "Unexpected error" dialog, and offers a "Restart application" prompt. After the restart, the same fault re-occurs the moment the editor is opened again, making it impossible to assign user-defined menus, function keys, or toolbars to the HMI project. This article documents the confirmed root cause, the two recovery paths confirmed by Siemens support, and the supporting diagnostics for distinguishing user-profile corruption from project-level corruption.

1. Problem Symptoms

The failure presents with a deterministic sequence of events. Engineers should confirm all of the following before applying the recovery procedure, because the same symptom can be produced by unrelated defects (e.g., a corrupted HMI project file or an .NET runtime mismatch):

1. The user selects an HMI device (or opens the project library) in the TIA Portal project tree.
2. The user right-clicks Menu & Toolbar under HMI tags / Screen management and chooses Edit, or opens the editor by double-clicking.
3. The TIA Portal host (Siemens.Automation.Portal.exe) terminates with the modal dialog:
   "An unexpected error has occurred. We are sorry for the inconvenience. Restart the application?"
4. After clicking Restart, the environment reloads, but the editor crashes identically the next time it is opened.
5. The defect reproduces in every project on the workstation, including newly created ones with no user-added HMI screens.

Two related secondary symptoms are sometimes reported in the same environment:

• Missing menu entries when the HMI runtime editor is opened for the first time after installation.
• Slow first-launch of the Menu & Toolbar editor followed by an out-of-memory exception on x86 hosts with less than 4 GB RAM.

2. Affected Versions and Configuration

The defect is independent of the Windows version, but is most frequently observed on Windows 7 SP1 (32-bit and 64-bit) with .NET Framework 4.0/4.5. On Windows 8 and Windows Server 2008 R2 hosts, the same root cause produces a similar stack trace in the TIA Portal log.

3. Root Cause Analysis

Siemens has not published a detailed public RCA, but two distinct triggers are documented in the engineering support database and reproduced by field engineers:

1. Corrupt user-scoped settings file. The TIA Portal stores editor layouts, last-opened paths, and the Menu & Toolbar state for the HMI runtime editor in Settings.xml under the per-user roaming profile. When this file becomes inconsistent with the host schema (typically after a partial Update installation, an aborted Windows shutdown, or a copy of a profile between machines), the editor fails to deserialize its configuration and throws the unhandled exception.
2. Defect in V11 SP2 base build. Even with a clean Settings.xml, the base SP2 build (without Update 5) can produce the same stack trace when the Menu & Toolbar editor instantiates a non-initialized IEditorContext. The fix ships in Update 5 for V11 SP2.

Because the two triggers are indistinguishable from the user interface, the recovery workflow attempts the lighter user-profile fix first, then escalates to the software hotfix.

4. The Settings.xml File – Location and Function

The TIA Portal V11 stores editor and view state information in a per-user XML file. The file is regenerated automatically on first launch if it is missing or invalid, but only if the host process does not crash on a partial read.

Backup the file before any manipulation. The path is the same for both the single-user installation and a parallel admin install: only the user profile component changes.

5. Pre-Flight Diagnostics

Before touching the engineering workstation, perform the following checks to confirm the failure mode:

1. Inspect the TIA Portal log. Open %LOCALAPPDATA%\Siemens\Automation\Portal V11\Logs (or the equivalent for older TIA Portal builds) and look for EditorHostException with the inner exception NullReferenceException at Siemens.Hmi.Editor.Toolbar.ToolbarEditor.Load(). This signature is the Menu & Toolbar defect.
2. Test with a brand-new project. File > New project > PC station with WinCC Professional. If the crash reproduces with no custom HMI screens, the cause is environmental (user profile or installation), not project-level.
3. Test with a second Windows user. Create a local Windows account, log in once, and open the same TIA Portal project. A clean profile that does not crash confirms the corrupt Settings.xml theory.
4. Confirm the build number. In TIA Portal: Help > About. The build should be reported in the form V11.0 + SP2 + Update X. A value of V11.0 + SP2 without any Update suffix is the affected configuration.

If only the original user is affected and a second user is clean, the problem is isolated to Settings.xml and can be fixed without touching the installation.

6. Solution 1 – Reset the User Settings File

This is the lowest-impact fix and resolves the majority of field cases. It does not require administrator rights and does not modify the TIA Portal installation.

6.1 Step-by-Step Procedure

1. Close all instances of TIA Portal, including the TIA Portal Help system and the Automation License Manager.
2. Open Windows Explorer and navigate to:
   C:\Users\<your_user>\AppData\Roaming\Siemens\Automation\Portal V11\Settings\
   On Windows 7/8 you can paste the path directly into the address bar. The AppData folder is hidden; enable Show hidden files in Explorer if necessary.
3. Copy Settings.xml to a backup location, for example D:\TIA_backup\Settings_<date>.xml. Keep this file – it may contain custom HMI symbol library paths you want to restore.
4. Delete the original Settings.xml from the Settings folder (or move it to a temporary folder outside the Siemens tree).
5. Start TIA Portal V11. On first launch the host recreates Settings.xml with default values.
6. Open a project containing an HMI device and double-click Menu & Toolbar. The editor should now open without the restart prompt.
7. If the editor still crashes, restore the backup Settings.xml and proceed to Solution 2 – Update 5. The user-profile fix is not the cause in this case.

6.2 Verification

After the editor opens, perform a non-trivial test to confirm the fix is durable:

• Add a new menu entry, bind it to a script function, save the project, close the project, and reopen it.
• Export the HMI project to a USB drive and import it on a second workstation running the same TIA Portal build to verify portability of the new Settings.xml.

7. Solution 2 – Apply TIA Portal V11 Update 5

If resetting the user settings does not resolve the crash, the cause is the base SP2 defect, and the only supported fix is the software hotfix V11 SP2 Update 5 (sometimes referred to as Hotfix 5 or HSP 1105). A clean reinstall is not required and is explicitly discouraged by Siemens support for this symptom.

7.1 Where to Obtain Update 5

Update 5 is delivered through the standard Siemens support channels:

• Siemens Industry Online Support – search for article ID W7XP10004886 or the keyword TIA Portal V11 SP2 Update 5.
• The Software Update Service (SUS) channel, for customers with a valid SUS contract covering the engineering license.
• The Siemens Support Request reply, which delivers a private download link to the customer who opened the SR (see Solution 3).

Updates are cumulative: installing Update 5 brings the build to V11.0 + SP2 + Update 5; Update 6 and Update 7 are incremental and may be installed on top of Update 5 without regression.

7.2 Prerequisites

• Local administrator rights.
• At least 6 GB free disk space on the system drive (the update temporarily extracts the patch payload).
• All TIA Portal instances closed, including the License Manager and the Help Viewer.
• The TIA Portal DVD or original media must be present in the installer cache, because the update verifies the base installation paths.

7.3 Step-by-Step Procedure

1. Extract the Update 5 package to a local folder, e.g. D:\TIA_V11_SP2_Update5.
2. Right-click Start.exe in the extracted folder and select Run as administrator. The TIA Portal Update Wizard launches.
3. Accept the license agreement and confirm the target installation directory.
4. Wait for the wizard to complete the file replacement. The process typically takes 8 – 15 minutes on a typical workstation.
5. Reboot when prompted. The reboot is required to release locked DLLs in C:\Program Files\Siemens\Automation\Portal V11\Bin.
6. Start TIA Portal and verify the build string in Help > About now reads V11.0 + SP2 + Update 5 (or later).
7. Open the previously failing project and test the Menu & Toolbar editor.

7.4 Rollback Procedure

If Update 5 introduces an unrelated regression (rare, but documented in mixed C#-VBScript HMI projects), the update can be removed via Control Panel > Programs and Features > View installed updates. The base SP2 build is left untouched. Note that any projects saved with Update 5 cannot be opened on a pre-Update-5 workstation; preserve a pre-update project copy if backward compatibility is required.

8. Solution 3 – Open a Siemens Support Request

If both solutions above fail, the issue is most likely a project-specific defect (e.g., a corrupted HMI tag table or an embedded third-party ActiveX control that conflicts with the editor). The next step is a Siemens Support Request (SR) with the failing project attached.

1. Open the Siemens Industry Online Support portal and log in with the customer account.
2. Navigate to My Support > Support Requests > Create new request.
3. Choose the product STEP 7 / WinCC Professional V11 and the support type Software > TIA Portal.
4. Attach the project archive (use Project > Archive > Archive with simulated data in the TIA Portal), the Settings.xml from the affected user profile, and the contents of the %LOCALAPPDATA%\Siemens\Automation\Portal V11\Logs directory.
5. Describe the symptom, the build number, and confirm that the user-profile fix (Section 6) and the Update 5 fix (Section 7) have both been attempted.
6. Submit the SR. Siemens typically responds with a workaround or a private hotfix within 2 – 5 business days, depending on the contract.

9. Distinguishing Project-Level vs Installation-Level Corruption

The Menu & Toolbar crash can also be triggered by a single corrupted object reference inside the HMI project tree. The following matrix helps separate the three primary causes:

10. Preventive Measures

1. Install all V11 updates before commissioning a new HMI workstation. The Menu & Toolbar defect was the most common V11 SP2 hotfix trigger; Update 5 removes it permanently.
2. Avoid manual edits to Settings.xml. The file is not intended to be edited by hand. Use the TIA Portal Options > Settings dialog to change the corresponding user options.
3. Do not share Settings.xml between Windows users. Each user must generate their own Settings.xml on first launch. If a common configuration is required, distribute a project archive, not a user-profile file.
4. Maintain a per-user backup of Settings.xml after a working configuration is achieved. A simple scheduled task copying the file to a network share is sufficient and is a low-cost safety net against the same defect class in later TIA Portal versions.
5. Apply Windows updates in a controlled window. Unattended Windows reboots during an active TIA Portal editing session can corrupt the file lock on Settings.xml and trigger the same exception class on the next launch.
6. Keep the Automation License Manager updated. Older License Manager builds (V5.x) interfere with the Menu & Toolbar activation on hosts with the standard runtime license model.

11. Related Known Issues in TIA Portal V11 SP2

The Menu & Toolbar crash is one of several editor-level defects fixed in Update 5. Engineers working in the same environment should be aware of the following related symptoms, which Update 5 (and later updates) also address:

All of the above are bundled in the same Update 5 / Update 6 / Update 7 stream, so installing the latest available V11 SP2 update generally closes the entire defect class in a single maintenance window.

12. Verification Checklist

After applying the recovery procedure, run through the following checklist before signing off the workstation:

• TIA Portal opens without warnings on the affected user account.
• A new project is created successfully (PC station + HMI tag).
• Menu & Toolbar editor opens and the user can add, bind, and remove menu entries.
• A previously archived project opens with all menu entries intact.
• Help > About reports the expected build (V11.0 + SP2 + Update 5 or later).
• The Settings.xml exists in the expected user-profile path.
• The TIA Portal log directory contains no new EditorHostException entries from the most recent test session.
• A second Windows user account can open the same project and the Menu & Toolbar editor without the crash (proves the issue is not project-bound).

If all eight items pass, the workstation is considered recovered and the original change ticket can be closed.

13. Frequently Asked Questions