Installing Siemens STEP 7 on Windows 7 64-bit: VM Workaround

Overview: STEP 7 V5.x Compatibility on Windows 7 64-bit

Siemens STEP 7 V5.x is the engineering tool for the SIMATIC S7-300, S7-400, C7, and ET 200S station families. The V5.x line (V5.1 through V5.5 + SP4) is built strictly as a 32-bit Win32 application and was qualified only against Windows XP Professional SP2/SP3 and Windows 7 32-bit. When the InstallShield launcher runs on Windows 7 Professional, Enterprise, or Ultimate in its x64 edition, the package authoring tool aborts the transaction with a generic "not all programs were installed" message and rolls back any partially registered components. Hand-editing the .msi launch conditions to suppress the OS-version check may clear the gate, but it does not produce a working STEP 7 instance because several shared components are registered as 32-bit shell extensions that the 64-bit Windows component manager refuses to bind.

The supported workaround — until Siemens released TIA Portal V13 with full Windows 7 64-bit native support and later migrated V5.6 into SIMATIC STEP 7 V5.6 (Win 10 x64 capable) — was to host the STEP 7 V5.x suite inside a 32-bit Windows guest. Two virtualization stacks were used in the field:

• Microsoft Windows XP Mode (Windows Virtual PC) — free, requires Windows 7 Professional, Enterprise, or Ultimate SKU. Ships with a pre-built Windows XP SP3 VHD and the Windows Virtual PC console.
• VMware Workstation 7 / 8 / 9 / 10 — paid, runs on any Windows 7 SKU including Home Premium. Requires a separately licensed copy of Windows XP Professional SP3.

Both stacks isolate the 32-bit STEP 7 process, its Automation License Manager service, the S7DOS / S7EHSVRT helper services, and the CP 5511/CP 5611/CP 5612 device drivers from the 64-bit host. The PLC traffic crosses a virtual NIC bridged to the physical Ethernet adapter; MPI/PROFIBUS traffic traverses a USB or PCI-passthrough device mapped into the guest.

Prerequisites

Before starting, validate the host platform, licenses, and STEP 7 distribution:

Why Direct Installation on Windows 7 x64 Fails

The STEP 7 V5.x setup launches Setup.exe from the root of the DVD. This bootstrapper queries the Windows NT major/minor version through GetVersionEx and rejects any host that reports a 64-bit SKU in WOW64 mode with major version 6 and minor version 1. The MSI files under STEP7\Disk1\ include a launch-condition table row keyed on VersionNT64. The reported failure window is generic:

Error 1311. Source file not found: Common Files\Siemens\S7IEP32\...\<dll>
Setup cannot continue because some files could not be installed.
"Not all programs were installed successfully."

Field tests showed three failure modes:

1. MSI launch-condition rejection. Even after editing the launch-condition table with Orca.exe to set VersionNT64 = "" (null), the bootstrapper rejects the install midway because S7SINIT.exe and S7DOS.exe register Windows services that the 64-bit SCM cannot host under %SystemRoot%\SysWOW64\config\.
2. WOW64 registry mismatch. Components write to HKLM\SOFTWARE\Siemens\Automation. The WOW64 layer reflects this to HKLM\SOFTWARE\Wow6432Node\Siemens\Automation, but the SIMATIC Manager process tree hard-codes the non-Wow6432Node path on startup.
3. CP 5511/CP 5611 driver stack. The Siemens S7ONLINE NDIS miniport driver is signed for 32-bit Windows XP/2003. It does not load under the 64-bit Windows 7 kernel, so PG/PC interface selection shows "Unknown" for MPI/PROFIBUS.

The clean solution is to host STEP 7 inside a 32-bit Windows guest where the entire Win32 contract is satisfied.

Method 1 — Windows XP Mode (Windows Virtual PC)

XP Mode is the lowest-friction path because Microsoft bundles a pre-built Windows XP SP3 VHD licensed for use on the Windows 7 host. The full toolchain of STEP 7 + WinCC Flexible + ProTool + Micro/WIN installs cleanly with no manual registry edits.

