IMDTouchKnowledge BaseShop main store

Troubleshooting

Create a desktop shortcut for WinCC Runtime Advanced

HMI and touchscreens Published 5 min read

Short answer

The .fwx prompt means the shortcut starts the runtime executable with no project attached. Start runtime once from the engineering software so the HMI subfolder receives the generated runtime file and a working runtime shortcut, then copy that shortcut's Target into your desktop shortcut. Verify the same runtime release and license exist on any other computer before copying it there.

On this page
  1. Why does the shortcut ask for a .fwx file you cannot find?
  2. Where does the .fwx file appear in the project?
  3. How do you copy the working launch into a desktop shortcut?
  4. Should you use a desktop shortcut or autostart?
  5. Will the shortcut work on a different computer?
  6. How do you confirm the shortcut opens the right project?
  7. Questions asked

A desktop shortcut that demands a .fwx file is not a broken shortcut, and the project is not missing anything: the icon you started points at the runtime executable, and .fwx is the generated runtime file that executable loads. Generate that file by starting runtime once from inside the engineering software, then copy the Target line from the runtime shortcut that appears in the project's HMI subfolder into your own desktop shortcut. The sections below follow the order you meet the problem: why the prompt appears, where the file lands, how to copy the working launch, when autostart fits better, what a second computer needs, and how to verify the result.

Why does the shortcut ask for a .fwx file you cannot find? #

Because the icon you started launches the runtime executable on its own, and the .fwx file it demands is generated output that only exists after the HMI target has produced it — so generate first, shortcut second. The dialog is the executable asking for its input, not Windows reporting a lost file.

The engineering project and the runtime file are different objects, the same split behind why the compiled HMI project view is not for editing: the project holds editable configuration, the .fwx holds the compiled form the runtime application consumes. Searching the project's source files for something to feed the dialog finds nothing, because the artifact has not been generated where you are looking.

One check belongs here: read the executable name in the dialog's title or the shortcut's properties and confirm it belongs to the installed Runtime Advanced. WinCC variants and releases arrange their launchers differently, and a launcher picked by icon alone may accept a different file type altogether.

Where does the .fwx file appear in the project? #

In the HMI subfolder of the project directory, and only after runtime has been triggered at least once from inside the engineering software; the subfolder also receives a runtime shortcut whose Target line already points at the executable and the project. One successful trigger creates it — repeated starts add nothing.

Work in this order:

  1. Save the project and compile the intended HMI target; generation must finish with no unresolved errors, because a failed generation leaves nothing for a shortcut to point at.
  2. Start that same target from the engineering software and confirm the intended screens open.
  3. Open the HMI subfolder inside the project directory and confirm the two generated items are there.

If the compile reports errors, clear them first. If the compile is clean and the runtime file still never appears, that is a separate generation failure with its own workaround for an fwx runtime file that is not generated.

How do you copy the working launch into a desktop shortcut? #

Copy it: open the properties of the runtime shortcut the engineering tool generated, read its Target and Start-in values, and put those same values into a new desktop shortcut — that is the whole procedure. Do not type the reference from memory and do not browse for the file again.

  1. Right-click the runtime shortcut in the HMI subfolder and open Properties.
  2. Copy the Target field exactly: the full path of the runtime executable, then the project reference and any options after it.
  3. Copy the Start-in value as well, because the executable expects to start from its own folder.
  4. Create the desktop shortcut, paste both values unchanged, and name it after the intended HMI target.

As a pattern for what a Target holds, the documented desktop route for classic WinCC 7.4 is a shortcut to the executable at "C:\Program Files (x86)\Siemens\WinCC\bin\PdlRt.exe"; Runtime Advanced uses the same shape — executable path plus project reference — with the exact strings read from the generated shortcut. Options added to a Target go after the executable path, which is standard Windows shortcut behavior, not a WinCC feature.

The test that proves it: double-click the new shortcut and the intended screens open with no file dialog, the same result the engineering-launched start gives.

Should you use a desktop shortcut or autostart? #

Decide by who launches it: an operator double-click needs the desktop shortcut, an unattended boot needs the autostart configuration in the WinCC tray icon — and you configure exactly one of them for a given project. Two methods on one project launch it twice, which is a fault, not redundancy.

