TIA Portal V17 Update 4: Fixing Browse Button and Save As Crash

Overview

Engineers running TIA Portal V17 Update 4 on Windows 10/11 workstations report that the engineering framework terminates unexpectedly when invoking the Browse file dialog (folder picker) or executing Save As on a project. The crash is silent: no Siemens error dialog appears, no APLog.xml is generated at the expected location, and the Windows event log records only a generic application fault. This document consolidates the field-verified root cause, the underlying registry/option path that triggers the failure, and the complete set of workarounds that restore stable operation without requiring administrative change to the company domain.

Symptoms and Error Conditions

The absence of a Siemens-branded crash dialog distinguishes this failure mode from generic TIA Portal faults and is a reliable diagnostic fingerprint. A standard Application Error event is written to Windows Event Viewer → Windows Logs → Application with Event ID 1000 and the faulting module named S7WsiF.dll or Siemens.Automation.Portal.exe depending on the call stack.

Root Cause Analysis

The fault is reproducible only when the framework attempts to populate the Recently Used Storage Location list during file system enumeration. Specifically, the option is located at:

Menu path: Options → Settings → General → Storage settings → Recently used storage location

When this checkbox is enabled, TIA Portal V17 Update 4 records the absolute path of every project the user opens in the user profile and replays that list whenever a file dialog is constructed. If any entry in the persisted list refers to a path that no longer exists — for example, a network share that has been unmounted, a redirected %USERPROFILE%\Documents folder that has been remapped by Group Policy, or a folder on a removable drive that has been ejected — the dialog code path performs an unguarded SHParseDisplayName followed by an IFileDialog::SetFolder call. The Windows shell COM object returns E_INVALIDARG or E_FAIL on the missing path, and the TIA Portal wrapper does not catch the resulting System.Runtime.InteropServices.COMException, causing the process to terminate.

The crash is therefore a path validation gap in the recently-used persistence layer and is independent of project content. Opening two projects side by side — one whose last-saved location still exists and one whose last-saved location has been deleted — demonstrates the asymmetry: only the project with the stale path crashes. The list is stored per-project in the project metadata, which explains why the failure tracks with individual .ap17 archives and not with the user profile alone.

Affected Versions and Configuration

The condition is independent of TIA Portal project type — it reproduces on S7-1200/1500 CPU projects, S7-300/400 retrofits, HMI Tag-based projects, and SINAMICS Startdrive topologies. The Windows edition (Windows 10 21H2, 22H2, Windows 11 22H2) is also non-determinative; the failure is in the application layer above the shell version.

Step-by-Step Resolution

Workaround A — Disable Recently Used Storage Location (fastest fix)

1. Open TIA Portal V17 Update 4.
2. From the menu bar select Options → Settings.
3. In the left navigation tree, expand General and select Storage settings.
4. Uncheck the box labelled Recently used storage location.
5. Click OK to commit. No restart is required.
6. Test by performing a Save As on a project that previously crashed.

With the option disabled, TIA Portal no longer persists per-project path history, and the Browse dialog uses the Default storage location field as the initial folder. The crash no longer occurs because the stale path list is never queried.

Workaround B — Specify a Valid Default Storage Location

1. Navigate to Options → Settings → General → Storage settings.
2. With Recently used storage location disabled, set the Default storage location to a fully qualified local path such as D:\TIA_Projects.
3. Verify the folder exists, is writable by the current user, and is on an NTFS volume with FILE_TREE_INSERTION_FILE_BUFFER_SIZE-class attributes — in practice any standard local folder is sufficient.
4. Click OK and test the Save As workflow.

Workaround C — Pin Project Path to a Local Folder (domain-laptop scenario)

Engineers who do not control Group Policy and whose My Documents is redirected to a network share should follow this sequence to neutralise path volatility:

1. Create a folder at a fixed local path, for example C:\Automation.
2. Move (do not copy, to avoid dual-path persistence) all active .ap17 archives to C:\Automation.
3. Open TIA Portal and confirm Options → Settings → General → Storage settings → Default storage location points to C:\Automation.
4. Disable Recently used storage location (Workaround A).
5. Open each project directly via File → Open → Project from file system using the new path.
6. Perform a Save (not Save As) on each project once to re-anchor the in-project path metadata.

Domain Profile Hardening

On corporate laptops where My Documents is redirected via Folder Redirection, the underlying fault becomes more frequent as the share availability fluctuates. The defensive pattern is to keep project storage on local NTFS and back it up with a controlled mirror script rather than relying on the redirected profile.

