Creating WinCC Runtime Desktop Shortcuts: Complete Guide

Siemens WinCC Runtime projects are typically launched through the WinCC Explorer or, on TIA Portal, through WinCCRTStart.exe. Operators and commissioning engineers often need a single-click method to start a runtime project without opening the configuration environment. This guide consolidates the supported methods: direct desktop shortcut, batch file wrapper, autostart configuration, and modern MSIX-packaged deployment.

Overview of WinCC Runtime Launch Methods

WinCC Runtime can be started in four operator-facing ways:

Prerequisites

1. Installed WinCC Runtime on the target PC. Verify via Start → Control Panel → Programs and Features; the entries to look for are SIMATIC WinCC Runtime (V7) or SIMATIC WinCC Runtime Professional (TIA Portal).
2. Compiled project files. WinCC V7: *.MCP plus *.LDF/*.MDF. WinCC Professional (TIA): *.simatic runtime package, usually located in the project path under \System\<PCName>\.
3. Windows user with rights to write to C:\ProgramData\Microsoft\Windows\Start Menu\Programs and the desktop.
4. WinCC project activated on the WinCC server or on the local PC if running single-station. Activation is a separate step from starting the runtime.

WinCC Runtime Executables and Command-Line Parameters

The executable that actually brings the runtime pictures to the screen is product-specific. Use the table below to pick the correct binary when authoring a shortcut.

For WinCC V7, you can activate a project from the command line using CCStartStop.exe together with the /ACTIVATION argument, or use the project name with WinCCExplorer.exe as a parameter:

For WinCC Professional (TIA Portal), the runtime project path is required:

Method 1: Direct Desktop Shortcut

This is the fastest deployment for a single panel PC or engineering workstation. No script wrapper is required.

1. Right-click on the desktop and choose New → Shortcut.
2. In Type the location of the item, enter the full path to the runtime executable plus the project path (see command-line examples above).
3. Click Next, give the shortcut a meaningful name such as Start Line 1 Runtime, and click Finish.
4. Right-click the new shortcut → Properties. Under Shortcut tab, set Run to Minimized if you do not want the console window from the launcher.
5. (Optional) Click Change Icon and browse to a WinCC-supplied icon, e.g. C:\Program Files (x86)\Siemens\Automation\WinCC\WinCC\bin\S7WCCX.ico.
6. Click Advanced… and tick Run as administrator if your WinCC project uses service-mode tags or OPC connections that require elevated rights.

Method 2: Batch File Wrapper

A batch file is preferred when you need to perform pre-checks (license dongle, network share availability, project file existence) before launching runtime, or when you want to log the start event.

Step-by-step

1. Open Notepad (or any plain-text editor).
2. Paste the following template and adapt the paths:

@echo off
REM ============================================================
REM WinCC Runtime launcher for MyPlant project
REM ============================================================
set PROJECT="C:\Projects\MyPlant\MyPlant.MCP"
set WINCC="C:\Program Files (x86)\Siemens\Automation\WinCC\WinCC\bin\WinCCExplorer.exe"
set LOGFILE="C:\WinCCLogs\startup_%date:~-4%%date:~3,2%%date:~0,2%.log"

echo [%date% %time%] Launching WinCC Runtime >> %LOGFILE%
if not exist %PROJECT% (
    echo [%date% %time%] ERROR: project not found at %PROJECT% >> %LOGFILE%
    msg * "WinCC project not found. Contact maintenance."
    exit /b 1
)

start "" /WAIT %WINCC% /ACTIVATION=%PROJECT%
echo [%date% %time%] Runtime exited with code %ERRORLEVEL% >> %LOGFILE%
exit /b %ERRORLEVEL%

3. Save the file as StartMyPlant.bat in a fixed directory, e.g. C:\WinCCScripts\.
4. Right-click the .bat file → Send to → Desktop (create shortcut).
5. Edit the shortcut properties: set Target to C:\WinCCScripts\StartMyPlant.bat, and Start in to C:\WinCCScripts\.
6. Under Shortcut → Advanced, tick Run as administrator if required.

Method 3: Autostart on Windows Boot

For operator panels that should boot directly into runtime, use the Siemens-supplied Autostart tool or a registry entry.

Option A: Siemens Autostart tool

1. Open Start → SIMATIC → WinCC → Tools → Autostart.
2. Click Add and select the WinCC project (.MCP for V7, or browse to the TIA runtime folder for Professional).
3. Choose Start → Activate as the autostart action.
4. Confirm and close. The tool writes the necessary entries to the Windows Run keys and to the WinCC project list.

Option B: Direct registry entry

Equivalent registry entries for the local machine autostart:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"WinCCMyPlant"="\"C:\\Program Files (x86)\\Siemens\\Automation\\WinCC\\WinCC\\bin\\WinCCExplorer.exe\" /ACTIVATION=\"C:\\Projects\\MyPlant\\MyPlant.MCP\""

For a per-user autostart, use HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run instead.

Method 4: MSIX Package with PSF (Modern Image Rollout)

For modern Windows 10/11 image deployments where the panel image is provisioned through an MSIX package, the Package Support Framework (PSF) lets you wrap the WinCC executable inside a script and surface a Windows Start Menu shortcut to it. Microsoft's official guide is at Create an application shortcut by running a script using Package Support Framework.

1. Install the MSIX Packaging Tool on a technician PC.
2. Capture the WinCC Runtime installation into an MSIX package.
3. Add the PSF launcher (PsfLauncher.exe) and a config.json describing the script entry point:

{
  "applications": [
    {
      "id": "WinCCRT",
      "executable": "WinCCRTStart.exe",
      "arguments": "C:\\Program Files\\Siemens\\Automation\\WinCC RT\\Projects\\MyHMI\\System\\HMI_RT_1\\HMI_RT_1.fwc",
      "workingDirectory": "C:\\Program Files\\Siemens\\Automation\\WinCC RT\\"
    }
  ],
  "startScript": {
    "scriptPath": "StartWinCC.ps1",
    "runInVirtualEnvironment": true
  }
}

4. Use the assets folder inside the package to drop StartWinCC.ps1 that pre-validates the project file before invoking the runtime.
5. Define a Start Menu entry in AppxManifest.xml pointing to PsfLauncher.exe with the appropriate uap:Extension declaration for a desktop shortcut.
6. Sign the MSIX and deploy via Add-AppxPackage or via MDM (Intune / Workspace ONE).

Verification

After any of the four methods, verify the runtime actually loaded the correct project:

1. Double-click the shortcut (or reboot the panel if autostart).
2. Open WinCC Explorer → Computer → Properties; the Project field must show the expected .MCP name and path.
3. Check that the WinCC alarm line shows the configured start picture and that tag values update.
4. Open Windows Task Manager → Details and confirm WinCCExplorer.exe (V7) or WinCCRTStart.exe (TIA) is present with the expected user context.
5. Inspect the log file from the batch wrapper (Method 2) for the Runtime exited with code line; a clean exit code is 0.
6. For MSIX deployment, run Get-AppxPackage -Name "*WinCC*" in PowerShell to confirm the package is installed and registered.

Troubleshooting Matrix

Security and Operational Considerations

• License handling. WinCC V7 uses License Key USB dongles or soft containers. A shortcut that launches runtime on a PC without a valid license will start in demo mode with a periodic nag screen. Verify with Automation License Manager before shipping the image.
• Service mode vs. interactive mode. TIA-based runtime can run as a Windows service (Siemens S7Tracesvc, SIMATIC HMI RT). A desktop shortcut always starts the interactive variant; do not mix it with the service variant or duplicate tag connections will appear.
• Multi-user panels. If the panel uses Windows fast user switching, place the autostart entry under HKCU so it fires once per user, or under HKLM if only one operator account is ever used.
• UAC. On Windows 10/11 IoT, UAC is on by default. A shortcut to a script that writes to Program Files or ProgramData requires elevation; configure it through the manifest, not by users right-clicking Run as administrator.

Frequently Asked Questions