Resolving STEP 7 Professional Installation Error on Windows 7 SP1

Problem Overview

Engineers and commissioning specialists frequently encounter a hard-stop failure when launching the setup executable for SIMATIC STEP 7 Professional 2010 SR4 (the last shipping release of the STEP 7 V5.5 line, catalog number 6ES7810-4CC10-0YA7) on a Windows 7 Professional SP1 workstation. The setup wizard fails before the EULA screen, often with a dialog containing the literal phrase "Error 1722", "Internal Error 2337", or a generic "There is a problem with this Windows Installer package" wrapper. The failure reproduces on cold boot and is independent of the local user account, which signals an OS-level environment problem rather than a corrupt installer image.

The same fault pattern is reported on TIA Portal V14, V15.1, V16, and V17 setup launches, and on VirtualBox-hosted Windows guests running the classic STEP 7 Professional 2006 SR4 media. The root cause cluster is identical in all cases: incompatible Windows Installer service state, blocked startup services, missing or corrupted .NET Framework assemblies, and insufficient UAC elevation during the bootstrap phase.

Affected Products and Versions

Root Cause Analysis

The Siemens support article Entry ID 8861819 — Installation problems with STEP 7 / TIA Portal consolidates the four most common failure classes reported by field engineers. The Windows 7 SP1 platform amplifies each one because Microsoft ended mainstream support for Win 7 on January 13, 2015, and stopped shipping installer-related hotfixes for it after October 2020.

Cause 1 — Blocked Windows Installer Service

The MSIServer service (display name: Windows Installer) must be set to Manual start and must not be disabled by Group Policy. On hardened corporate images the policy DisableMSIServer is set to 1, which silently kills the setup half-way through the extraction phase.

Cause 2 — Conflicting Background Services and Startup Items

Antivirus hooks (Kaspersky, McAfee, Trend Micro, Symantec Endpoint Protection), backup agents, and third-party shell extensions attach to the msi.dll call chain. A clean-boot state, with all non-Microsoft services disabled, is the standard isolation method documented in the Microsoft Q&A thread Error installing program: Simatic Step7 Professional.

Cause 3 — Missing or Damaged .NET Framework

STEP 7 V5.5 SP4 requires .NET Framework 3.5 SP1 enabled as a Windows feature and .NET Framework 4.x as a side-by-side runtime. TIA Portal V17 requires .NET 4.6.2 minimum and the .NET Desktop Runtime 6.0.x. Damaged assemblies in the Global Assembly Cache (GAC) produce HRESULT 0x80131040 or 0x80070002 error codes inside the bootstrapper log.

Cause 4 — UAC and Installer Elevation Token

Launching Setup.exe by double-click from an elevated Explorer window still produces a medium-integrity token on UAC-protected Windows 7 SP1. The MSI must run under a high-integrity token, which requires an explicit Run as administrator action and the compatibility flag "Run this program as an administrator" on the executable properties.

Pre-Installation Prerequisites

Verify the following baseline before launching setup. All values are taken from the STEP 7 V5.5 SP4 readme and the TIA Portal V17 installation manual on SIOS.

Solution 1 — Clean Boot Procedure

The clean-boot method is the recommended first response because it isolates whether a third-party driver, service, or shell extension is intercepting the MSI chain. Perform the steps from an account with local administrator rights.

1. Press Win + R, type msconfig, press Enter to open System Configuration.
2. On the General tab, select Selective startup and clear Load startup items.
3. On the Services tab, check Hide all Microsoft services, then click Disable all.
4. Click OK and reboot when prompted. You will boot into a clean state with only Microsoft services active.
5. Right-click the STEP 7 / TIA setup executable and choose Run as administrator.
6. After the install completes, return to msconfig, switch back to Normal startup, and reboot.

Solution 2 — Compatibility Mode and Elevation

Windows 7 SP1 supports the application compatibility shim database, which can force the setup into the documented behavior expected by STEP 7 V5.x. Apply the following properties to Setup.exe in the install media root:

1. Right-click Setup.exe → Properties → Compatibility tab.
2. Check Run this program in compatibility mode for and select Windows XP (Service Pack 3).
3. Check Run this program as an administrator.
4. Check Change settings for all users at the bottom and repeat the two flags.
5. Click Apply and launch the setup again.