1. Install Windows Virtual PC and XP Mode. Download "Windows Virtual PC" and "Windows XP Mode" from the official Microsoft download center. Run WindowsXPMode_en-us.exe to extract the VHD to %SystemDrive%\Users\<user>\AppData\Local\Microsoft\Windows Virtual PC\Virtual Machines\. Run Windows6.1-KB958559-x64.msu to install the Windows Virtual PC console.
2. Boot the XP guest. Launch "Windows Virtual PC" from the Start menu, double-click Windows XP Mode.vhd. Accept the EULA, complete the Windows XP out-of-box experience, apply Windows XP SP3 (slipstream into the VHD or run Windows Update inside the guest).
3. Disable Windows XP activation nag. The XP Mode VHD uses a Volume License channel key already activated against the host's Windows 7 activation. No further action is required.
4. Install STEP 7 V5.5 SP4. Mount the STEP 7 DVD into the guest via the XP Mode toolbar "Tools → Settings → DVD Drive" path. From the guest, run D:\Setup.exe. Accept the default installation path C:\Program Files\Siemens\Automation. During the install select "STEP 7 V5.5", "S7-PLCSIM V5.4", and "Automation License Manager V5.2".
5. Apply the SP4 patch. Mount the SP4 ISO and run Setup.exe. The SP4 installer detects V5.5 and upgrades in place.
6. Configure the SIMATIC Manager desktop shortcut. Verify C:\Program Files\Siemens\Automation\SIMATIC Manager\s7hlp64.exe launches the SIMATIC Manager shell. On first run, the SIMATIC Manager wizard prompts for the project storage path; default C:\Program Files\Siemens\Automation\Projects\.
7. Install parallel-port license drivers. Inside the guest, install the parallel-port redirector (USB-to-parallel for the legacy AuthorsW key) using the XP native driver. The Siemens S7USBDRV package installs the parallel dongle driver for ALM.
8. Install the CP 5511/CP 5611 driver inside the guest. Map the CardBus/PCI device to the guest via XP Mode's USB passthrough or attach the CP directly. The Siemens CP5511_PCMCIA_Driver_V5.5 or CP5611_PCI_Driver_V5.5 installs under the XP kernel and registers as S7ONLINE.

XP Mode uses Seamless Windows to integrate the guest application window with the host taskbar. STEP 7 SIMATIC Manager appears as if it were native to Windows 7. CPU overhead is moderate: a Core i5-2520M with 8 GB RAM runs STEP 7 V5.5 SP4 + WinCC Flexible 2008 SP5 concurrently inside XP Mode with comfortable headroom.

Method 2 — VMware Workstation

VMware Workstation is required when the host is Windows 7 Home Premium x64 (XP Mode is locked to Professional and above), or when the engineer needs USB 3.0 device passthrough, multiple snapshot checkpoints, or bridged networking for PROFINET IRT. VMware Workstation 7.x supports Windows XP SP3 guests; VMware Workstation 8/9/10 add Windows 8/8.1 guest support but retain full XP compatibility.

1. Install VMware Workstation. Run VMware-workstation-full-9.0.2-1031769.exe (or newer). Reboot the host to load the vmci and vmmon kernel drivers.
2. Create a Windows XP SP3 VM. File → New Virtual Machine → Custom (advanced). Select "Windows XP Professional" as the guest OS. Allocate 2 GB RAM, 40 GB dynamically allocated virtual disk, LSI Logic virtual SCSI, IDE virtual disk type (XP lacks AHCI driver support without F6 slipstream). Mount the Windows XP SP3 ISO to the virtual CD-ROM.
3. Install Windows XP SP3 and VMware Tools. Complete the XP install, install VMware Tools from the VM menu to enable display scaling, drag-and-drop, and time synchronization.
4. Bridged networking. In the VM settings, Network Adapter → Bridged: Replicate physical network connection state ✓. This binds the VM's virtual NIC directly to the host's physical Ethernet adapter so the guest appears as a separate IP node on the plant LAN.
5. Install STEP 7 V5.5 SP4. Same procedure as the XP Mode path: mount the DVD, run Setup.exe, accept defaults, apply SP4.
6. USB device passthrough for CP 5511. VM → Removable Devices → CP 5511 PCMCIA → Connect (Disconnect from Host). The CP 5511 is a CardBus PC Card; if the host CardBus slot is exposed to the guest, VMware binds the CardBus controller to the guest and the Siemens driver loads normally.
7. Snapshot before commissioning. Take a VM snapshot labeled "STEP 7 V5.5 SP4 baseline" before any project work. This rolls back in seconds if a project corrupted the S7 project database.

Network Configuration for PLC Communication

