Resolving TIA Portal V13 SP1 Offline Update Detection Issues

Overview

Engineers maintaining legacy Siemens automation cells frequently deploy TIA Portal V13 SP1 (totally integrated automation portal, released in the V13 generation that succeeded V12) on engineering stations that operate inside air-gapped or restricted networks. When the SIMATIC Updater component fails to recognize the locally staged update payload and instead attempts to reach the Siemens update server over HTTPS, the update procedure aborts after the configured timeout. This article documents the root cause, the prerequisite update chain, the offline configuration of the SIMATIC Updater, and the alternative direct-setup procedure used as a fallback.

The fix addresses the behavior where the user has downloaded the full update archive, redirected the updater to a local folder through Options > Download Directory, and yet the tool still issues DNS requests and waits for a network response. Two valid workarounds exist: correcting the updater's local cache discovery path, and bypassing the updater entirely by launching the embedded Setup.exe from the unpacked update folder.

Affected Products and Versions

Per the official Siemens support note Updates for STEP 7 V13 SP1 and WinCC V13 SP1 (ID 109311724), subsequent updates for TIA Portal V13 are only delivered on the basis of V13 SP2, meaning V13 SP1 reaches its terminal service-pack state with Update 1. No further cumulative service pack (SP2 Update 1, SP3) is published for the V13 SP1 branch.

Problem Description

Symptom observed on engineering workstations that do not have outbound HTTPS access to support.industry.siemens.com:

1. User downloads the V13 SP1 Update 1 archive (commonly distributed as SIMATIC_TIA_Portal_V13_SP1_Upd1.zip or per-component .zip packages) from the Siemens Online Support portal using a connected workstation or staging PC.
2. The archive is transferred to the engineering workstation (USB, secure file transfer, internal share) and extracted to a known directory, for example D:\TIA_Updates\V13_SP1_Upd1\.
3. Inside TIA Portal Administrator or the SIMATIC Updater desktop shortcut, the user opens Options > Settings and configures the download directory to the path above.
4. The user selects Check for Updates. The progress dialog hangs on "Searching for updates..." with the caption indicating an internet connection attempt, then fails with a timeout error (typical wait 30-120 s) such as: "Update server not reachable. Check your internet connection."

The updater ignores the local files in the configured path even though they exist on disk and have the correct naming convention. The tool continues to assume that the local path is only a download cache and queries the remote service for the canonical catalog.

Root Cause Analysis

The SIMATIC Updater is a dual-mode application. It supports two flows:

• Online flow: Query Siemens update servers, download delta or full packages, and apply them in sequence.
• Offline / staged flow: Read a pre-populated download directory, parse the embedded UpdateCatalog.xml (or Manifest.xml depending on version), and apply the packages that match the installed TIA Portal inventory.

The path configured under Options > Settings > Download Directory is interpreted as the download cache, not as the offline update source. The updater still attempts to validate the local catalog against the server catalog before installing. When the catalog contains entries that the server is expected to acknowledge, the absence of a network path causes the timeout. In addition, when the archive is extracted, the inner structure expected by the offline installer may not match the directory the updater scans. The updater expects files placed in a sub-folder tree named after the package ID, not flat at the root of the configured path.

A secondary root cause is a missing or incorrect Windows registry entry that disables the online check. Without that switch, the updater always initiates the HTTPS connection on startup.

Prerequisites

Step-by-Step Solution: Configure Offline Mode in the SIMATIC Updater

1. Stop the updater service. Close any open TIA Portal instance, the TIA Administrator, and the SIMATIC Updater. Open Task Manager > Services and confirm Siemens.Automation.Portal.UpdaterService is stopped. If running, right-click and select Stop.
2. Verify the update chain. TIA Portal V13 requires strict ordering: V13 base → V13 SP1 → V13 SP1 Update 1. Attempting to apply Update 1 over V13 base without the SP1 baseline raises a manifest mismatch. Confirm via Help > About in TIA Portal that the version string reads V13 SP1 (not V13 SP1 Upd 1) before proceeding.
3. Stage the update files in the correct directory tree. Each .zip must be extracted under the updater download directory using its native folder name. The typical layout is:

D:\TIA_Updates\V13_SP1_Upd1\
├── STEP7_Professional_V13_SP1_Upd1\
│   ├── Setup.exe
│   ├── Manifest.xml
│   └── ...
├── WinCC_Professional_V13_SP1_Upd1\
│   ├── Setup.exe
│   └── ...
├── PLCSIM_V13_SP1_Upd1\
└── Startdrive_V13_SP1_Upd1\

