IMD SolutionComputing LibraryShop main store

Troubleshooting

When a PLC runtime installer fails on the controller OS

Operating systems on the plant floor Published 7 min read

Short answer

The installer fails because the controller OS, Windows Embedded Compact 7 on the CX5120, is not on the runtime vendor's supported list; there is no WEC7 build of the product. No retry, timeout change or repackaged file fixes that. Move the controller to an operating system both the runtime package and the controller manufacturer document, and protect the application and license before you image.

On this page
  1. Why does a PLC runtime installer fail on Windows Embedded Compact 7?
  2. Why does a package that transferred fine still fail to install?
  3. Can you request or build a compatible deployment file?
  4. Which operating system should the controller move to?
  5. What do you save before you switch the controller OS?
  6. When should you replace the controller instead of reimaging it?
  7. Questions asked

A PLC runtime installer that will not deploy on the controller has almost always failed at the operating-system gate, not the network: the controller OS is not on the runtime vendor's supported list. That is exactly what happens when CODESYS Control RTE SL is aimed at a Beckhoff CX5120 running Windows Embedded Compact 7 (WEC7). There is no WEC7 build of the product, so no compatible deployment file exists to request, convert or retry, and no timeout, port or file renaming changes that. The fix is an operating system that both the runtime package and the controller manufacturer document. This article shows how to confirm the failed stage, choose the replacement OS, protect the application and license through the switch, and decide when replacing the controller beats reimaging it.

Why does a PLC runtime installer fail on Windows Embedded Compact 7? #

Windows Embedded Compact 7 is a different operating system from the desktop Windows this runtime documents: the product line targets industrial PCs running Windows and devices running Linux, so a WEC7 image gives the installer no environment it can execute in and setup stops at launch.

WEC7 and desktop Windows share a name and little else. WEC7 is a componentized real-time operating system that the controller manufacturer builds into a device image, with its own executable formats, system services and configuration stores. The installer and the runtime it lays down are written against the interfaces of the platforms on the requirement page; on any other platform the loader has nothing to bind to, and the failure message points at the platform rather than at a network fault.

The product name does not rescue the attempt either. A tag like 'for Beckhoff CX' says where the package is meant to be used, not which operating system it executes on; only the requirement list decides that. A processor match decides nothing too: WEC7 runs on x86 and Arm CPUs, the same families the desktop packages target, so the CX5120's architecture proves nothing about installer compatibility.

Why does a package that transferred fine still fail to install? #

Delivery and execution are separate gates: the package can arrive complete in controller storage and still be refused at launch, which is a failure at gate 3 of the four-gate deployment path rather than a transfer fault.

  1. Media and reachability — the engineering PC reaches the controller over the link, or the controller reads the removable medium.
  2. Transfer — the complete package sits in controller storage at the same size as the source.
  3. Operating-system execution — the controller OS launches the installer; a platform the package does not support fails here.
  4. Runtime startup and engineering communication — the runtime starts and answers the engineering tool; this stage is never reached in this failure.

On the CX5120 case the trace reads: gate 1 passed, gate 2 passed, gate 3 failed, gate 4 untouched. If you can list the file in the controller's storage, the network is exonerated and the deciding question becomes what the OS can execute. A longer timeout, a different port or a re-copied file cannot move the failure past gate 3, because nothing in the transfer path supplies the missing OS interfaces. Record the installer's exact message before changing anything: a launch refusal, an install that rolls back and a runtime that never starts are three different faults, and each is fixed at its own gate.

Can you request or build a compatible deployment file? #

No — the product line has no Windows Embedded Compact 7 build, so there is no file to request, and extraction or file-copy tricks cannot create one because the missing operating-system interfaces cannot be packed into a file.

The platform list behind the first section shows no WEC7 entry, so a request for a WEC7 package ends the same way as the install attempt: switch the operating system. The workarounds fail predictably. Renaming the file changes nothing the loader reads. Unpacking the installer container yields binaries built for a different OS family. Copying installed files from a working desktop machine brings the same binaries without the OS services they call. Compatibility shims are a desktop-Windows mechanism and do not exist on a WEC7 image. None of these attempts damages the controller, but none can succeed, and each spends downtime you will spend again on the reimage.

Which operating system should the controller move to? #

Pick the OS that clears two independent acceptance conditions: it is named in the runtime package's documented requirements, and the controller manufacturer documents an image, drivers and an installation method for it on your exact device.

Read the runtime requirement page first, because it selects the platform: the exact Windows edition or Linux variant the package names, not whichever OS is easiest to obtain. Then open the controller documentation and check that the manufacturer offers that OS as a documented image for the CX51xx family. The manufacturer's product documentation for this line lists Windows 10 IoT Enterprise as an image option beside WEC7, so the documented exit for the CX5120 is to apply that desktop-Windows image with the vendor's image-update procedure, then install the runtime package that names it. Match the edition to what the runtime package requires, because runtime packages specify Windows builds.

The two lists can fail to intersect. If no runtime-compatible image is documented for your device, or the controller cannot carry the OS the package needs, stop before ordering a license and select a different controller and runtime pair. The same product family includes a Linux SoftPLC build, but that path only opens when the controller manufacturer documents a Linux image and drivers for the device.

