How-to
P2V migration plan for an aging Windows machine controller
Short answer
Converter 6.3 does not support Windows 7 as the computer it installs on, which is what the openssl.exe startup failure and the Error 29190 SSL-key message are reporting. Stop installing on the failing controller: back it up, run the converter from a supported management computer, and convert the Windows 7 source only with a release whose supported lists cover it — otherwise rebuild on a supported system. Current 6.6 and 9.0 lists start at Windows Server 2012 and Windows 10.
On this page
The installation is failing because vCenter Converter Standalone 6.3 does not support Windows 7 as the computer it installs on: the 0x000007b startup failure of openssl.exe and the Error 29190 SSL key-generation message report that mismatch, not a fault you can patch. Stop installing on the failing machine controller. Back it up first, then run the converter from a supported management computer and convert the Windows 7 source over the network — but only with a release whose supported lists include Windows 7, because the published 6.6 and 9.0 lists start at Windows Server 2012 and Windows 10. If your vendor account cannot produce a qualifying release, treat the rebuild on a supported system as the answer, not the fallback.
What the two installer errors mean #
The order of the messages is the diagnosis. openssl.exe fails to start — Windows reports 0x000007b — so the installer never receives the SSL key it asked that component to generate, and then reports Error 29190. The second message is a consequence, not an independent fault: no certificate, trust store or network problem is involved. Nothing downstream of installation has started either. No disk has been read and no virtual machine exists yet, so virtual disk formats, destination networking and guest boot settings cannot affect this failure.
The repair attempts each fail for the same reason: none of them changes which operating systems the release supports.
- Reinstalling runtime libraries changes the libraries on an unsupported host, not the release's supported platforms.
- Renaming or deleting openssl.exe removes the component the key-generation step calls; it cannot make that step succeed.
- The compatibility-settings prompt Windows offers after a failure is not a support statement and cannot supply what the release's requirements omit.
Keep the installer log and the Application event log entries from the failing attempts. The first failing operation is what a vendor support case will turn on, not the final summary message.
Match the release to both computers #
Two compatibility decisions hide in one P2V project, and they fail independently.
The first is the computer the converter installs on. Version 6.3 does not support Windows 7 as its install host — that is the verdict the 0x000007b and Error 29190 pair is delivering. Read 6.4's own requirements rather than assuming 6.3's verdict carries over, though two identical installation failures from two releases point at the host computer, not at either installer's files.
The second is the computer being converted. The supported-source tables published for 6.6 name Windows Server 2012 (64-bit), Windows Server 2012 R2 (64-bit) and Windows 10 (64-bit, Home editions excepted); the 9.0 release notes name the same server pair plus Windows 10 in both 32- and 64-bit. Windows 7 is on neither list.
The releases that did list that Windows generation are no longer offered for public download — 4.0.1's compatibility list starts at Windows NT SP6 and runs through Windows 2000 SP4 and Windows XP Professional (32- and 64-bit). If your support account can still produce a qualifying release, take it only through the vendor's own channel, and confirm from that release's own lists that Windows 7 qualifies both as install host and as source before installing anything.
The decision: a Windows 7 machine controller converts only with a release you can legitimately obtain that lists Windows 7 on both sides. If no such release exists for you, the supported path is the rebuild, not another installer attempt.
Worked example: copy window for a 180 GB volume over a 1 Gbit/s link #
Inputs, with their sources: used capacity 180 GB — an illustrative figure, because the real number is read from the volume's properties in Windows on the controller; link 1 Gbit/s — the rated speed of a dedicated switch port between the management computer and the source; planning rate 600 Mbit/s — my planning assumption of 60 percent of line rate, to be replaced after ten minutes by the rate the task actually reports.
The rule, in words: copy time equals used capacity times eight, divided by the achieved rate, because a byte is eight bits and the conversion has to move the volume's used data across that link.
Arithmetic:
- Payload: 180 GB × 8 = 1440 Gbit.
- Copy time at the planning rate: 1440 Gbit ÷ 0.6 Gbit/s = 2400 s = 40 min.
- Scaling rule per 100 GB used: 100 GB × 8 ÷ 0.6 Gbit/s = 1333 s ≈ 22 min.
- Bounds: at the full 1000 Mbit/s the copy takes 1440 s = 24 min; on a link shared with backup traffic and delivering 300 Mbit/s it takes 4800 s = 80 min.
Result: about 40 minutes of wire time for this volume, before agent deployment, the destination's own provisioning and the first-boot checks — which is why the maintenance window should be twice the estimate, 80 min here.
Decision: at a 600 Mbit/s planning rate, a two-hour production stop covers any source up to roughly 270 GB used — 270 GB × 8 ÷ 0.6 Gbit/s = 3600 s = 60 min of copy, doubled to 120 min. The 180 GB case fits with margin. What moves the number most is the achieved rate: halve it to 300 Mbit/s and every figure above doubles, so put the copy on a dedicated link or accept a maintenance night instead of a short stop.
The migration sequence #
- Back up before anything else. Copy application projects and parameter sets, licence or activation files, and the installers the application needs; if the controller still boots reliably, add a full disk image. Verify the backup opens on another computer. A conversion is a migration, not a backup — a failing source must survive a failed conversion attempt.
- Record the source precisely. Edition, service pack level and architecture, read from the system information on the controller. "Windows 7" alone is not enough to check a supported-source list.
- Choose the release by its lists. Both lists, per the compatibility section: the operating system the converter installs on, and the operating system being converted.
- Install the converter on the management computer, never on the controller. A remote conversion task deploys the release's own source-side agent to the Windows 7 machine over the network, so the failing installer never has to run on the box you are trying to save.
- Point the task at the source and size the destination. Supply an administrator account of the source, and give each converted volume a virtual disk at least as large as that volume's used capacity. Leave the converter's volume and disk defaults alone unless the control application's documentation requires a specific layout.
- Run the copy inside the worked window, at a production stop. Watch the achieved rate in the first ten minutes and recompute the finish time with the same rule; if the rate sits far below the planning assumption, extend the window or move the copy to a dedicated link before you commit.
- Boot the copy on an isolated network first. No route to the control network until the application starts, its services come up and its licence state is confirmed.
- Cut over deliberately. Keep the physical machine intact until the copy is accepted; retire it only at a production stop, with exactly one controller active.
Destination host and first boot #
The destination deserves the same care as the source. For a host that will carry SCADA and PLC engineering duty, the checklist in Proxmox for SCADA and PLC engineering virtual machines is the starting point, and the trade-offs between hypervisor options, including the host CPU sizing behind them, are set out in a hypervisor selection and host CPU sizing comparison. If the destination is a repurposed workstation rather than a rack server, a workstation-class virtualization build for a SCADA edge host shows what that looks like assembled and configured.
First boot the copy with no route to the control network, so it cannot collide with the physical machine's name or addresses. A PC-based control runtime also validates the platform it lands on; running TwinCAT XAR on a third-party industrial PC covers what to verify before a control runtime is trusted on a host it was not shipped with. Never bring the converted controller onto the live control network while the physical machine is still wired to the process: two active controllers on one process is a hazard, not a test.
When the P2V path is closed #
If no release you can legitimately obtain lists Windows 7 on both sides, stop spending maintenance stops on installer attempts. The dependable decision is a rebuild: restore the application and its backed-up projects on a supported operating system on current hardware, and revalidate the machine's behaviour before it runs production again. The image decisions that rebuild starts with are laid out in choosing an operating system image for an industrial PC. When the failing tower itself is what you are replacing, the category to look at is an industrial mini PC for a cabinet-mounted machine. A supported operating system on current hardware returns the controller to something you can patch, image and support; a Windows 7 image carried by releases that no longer list it never does.
Questions asked
Reinstalling runtime libraries did not fix it — what else could the 0x000007b failure be?
A startup failure of that kind can also come from damaged components or a wrong-architecture library, but on Windows 7 the release's support status is the deciding cause and no repair changes it. If you retry on a supported management computer, remove any half-installed copy through its uninstaller instead of deleting files.
Can I turn off SSL encryption to make the conversion copy faster?
The vendor documents a setting that turns the converter's traffic encryption off, followed by a service restart to apply it. It removes encryption overhead from the copy, but that copy carries a complete image of a machine controller — application data, projects and credentials — across the plant network. Keep the documented encryption in place for a controller migration; recover throughput with a dedicated link and the copy-window estimate instead.
Can the converted virtual machine keep its application licence?
Application licences are often tied to hardware, and a converted controller can fail activation on a virtual machine. Check the control application's licensing terms for virtualized machines before the cutover is planned, and record the licence transfer or reactivation procedure exactly as the vendor documents it. Do the transfer during the planned production stop, with the old unit powered down, so only one controller is ever licensed and running.
Does the converted virtual machine keep the source's network identity?
Yes — a conversion copies identity along with data. The virtual machine comes up with the source's computer name, its static IP settings and its domain or workgroup membership, which is why the first boot belongs on an isolated network. Bringing the copy up on the plant network can collide with the physical machine's addresses. Plan a rename and readdressing step before the copy joins any shared network, and change both before the cutover.