IMDTouchKnowledge BaseShop main store

How-to

Migrating a WinCC 7.0 Project From Windows XP to Windows 7

HMI and touchscreens Published 8 min read

Short answer

Install WinCC 7.4 on Windows 7, reinstall cleanly if the SP1 package fails, migrate the project through 7.2 with Project Migrator, license the runtime for 1024 tags because 128 runs demo mode, and replace the CP 5611 card with a CP 5612, which has 64-bit SIMATIC NET support. Each gate fails separately, so test each one.

On this page
  1. Which WinCC 7.4 components do I install on Windows 7?
  2. What do SP1, UD1 and UD2 mean on WinCC packages?
  3. Why did the runtime installation fail during 7.4 SP1 setup?
  4. Why does the copied project hang with a Local server warning?
  5. How do I migrate the project from WinCC 7.0 SP3 to 7.4?
  6. Why does runtime drop into demo mode with a 128-tag limit?
  7. Will the CP 5611 PROFIBUS card work on 64-bit Windows?
  8. What order do I commission the new station in?
  9. Questions asked

A WinCC 7.0 SP3 project that ran on 32-bit Windows XP Professional SP3 runs on Windows 7 64-bit after five gates pass, in this order: a supported WinCC 7.4 plus SIMATIC NET combination, a clean runtime installation, a staged migration through 7.2, a runtime license above the 128-tag demo limit, and a 64-bit-capable PROFIBUS adapter — CP 5611 out, CP 5612 in. The replacement hardware proves none of them: an i7 at 3.5 GHz, 8 GB of RAM and an SSD say nothing about installation integrity, licensing or driver support. The numbers below come from the reported job: Windows 7 Ultimate 64-bit replacing Windows XP Professional SP3, WinCC 7.0 SP3 EUROPE on the old station, a project above 1000 tags, and a motherboard-slot PROFIBUS card labeled CP 5511/CP 5611.

Which WinCC 7.4 components do I install on Windows 7? #

Install WinCC 7.4 in the role the project actually uses, with only the communication options the configured channels need — not every package the XP station listed — and match the SIMATIC NET release to it as one supported combination.

The old station's installed list — WinCC RC, RT, Server, Redundancy and User Archives 7.0, the S5 Ethernet Layer4, TI Ethernet Layer4, SIMATIC 505 TCP/IP and Profibus FMS channel options, and the SIMATIC NET 7.1 PC software — is an inventory, not a shopping list. Read the project instead: which channels are configured, whether user archives are used, whether the station acts as a server or half of a redundant pair. Install that subset and nothing more; every legacy option you add is another component that must match the combination.

SIMATIC NET supplies the PC-side communication components for the configured channel, so its release is chosen together with the WinCC release, never separately. STEP 7 stays a separate decision — PLC programming was excluded on this job — and a STEP 7 station that connects and downloads proves the engineering path only, never the runtime. Apply the version-first discipline of checking HMI engineering software before a panel replacement: tool and target must match before anything moves.

If the replacement station is also the machine's operator surface, compare industrial panel PCs as the class of touchscreen computer that carries a WinCC runtime at the machine.

What do SP1, UD1 and UD2 mean on WinCC packages? #

SP and UD are maintenance levels of one release — a service pack and an update — and the full designation is part of the compatibility claim: SP1, UD1 and UD2 are not interchangeable labels, and the designation decides the Windows and SIMATIC NET that package supports.

A service pack is a full maintenance package for a release; an update is a smaller maintenance delivery between service packs. Because they are maintenance levels, they ship as separate packages with separate support statements — a compatibility statement covers the release together with its maintenance level, so read the full designation, not just "7.4".

The reported job is the evidence: the 7.4 SP1 package threw an error at the automatic runtime installation and would only continue manually, while a different, plain 7.4 package installed with zero errors. That result makes package integrity a diagnostic branch — reinstall from a different package of the same release — and nothing more. It does not make "avoid SP1" a rule; install the maintenance level your documented combination requires, from a package that completes cleanly.

Why did the runtime installation fail during 7.4 SP1 setup? #

The fault is in the installation, not the project: a setup that reports an error and continues only when you press on manually has failed, and on this job the plain 7.4 package completed with zero errors where the 7.4 SP1 package had failed.