For the Setup.msi file inside the same media root, apply the same flags. The MSI sub-package is where the Error 1722 / Error 2337 dialogs are generated, not in the bootstrapper.

Solution 3 — Windows Installer Service Repair

1. Open services.msc and locate Windows Installer.
2. Confirm Startup type is Manual, not Disabled. If it is set to Disabled, change to Manual and start the service.
3. Open regedit and navigate to HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer. Verify the key exists and contains the default value Service.
4. Open an elevated command prompt and execute:
   msiexec /unregister
msiexec /regserver
5. Re-register the MSI handler DLLs:
   regsvr32 /u mshtml.dll
regsvr32 /i mshtml.dll
6. Reboot and retry the install.

Solution 4 — .NET Framework and Runtime Prerequisite Repair

1. Open Control Panel → Programs and Features and verify that Microsoft .NET Framework 3.5 SP1 is installed and active.
2. If absent, open Control Panel → Programs → Turn Windows features on or off and tick .NET Framework 3.5.1. Windows will prompt for the install media or pull the source from Windows Update.
3. Download and run the Microsoft .NET Framework Repair Tool to fix broken bindings in v4.x.
4. Clear the contents of %TEMP%\..\Microsoft .NET Framework 4.0 setup to remove a stuck partial install state.
5. For TIA Portal V17, install the .NET Desktop Runtime 6.0.x (x64) before re-launching the setup.

Solution 5 — Registry and Permission Repairs

Corrupt COM registration and missing shell open verbs also break the installer. Run the following from an elevated command prompt:

cd /d %windir%\system32
regsvr32 msi.dll
regsvr32 msihnd.dll
regsvr32 msisip.dll

Verify the installer package CLSID binding in the registry at HKCR\Msi.Package\shell\open\command contains the default value:

If this key is missing or modified by third-party software, restore it manually and reboot.

Virtual Machine Considerations (Oracle VM VirtualBox)

When installing STEP 7 Professional 2006 SR4 inside an Oracle VM VirtualBox guest (a configuration sometimes used for legacy test rigs), two additional settings are required:

1. Set the guest VM 3D Acceleration to Disabled in Settings → Display → Screen. STEP 7 setup triggers a Direct3D capability check that fails on VirtualBox virtual GPUs.
2. Allocate a fixed-size virtual disk of at least 60 GB. Dynamically expanding disks trigger MSI file-lock errors during the InstallShield extraction phase on sparse VDI volumes.
3. Enable the VirtualBox Guest Additions ISO and confirm the VirtualBox System Services are running before launching setup.

TIA Portal V17 Specific Failure Mode

The TIA Portal V17 installer introduced a .NET Hosting Bundle check that blocks the install with dialog "The prerequisite check failed. Restart your computer and run Setup again" when the prior uninstall left orphaned Siemens.Automation.Portal.* assemblies in the GAC. The recovery sequence is:

1. Run cmd /c "gacutil /u Siemens.Automation.Portal.Common" for each orphaned assembly listed in %LOCALAPPDATA%\Temp\Siemens.Setup.log.
2. Delete the directory %ProgramData%\Siemens\Automation\InstallData if it exists.
3. Reboot and re-run the TIA Portal V17 setup with the SIMATIC license key USB dongle removed from the host.

Diagnostic Logging

Capture the MSI verbose log for any future escalation to Siemens Technical Support:

For TIA Portal:

Attach the resulting log file to the support case opened in Siemens Industry Online Support.

Verification

1. After the setup reports success, confirm the installation via Control Panel → Programs and Features. The entry SIMATIC STEP 7 Professional 2010 SR4 must show Publisher: SIEMENS AG and a version of 05.05.04.00.
2. Launch SIMATIC Manager from the Start menu. The S7 project tree should open without S7WIN DLL load errors.
3. Open Options → PG/PC Interface and confirm the installed S7ONLINE access point is bound to TCP/IP → Network Card.
4. Run the Automation License Manager and verify it can read the USB license dongle (SLC 2.0) or the local activated license.
5. For TIA Portal, launch TIA Portal V17 and confirm the Project view tab loads. A successful open verifies the .NET, SQL Express, and OPC stack all initialized correctly.

Troubleshooting Matrix

FAQ