WinCC 7.4 SP1 Installation: Resolving the "Rahmensetup not registered" Error

1. Problem Description

When launching the Setup.exe of SIMATIC WinCC 7.4 SP1 on a Windows-based engineering station, the installer terminates immediately with a localized dialog:

Rahmensetup not registered. Please contact your local setup dealer.

The message text originates from the German-language Rahmensetup ("framework setup") component of the WinCC installation shell, which is delivered as an MSI-based bootstrapper. The English equivalent typically rendered is "Windows Installer framework is not registered". The setup process exits with no further logging, no rollback, and no entry in %TEMP%\Siemens\Setup.log beyond a hard return code.

This error is reported across both Windows Server 2012 R2 and Windows 10 hosts, and is most often observed on:

• Dell OEM workstations delivered with Windows 10 build 10.0.16299.64 (Fall Creators Update, 1709) pre-installed.
• Systems that have been upgraded in-place from a supported build to a later build (1709, 1803, 1809, 1903, 1909, 2004) without re-validating the SCADA compatibility matrix.
• Machines where the Windows Installer service has been disabled by group policy or a security hardening script.

2. Error Message Decoding

The dialog text is generated by the bootstrapper WinCCSetup.msi when a prerequisite component check returns a non-zero result. The most common internal error codes produced by the wrapper are:

Enable verbose MSI logging to confirm which return code your installation is producing:

1. Open an elevated command prompt.
2. Execute: reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Debug /t REG_DWORD /d 7 /f
3. Re-launch Setup.exe.
4. Inspect %TEMP%\MSI*.LOG and look for the lines immediately preceding Return value 3.

Disable verbose logging once the issue is resolved:

reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Debug /f

3. Root Cause Analysis

The "Rahmensetup not registered" condition has three confirmed root causes in the field. Identify which one applies to your host before applying the fix.

3.1 Incompatible Windows 10 Build (most common)

WinCC 7.4 SP1 was certified against Windows 10 build 10.0.14393 (Anniversary Update, 1607) and, on a case-by-case basis, build 10.0.15063 (Creators Update, 1703). The Fall Creators Update (build 10.0.16299, 1709) introduced changes to the Windows Installer service, .NET Framework servicing model, and DCOM activation scope that broke the WinCC setup bootstrapper. The error is not resolved by uninstalling/reinstalling the .NET Framework or by repairing the WinCC media; the OS itself is the source of incompatibility.

3.2 Windows Installer Service Disabled or Corrupted

If the msiserver service is set to Disabled by group policy, or if the msi.dll in %WINDIR%\System32 is not properly registered, the setup bootstrapper cannot enumerate its prerequisites and aborts with the framework error. This condition can occur on hardened engineering hosts, on VMs cloned from a Sysprep image with an unattend.xml that disables MSI, or after a Windows feature update.

3.3 Missing COM Registration of WinCC Bootstrapper Classes

When prerequisite software (Visual C++ 2005/2008/2010/2013 redistributables, .NET 4.6.x, SQL Server 2014 client tools) has been partially removed or upgraded, the WinCC setup wrapper fails its COM activation probes for Siemens.Simatic.Setup.Rahmensetup and returns the localized error.

4. WinCC 7.4 SP1 System Requirements

Before troubleshooting further, confirm the host meets the official compatibility envelope. The supported operating system matrix per the WinCC 7.4 SP1 release notes is:

Verify your exact build with:

cmd /c winver  or  powershell -Command "(Get-CimInstance Win32_OperatingSystem).BuildNumber"

Other minimum requirements for the WinCC 7.4 SP1 setup itself:

• Microsoft .NET Framework 4.6.x (4.6.2 minimum, 4.7+ not tested by Siemens at the time of release)
• Microsoft Visual C++ 2005, 2008, 2010, 2012, 2013, 2015-2019 redistributables
• SQL Server 2014 SP2 (or SQL Server 2016 SP1 as documented in WinCC 7.4 SP1 update packages)
• Windows Installer 4.5 or higher (5.0 ships with all supported OSes)
• Administrator-level local account (built-in Administrator, not a UAC-elevated regular user)
• 8 GB free disk space minimum for a single-station installation

