Resolving Microsoft Visual C++ and SQL Server Installation Errors in SIMATIC PCS 7 v8.2

During SIMATIC PCS 7 v8.2 software installation, setup abort errors concerning Microsoft Visual C++ Redistributable ('vc_redist' / 'vcredist') and Microsoft SQL Server for WinCC ('SQL Server installation failed') are typically caused by corrupted file extraction or broken digital signatures when installing from ISO disk images mounted through third-party virtual drive utilities (such as UltraISO or Daemon Tools). These virtual drive utilities frequently truncate long 8.3 filenames, mishandle multi-gigabyte cabinet (.cab) files, or strip internal digital certificates required by Windows User Account Control. To resolve these errors, engineers must extract the official Siemens ISO installation media using 7-Zip, utilize the native Windows ISO mounting feature, or install directly from physical DVD/USB media.

Root Causes of Setup Aborts with Third-Party Virtual Drives

Installing SIMATIC PCS 7 v8.2 on an Engineering Station or OS Server is an extensive deployment process involving over 20 separate sub-installers, including Microsoft SQL Server 2014, Microsoft Visual C++ Runtime libraries (2005, 2008, 2010, 2012, 2015), SIMATIC NET, and WinCC v7.4.

When engineers mount the official PCS 7 installation ISO image using legacy third-party virtual drive software (such as UltraISO, MagicISO, or Daemon Tools Lite):
- Filename Truncation: These utilities often do not support extended ISO-9660 / Joliet / UDF file paths greater than 260 characters, silently corrupting or truncating sub-installer file names.
- Corrupted Cabinet Archives: Large SQL Server cabinet archives (SqlRun_Tools.cab, SqlRun_Engine.cab) are partially uncompressed or time out during high-speed extraction across virtual SCSI emulators.
- Certificate Validation Failure: Windows Installer validates digital certificate timestamps for packages like vcredist_x86.exe and vcredist_x64.exe. Third-party emulators can alter file hashes, causing Windows to block execution with code 0x80070002 or 0x80070005.

Microsoft Visual C++ and SQL Server Prerequisites in PCS 7 v8.2

Before launching the PCS 7 setup, Windows must be prepared with exact system prerequisites:
- Operating System Baseline: Windows 7 SP1 Enterprise/Ultimate (64-bit) or Windows Server 2012 R2.
- Microsoft .NET Framework: .NET Framework 3.5 SP1 (must be activated as a Windows Feature) and .NET Framework 4.6.2+.
- Windows Message Queuing (MSMQ): Must be active under Windows Features.
- Visual C++ Redistributable Packages: Both 32-bit (x86) and 64-bit (x64) architectures must be installed sequentially.
- SQL Server Clean State: If a previous failed PCS 7 or WinCC installation occurred, orphaned registry entries under HKLM\Software\Microsoft\Microsoft SQL Server will block new instance creation (WINCC).

Step-by-Step Procedure: Clean Media Preparation and Installation

Follow this procedure to eliminate setup errors:

Step 1: Clean Extraction of Installation Media

Download the official PCS 7 v8.2 ISO images from Siemens Industry Online Support (SIOS) or use the physical media.
Do NOT use virtual CD/DVD emulator software.
Install 7-Zip (version 19.00 or newer).
Right-click the PCS 7 ISO file (e.g., PCS7_V82.iso) and select 7-Zip > Extract to "PCS7_V82\".
Ensure the target directory resides on a local SSD root partition (e.g., C:\Install\PCS7_V82\) to prevent path length issues.

Step 2: Pre-Install Visual C++ Runtimes

Navigate to the extracted media folder: C:\Install\PCS7_V82\Support\VCREDIST\.
Right-click and run each executable as Administrator:
- vcredist_2008_x86.exe and vcredist_2008_x64.exe
- vcredist_2010_x86.exe and vcredist_2010_x64.exe
- vcredist_2012_x86.exe and vcredist_2012_x64.exe
- vcredist_2015_x86.exe and vcredist_2015_x64.exe
Restart the operating system.

Step 3: Execute PCS 7 Setup

Open the root installation folder: C:\Install\PCS7_V82\.
Right-click Setup.exe and select Run as Administrator.
In the setup wizard, select Package installation and choose the appropriate station type (Engineering Station or OS Single Station).
Allow the installer to deploy Microsoft SQL Server 2014 instance WINCC. The installer will complete without Visual C++ or SQL errors.

Comparative Installation Media and Tooling Matrix

The table below compares installation media preparation techniques:

Media Deployment MethodFile IntegrityCertificate RetentionLong Path SupportRecommendationUltraISO / Daemon ToolsUnreliable (Corrupts .cab)Can strip signaturesPoor (< 260 chars)STRICTLY DISCOURAGED7-Zip File Extraction100% ReliableFully preservedFull supportRecommended Best PracticeWindows Native ISO Mount100% ReliableFully preservedFull supportRecommended for Win 8/10/ServerPhysical Siemens DVD / USB100% ReliableFactory certifiedNative hardware readOfficial Manufacturing Standard

Verification

To confirm that all components installed successfully:
1. Installed Software Verification: In SIMATIC Manager, select Help > About... > Installed Software; verify that SIMATIC PCS 7 V8.2, WinCC V7.4, and STEP 7 V5.5 SP4 are listed with status 'Installed'.
2. SQL Server Instance Check: Open Windows Services (services.msc); confirm that SQL Server (WINCC) and SQL Server Integration Services are running with Automatic startup.
3. Event Viewer Audit: Inspect Windows Application Event Logs; confirm that event source MsiInstaller logged status 0 (Installation completed successfully) for all deployed packages.

Limitations and Operational Precautions

Engineering teams must observe the following precautions:
- Never install PCS 7 on an operating system where a commercial edition of Microsoft SQL Server is already running; the WinCC instance requires specialized instance collation (Latin1_General_BIN).
- Ensure Windows Update is paused during PCS 7 setup to prevent operating system file lock deadlocks.
- Always validate final license quantities and MLFBs against the applicable Siemens catalog and authorized distributor quotation when procuring PCS 7 software media and license keys.

Engineer FAQ

Can I install PCS 7 v8.2 on Windows 10?

PCS 7 v8.2 was originally released for Windows 7 SP1 (64-bit) and Windows Server 2012 R2. Windows 10 support was introduced with PCS 7 v8.2 SP1 / PCS 7 v9.0. Always verify compatibility in the Siemens Kompatool before installing.

What should I do if the SQL Server WINCC instance fails to uninstall?

If the SQL instance is corrupted, use the Microsoft SQL Server uninstall wizard from Control Panel, or run the PCS 7 DVD cleanup script located under Support\SQL_Cleanup\ before attempting reinstallation.

Why does the installer prompt for a reboot repeatedly before starting?

A pending file rename flag exists in the Windows registry. Open regedit, navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager, and delete the string value PendingFileRenameOperations.