Installing STEP 7 V5.5 SP1 on Windows 7 64-bit Compatibility

Problem Overview

Engineers migrating to a 64-bit Windows 7 workstation frequently encounter a hard failure when launching SIMATIC STEP 7 V5.5 (base release, build 5.5.0.0). The setup either refuses to install, or installs but the SIMATIC Manager (S7PCT.exe / S7Manager.exe shell) crashes on launch with a missing-dependency error, typically referencing msvcr71.dll, CCMBase.dll, or a generic 0xC000007B STATUS_INVALID_IMAGE_FORMAT. The base build of STEP 7 V5.5 was compiled and signed against the 32-bit Windows XP/2003 stack; it does not contain the manifest shims, WOW64 redirection paths, and signed driver packages required for Windows 7 x64.

The official remediation path documented by Siemens is to bring the installation to STEP 7 V5.5 + SP1 (entry ID 52336355) or to migrate the license media to STEP 7 Professional 2010 SR2, which integrates the SP2 service pack and is the only media variant certified for Windows 7 64-bit from a single DVD image.

Root Cause Analysis

Three distinct root causes produce the symptoms reported above. Identifying the exact cause determines whether SP1, SP2, or a full media swap is required.

Cause 1 — Binary Not Signed for WOW64 Strict Mode

STEP 7 V5.5 SP0 binaries lack the IMAGE_DLLCHARACTERISTICS_FORCE_INTEGRITY flag updates and the redirected registry paths needed to enumerate under HKLM\SOFTWARE\Wow6432Node\Siemens\Automation. The installer writes values to the native 64-bit hive (HKLM\SOFTWARE\Siemens) where the 32-bit runtime cannot resolve them, and SIMATIC Manager fails to enumerate installed components on first launch.

Cause 2 — Missing 64-bit USB EPROM / MPI Prommer Driver

The original S7USBEPD.sys driver shipped with V5.5 SP0 is unsigned and rejected by Windows 7 x64 driver signature enforcement. SP1 introduces a re-signed version and an updated S7EpaSrv.exe that registers correctly under the new SCM (Service Control Manager) policy.

Cause 3 — Microsoft Visual C++ 2005 / 2008 Runtime Conflict

STEP 7 V5.5 SP0 links against MSVCR80/MSVCR90 in a non-side-by-side manner. Windows 7 x64 ships MSVCR90 v9.0.30729.6161 as a system component, but STEP 7's private SxS assembly is the older 9.0.21022.8. The activation context fails, producing the 0xC000007B error. SP1 ships the redistributable update that resolves this without requiring manual vcredist_x86.exe intervention in most cases.

STEP 7 V5.5 — Windows Compatibility Matrix

The following table consolidates the official Siemens compatibility statements. Use it to determine the correct installation media for the target OS before downloading or requesting a replacement DVD.

* Windows 10 64-bit support is documented for STEP 7 V5.6 and later; V5.5 family is not certified for Windows 10 and requires a virtualized Windows 7 x64 host or migration to TIA Portal V13+.

Prerequisites

1. Valid STEP 7 V5.5 license — confirmed License Key on the parallel (LPT) dongle, USB hardlock, or the floating License Server. The SP1 download itself is free per Siemens entry ID 52336355, but the underlying product license is mandatory and non-transferable between machines without reauthorization through the Siemens Automation License Manager.
2. Administrator account on the Windows 7 64-bit target with UAC disabled or set to the lowest level for the duration of the install. Re-enable UAC after the final reboot.
3. 20 GB free disk space minimum on the system drive; 40 GB recommended for full installation including optional components (S7-PLCSIM, S7-GRAPH, S7-SCL, S7-HiGraph, S7-PCT, NetPro).
4. Internet Explorer 8 or 9 — STEP 7 V5.5 uses IE-based HTML help and the Online Help shell. Windows 7 ships IE8; IE9 is also accepted. IE10/11 will load but the help viewer may render blank pages.
5. .NET Framework 3.5 SP1 — enable via Programs and Features → Turn Windows features on or off. Windows 7 does not include .NET 3.5 by default; the install will fail at the Setup.exe prerequisite check if it is missing.
6. SIMATIC Logon V1.4+SP1 or later — install before STEP 7 if your plant enforces role-based access on the S7-300/400 project.

Solution A — Apply STEP 7 V5.5 SP1 (Recommended Path)

This is the minimum-change remediation for engineers who already own a STEP 7 V5.5 SP0 media and a valid license, and who wish to retain their existing project archives and component configuration on the new Windows 7 x64 workstation.

Step 1 — Acquire the SP1 Installer

Download the SP1 package from Siemens Industry Online Support at entry ID 52336355. The download is free of charge; Siemens login is required. The package is delivered as STEP7_V55_SP1.exe, a self-extracting installer of approximately 1.2 GB extracted.

Step 2 — Verify the Base Installation

Confirm that STEP 7 V5.5 SP0 is installed. Open Control Panel → Programs and Features and verify that SIMATIC STEP 7 V5.5 shows version 5.5.0.0. If it is not installed, install it first from your original DVD. Do not skip this step — SP1 is a service pack and assumes the base product is present.