4. Set the registry switch to force offline behavior. Open regedit as Administrator and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Automation\Portal\V13\Updater. Create or modify the DWORD value OfflineMode and set it to 1. This tells the SIMATIC Updater to treat the configured directory as authoritative and skip the server handshake. (If the key does not exist, create the full path.)
5. Re-launch the SIMATIC Updater. Use the Start menu shortcut Siemens Automation > SIMATIC Updater or invoke "C:\Program Files\Siemens\Automation\Portal V13\Bin\Siemens.Automation.Portal.Updater.exe".
6. Open Options. Click Options > Settings. Confirm the Download directory field shows the staging path from step 3. If not, browse to it.
7. Disable automatic online check. Uncheck Automatically check for updates and uncheck Use HTTPS proxy for updates if your environment does not provide a proxy.
8. Run Check for Updates. The progress dialog should now show local scanning ("Reading local update catalog...") instead of "Connecting to update server...". The detected updates populate the list with a green check.
9. Apply updates in the correct order. Select all detected components and click Install. The installer displays progress for each component; do not interrupt.
10. Reboot if prompted. Some updates (PLCSIM, Startdrive, WinCC Runtime) request a restart to finalize COM registration and service install. Reboot before re-opening TIA Portal.

Alternative Solution: Run the Embedded Setup Directly

If the SIMATIC Updater continues to misbehave despite the registry switch, bypass the updater and launch the installer inside each package directly. This is the method Siemens support recommends for fully air-gapped sites.

1. Extract every .zip to a working folder as shown in the tree above.
2. Open an elevated command prompt: right-click Command Prompt > Run as administrator.
3. Install STEP 7 first (the dependency for WinCC and other add-ins):

cd /d "D:\TIA_Updates\V13_SP1_Upd1\STEP7_Professional_V13_SP1_Upd1"
Setup.exe /silent /norestart

4. Wait for the installer to complete (typically 4-8 minutes per component on a typical workstation). Check the log at %TEMP%\SiemensInstall_*.log for any ERROR entries.
5. Repeat for each component, in the dependency order: STEP 7 → S7-PLCSIM → WinCC Professional → WinCC Comfort/Advanced → Startdrive → Safety Advanced → Energy Suite → ODK.
6. After all setups complete, run a final inventory check by launching TIA Portal and opening Help > About. The version string for each installed product should now show V13 SP1 Update 1.

Update Chain Requirements

The TIA Portal V13 generation enforces a cumulative chain. Skipping a service pack or applying an update out of order corrupts the installation registry under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Automation\Portal and results in license re-activation failures.

Verification

After applying the updates, perform the following checks:

1. Version verification. Open TIA Portal > Help > About. Confirm every installed software product displays V13 SP1 Update 1 (or the equivalent build number, commonly V13.0 SP1 Upd 1).
2. Compilation test. Open a representative S7-1200 / S7-1500 project and click Compile > Software (rebuild all). Successful compilation confirms the compiler hotfixes are active.
3. HMI compile test. Open a WinCC Comfort / Advanced project and recompile. Verify that the HMI tags resolve and the runtime files generate without warnings.
4. PLCSIM test. Launch S7-PLCSIM V13 SP1, download the test program, and confirm the simulated CPU enters RUN.
5. Updater self-test. Re-run the SIMATIC Updater. The catalog should show "No updates available" rather than re-attempting the server query.
6. Registry audit. Verify HKLM\SOFTWARE\Siemens\Automation\Portal\V13\Updater\OfflineMode = 1 persists.

Troubleshooting Matrix

Edge Cases and Field-Proven Caveats

Hosts file workaround: If modifying the registry is not permitted by site policy, redirect support.industry.siemens.com in C:\Windows\System32\drivers\etc\hosts to 127.0.0.1. The updater fails fast (connection refused) and then falls back to local-only scanning. This is a documented field workaround for locked-down workstations.

Antivirus interaction: Several endpoint protection suites (Symantec, McAfee, Windows Defender) quarantine the Setup.exe inside extracted update folders when the parent .zip is downloaded. Always create an antivirus exclusion for the staging directory before extraction. Re-enable real-time scanning after installation.

Concurrent installations: TIA Portal V13 SP1 components share a common COM registry branch. Installing two components in parallel (for example, launching two Setup.exe sessions) corrupts the registration and produces 0x80040154 ("Class not registered") errors when TIA Portal starts. Always run setups sequentially.

Project upgrade path: After Update 1 is applied, projects created in V13 SP1 Update 1 cannot be downgraded back to V13 SP1. Save backups under version control before installing Update 1 if a rollback path is required.

Migration to V13 SP2: When the project demands newer features (for example, S7-1500 CPU firmware V2.x support), the supported path is a clean installation of TIA Portal V13 SP2 on a separate partition. In-place upgrade from V13 SP1 to V13 SP2 is not supported per the Siemens release notes.

FAQ