Robocopy Mirror Script (project-to-backup)

@echo off
REM Mirror local Automation folder to redirected Documents for backup compliance
robocopy "C:\Automation" "%USERPROFILE%\Documents\Automation" /MIR /Z /XA:H /R:3 /W:5 /MT:8 /LOG+:C:\Logs\portal_mirror.log
exit /b 0

Launch Wrapper (backup-after-close)

@echo off
REM Launch TIA Portal and run mirror script after the process exits
start "" /WAIT "C:\Program Files\Siemens\Automation\Portal V17\Bin\Siemens.Automation.Portal.exe"
call "C:\Scripts\portal_mirror.bat"

Place the wrapper on the desktop or taskbar. Every close of the engineering environment is followed by a deterministic mirror to the network share, satisfying corporate backup policy without coupling TIA Portal to share availability at runtime.

Settings Export and Import Workflow

Engineers who manage multiple TIA Portal installations — for example, lab benches, commissioning laptops, and engineering office PCs — benefit from a portable settings file. The export/import flow is the cleanest way to guarantee that the disabled Recently used storage location setting travels with the user.

1. On a known-good installation, navigate to Options → Settings.
2. Configure Default storage location to the agreed fixed path (for example D:\TIA_Projects).
3. Disable Recently used storage location.
4. Click Export in the lower-left of the settings dialog and save the file as portal_settings.tia17cfg at a network-accessible location.
5. On each target installation, open TIA Portal, navigate to Options → Settings, and click Import.
6. After import, manually verify the Default storage location field on the target machine — the importer can leave a path that does not exist on the new host.

Registry and Configuration File Reference

For engineers who script deployment, the relevant registry keys are:

The XML persistence file is located at:

%APPDATA%\Siemens\Automation\Portal V17\StorageLocations.xml

To forcibly clear the corrupted cache after upgrading to a fixed U4 build, close TIA Portal, delete the file above, and reopen. The framework regenerates it on the next dialog close.

Diagnostic Checklist

When the crash recurs after applying the workarounds, run the following verification sequence before opening a Siemens support ticket:

1. Confirm TIA Portal build: Help → About — should read V17.4.0.x or later cumulative build.
2. Confirm Windows event log entry: Event ID 1000, faulting module S7WsiF.dll or Siemens.Automation.Portal.exe.
3. Confirm the Recently used storage location checkbox is cleared.
4. Confirm Default storage location resolves to an existing, writable local path.
5. Run Project → Cleanup → Reorganize to clear orphan references inside the .ap17 archive.
6. Test the Save As on a freshly created throwaway project to isolate the failure from existing project metadata.
7. If the throwaway project succeeds, the original project has a stale internal path record — extract it with Project → Archive → Retrieve to a new folder, then continue working from the retrieved copy.

Verification Steps

1. Open TIA Portal V17 Update 4.
2. Open a previously crashing project.
3. Invoke File → Save As; the dialog should open without termination.
4. Click the Browse button next to Path; the folder picker should open and accept selection without termination.
5. Save the project to a new local path; confirm the .ap17 archive exists at the target and the source remains intact (regression guard for partial rename).
6. Close and reopen the project from the new path; verify all device and connection data round-trips correctly.

Field-Proven Caveats

• The crash can resurface if a user re-enables Recently used storage location after the workaround is applied. Communicate the setting change to all engineering team members.
• Antivirus software that virtualises file I/O on %USERPROFILE%\Documents (notably some endpoint protection products) can also produce E_INVALIDARG at dialog open. Exclude %APPDATA%\Siemens and the project root from real-time scanning.
• OneDrive's Files On-Demand feature can place %USERPROFILE%\Documents in a state where folders exist as cloud placeholders only; TIA Portal V17 U4 does not handle the cloud placeholder attribute correctly. Move projects to a non-OneDrive-managed path.
• Some users have reported that the crash correlates with the Automatic save interval. Disabling Options → Settings → General → Automatic save while troubleshooting isolates the failure from the autosave thread.

Related Siemens Documentation

For engineers tracking the underlying product behaviour, the following Siemens knowledge base and manual references are the authoritative starting points:

• Siemens Industry Online Support — TIA Portal V17 entry portal
• TIA Portal V17 Readme — installation notes and known issues
• STEP 7 Professional V17 system manual
• TIA Portal V17 Update 4 release notes
• Siemens Technical Forum (registered customers)

Frequently Asked Questions