Step 3 — Disable UAC and Reboot

Open msconfig → Tools → Disable UAC, or run cmd /c %windir%\System32\cmd.exe /k %windir%\System32\reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f as Administrator. Reboot. UAC must remain off until the post-install verification is complete.

Step 4 — Run the SP1 Installer

1. Right-click STEP7_V55_SP1.exe and select Run as Administrator.
2. Select the installation language. The installer supports German, English, French, Italian, Spanish, and Chinese (Simplified) at the UI level; project content languages are independent.
3. Accept the license agreement. Siemens licensing is per-seat, not per-installation; a single license permits the software on one development workstation at a time.
4. Choose Complete for a full module install, or Custom to deselect optional packages such as S7-PLCSIM if disk space is constrained.
5. The installer replaces the SP0 binaries with SP1, registers the 64-bit-safe MPI/Profibus drivers, and writes the corrected registry hive under HKLM\SOFTWARE\Wow6432Node\Siemens.
6. Reboot when prompted.

Step 5 — Re-apply License

Open Siemens Automation License Manager → License Key → Transfer. Re-authorize against the local USB hardlock or the network License Server. SP1 does not alter the license fingerprint, so existing keys are accepted without reactivation by Siemens.

Solution B — Install STEP 7 Professional 2010 SR2 (Clean Path)

If the SP1 download link is unavailable in your region, or if you need a media that can be rebuilt from a single DVD, request STEP 7 Professional 2010 SR2 from your local Siemens representative. The official Siemens statement per the SP2 entry reads: "If you wish to change to Windows 7 64 Bit with STEP 7 Professional, you require STEP 7 Professional 2010 SR2. It is not sufficient to only install the Service Pack 2 for STEP 7 V5.5."

SR2 embeds SP1, SP2, and the WinCC flexible 2008 SP2 integration layer into a single redistributable. This path is mandatory for clean-room deployments where the SP0 base install cannot be re-performed.

Step-by-Step

1. Request the SR2 DVD from Siemens (order number 6ES7 810-4CC10-0YA7, or your local equivalent).
2. Boot Windows 7 64-bit to a clean state. Uninstall any prior STEP 7 install via Control Panel → Programs and Features and delete residual folders in %ProgramFiles(x86)%\Siemens if present.
3. Insert the SR2 DVD. Autorun will launch Setup.exe. If autorun is suppressed, run it manually as Administrator.
4. Select the package set: STEP 7 V5.5, S7-PLCSIM, S7-SCL, S7-GRAPH, S7-HiGraph, and optionally the WinCC flexible RT 2008 component.
5. Complete the wizard. Total install time is typically 35–55 minutes on a modern SSD-equipped workstation.
6. Activate the license through Automation License Manager.
7. Reboot and proceed to verification.

Solution C — Patch Path: V5.5 SP0 → SP2 in Two Stages

Some engineering teams report success installing SP2 directly on a clean SP0 base when the SP1 download is temporarily unavailable. This is not an officially supported scenario — the SP2 setup explicitly checks for SP1 in the registry. The reported success cases are typically installations where the SP2 detection logic misreads the registry because of an unrelated vendor MSI residue, leaving an unstable system state. Use this path only if Solutions A and B are not viable, and budget time for a complete reinstall under Solution B.

Verification Procedure

1. Launch SIMATIC Manager from Start → SIMATIC → SIMATIC Manager. The shell must open without the 0xC000007B error. On first launch, the "Set PG/PC Interface" dialog may appear — select S7ONLINE (STEP7) → TCP/IP or the appropriate MPI/Profibus adapter, then click OK.
2. Open a sample project: File → Open → Sample Projects → zEn01_01_STEP7_Tutorial (or the English equivalent shipped with your installation). Verify the S7 Program, Blocks, and Hardware Config views all load without "Class not registered" errors.
3. Verify MPI/Profibus driver: Open Start → SIMATIC → STEP 7 → Set PG-PC Interface. The S7ONLINE (STEP7) → PC Adapter (MPI) and ... → PC Adapter (PROFIBUS) entries must both appear in the access point list. If they are missing, the USB EPROM driver failed to install; reinstall from %ProgramFiles(x86)%\Siemens\Automation\S7\Driver\Setup.exe as Administrator.
4. Run a hardware check: From SIMATIC Manager, Options → PC Interface → Diagnostics. The diagnostics should show a green status with the local node address. If the test fails with error 0x031A, the PC Adapter cable or the USB hardlock is interfering with the COM port; remove all USB devices other than the license dongle and re-test.
5. Verify online help: Press F1 on any block. The HTML help must render. If it opens an empty page, register the S7hRegSvr.dll manually: regsvr32 "%ProgramFiles(x86)%\Siemens\Automation\S7\Help\S7hRegSvr.dll".
6. Re-enable UAC and reboot. Repeat steps 1 and 2. UAC reactivation is the final stability check — if SIMATIC Manager fails under UAC, restore the Compatibility tab setting to Run this program as an administrator on the S7PCT.exe shortcut.

