Troubleshooting
Why the WinCC V13 Professional runtime command stays disabled
Short answer
The greyed-out start command is an installation and target problem, not a license problem. The active Advanced button proves only that the Advanced runtime is installed. Install WinCC Runtime Professional so UPD1 has a base to update, generate the .MCX by compiling and transferring, and leave SP1 out of the decision.
On this page
- Why is start runtime greyed out in WinCC V13 Professional?
- Does a valid license make the start runtime button active?
- Why does Advanced start while the Professional command stays disabled?
- Why does WinCC V13 Professional Runtime UPD1 demand the base runtime?
- How do you create the .MCX file the Professional runtime asks for?
- What should you recheck once the runtime is installed?
- Should you install SP1 to bring the command back?
- What does the complete fix look like on one workstation?
- Questions asked
The greyed-out start command in WinCC V13 Professional is an installation and target problem, not a license problem. The fact that "Start runtime on this PC" works for Advanced proves only that the Advanced runtime is installed on that PC; it says nothing about Runtime Professional. The fix is to confirm that WinCC Runtime Professional appears in the installed-program inventory, install it from the base media if it does not, let WinCC V13 Professional Runtime UPD1 apply on top of that base, and generate the .MCX runtime project by compiling and transferring — before any thought of SP1. Four layers have to stay separate here: license, installed component, update prerequisite and project target.
Why is start runtime greyed out in WinCC V13 Professional? #
The command is greyed out because the workstation does not offer Professional execution for what is installed and selected: either WinCC Runtime Professional is not installed, or the selected project target is not a Professional PC runtime.
The engineering installation configures screens, tags and alarms; the runtime installation executes them. A greyed-out command means the environment finds no executable matching the current selection. Each observation you can make points at exactly one layer:
- Professional command greyed out — no Professional execution is offered for the current installation and selection; check the project target first, then the installed runtime entry.
- Advanced command active — an Advanced execution path exists on this PC; it validates nothing about Professional.
- License display clean — entitlement recognition and software installation are independent conditions; read the license product name and the installed-program list separately.
- UPD1 asks for the base runtime — setup found no qualifying base product; verify the exact installed runtime name and version.
- Runtime asks for an .MCX location — it expects a generated runtime project, not an engineering file.
A greyed-out command is also a different fault from a runtime that starts and then reports a licensing or communication error, so record which of the two you actually have before changing anything.
Does a valid license make the start runtime button active? #
No. A license authorizes the product; it does not install its executable components, so a clean license display under a greyed-out command points at the component layer, not the entitlement layer.
Read the license product designation and confirm it names the Professional runtime rather than the engineering tool or the Advanced runtime. If the designation is right and the button is still grey, licensing is ruled out: the installation owns the fault, and no license reinstall changes that.
Why does Advanced start while the Professional command stays disabled? #
Because Runtime Advanced is installed on that PC and Runtime Professional is not: the active Advanced button proves Advanced execution only, and it says nothing about the Professional target a SCADA project needs.
WinCC Advanced and WinCC Professional are different runtime targets with separately installed components, and the project's configured runtime type must match the runtime product on the PC. If the station genuinely needs only an Advanced target, that is its own question, the one answered in Run a TIA Portal V14 HMI on WinCC Runtime Advanced; a V13 project configured for Professional does not get executed by the Advanced runtime. The working Advanced button is still useful evidence: it proves the start mechanism itself works and isolates the fault to the Professional component or the target selection. Select the HMI PC station in the project tree and read its configured runtime type before touching the installation.
Why does WinCC V13 Professional Runtime UPD1 demand the base runtime? #
UPD1 is an update package, and an update only modifies a qualifying base product: when setup cannot find an installed WinCC Runtime Professional base, it stops and asks for one, even with the WinCC Professional engineering product present.
When UPD1 refuses, exactly one of three things is true:
- the runtime base is not installed at all;
- the visible entry is the engineering product, which is a different product and never satisfies the prerequisite;
- a runtime base exists but its version does not match the package prerequisites.
The installed-program list decides which. An entry whose name does not carry the runtime designation is the engineering tool and will never qualify. The decisions follow directly: no runtime entry — install the base from its own media; wrong product family — install the runtime product; version mismatch — align the base with the package prerequisites and rerun UPD1.
How do you create the .MCX file the Professional runtime asks for? #
The .MCX file is the generated runtime project: produce it from the engineering project through the compile and transfer workflow, using "Download to file system" under the Online menu, never by renaming an engineering file.
Renaming changes only the file name; the executable data is created by the compile step, which is why the runtime rejects a renamed file. With the Professional target selected, run the transfer to write the runtime project to the folder runtime will load from, then start it with the "WinCC RT Start" application, which also carries the Autostart option for unattended start. In the runtime context, activation is indicated by a checkmark on the "File > Start RT" command, so that checkmark is your confirmation the project is actually running.
What should you recheck once the runtime is installed? #
Four things: the selected project target, the installed Runtime Professional entry with its version, the documented hardware baseline from the delivery release, and the PG/PC interface once runtime actually starts.
- Reopen the project and select the Professional target again, because the command's availability follows the active selection.
- Read the installed-program entry: WinCC Runtime Professional, with a version matching the project generation you are building.
- Compare the PC with the documented baseline. The delivery release for SIMATIC WinCC V13 SP1, support entry 104509915, recommends for 64-bit WinCC Professional an Intel Core i5-3320M at 3.3 GHz or comparable, 8 GB of RAM and a 1920x1080 display.
- Set the PG/PC interface so runtime can reach the PLC. This layer matters only after runtime starts: if it starts and the S7 connection fails, Fix WinCC Professional runtime not connecting to the S7-1500 covers that failure on its own.
Should you install SP1 to bring the command back? #
Not as the fix. SP1 is a maintenance package for a specified baseline; it cannot supply a base runtime that setup cannot find, so applying it while the prerequisite still fails changes nothing about the greyed-out command.
The order is fixed: base runtime first, UPD1 second, service pack last, each step verified before the next. Use the V13 SP1 delivery release as the compatibility reference for what the service pack requires on top of which baseline, and apply it as maintenance on a working installation, never as a repair for a missing component.
What does the complete fix look like on one workstation? #
On one V13 workstation the sequence is: inventory the installed programs, install the missing base runtime, apply UPD1, verify hardware against the delivery release, generate the .MCX, and start through WinCC RT Start.
Do this in a maintenance window with the engineering project backed up, because setup changes on a station operators are watching read as downtime. Then work the numbers:
- The installed-program inventory shows the WinCC Professional V13 engineering entry and no runtime entry: 2 required products - 1 found = 1 missing. That single missing entry explains both the grey command and the UPD1 refusal.
- Install WinCC V13 Professional Runtime from its base media; UPD1 now finds a base and applies.
- The PC carries 4 GB of RAM against the 8 GB the delivery release recommends for 64-bit: 8 GB - 4 GB = 4 GB short, so the memory is upgraded before the runtime is expected to load the project.
- Compile and run "Download to file system"; the .MCX lands on disk.
- Start with "WinCC RT Start", with Autostart configured if the station must come up unattended.
The command is active at the end because the selected target and the installed runtime finally match. If the next symptom is a dead PLC connection instead of a grey button, the fault has moved to the communication layer and the PG/PC setting owns it.
Questions asked
Why can I simulate the Professional project but not start the runtime?
Simulation runs inside the engineering environment and needs no separately installed runtime product. The start command on the PC requires WinCC Runtime Professional to be installed, which is exactly what the greyed-out button says is missing. Simulation works while start stays grey, and the fix is installing the runtime.
How do I stop the runtime from launching automatically at boot?
Open the WinCC RT Start application, disable the Autostart option and confirm with Apply. Autostart is the documented way to bring the runtime up unattended, so disabling it returns manual control; make the change deliberately, because an operator station whose HMI no longer starts on boot looks like a fault.
Does WinCC V13 Professional Runtime UPD1 contain the base runtime?
No. UPD1 modifies an installed base product and refuses to run when it cannot find one. The refusal is not a license error and not a package fault; it is setup telling you the runtime base is absent from the installed-program list. Install the base first, then run UPD1 against it.
Does the 32-bit WinCC Professional variant need the same PC as the 64-bit one?
No. The delivery release for SIMATIC WinCC V13 SP1 lists an Intel Core i3 at 1.6 GHz or better for the 32-bit variant, against the 64-bit recommendation of an Intel Core i5-3320M at 3.3 GHz or comparable with 8 GB of RAM and a 1920x1080 display. Size the PC against the variant you install.