Fixing S7 Distributed Safety V5.4 SP5 Installation on Windows 10

Problem Overview

The S7 Distributed Safety V5.4 SP5 Update 2 installer aborts silently on Windows 10 Enterprise (64-bit) systems that already host a STEP 7 Professional V17 / 2021 Combo and WinCC Comfort V17 stack. The Setup wizard halts without surfacing a Windows error code, an MSI return value, or a Setup log line item in %TEMP%. The InstallShield engine simply stops after the welcome screen and never advances to the feature selection dialog.

This failure mode is specific to mixed-version environments where the classic V5.x line coexists with the TIA Portal V17 line. Both packages rely on the same legacy InstallShield driver cache at C:\Program Files (x86)\Common Files\InstallShield\Driver\<version>\. When the V17 setup rotates the driver cache entries but leaves stale references, the V5.4 SP5 Setup cannot resolve its own package dependency tree and exits silently.

Affected Software Stack

Prerequisites Before Re-Running Setup

Before retrying the V5.4 SP5 Update 2 install, confirm each prerequisite. Skipping any one will reproduce the silent abort.

1. Install SIMATIC Manager V5.7 (or V5.6). Open Control Panel → Programs and Features and verify entries for SIMATIC Manager V5.7 (or STEP 7 V5.6). If absent, mount the appropriate DVD image and install before attempting the safety package.
2. Stop all Siemens background services. Open services.msc and stop S7DOS Help Server, SNMP Siemens Automation, SIMATIC Event Service, and any TraceService process tied to the TIA Portal. Leaving these services running locks files in %ProgramFiles(x86)%\Siemens\Automation.
3. Disable antivirus real-time scanning on %ProgramFiles(x86)%\Siemens and the InstallShield cache directory for the duration of the install.
4. Verify disk space. Distributed Safety V5.4 SP5 Update 2 consumes approximately 380 MB on the system drive and 220 MB on the installation drive. Confirm a minimum of 2 GB free on the boot partition to leave room for the InstallShield scratch volume.
5. Confirm local administrator rights. The installer creates DCOM entries under HKLM\SOFTWARE\Classes\AppID and registers the S7DSHF service. A standard user account cannot complete these operations even when elevation succeeds on the UI side.

Root Cause: InstallShield Driver Cache Mismatch

InstallShield 2011/2012/2018 share a numbered driver folder scheme under C:\Program Files (x86)\Common Files\InstallShield\Driver\<n>\. Each new install shifts the working set; a torn upgrade leaves an empty or partially populated 11 folder that V5.4 SP5 Update 2 attempts to use.

The InstallShield bootstrapper of S7 Distributed Safety V5.4 SP5 Update 2 calls into Driver\11\Intel 32 for its prerequisite scanner. If the binary setup.exe resolves but iGdi32.dll or iUser32.dll is missing or zero-byte, the bootstrap calls EndDialog(IDABORT) without writing a log line, producing the observed silent failure.

Two diagnostic checks confirm the corruption:

1. Open C:\Program Files (x86)\Common Files\InstallShield\Driver\11\Intel 32\. If the directory is empty, missing, or contains only setup.dll, the cache is torn.
2. Launch the V5.4 SP5 Update 2 setup with logging enabled: Setup.exe /debuglog"%USERPROFILE%\Desktop\S7DS_setup.log". The resulting log will terminate with "ISDEV: error 0" immediately after the prerequisite resolution phase if the driver cache is the failure point.

Pre-Installation Cleanup Procedure

Perform this sequence in order. Do not reboot between steps unless instructed.

Step 1 — Remove the broken driver cache

1. Close all Siemens applications and the TIA Portal.
2. Open Command Prompt (Admin) and stop the Windows Installer service to prevent concurrent MSI operations:
   net stop msiserver /y
3. Rename, do not delete, the corrupt cache so it can be restored if recovery fails:
   ren "C:\Program Files (x86)\Common Files\InstallShield\Driver\11" "11_corrupt_%date:~10,4%%date:~4,2%%date:~7,2%"
4. Create a fresh empty directory:
   mkdir "C:\Program Files (x86)\Common Files\InstallShield\Driver\11\Intel 32"

Step 2 — Clear residual MSI registration entries

1. Open regedit as administrator and navigate to:
   HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products
2. Search for any product GUID that contains "S7 Distributed Safety" in its DisplayName value. Right-click and Export the key first as a safety backup, then delete only the matching product GUIDs (do not delete sibling keys).
3. Repeat under HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products for 32-bit registry redirection.

Step 3 — Reset DCOM and security descriptors

1. Open dcomcnfg.
2. Navigate to Component Services → Computers → My Computer → DCOM Config.
3. Sort by Application Name and remove any entry starting with SIMATIC or S7F that points to a missing file under %ProgramFiles(x86)%\Siemens\Automation\S7DS\. Right-click → Properties → confirm the Location path exists. If it does not, the DCOM stub must be removed; otherwise the V5.4 SP5 installer's DCOM registration step will fail with 0x80070005 (access denied) and roll back silently.

Step 4 — Validate the source media

1. Recopy the V5.4 SP5 Update 2 archive to a local drive. Avoid running from a network share or USB drive with power-saving suspension; both produce truncated read errors that mimic the InstallShield bug.
2. Compare the SHA-256 of the Setup.exe with the value published on the Siemens Industry Online Support portal under the article referenced above. A mismatch indicates a damaged download.

Required Installation Sequence

The packages must be installed in this strict order. Deviating produces cascading dependency faults that surface as silent aborts at later stages.

Running the Installer as Administrator

Even with the cache repaired, UAC virtualization on Windows 10 Enterprise can mask the failure. Always launch the Setup with full administrator privileges:

1. Right-click Setup.exe in the V5.4 SP5 Update 2 directory.
2. Select Run as administrator.
3. When prompted, enter local administrator credentials — do not accept the elevation prompt under a non-admin domain account.
4. On the User Settings dialog, select Install for all users of this computer. The Current user only option creates per-user HKCU entries that conflict with the V17 add-in loader.

If Group Policy blocks the elevation prompt, run from an elevated command prompt:

cd /d "D:\Siemens\S7_Distributed_Safety_V5_4_SP5_Upd2"

Setup.exe /debuglog"%USERPROFILE%\Desktop\S7DS_setup.log"

Step-by-Step Clean Installation

1. Disable UAC temporarily for the install only: reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v ConsentPromptBehaviorAdmin /t REG_DWORD /d 0 /f. Re-enable with /d 5 after verification.
2. Stop the Windows Installer service: net stop msiserver.
3. Insert or mount the SIMATIC Manager DVD or ISO for V5.7. Run Setup.exe as administrator. Accept the license agreement and choose Install.
4. Reboot when prompted. The V5.7 setup requires a restart to finalize DCOM and WMI registrations.
5. Mount and install the S7 F Configuration Pack V5.6 / V5.7 next.
6. Mount and install S7 Distributed Safety V5.4 SP5 (full package, not the Update 2 delta). This step registers the F-shared library at %ProgramFiles(x86)%\Siemens\Automation\S7DS\Lib\.
7. Mount and install S7 Distributed Safety V5.4 SP5 Update 2 over the SP5 base.
8. Reboot.
9. Re-enable UAC: reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v ConsentPromptBehaviorAdmin /t REG_DWORD /d 5 /f.
10. Re-enable antivirus on the Siemens directory tree.

Verifying the Installation

After the final reboot, confirm the package is fully registered before opening any F-project:

1. Open Control Panel → Programs and Features. The following entries must be present:
   • SIMATIC S7 Distributed Safety V5.4 + SP5
   • SIMATIC S7 Distributed Safety V5.4 SP5 Update 2
   • SIMATIC S7 F Configuration Pack V5.7 (or V5.6)
2. Launch SIMATIC Manager from the desktop shortcut. Open Options → Install F-Blocks. The dialog must list the F-shared blocks F_SHUTDN, F_STARTUP, F_PSF, and the F-runtime library.
3. Launch STEP 7 V17 from the TIA Portal. Open Options → Safety. The wizard must recognize the V5.4 SP5 catalog and offer migration to STEP 7 Safety Advanced V17.
4. Open regedit and confirm the registry key HKLM\SOFTWARE\Siemens\Automation\S7DS\5.4\ServicePacks contains the string "5.4.5.2".
5. Check %ProgramFiles(x86)%\Siemens\Automation\S7DS\Bin\S7DSCfg.dll for a file version of 5.4.5.2 (right-click → Properties → Details).

If any check fails, re-run the patch with /REINSTALLMODE=omus:

Project Migration to STEP 7 Safety Advanced

If the legacy project can be opened under the now-functional V5.4 SP5 environment but the engineering roadmap calls for TIA Portal, the F-blocks must be cleaned before migration. The official TIA Portal documentation at Migrating projects from S7 Distributed Safety V5.4 SP5 to STEP 7 Safety Advanced lists the prerequisite:

Delete all F-blocks not required by the safety program in your S7 Distributed Safety V5.4 SP5 project prior to migration. Procedure as in STEP 7 Professional.

The procedure is:

1. Open the F-project in the SIMATIC Manager with V5.4 SP5 Update 2.
2. Right-click the F-Program container in the project tree and select F-Block Container → Check Block Consistency.
3. Identify any F-block whose safety signature is not referenced in the safety program. Cross-reference with the Safety Program Structure document.
4. Delete unreferenced F-blocks, recompile the safety program, and re-run the consistency check.
5. Export the project to .s7p format with Archive → User-defined Archive.
6. In TIA Portal V17, open the project with Migrate Project. The TIA Portal Safety Advanced wizard consumes the cleaned archive and produces a STEP 7 Safety Advanced project.

Choosing Between S7 Distributed Safety and STEP 7 Safety Advanced V17

The Siemens portfolio offers two parallel safety engineering toolchains. The correct one depends on the target runtime and project history:

If the project carries F-blocks compiled with libraries before V13, the only viable editor is S7 Distributed Safety V5.4 SP5. If the F-CPU is an S7-1500F, the only supported editor is STEP 7 Safety Advanced V17.

Troubleshooting Matrix

Edge Cases and Field Notes

• Windows 10 22H2 and later: Microsoft tightened DCOM launch security in 22H2. If the V5.4 SP5 installer fails after October 2022 with a DCOM error, raise the Machine Launch Restrictions in dcomcnfg under Component Services → Computers → My Computer → Properties → Default Properties → Enable Distributed COM on this computer.
• Volume Licensing (KVL): Siemens Open License installations use a different MSI bootstrapper. The Setup.exe for KVL packages skips the InstallShield prerequisite scan, but it requires the SSF service to be running. Start it with net start "Siemens Automation License Manager".
• Container-based deployment: If the target machine is provisioned from a gold image that already contains a broken InstallShield cache, the silent abort reproduces on every container. Bake the cleanup Step 1 into the image preparation script.
• Multi-language packs: Installing every available language pack inflates the package to over 1.2 GB and triggers an MSI rollback if the disk free threshold falls below 5%. Limit language packs to the ones actually deployed.
• Coexistence with TIA Portal V18 / V19: TIA Portal V18 and V19 also share the InstallShield cache. Do not install V5.4 SP5 Update 2 after V18 or V19 without first refreshing the InstallShield cache.

Operational Checklist

FAQ