Post-Install Hardening

Apply the following hardening steps to prevent the most common post-installation failures on Windows 7 x64. Each item addresses a known regression observed in the field.

Common Errors and Remedies

Error 0xC000007B on SIMATIC Manager Launch

Symptom: Application fails to start correctly. STATUS_INVALID_IMAGE_FORMAT, almost always after a Windows update or DEP tightening.

Remedy: Reinstall the x86 VC++ 2008 SP1 redistributable. If persistent, copy msvcr90.dll v9.0.30729.6161 from %WinDir%\SysWOW64 into %ProgramFiles(x86)%\Siemens\Automation\S7\BIN and re-register. Validate with dumpbin /headers S7Manager.exe | findstr machine — output must be 14C (x86).

Error "STEP 7 is not installed" on Startup Wizard

Symptom: First-run wizard cannot detect STEP 7 even though it is listed in Programs and Features.

Remedy: The 32-bit registry hive is not being enumerated. Run regedit as Administrator and confirm the key HKLM\SOFTWARE\Wow6432Node\Siemens\Automation\STEP7 exists with value Version = "5.5.1.0" (SP1) or higher. If missing, repair the installation: Control Panel → Programs and Features → SIMATIC STEP 7 V5.5 → Repair.

PC Adapter Not Recognized After Driver Update

Symptom: The PC Adapter USB cable is listed in Device Manager but Set PG-PC Interface shows it as grayed out.

Remedy: Reinstall the S7USBEPD.sys driver from the SP1 redistributable: %ProgramFiles(x86)%\Siemens\Automation\S7\Driver\Setup.exe. The driver must be version 5.5.1.0 or later for Windows 7 x64 signature enforcement.

Automation License Manager Reports "Invalid License"

Symptom: License appears valid in ALM but STEP 7 still reports the license as missing.

Remedy: The license was generated against the SP0 build hash. Re-authorize the license through the Siemens License Generator portal (requires your license certificate number) or migrate to a STEP 7 Professional 2010 SR2 license which is hash-compatible with SP1+.

Project Opens with "Class not registered" on Hardware Config

Symptom: S7 Program opens, but HW Config crashes on the first station with a CLSID lookup failure.

Remedy: Re-register the HW Config COM components: cd "%ProgramFiles(x86)%\Siemens\Automation\S7\BIN" && for %i in (*.dll) do regsvr32 /s %i. If still failing, the optional package (S7-GRAPH, S7-SCL) referenced in the project was not installed; install the missing option package and retry.

Migration Path to TIA Portal

STEP 7 V5.5 SP1 is end-of-life. New deployments should consider TIA Portal V16+ for S7-300/S7-400, S7-1200, S7-1500, and ET 200 mixed-system projects. The Siemens migration tool STEP 7 V5.5 → TIA Portal (TIA Portal menu Project → Migrate project) converts .s7p archives to .ap16 with the following caveats:

• Hardware Config (HW Config) configurations transfer, but unsupported CP/IM modules must be manually mapped.
• S7-GRAPH and S7-HiGraph FBs convert to GRAPH and PRODIAG in TIA Portal; SCL sources convert cleanly but may require re-compile due to type-strict enforcement.
• Multi-project (S7-Program, S7-300 station, S7-400 station) structures require manual regrouping.
• F-technology (Failsafe) blocks require TIA Portal V15.1 or later for lossless transfer.

For shop floors that cannot migrate immediately, continue running STEP 7 V5.5 SP1/SP2 inside a Windows 7 x64 VM on a Windows 10/11 host. VMware Workstation 16+ and Hyper-V Generation 2 with a fixed VHD both support the PC Adapter USB cable passthrough required for online programming.

Field-Engineering Best Practices

1. Document the build hash. On every install, record the file version of S7Manager.exe and the registry value of HKLM\SOFTWARE\Wow6432Node\Siemens\Automation\STEP7\Version. This makes it possible to verify, six months later, exactly which patch level is on a given engineering workstation.
2. Isolate the engineering workstation. Do not co-install STEP 7 V5.5 with TIA Portal V13 SP1 or earlier on the same image; the shared Automation License Manager service has known conflicts that require manual registry edits to resolve.
3. Maintain a project-side VM template. Use Sysprep + a golden VHD to rapidly deploy a known-good Windows 7 64-bit + STEP 7 V5.5 SP1 image to new engineers. The template should include all optional packages, the VC++ runtimes, the firewall rules, and the DEP exception list.
4. Do not apply convenience rollups indiscriminately. Block the Windows 7 April 2015 update rollup (KB3033929 chain) and the March 2017 SHA-2 patch on engineering workstations until STEP 7 is fully verified. These updates have a documented history of replacing the MSVCR90 assembly.
5. Keep the Automation License Manager service patched. Siemens releases ALM service packs independently of STEP 7 service packs. ALM V6.0 SP3 or later is required for clean coexistence on Windows 7 x64.

FAQ