The WinCC icon in the Windows notification area carries the autostart configuration: open it, select the project, and the runtime comes up at every boot. After setting it, verify under Start > Programs > Startup that the runtime shortcut actually sits in the startup folder — the tray icon being present does not by itself prove the project is configured.

Will the shortcut work on a different computer? #

No — a shortcut is a reference, not a deployment; the second computer needs the same runtime release installed and licensed, and the generated runtime present locally, before a copy of the shortcut can work there. A shortcut stores paths, not software, and every path it stores must exist on the machine it runs from.

Install and license the runtime on the destination through Siemens or its authorized distribution channels, deploy the generated runtime there, and build the shortcut from the destination's own paths. Match the runtime release to the project's configured target — the checks are the ones shown for how to run a TIA Portal V14 HMI on WinCC Runtime Advanced. When that destination is the operator station at the machine itself, industrial panel PCs are the hardware class that hosts a PC runtime like this one.

How do you confirm the shortcut opens the right project? #

Run it once and read two things: the screens that open — they must be the intended target's — and the modification time of the .fwx file, which must match your last generation. Both readings come from one double-click.

  • No file-selection dialog appears; the runtime goes straight to the screens.
  • The .fwx modification time equals the time of your last generation, proving the shortcut points at fresh output rather than a stale file from an earlier edit.
  • If the project holds several HMI targets, confirm the shortcut was copied from the intended target's subfolder, because each target generates its own runtime file.

Both checks passing, the desktop launch is as dependable as the engineering-launched one; a failure at either reading points back to the launcher identity or the generation step.

Questions asked

Can you rename another project file to .fwx so the launcher accepts it?

No. Renaming changes the file's name, not its contents; the runtime executable reads a generated structure, so a renamed source file opens nothing. Produce the real file by compiling and starting the intended HMI target from the engineering software, then let the generated runtime shortcut show you the exact reference the executable expects.

Does the runtime computer need the engineering software installed?

No. Running a deployed project needs the runtime installation, the license that covers it, and the generated runtime files present on that machine. The engineering software is needed there only to edit the project or to regenerate the runtime locally; execution alone does not require it.

What is CCStartStop.exe used for?

It is a documented command-prompt tool for basic start and stop actions on WinCC runtime, configured with the supplementary parameters /domain, /user and /password. Use it when the launch has to be scripted instead of triggered by a double-click or the autostart configuration; it does not replace the runtime installation or its license.

Is a desktop shortcut enough to bring the HMI back after a power cut?

No. A desktop shortcut waits for an operator and depends on a user session being active. For an unattended machine, use the autostart configuration in the WinCC tray icon, confirm under Start > Programs > Startup that the runtime shortcut sits in the startup folder, and check that the machine logs into the session that trigger needs.

Keep reading

  • Selection guide

    Where WinCC Unified Runtime Can Run and Remote HMI Options

    The Unified runtime executes only on a PC, a Panel IPC, a Unified Comfort Panel or the MD-34 tablet; a browser or Sm@rtServer VNC client displays it and never replaces the host. With no PC in the cabinet, a Unified Comfort Panel is the host and the tablet browser is the client. If a safety function must travel with the operator, no Unified mobile panel exists and the design stays Comfort-based.

    HMI and touchscreens

  • Troubleshooting

    Cleaning EasyBuilder Pro AppData CloudHMI Files Safely

    Treat the Weintek CloudHMI xob tree under AppData\Roaming as application-managed data, not confirmed temporary cache, because no vendor documentation marks it disposable. Copy the whole tree to storage outside the VM, verify the copy, then remove the guest contents as a controlled test after closing EasyBuilder Pro. Deleting the roughly 1 GB frees guest space only; the host virtual disk shrinks after the hypervisor's documented space reclamation runs.

    HMI and touchscreens

  • Selection guide

    How to Prove a PC-Based HMI Before Replacing Panel Terminals

    Use an isolated bench controller to compare candidate PC-based HMI runtimes. Test the read path, one write to a spare test tag, touch response, communication loss and automatic recovery. Check the deployed license on the target PC.

    HMI and touchscreens