For the canonical Siemens compatibility list, consult the WinCC V7.4 SP1 release notes and system requirements entry on the Siemens Industry Online Support portal.

5. Pre-Installation Checklist

Run through this list before launching the WinCC setup. Items 1-3 are the most common cause of the Rahmensetup error.

1. Confirm Windows build. Open winver and verify the build number. If it is 10.0.16299.x or later, you must roll back or re-image before proceeding.
2. Confirm Windows Installer service state. sc query msiserver must return STATE: 4 RUNNING. Startup type should be Manual (the service self-starts on demand).
3. Verify admin context. Run whoami /groups | findstr /i "S-1-16-12288". A match confirms the elevated token is active.
4. Disable antivirus and tamper protection. Products such as Trend Micro, CrowdStrike, and Windows Defender with Controlled Folder Access active can intercept msi.dll registration calls.
5. Mount the installation media as a local path. Network shares without SMB signing negotiation or UNC paths longer than 248 characters will produce the same framework error.
6. Free disk space. A minimum of 8 GB on C:\ is required even if WinCC is being installed to a different volume.
7. Apply the latest cumulative update for the currently installed Windows build before retrying.

6. Resolution Procedure

Apply the steps in the following order. Stop at the first resolution that allows Setup.exe to advance past the framework check.

6.1 Path A: Correct an Incompatible Windows 10 Build

This is the only path that resolves the error on hosts running build 10.0.16299.x or newer.

1. Open Settings → Update & Security → Recovery.
2. If a "Go back to the previous version of Windows 10" option is present and within 10 days of the feature update, click it. This restores the prior build (typically 1703) with user data preserved.
3. If the rollback option is not available, perform a clean re-installation of Windows 10 1607 (build 10.0.14393) using the Windows 10 1607 Enterprise LTSC ISO. LTSC is preferred because it does not receive the 1709/1803/1809 feature updates that re-introduce the incompatibility.
4. Install the most recent cumulative update for 1607 before applying any other software.
5. Re-launch Setup.exe as Administrator from a local path.

6.2 Path B: Re-register the Windows Installer Service

For Windows Server 2012 R2 hosts or Windows 10 hosts on a supported build where the MSI service has been disabled or corrupted.

1. Open an elevated command prompt.
2. Stop the service and unregister the COM server:
   net stop msiserver
msiexec /unreg
3. Wait 30 seconds. The service msiserver will be in STOP_PENDING.
4. Re-register the COM server:
   msiexec /regserver
5. Set the startup type back to Manual (the default):
   sc config msiserver start= demand
6. Reboot the host.
7. Verify: sc qc msiserver should show START_TYPE: 3 DEMAND_START.
8. Test: msiexec /? should return the Windows Installer help banner.

If msiexec /regserver itself fails with 0x80070005, the issue is a security policy. Inspect:

gpresult /h %USERPROFILE%\Desktop\gpo.html and look under Computer Configuration → Administrative Templates → Windows Components → Windows Installer. The setting Turn off Windows Installer must be set to Not Configured or Enabled/Always; it must not be set to Disabled.

6.3 Path C: Repair the WinCC Bootstrapper Prerequisites

Use this path if Path A and Path B are both N/A and the error is traced to a missing .NET or VC++ runtime.

1. Reinstall the .NET Framework 4.6.2 offline installer:
   dotnetfx46_full_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT
2. Reinstall the Visual C++ 2013 redistributable (x64):
   vc_redist.x64.exe /quiet /norestart
3. Reinstall the Visual C++ 2015-2019 redistributable (x64):
   vc_redist.x64.exe /repair /quiet /norestart
4. Reboot.
5. Re-run Setup.exe from an elevated command prompt using the verbose flag:
   Start /wait Setup.exe /L*vx "%TEMP%\WinCCSetup.log"

6.4 Path D: Clean the Windows Installer Cache

If %WINDIR%\Installer contains orphaned or corrupted .msi/.msp files, the WinCC setup may be unable to enumerate its own cached payloads.