An error during the automatic runtime installation is a failed gate even if the runtime later appears in the installed-programs list. Appearance in that list records that files landed, not that the component works.

Work the gate this way: obtain the installation media from the manufacturer or an authorized distributor, run setup, complete every restart it requests, then verify the installed component versions and the services the release depends on. Any unresolved error sends you back for a different package of the same release until setup finishes with none.

Then prove the station with a new, minimal WinCC project before touching production data: create it, open it in WinCC Explorer, start runtime, and confirm it does not hang. Add one tag on a test connection against a spare PLC and compare the value with the PLC. A station that fails this has no business opening a migrated 1000-tag project.

Why does the copied project hang with a Local server warning? #

Two faults are stacked: the folder copy never converted the project to the 7.4 format, and the project still stores the old station's identity — the Local server warning — so neither the migration nor the computer-name alignment has happened yet.

Copying the project folder moves files; it performs no format conversion, installs no dependencies and changes no station identity. Conversion happens in the Project Migrator, and identity lives in the project itself: WinCC records the computer name of the station it was configured on, so the replacement PC must carry the name the project expects, or the project's stored computer entry must be updated to the new station — a per-station setting in the project's computer configuration, not a file to edit by hand.

The rotating cursor with Task Manager reporting the program as running says the process exists; it says nothing about initialization. On the reported job the hang cleared once the installation gate passed — a station with a broken runtime install will hang on a good project. Order the fixes: clean install, migration, then computer-name alignment.

How do I migrate the project from WinCC 7.0 SP3 to 7.4? #

Migrate in two hops with the Project Migrator, 7.0 SP3 to 7.2 first and then 7.2 to 7.4, on an installation that has already passed the setup gate — copying files is transport, and conversion only happens in the migrator.

The Project Migrator opens from the Windows Start menu under "Simatic" > WinCC > Tools > Project Migrator. Run the hops in this order and test after each one:

  1. Back up the 7.0 SP3 project and leave the XP station running as the fallback runtime.
  2. On a station with WinCC 7.2, migrate the 7.0 SP3 project to 7.2 with the Project Migrator, then test the result there.
  3. On the new station, migrate the 7.2 result to 7.4 with the Project Migrator, then confirm the project reports 7.4 — the same check as verifying the HMI project version running on a panel.
  4. Align the computer name if the Local server warning persists, open the project, start runtime, and run the variable checks covered in validating HMI variables during a software migration before you call the gate passed.

Why does runtime drop into demo mode with a 128-tag limit? #

Demo mode means the license-counted tag total outruns the license: the reported project uses more than 1000 tags against a 128-tag allowance — at least 872 short — and the fix is a runtime license for 1024 tags or larger.

Demo mode is a licensing state, not a fault to troubleshoot: the runtime starts because the installation is healthy, and it runs restricted because the tag total exceeds what the installed license permits.

Worked example, using the reported numbers. The project uses more than 1000 tags; the installed license permits 128. The shortfall at the reported floor is 1000 − 128 = 872 tags. The step taken on this job was a license for 1024 tags or larger, which covers the floor with 1024 − 1000 = 24 tags of headroom. If your own count reads higher — 1100, for example — the 1024 step fails by 1100 − 1024 = 76 tags and you license the next larger size.

The decision for the reported project: upgrade the runtime license to 1024 tags or larger. Cutting 872 tags out of a running plant is not an engineering option, and production does not run in demo mode.

Will the CP 5611 PROFIBUS card work on 64-bit Windows? #

No — the CP 5611 has no 64-bit SIMATIC NET support, so on Windows 7 64-bit the documented path is the CP 5612 card, and the project's channel configuration must be re-pointed at whichever adapter you actually install.

The old card, labeled CP 5511/CP 5611, cannot follow the project to the new station; that is why the adapter is a gate rather than a carry-over. The CP 5612 is the card used on this job and the documented choice for 64-bit.

USB-to-PROFIBUS converters exist, and one is usable only when its provider documents support for your exact SIMATIC NET release on 64-bit Windows — an undocumented converter is a future outage, not a shortcut. Whichever adapter goes in, the work is the same: the communication configuration must select that adapter for the channel and the PROFIBUS parameters set again, because the project's connection settings point at hardware that is no longer there. Close the gate by confirming live tag quality over the new card before the station takes production.