The edition, build and driver checks that decide an image swap on a plant PC are set out in the guide on choosing an operating system image for an industrial PC.

What do you save before you switch the controller OS? #

Treat the switch as a rebuild rather than an update: capture a restorable image, export the application and license state, and run the changeover with the machine stopped and outputs forced safe, because a failed image leaves the controller unable to boot the old system either.

  • Record the installed OS product and build from the controller's system information, plus the storage layout, before you overwrite anything.
  • Export the PLC application and its communication settings from the old runtime in a form the new runtime can import.
  • Inventory the attached I/O and anything that depends on the current environment, and note how each item behaves after the swap.
  • Back up the current image with the manufacturer's documented method, and prove the restore path before writing the new OS.
  • Confirm the runtime license transfer or reactivation procedure with the vendor before the downtime window opens.
  • After imaging, re-read the OS identity from the running system and compare it with the package requirements before launching the installer; the label on the installation media is not evidence of what booted.

Where the controller supports network boot, a PXE boot server for an industrial PC applies the image to several units from one server, which keeps a fleet of controllers on identical builds.

When should you replace the controller instead of reimaging it? #

Replace the controller when no supported image exists for it, when its CPU or storage can no longer carry the runtime, or when the reimage and revalidation downtime costs more than a spare unit; otherwise reimaging is the cheaper exit.

Approach What it changes Decision for the CX5120 on WEC7
Retry the installer Nothing on the platform Dead end: no supported package exists
Repackage or extract for WEC7 File form only Dead end: the missing OS interfaces stay missing
Apply the manufacturer's desktop-Windows image Platform The fix where your build is documented for it
Move the device to Linux Platform Only with a documented controller Linux image
Replace the controller Platform and hardware Fastest exit when no image path exists or the downtime rules the reimage out

If the CX5120 lands in that last row — no documented desktop-Windows image for your exact build, or downtime you cannot fit into the schedule — retire it and put the runtime on a fanless industrial mini PC that ships with a supported Windows or Linux image instead of an embedded OS. Where the goal is to move a Windows machine application off aging hardware rather than rebuild it in place, a P2V migration plan for an aging Windows machine controller gives the migration order and the fallback points.

Decision, stated plainly: a CX5120 running Windows Embedded Compact 7 cannot host this runtime, and no amount of transfer tuning changes that. Apply the manufacturer's documented desktop-Windows image for the CX51xx family, verify the running OS against the package requirements, then install and license the runtime — or replace the controller with hardware documented for a supported OS. The one thing you cannot do is install it on WEC7.

Questions asked

Does matching the CPU architecture make the installer work?

No. Windows Embedded Compact 7 runs on x86 and Arm processors, the same families the desktop runtime packages target, so an architecture match proves nothing. An installer and the runtime it installs depend on operating-system interfaces, executable formats and system services, and those differ between an embedded compact image and desktop Windows regardless of the processor.

Can the runtime run in a virtual machine on the controller instead?

Not on this image. A hypervisor needs a host operating system it documents as supported, and Windows Embedded Compact 7 is not one, and no supported guest OS exists for it either. Reimage the controller to a supported host first; then decide whether a virtual machine earns its overhead on a controller-class device, because a real-time runtime usually wants the host timing directly.

Is there a Linux build of this runtime family?

Yes. CODESYS Control Linux SL is an IEC 61131-3-compliant SoftPLC documented for PC-based industrial controllers running Linux, with soft real-time. Soft real-time means cycle timing tolerates some variance, so match it against the demands of the task before picking it over a desktop-Windows build, and use it only where the controller manufacturer documents a Linux image and drivers.

What happens to the runtime license after the OS switch?

Plan it before the downtime window. Many PLC runtime licenses bind to the controller image or to a hardware identity, so reimaging can require a license reactivation, and new hardware can require a rehost, both through the vendor's documented process. Export and record the license state while the old system still boots, and confirm the procedure with the vendor before overwriting storage.

Keep reading

  • Selection guide

    Choosing an operating system image for an industrial PC

    Order the industrial PC with the vendor image closest to your runtime: Windows IoT Enterprise LTSC where the vendor documents it for your model, the vendor's qualified Linux for a Linux stack, or the BSD image if your code builds on FreeBSD. Bring-your-own images are the fallback for monitoring-class loads. Qualify your binaries on the exact model and image; support and real-time behavior are model-specific.

    Operating systems on the plant floor

  • How-to

    Running TwinCAT XAR on a third-party industrial PC

    Do not clone a factory IPC image onto other hardware. Install a licensed Windows 10 IoT Enterprise LTSC edition, install the runtime fresh, and qualify the real-time Ethernet port, CPU priority and jitter on the actual machine. A successful boot proves nothing, and network hardware the runtime vendor did not sell you is a self-supported component.

    Operating systems on the plant floor

  • How-to

    Set up a PXE boot server for an industrial PC

    Put dnsmasq on an isolated 192.168.0.0/24 segment as its only DHCP server, serve pxelinux.0 and syslinux.efi from the TFTP root, open UDP 67, 69 and 4011, and set the industrial PC's firmware to boot from the network first. A Debian netinst menu arriving over TFTP proves the full DHCP-to-TFTP chain without touching the plant DHCP server.

    Operating systems on the plant floor