The S7 protocol runs over three transports: ISO-on-TCP (RFC 1006) on TCP port 102, native TCP/IP for S7-communication on port 102, and MPI/PROFIBUS over the CP 5511/CP 5611/CP 5612 driver stack. Each transport has its own binding requirements in the guest VM.

TCP/IP S7 Communication (ISO-on-TCP)

For Ethernet-attached S7-300 (CP 343-1, CP 343-1 Lean) and S7-400 (CP 443-1) PLCs, the guest VM must reach the PLC's IP address directly. Use bridged networking:

1. In the XP Mode VM settings, set Network Adapter 1 to "Your network card" (physical NIC binding).
2. Disable NAT mode. NAT mode hides the guest behind the host's IP stack, breaking the bidirectional TCP/102 connection that S7 communication requires.
3. Inside the guest, set a static IP address in the same subnet as the PLC (for example, host = 192.168.0.10, PLC = 192.168.0.20, subnet = 255.255.255.0, gateway = 192.168.0.1).
4. Open the SIMATIC Manager → Options → Set PG/PC Interface → TCP/IP → Network Card (the bridged virtual NIC).
5. From Accessible Nodes, the S7 CPU should appear within 2 seconds with its MPI/PROFIBUS or IP address and rack/slot.

MPI/PROFIBUS over CP 5511 / CP 5611 / CP 5612

For sub-TCP/IP MPI traffic (S7-300 with MPI port, S7-200 via PC/PPI cable), the CP 5511 (PCMCIA/CardBus) or CP 5611/CP 5612 (PCI) is bound to the guest kernel:

1. Install the Siemens SIMATIC NET PC software V8.x inside the guest first. This registers the S7ONLINE device driver and the cp5611.cfg configuration file.
2. Connect the CP. XP Mode maps CardBus cards through USB passthrough if the host exposes the CardBus controller; VMware Workstation supports direct PCI passthrough with VT-d enabled.
3. Verify in Device Manager: S7ONLINE appears under Network Adapters, no yellow exclamation marks.
4. Open Set PG/PC Interface → CP5511(PCCard) → Properties. Set transmission rate to 187.5 kbps (default MPI) or 1.5 Mbps / 12 Mbps for PROFIBUS. The MPI address of the PG must be unique on the segment (default 0).
5. If the CP 5511 enumerates as a "CardBus Multimedia Card" rather than a Siemens CP, the field fix is to disable CardBus in the host BIOS, leaving the host CardBus slot inactive and the guest binding to the bare silicon.

Remote Access: VNC vs. Windows RDP

STEP 7 V5.x setup and update installers occasionally refuse to launch under Windows Remote Desktop Protocol (RDP). The Microsoft Terminal Services compatibility layer redirects the installer's interactive desktop session, and several MSI custom actions rely on Session 0 APIs that RDP does not forward. The field-proven fix is to install a VNC server inside the guest and a VNC client on the host:

Configuration steps:

1. Inside the guest, install the VNC server of choice. Configure password authentication (do not leave it blank).
2. On the Windows 7 host, install the matching VNC client.
3. Connect to the guest's bridged IP (for example, 192.168.0.11) on VNC display :0 (5900/TCP) or :1 (5901/TCP).
4. Run STEP 7 setup under the VNC session. Installers that refused under RDP run cleanly under VNC.

Verification and Commissioning

After installing STEP 7 V5.5 SP4 inside the guest, run the verification sequence below before commissioning the first project:

Limitations and Support Considerations

Siemens officially supports STEP 7 V5.5 SP4 only on Windows XP SP3 and Windows 7 32-bit. Siemens Global Technical Support will refuse to open a case against a STEP 7 instance running inside any virtualization stack. The engineer accepts this risk when choosing the VM workaround. Mitigations:

• Maintain a separate bare-metal Windows XP or Windows 7 32-bit image on a spare drive for support escalations.
• Document the VM build (host SKU, VMware/XP Mode version, host driver revisions) in the project handover package.
• Keep the STEP 7 DVD and SP4 ISO in the project archive so a fresh VM can be re-deployed within an hour.
• For new deployments, prefer Siemens TIA Portal V16/V17/V18 on Windows 10 64-bit — the entire Win64 migration problem disappears.

Beyond Windows 7, the VM approach extends cleanly to Windows 8.1 and Windows 10 hosts. VMware Workstation 15/16 supports Windows 10 hosts with the same STEP 7 V5.5 SP4 guest configuration.

FAQ