What order do I commission the new station in? #

Commission in this fixed order — supported combination, clean installation, minimal-project test, staged migration, tag license, then the PROFIBUS adapter — because every later gate is meaningless until the one before it passes.

  1. Record the combination: Windows edition and bitness, WinCC release with its full maintenance-level designation, the options the project uses, the SIMATIC NET release and the adapter model — one documented combination, decided before anything is installed.
  2. Install from manufacturer or authorized-distributor media; finish every restart; verify components and services; accept zero setup errors, changing packages until setup is clean.
  3. Prove the station with a new minimal project and one test tag against a spare PLC, comparing values.
  4. Migrate 7.0 SP3 to 7.2, then 7.2 to 7.4, testing after each hop, and confirm the project reports 7.4.
  5. Align the computer name, open the production project, and clear the Local server warning.
  6. Count license tags and install the 1024-tag-or-larger runtime license; runtime must start with no demo mode.
  7. Install the CP 5612, select it in the communication configuration, and confirm PROFIBUS tag quality.
  8. Keep the XP station as fallback until the new station has carried production shifts, then retire it.

Questions asked

Do I need to keep the old Windows XP station available?

Yes, until every gate has passed and the new station has carried production shifts. The XP machine is your only proven runtime, the source of a clean project backup, and the record of which options and channel software the project actually used. Retire it only after the Windows 7 station runs the project fully licensed with the PROFIBUS link live.

What is the difference between WinCC RC and RT?

RC licenses the engineering tools together with the runtime, so projects can be edited on that station; RT runs finished projects only. Put RC where engineers will modify the application and RT where it only executes. The demo-mode problem in this migration is decided by the tag-count license, not by the RC versus RT choice.

Can a USB-to-PROFIBUS converter replace the internal card?

Converters exist, but a converter is usable only if its provider documents support for your exact SIMATIC NET release on 64-bit Windows, and the project's channel configuration must be re-pointed to the new adapter either way. The documented path on this job was the CP 5612 PCI card, and that is the safe default.

The Project Migrator refuses the project as too old. What now?

The migrator accepts projects only from a minimum source version upward, and versions reported as below V6.0 are refused. Hop in steps: open the project on whichever older release still runs it, migrate to that release's successor, and repeat until the project is new enough for the 7.x path. Test after each hop.

Does 32-bit versus 64-bit Windows change the WinCC project itself?

No. The project data is not tied to Windows bitness, and the same project runs on either. What bitness decides is driver support: the CP 5611 card has none under 64-bit SIMATIC NET, which is why the adapter is a gate at all. Everything else in this migration is release, installation and licensing.

Keep reading

  • Comparison

    WinCC V7.4, WinCC Flexible 2008 and TIA Portal Compared

    WinCC V7.x is PC-based SCADA software, WinCC Flexible 2008 engineers operator panels and single PC stations and is discontinued as a standalone tool, and WinCC inside TIA Portal is the successor engineering platform alongside STEP 7. Decide by the target device and the exact project files on your engineering workstation, not by the shared WinCC name. STEP 7 is the PLC tool, not a WinCC product.

    HMI and touchscreens

  • How-to

    Reuse a legacy HMI program and graphics in a new runtime

    You cannot import a vendor HMI project into a PC HMI or SCADA runtime, and you cannot layer the new runtime on top of the panel. Run the new runtime beside the panel on the same PLC, carry over only the tag addresses and exported images, rebuild screens, alarms and users fresh, then strip write access from the old panel so the audit trail covers every operator write.

    HMI and touchscreens

  • Troubleshooting

    Why WinCC 8.0 Runtime Deactivates After a V7.5 Migration

    The pop-up means an unhandled exception terminated a runtime component, so the whole project leaves runtime. Read the first exception in PDRTSh.log at the stop timestamp, then activate a blank project on the same machine: if it also stops, repair the installation or Windows build against the WinCC 8.0 Update 7 readme; if it runs, bisect the migrated content.

    HMI and touchscreens