1. Stop the msiserver service: net stop msiserver
2. Identify orphaned installers with Microsoft's msizap utility (deprecated but still functional) or the safer Microsoft MSI Cleanup Utility guidance.
3. Do not manually delete files in %WINDIR%\Installer unless you have a verified inventory. Corrupt cache is a last-resort cleanup.
4. Rebuild the MSI repository:
   rundll32.exe mshtml.dll,PrintHTML "%WINDIR%\Web\Wallpaper\Windows\img0.jpg" (forces a WMI registration rebuild, harmless)
5. Reboot and retry the install.

7. Verification

After the setup completes (or, if it failed, after applying a fix), perform the following checks to confirm the error is fully resolved.

1. Setup log review. Inspect %TEMP%\Siemens\Setup.log. The last line should be Return value 0. Any value other than 0 indicates the install has not actually succeeded even if the dialog closed cleanly.
2. Service verification. Open

   services.msc. The following services must be present and set to Automatic:
   
   CCAgent
   

   (WinCC Agent)
3. CCMsgRtr (WinCC Message Router)
4. CCProjectMgr (WinCC Project Manager)
5. SQLSERVERAGENT (if SQL Server 2014 was installed locally)
6. License verification. Launch the WinCC Explorer. The status bar should read Runtime not started - License OK. If it reads License missing, the install succeeded but the license transfer was interrupted.
7. Database attach. In WinCC Explorer, open an existing project or create a new one. The \\\ tree should populate without any CCLStrap errors in the Windows Application event log.
8. Event log audit. eventvwr.msc → Windows Logs → Application. Filter for Source: MsiInstaller. There should be no Event ID 11708 (Install failed) entries referencing the WinCC packages.

8. Troubleshooting Matrix

9. Common Pitfalls and Field Caveats

• Auto-upgrade after install. On Windows 10 SAC, the next feature update can re-create this error on a previously working install. Configure Windows Update for Business deferrals or migrate the host to LTSC before the next SAC wave.
• Dell OEM preloads. Factory Windows images on Dell Precision 3000/5000/7000 series delivered between November 2017 and mid-2018 ship build 10.0.16299. These must be wiped and re-imaged; the OEM image also includes Dell Command Update and SupportAssist agents that interfere with the SCADA baseline if left in place.
• Sysprep generalization. WinCC 7.4 SP1 is not Sysprep-compatible. The setup must run on the final, ungeneralized host. Attempting to capture a Sysprep image after WinCC is installed will produce the framework error on first boot of the deployed image.
• Path Length. The WinCC setup chain references registry keys under HKLM\SOFTWARE\Siemens\Automation\WinCC\Setup that exceed 250 characters. Ensure LongPathsEnabled in HKLM\SYSTEM\CurrentControlSet\Control\FileSystem is set to 1.
• Language pack conflicts. A German-language Windows host running an English-language WinCC media (or vice versa) can produce the localized "Rahmensetup" error even when the underlying prerequisites are satisfied. Match the OS UI language to the WinCC media language, or apply the matching Language Pack (MUI) before installing.
• SQL Server 2016. WinCC 7.4 SP1 Update 5 and later formally support SQL Server 2016 SP1. Earlier WinCC 7.4 SP1 Update levels only support SQL Server 2014. Confirm your Update level matches the database engine installed; mixing them will fail the bootstrapper prerequisite check.

10. Long-Term Recommendation

If you are still deploying WinCC 7.4 SP1 on new engineering hosts in 2024 or later, Siemens support for the V7.4 line is in the Extended Phase. Plan a migration path to WinCC V7.5 SP2 or WinCC Unified V18 depending on your HMI hardware, and standardize your engineering host image on Windows 10 Enterprise LTSC 2019 (build 10.0.17763) or Windows 10 Enterprise LTSC 2021 (build 10.0.19044). Both LTSC releases avoid the SAC auto-upgrade trap that re-introduces the Rahmensetup error on hosts that are running perfectly today.

For migration planning, refer to the WinCC V7.4 / V7.5 compatibility matrix and the SIMATIC WinCC installation guide on the Siemens Industry Online Support portal.