Troubleshooting
Why Installing WinCC Flexible Breaks TIA Portal V13
Short answer
No — TIA Portal V13 does not bundle WinCC Flexible; the Root Screen editor you already opened is its integrated WinCC editor, and that is where KTP panels are engineered. WinCC Flexible 2008 is the separate previous-generation tool, and installing it on the V13 machine is what stops TIA Portal starting, so uninstall it, run the V13 repair, and keep the two tools on separate machines or migrate the project.
On this page
No, TIA Portal V13 does not come with WinCC Flexible inside it. The editor you already reached — new project, KTP series device, a screen called Root Screen with a button toolbox — is TIA Portal's integrated WinCC editor, and that is the tool for KTP panels. WinCC Flexible 2008 is the separate, previous-generation engineering tool for the older operator panels, which is why nothing in your book matches what is on screen. Installing WinCC Flexible on the V13 machine is also what broke TIA Portal: a failure that begins the moment another engineering package is installed points at the installation state, not at your project or your license. Uninstall it, repair V13, and keep the two tools apart — Flexible on its own PC or virtual machine, or its project migrated once and the tool retired.
What V13 gives you instead of WinCC Flexible #
The HMI engineering inside TIA Portal V13 is WinCC in editions, and the chain runs Basic, Comfort, Advanced, Professional, each level including the targets of the ones below it: WinCC Advanced alone engineers comfort panels, basic panels and PC runtime. The KTP series device you selected opens that editor — screen tree, object toolbox, properties area — and nothing further is installed or needed for the screen design you described. WinCC Flexible 2008 belongs to the generation before TIA Portal and is not inside V13 in any form. For the whole family in one view, see WinCC V7.4, WinCC Flexible 2008 and TIA Portal compared.
Why the Flexible install stops V13 starting #
These packages share services, libraries and licensing components on one Windows system. The compatibility documentation for V13 pairs it with its own generation: STEP 7 Basic, STEP 7 Professional, WinCC Basic and WinCC Comfort/Advanced — four product lines. WinCC Professional carries the one hard stacking limit in the family, a single version per PC. WinCC Flexible 2008 is from the generation before and appears in none of those sets, so its setup writes into the same shared components V13 depends on, and an incompatible or incomplete combination there takes down an application that previously worked. When V13 dies immediately after that install, the timing is the evidence; do not chase a license error, and do not delete antivirus or switch off updates as a repair. Take installers only from Siemens or its authorized distribution, so the result of a repair is meaningful.
The recovery list #
- Write down the exact message TIA Portal shows when it fails to start.
- Uninstall WinCC Flexible 2008 from the Windows program list, then restart.
- Run the TIA Portal V13 setup again and use its repair option, then restart once more.
- Put V13 on a defined level before adding anything else: updates for V13 exist only on the basis of V13 SP2, and Windows 10 support starts at SP2, so read the service pack and the operating system together.
- Test with a new empty project and a KTP series device; if the editor opens and a button drops onto the screen, V13 is whole again.
- Reimage only if repair cannot restore it, and reinstall V13 alone on the clean system.
Where each tool is allowed to live #
- Several TIA Portal versions stack on one PC: V11, V12, V13 and V14 side by side is a working set.
- WinCC Professional is the exception — one version per PC, never two.
- WinCC Flexible 2008 fits none of those sets; it gets its own PC or a virtual machine.
- The KTP panel itself needs no second tool at all.
The decision falls out of that list: a PC that must run WinCC Flexible 2008 runs no TIA Portal, and a PC that runs TIA Portal takes no Flexible install. If it is the old project you want rather than the old tool, migrate a WinCC Flexible project to TIA Portal once and retire the legacy editor.
Working the case: one PC, V13, a Flexible book and a KTP panel #
Inputs:
- One engineering PC already running TIA Portal V13 — the machine you had to reformat.
- Target panel: a KTP series device, which opens the Root Screen editor in V13 with no additional product.
- A book built around WinCC Flexible 2008 and WinCC SCADA.
- Service pack and operating system unrecorded; Windows 10 requires V13 SP2.
Rule in words: one PC may stack several TIA Portal versions and one WinCC Professional, but zero packages from the Flexible generation beside a TIA installation.
The arithmetic:
- TIA-generation companions the compatibility list gives V13: STEP 7 Basic, STEP 7 Professional, WinCC Basic, WinCC Comfort/Advanced = 4 product lines.
- Flexible-generation packages wanted on this PC: 1 (WinCC Flexible 2008).
- Supported slots for it beside V13: 0.
- 1 wanted − 0 supported = 1 package that must move to another machine or a VM.
- Extra installs the KTP screen work needs: 0.
Nothing is missing from V13 for the KTP work, and WinCC Flexible 2008 has no supported place on this PC. The decision: above zero Flexible installs, TIA Portal lives elsewhere — so either the legacy tool gets its own machine, or the project is migrated and the book stays on the shelf as concept reading.
Motor colors, indicators and moving graphics in V13 #
- Fix the HMI connection first: the configured interface and controller must match the real ones. If the status value never moves, suspect the link before the graphic — the same diagnosis that clears a controller that shows link lights but TIA Portal still cannot connect.
- Drive color from a feedback tag, not the start command: a button proves an operator request, a status word proves the motor state.
- Select the motor image and configure its appearance against that tag: value ranges map to background and border colors, so running (1) reads green and stopped (0) reads red, with a second tag or a wider range separating forward from reverse.
- Buttons, indicators and keypads come from the screen toolbox with configurable appearance and events — the colored two-state buttons in your book are built here, under different names.
- When communication quality goes bad, show an unknown state rather than presenting the last value as current.
- Nothing has to be redrawn from scratch: you can reuse a legacy HMI program and graphics in a new runtime and keep the motor symbols you already have.
Questions asked
Does TIA Portal V13 include WinCC Flexible?
No. V13 integrates WinCC as editions inside the portal, and the chain runs Basic, Comfort, Advanced, Professional, each level including the targets below it — Advanced alone covers basic panels, comfort panels and PC runtime. WinCC Flexible 2008 is the separate tool of the previous generation; V13 neither installs it nor launches it.
TIA Portal V13 will not start after I installed WinCC Flexible. Do I have to reformat the PC?
Not as the first move. Copy your project archives somewhere safe, uninstall WinCC Flexible 2008, restart, then run the V13 setup and use its repair option. Reimage only when repair fails, and reinstall V13 alone — the fault came from the installation state, not from your license or your project.
Can several TIA Portal versions share one PC?
Yes — V11, V12, V13 and V14 stack side by side. The one limit in the family is WinCC Professional, which allows a single version per PC. That is why mixing generations, TIA Portal V13 plus WinCC Flexible 2008, is the combination that fails while two TIA versions coexist quietly.
How do I make the motor image green when running and red when stopped?
Select the image and bind its appearance to a motor-status feedback tag: map value ranges to colors, with 1 as green and 0 as red, and give fault values their own range so they cannot masquerade as a healthy state. Direction color comes from a second tag or a wider range, never from the start button.
My book teaches WinCC Flexible and WinCC SCADA. Is it useless now?
No, but read it for concepts, not menus. Tags, screens, events, appearance mappings and recipes all exist in the integrated editor under different names, and the SCADA chapters correspond to PC runtime targets in the TIA world. For the panels the book was written for, migration into V13 is the supported route.