Migrating SIMATIC PCS 7 V6.1 SP1 Systems and Licenses to Windows 7 64-Bit

SIMATIC PCS 7 V6.1 SP1 cannot be installed or migrated directly onto Windows 7 64-bit. PCS 7 V6.1 SP1 is certified exclusively for 32-bit Windows XP Professional and Windows Server 2003; 64-bit Windows 7 support was introduced in PCS 7 V8.0. Furthermore, legacy V6.1 software licenses cannot authorize modern PCS 7 releases and must be upgraded via official Siemens Upgrade Packages. Hardware communication cards such as the PCI-based CP 1613 can operate in Windows 7 32-bit/64-bit systems with legacy PCI slots, but modern IPCs require the PCIe-based CP 1623. Migrating the automation project requires a multi-stage database conversion through PCS 7 V7.1.

Incompatibility Between PCS 7 V6.1 SP1 and Modern 64-Bit Windows

SIMATIC PCS 7 V6.1 SP1 was developed during the 32-bit computing era, relying on 16-bit/32-bit installation routines, Microsoft SQL Server 2000, and obsolete device drivers. Microsoft Windows 7 64-bit enforces strict kernel-mode driver signing, lacks support for SQL Server 2000, and blocks legacy PCS 7 services.

Attempting to install PCS 7 V6.1 on Windows 7 fails during initial operating system checks. Migrating to modern PC hardware running Windows 7 mandates upgrading the PCS 7 software baseline to at least PCS 7 V8.2 or PCS 7 V9.0.

Hardware Migration: CP 1613 (PCI) vs CP 1623 (PCIe)

The physical communication processor must be assessed when transitioning PC hardware:

Hardware ProcessorBus InterfaceWindows 7 SupportWindows 10 / Server 2016 SupportHardware Migration RecommendationCP 1613 / CP 1613 A232-bit PCI (5V / 3.3V)Supported (SIMATIC NET V8.2)UnsupportedReplace with CP 1623; modern industrial motherboards lack 32-bit PCI slots.CP 1623PCI Express x1SupportedSupportedStandard replacement (6GK1162-3AA00) for all modern IPCs.Standard Intel NICOnboard / PCIeSupported (SOFTNET-IE)Supported (SOFTNET-IE)Suitable for non-redundant basic process automation networks.

Software and License Migration Strategy

A project cannot bridge the technological gap from V6.1 to V9.0 in a single step:

Step 1: Multi-Stage Project Conversion

Intermediate Migration (V6.1 -> V7.1 SP4): Open the project on a transition Engineering Station running PCS 7 V7.1 SP4 on Windows XP. Update block types, compile charts, and convert OS databases.
Final Migration (V7.1 SP4 -> V8.2 / V9.0): Transfer the migrated project to the target Windows 7 64-bit (or Windows 10) Engineering Station. Recompile AS and OS databases to modern APL standards.

Step 2: License Upgrades

Legacy authorizations or V6.1 license keys stored in Automation License Manager cannot authorize V8.2 or V9.0. Engineers must purchase official Upgrade Packages that upgrade legacy engineering and runtime licenses.

Procurement Schedule for Upgrade Packages

The following Equipment Schedule specifies the relevant order numbers for migration:

Hardware Communications Processor:
- SIMATIC NET CP 1623 PCIe Communications Card: 6GK1162-3AA00

Software Upgrade Packages (V6.x to V8.2):
- PCS 7 Engineering Upgrade Package V6.x to V8.2: 6ES7658-5AX28-0YE5
- PCS 7 OS Server Upgrade Package V6.x to V8.2:   6ES7658-2CX28-0YE0
- SIMATIC NET HARDNET-IE S7 Upgrade to V13/V14:   6GK1716-1CB00-0AE0

[!IMPORTANT]
Commercial Accuracy Disclaimer: Upgrades from legacy PCS 7 V6.x require purchasing specific migration and upgrade license entitlements. License keys from V6.1 are obsolete and do not authorize modern runtime software. Sizing must be re-evaluated for AS and OS Process Objects. Final license quantities and MLFBs must be validated against the applicable Siemens ST PCS 7 Catalog and authorized distributor quotations.

Verification

To verify successful migration to Windows 7 64-bit:

On the new Windows 7 64-bit PC, open Automation License Manager: confirm all upgraded licenses display status OK.
Open Device Manager: verify that the newly installed CP 1623 is recognized without driver warnings.
In SIMATIC Manager, open the migrated multiproject: perform a full consistency check (Check Consistency).
Compile CFC and OS: verify zero syntax errors or missing block type faults.
Open WinCC Explorer: confirm that the OS project opens cleanly and connects to the runtime database.

Limitations and Operational Precautions

Operational boundaries when modernizing legacy systems:

Classic Standard Library vs APL: PCS 7 V6.1 utilized the classic Standard Library. Modernizing to V8.2/V9.0 permits running in 'migration mode' with classic drivers, but new features require modernizing to the Advanced Process Library (APL).
Hardware Controller Firmware: S7-400 CPUs operating on V6.1 may feature older firmware (e.g., Firmware V3.x or V4.0) that cannot support modern PCS 7 functions. Verify CPU MLFB in the Siemens Compatibility Tool.
Direct Jump Prohibited: Never attempt to open a V6.1 project directly in PCS 7 V9.0 without the intermediate V7.1 migration step; database structures will be permanently corrupted.

Engineer FAQ

Can I install PCS 7 V6.1 SP1 on Windows 7 using compatibility mode?

No. Compatibility mode cannot bypass 64-bit kernel driver signing, obsolete DCOM requirements, and the lack of SQL Server 2000 support on Windows 7.

Can the CP 1613 card be used in a new Windows 7 64-bit PC?

The CP 1613 driver is supported on Windows 7 64-bit, but the physical card requires a legacy 32-bit PCI slot, which is absent from modern industrial motherboards. Upgrading to PCIe-based CP 1623 is standard.

Why is an intermediate migration step via PCS 7 V7.1 required?

PCS 7 V7.1 introduces major database redesigns in both CFC and WinCC. Direct conversion from V6.1 to modern V8.x/V9.x bypasses database schema upgrade scripts, corrupting the multiproject.

What happens to existing Process Object (PO) licenses during upgrade?

Upgrade packages convert legacy PO authorizations into modern ALM license keys, preserving your existing PO investment while updating version entitlement.