How-to
Running a USB License Dongle in VMware for WinCC
Short answer
Yes, a WinCC 7.x USB license dongle runs in a VMware guest. ESXi passes host-attached dongles to a virtual machine, so the real work is verifying three layers in order — guest USB enumeration, Automation License Manager recognition, WinCC license status — and proving the attachment survives guest restarts and reconnects before you trust it in production.
On this page
- Will a WinCC USB license dongle work inside a VMware virtual machine?
- What should I write down before touching the hypervisor?
- How do I attach the dongle to the guest in ESXi?
- Host passthrough or a network USB hub — which should I use?
- Which layer is failing when WinCC reports a missing license?
- What restart sequence proves the dongle survives?
- When should I keep the dongle on physical hardware instead?
- Questions asked
Yes — a WinCC 7.x USB license dongle runs inside a VMware guest once the hypervisor hands the device to that guest and the licensing stack in the guest recognizes it. VMware has passed host-attached USB devices to virtual machines — the security-dongle class included — since long before vSphere 7.0, so the dongle itself is rarely the part that fails. What fails is one of three layers: the USB assignment, the license recognition, or the attachment's survival across restarts. The sequence below gives the attach steps, the expected reading at each layer, and the acceptance test to run before a licensed WinCC server carries production.
Will a WinCC USB license dongle work inside a VMware virtual machine? #
Yes — ESXi and Workstation both hand host-attached USB devices to a guest, and VMware's vSphere 7.0 documentation names security dongles as a supported passthrough class, so the hypervisor is rarely the part that fails. What has to line up is three layers inside one guest.
The guest must enumerate the dongle as a USB device, the Siemens licensing software in the guest must recognize the license on it, and WinCC must read that license at startup. A documented WinCC V7.4 case shows why these stay separate: the dongle was plugged in, and WinCC Explorer still raised a missing-USB-license-key message, dropped into demo mode and closed the project when the demo time expired. The USB side was fine; the license layer was not.
Compatibility is decided per release, not per family. Siemens handles virtualization of its PCS 7 environments on a project-specific basis, so carry that expectation to WinCC: pin the exact release, dongle and hypervisor combination, and get that combination confirmed rather than the family label. The discipline is the same one behind which HMI software runs on which panel hardware: per release, in writing.
What should I write down before touching the hypervisor? #
Five identifiers, recorded before anything else: the exact WinCC release, the dongle's printed part number, the Automation License Manager version, the VMware product and build, and the guest OS build — a test result means nothing until that page exists.
Every support answer and compatibility statement is written against a release, not a family, and "WinCC 7.4" and its service packs are different strings to search and different support cases. The dongle part number is what tells you — and Siemens support — whether you hold a dongle-type license or a transferable key. The Automation License Manager version carries the dongle driver. And the VMware product decides the attach mechanism: ESXi and Workstation are not interchangeable, and instructions for one describe nothing about the other. Date the record; every comparison you make later hangs off it.
How do I attach the dongle to the guest in ESXi? #
Plug the dongle into the host, open the virtual machine's Edit Settings page, add a USB device, select the dongle from the host's device list, and save — that is the whole passthrough configuration on vSphere 7.
- Plug the dongle into a USB port on the ESXi host itself.
- Open the virtual machine's Edit Settings page.
- Add a USB device and select the dongle from the host's device list.
- Save the setting.
- Set the device to connect automatically at power-on.
- Boot the guest and confirm the dongle appears in its device list with no error.
- Open Automation License Manager in the guest and confirm the license is shown.
- Start WinCC and confirm it opens with no license message.
On Workstation, the same result comes from attaching the host device to the running guest through the USB device control, one guest at a time, then running steps 6 through 8 unchanged. Two rules hold on both platforms: while the dongle is attached to a guest, the host cannot use it; and Siemens documentation for dongle-licensed WinCC runtime (TIA) requires the dongle to remain plugged in at all times, so treat continuous presence as the design rule here too — pick a port, label it, and leave the dongle in it.
Host passthrough or a network USB hub — which should I use? #
Use host passthrough whenever the dongle can physically sit at the ESXi host; use a USB-over-TCP hub only for blade or remote hosts you cannot reach, because the hub adds a network path and a second driver to every license check.
A network USB hub presents physical ports over TCP/IP; the guest runs a client driver that maps a virtual port to the hub, and the dongle plugs into the hub instead of the host. The failure signature is distinctive: the dongle stays powered and lit while the guest loses the license, because a network interruption or a restarted service broke the path, not the device.
Decide by reach and sharing. One host you can touch: passthrough, always. A blade chassis or a locked computer room: the hub, with the reconnect test below treated as mandatory. One dongle that must serve several servers: only the hub can do it, and only within what the license terms permit.
Which layer is failing when WinCC reports a missing license? #
Test the layers in fixed order — guest USB enumeration, Automation License Manager recognition, WinCC license status — and stop at the first wrong reading, because nothing above a failed layer can pass.
| What you observe | Failing layer | Expected reading when healthy |
|---|---|---|
| Dongle absent from the guest's device list | USB assignment | Device listed with no error after attach |
| Device listed, Automation License Manager shows no license | License recognition | License entry visible in the manager |
| Manager shows the license, WinCC still complains | Application status | WinCC starts with no license message |
| Works until a restart or reconnect | Attachment persistence | Dongle reattaches on its own at power-on |
If the license layer never recognizes the dongle, the fix is a working dongle and a correct license in the manager — software emulation of the dongle violates the license terms and forfeits vendor support, so that door stays closed.
What restart sequence proves the dongle survives? #
Four steps: a guest reboot, a full guest power-off and power-on, an unplug-replug of the dongle at the host, and a 24-hour run — licensing must stay recognized through all four before the VM carries production.
- Reboot the guest. Expected reading: the dongle reappears in the device list, the manager shows the license, WinCC starts clean.
- Power the guest fully off and back on. Expected reading: the USB device connects by itself at power-on and all three readings hold.
- Unplug the dongle at the host and replug it. Expected reading: the guest reclaims the device with no manual attach and the readings return.
- Run the guest for 24 hours with WinCC active. Expected reading: no license messages, no demo-mode fallback, runtime still up.
The 24 hours is a commissioning soak, not a vendor limit; it is sized to cross the daily backup, update and antivirus windows that disturb USB paths. If step 3 fails, re-check the automatic power-on connection from the attach sequence before you suspect the dongle.
When should I keep the dongle on physical hardware instead? #
Two cases: the license layer never recognizes the dongle in the guest after the sequence above, or Siemens will not release your exact WinCC release for virtualization — in both, run the licensed WinCC on physical hardware and virtualize everything else.
The fallback architecture is straightforward: keep the licensed WinCC server physical and put industrial panel PCs at the machines as WinCC clients, which takes the operator stations off the virtualization question entirely. If the dongle can sit at the host and all four restart steps pass, go virtual with passthrough — the old advice that dongles and virtual machines do not mix described missing power-on attachment, not a hypervisor limit.
Questions asked
Does a dongle working with other software prove WinCC will work too?
No. Other dongle-licensed automation and GIS packages passing through an ESXi host prove the USB layer of that host, not the Siemens licensing layer or your WinCC release. Only the three checks inside your own guest — enumeration, Automation License Manager recognition, WinCC status — decide it.
What happens to a running WinCC project if the dongle detaches?
WinCC reports a missing license, switches to demo mode and closes the project when the demo time expires. That exact sequence is documented in a WinCC V7.4 case where the dongle was physically present but not recognized, so expect the runtime to stop. The unplug-replug test in the acceptance sequence guards against precisely this.
Can two virtual machines share one dongle?
Not through host passthrough: the device attaches to one guest at a time. Serving several servers from one physical dongle takes a network USB hub, with its added network dependency, and only within what the license terms actually permit. Confirm what your license allows before sharing anything.
Do I need the dongle only for engineering, or at runtime as well?
For a dongle-type license, at runtime as well: Siemens documentation for dongle-licensed WinCC runtime requires the dongle to remain plugged in continuously, so a production VM needs the same attachment as an engineering one. Licenses issued as transferable keys are different — Automation License Manager moves them between computers, and no dongle is involved.
Is ESXi or Workstation the better host for this?
Use ESXi when the VM is a server others depend on: the USB device belongs to the virtual machine's configuration and reconnects at power-on. Use Workstation when the guest is an engineering workstation on a PC you control; attach the dongle to the running guest and run the same three checks.