Troubleshooting SQL Server 2017 Installation Failures During SIMATIC PCS 7 V9.1 Setup

During the installation of SIMATIC PCS 7 V9.1 on Windows 10, the fatal setup error 'The following program could not be installed: SQL server 2017 - (Wincc) Setup cannot complete the installation' is primarily caused by operating system edition incompatibilities, missing Microsoft .NET Framework 3.5 prerequisites, or persistent Windows reboot flags in the Registry. PCS 7 V9.1 strictly requires Windows 10 Enterprise LTSC 2019 (64-bit) or Windows Server 2019; Windows 10 Pro is unsupported. To resolve the failure: 1. Ensure the OS is Windows 10 Enterprise LTSC 2019; 2. Enable .NET Framework 3.5 via Windows Features; 3. Delete the 'PendingFileRenameOperations' registry key; and 4. Verify the computer name contains no underscores or special characters.

Executive Summary

Deploying SIMATIC PCS 7 V9.1 requires an extensive software installation stack comprising STEP 7 V5.6, CFC, SFC, WinCC V7.5 SP2, and Microsoft SQL Server 2017 Standard Edition (64-bit). During setup initialization on newly formatted workstations, engineers frequently encounter an abrupt abort accompanied by repeated reboot prompts and the failure message: The following program could not be installed: SQL server 2017 - (Wincc) Setup cannot complete the installation. This error occurs frequently when testing on commercial Windows 10 Professional editions (e.g. Build 19042) or when critical Windows operating system prerequisites are missing. This article analyzes the operating system compatibility matrix for PCS 7 V9.1, outlines the root causes of SQL Server 2017 bootstrap crashes, and provides a verified installation recovery guide.

Architecture and Fundamental Mechanics

SQL Server 2017 Bootstrap Engine, PCS 7 V9.1 OS Compatibility Matrix, and Registry Prerequisite Mechanics:

Operating System Edition Restrictions (The Windows 10 Pro Incompatibility):
Siemens PCS 7 V9.1 is an enterprise DCS platform validated exclusively against specific Long-Term Servicing Channel (LTSC) releases:
- Supported Client OS: Windows 10 Enterprise LTSC 2019 (64-bit, Version 1809, Build 17763.x).
- Supported Server OS: Windows Server 2019 Standard / Datacenter (Version 1809).
Windows 10 Pro (e.g. Version 20H2 / Build 19042, 21H1) is STRICTLY UNSUPPORTED.
Windows 10 Pro semi-annual releases possess updated security baselines, modified DCOM permissions, and distinct Windows Installer service configurations that cause the Microsoft SQL Server 2017 setup bootstrap engine (setup.exe inside SQL Server) to abort with exit code 0x84B10001 or access violation.
Prerequisite 1: Microsoft .NET Framework 3.5 (Including .NET 2.0 and 3.0):
SQL Server 2017 setup requires legacy .NET Framework 3.5 binaries to execute setup bootstrap actions.
Modern Windows installations ship with .NET 4.8 enabled, but .NET 3.5 is disabled by default.
If .NET 3.5 is not pre-installed, SQL Server setup attempts to download it via Windows Update. On isolated industrial networks without internet access, the download times out, causing the entire SQL Server installation to fail.
Prerequisite 2: Persistent Windows Reboot Flags (PendingFileRenameOperations):
Windows Installer and third-party drivers frequently leave pending reboot flags in the Registry under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations.
The Siemens setup checks this key; if present, it prompts for a reboot. If third-party software continuously regenerates this key, the SQL setup engine aborts.
Prerequisite 3: Computer Name Syntax Rules:
Microsoft SQL Server and WinCC strictly mandate that the Windows computer name:
- Must NOT exceed 15 characters.
- Must contain ONLY alphanumeric characters (A-Z, a-z, 0-9) and hyphens (-).
- Must NEVER contain underscores (_), periods (.), or special characters.

Step-by-Step Implementation Procedure

Verify and Align Windows Operating System Edition:
* Press Win + R, type winver, and press Enter.
* Verify that the edition is Windows 10 Enterprise LTSC 2019 (Build 17763.x) or Windows Server 2019.
* If running Windows 10 Pro or a non-LTSC build, the workstation must be reimaged with the certified Siemens LTSC operating system.
Pre-Install Microsoft .NET Framework 3.5:
* Insert the Windows 10 Enterprise LTSC installation media (or mount the ISO, e.g. drive D:).
* Open Windows Command Prompt as Administrator.
* Execute the offline DISM deployment command:
cmd dism /online /enable-feature /featurename:NetFX3 /all /Source:D:\sources\sxs /LimitAccess
* Confirm that DISM reports 'The operation completed successfully'.
Clear Persistent Pending Reboot Flags in Registry:
* Open the Registry Editor (regedit.exe) as Administrator.
* Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
* In the right pane, locate the value PendingFileRenameOperations.
* Right-click and delete the value (or clear its contents).
* Do NOT reboot after clearing the key; immediately launch the installer.
Validate Computer Name and Security Settings:
* Check the computer name: ensure it is 15 characters or fewer without underscores (e.g. use ES-STATION01, not ES_STATION_01).
* Temporarily disable third-party antivirus software during installation.
Launch PCS 7 V9.1 Setup as Administrator:
* Open the PCS 7 V9.1 installation media.
* Right-click Setup.exe and select Run as administrator.
* Select the package (Engineering Station or OS Single Station).
* Observe SQL Server 2017 installing smoothly without bootstrap errors.

Verification

Confirm that the PCS 7 V9.1 setup completes with 'Installation completed successfully' without component error prompts.
Open Windows Services (services.msc); verify that SQL Server (WINCC) is present and Running.
Open the SQL Server installation summary log at C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\Summary.txt; confirm that all features report status 'Passed'.
Launch SIMATIC Manager; create a test project and compile an OS to confirm full SQL database connectivity.

Limitations and Operational Precautions

Attempting to bypass the Windows 10 Enterprise LTSC requirement using registry spoofing on Windows 10 Pro is unsupported and leads to latent database crashes, communication buffer overruns, and rejection of official Siemens Technical Support. Always utilize the exact OS build specified in the Siemens Compatibility Tool.

Engineer FAQ

Why does SQL Server 2017 fail to install during PCS 7 V9.1 setup?

Commonly caused by running an unsupported Windows edition (e.g. Windows 10 Pro instead of Enterprise LTSC 2019), missing .NET 3.5, or pending reboot registry flags.

Is Windows 10 Pro supported for SIMATIC PCS 7 V9.1?

No. PCS 7 V9.1 officially supports only Windows 10 Enterprise LTSC 2019 (64-bit) and Windows Server 2019.

How do I install .NET Framework 3.5 without internet access?

Use the DISM command pointing to the \sources\sxs folder on the Windows installation DVD: dism /online /enable-feature /featurename:NetFX3 /all /Source:<Drive>:\sources\sxs /LimitAccess.