How-to
Install the HMI base software before the service pack
Short answer
A Vijeo Designer service pack only patches an existing installation, so it fails on a clean PC by design. Install the licensed Vijeo Designer 6.2 base from your software pack, launch it once to confirm it runs, then apply SP10, and get lost base media replaced only through the vendor or the distributor who supplied the licence.
On this page
- Why a service pack fails on a clean PC
- Check the PC before you run any installer
- Installing the base, then the service pack
- Worked example: getting a clean PC to Vijeo Designer 6.2 SP10 in two setup runs
- When the base media is lost
- Mistakes that break this sequence
- Final checks before you program the HMI
- Questions asked
The installer that fails on a clean engineering PC is almost never the product itself — it is the service pack. A Vijeo Designer service pack, SP10 for version 6.2 included, patches an installation that already exists: it replaces files and registry entries the base setup created, so on a PC with no Vijeo Designer present there is nothing to patch and the setup aborts. The fix is sequence, not software repair. Install the licensed Vijeo Designer 6.2 base from the software pack supplied with your licence, start it once to confirm it runs, then apply the service pack; base plus SP10 is the whole job. If the base software pack is lost, get a replacement through the vendor's customer support or the distributor who supplied the licence, never a third-party download.
Why a service pack fails on a clean PC #
A Vijeo Designer service pack is an update layer, not the product. It carries only the files and registry entries that changed since the base release, and its setup searches for the installed product to patch. With no Vijeo Designer entry in Windows Programs and Features, the pack has nothing to patch and the install fails in a way that reads like a software fault but is a sequencing error. No registry edit or file workaround fixes this, because the missing component is the base installation itself. The same logic rules out using the service pack as a recovery: it cannot replace a lost software pack, because it never contained the base files.
Check the PC before you run any installer #
Gate the install on these readings:
- Open Programs and Features (the Apps list on newer Windows) and look for a Vijeo Designer entry. No entry means the base product is absent and any service pack will fail. An entry at 6.2 means SP10 applies directly on top of it. An entry at a different major version means the 6.2 service pack is the wrong patch for that installation.
- Identify the file you originally ran. A service pack is a separate, smaller download from the full software pack, so compare the file name and its source folder against the contents of the licensed software pack.
- Confirm you have administrator rights on the PC, that no earlier installer window is still open, and that no pending-restart prompt is showing — reboot first if one is.
Installing the base, then the service pack #
Run this on the engineering station. If the only machine available is a runtime PC that also controls a line, do the work while the line is stopped, because an install and its forced reboot can drop operator control.
- Run the base setup from the licensed Vijeo Designer 6.2 software pack as administrator, and confirm the setup names the full product at 6.2 rather than an update before you continue. Reboot if the wizard asks.
- Reopen Programs and Features and confirm the Vijeo Designer entry now exists at 6.2.
- Start Vijeo Designer once and let it reach the point where you can open or create a project, then close it. This proves the base installation is healthy before you patch it.
- Pick the service pack level. SP10 is the latest the vendor publishes for 6.2, and the vendor documents each 6.2 service pack as cumulative, so no earlier pack is needed first — unless your site or customer standardises on an earlier level, or you are maintaining an existing project, in which case match the level the project was last programmed at so the project file and target firmware agree.
- Run that service pack setup as administrator and reboot if prompted.
- Confirm the entry in Programs and Features, or its installed-updates view, now reflects the applied service pack.
Worked example: getting a clean PC to Vijeo Designer 6.2 SP10 in two setup runs #
Inputs. An engineering PC whose Programs and Features list shows no Vijeo Designer entry — the clean-PC condition that produces this failure. The licensed Vijeo Designer 6.2 software pack supplied with the licence. The SP10 installer from the vendor's own download page, where the vendor states two conditions: Vijeo Designer 6.2 must already be installed, and each 6.2 service pack is cumulative, so SP1, SP2, SP3, SP4, SP5, SP6, SP7, SP8 and SP9 are not needed first.
Rule. A service pack patches only what the base installation created, so the base must exist first. Cumulative means the SP10 package already contains SP1 through SP9, so one service-pack run brings any 6.2 base to the SP10 level.
Arithmetic. If the packs were not cumulative, the step-by-step path would be 1 base run + 10 service-pack runs (SP1, SP2, SP3, SP4, SP5, SP6, SP7, SP8, SP9, SP10) = 11 setup runs. The cumulative path is 1 base run + 1 SP10 run = 2 setup runs. Runs avoided: 11 − 2 = 9.
Result. Two setup runs, with one launch test between them, bring a clean PC to v6.2 SP10.
Decision. No Vijeo Designer entry in Programs and Features: start with the base software pack, never the service pack. An entry at 6.2 at any earlier service-pack level: the single SP10 run brings it current. An entry at another major version: this service pack is not for that installation.
When the base media is lost #
A service pack carries no base files, so it cannot substitute for the software pack. Contact the vendor's customer support, or the distributor who supplied the licence, and request a replacement copy or download link for Vijeo Designer 6.2, with the licence documentation to hand. Wait for that media before you install: installers from third-party sites can be mismatched or tampered with, and sourcing outside the vendor and its authorised distributors puts the licence terms at risk. If the PC previously held an installation that was removed or corrupted, the Programs and Features check shows whether a leftover entry remains, and a stale entry at the wrong version needs a clean uninstall through Windows before the base install is repeated.
Mistakes that break this sequence #
| Mistake | What happens | Correction |
|---|---|---|
| Running the service pack on a clean PC | Setup fails; nothing to patch | Install the 6.2 base first |
| Applying a 6.2 service pack over a different major version | Setup rejects it or the installation runs unstable | Use the pack that matches the installed base version |
| Patching without the launch test | A base fault appears later and gets blamed on the service pack | Launch the base once, then patch |
| Running setup without administrator rights | Partial install with missing components | Run as administrator and reboot when prompted |
Final checks before you program the HMI #
- Programs and Features lists Vijeo Designer at 6.2, with the applied service pack reflected in the version or the installed-updates view.
- Vijeo Designer starts with no installer prompt and no missing-component message.
- A new blank project selects your panel's target model, saves, and reopens — a project that survives that round trip confirms the installation is ready for programming.
If the panel's model does not appear in the target list, that is a separate fault from the install order, and when an HMI model is missing from the programming software covers it. With the software level confirmed, the target family itself may still need enabling before a project builds: activating the XBTOT target family in Vijeo Designer 6.2 walks through that step.
Questions asked
What do I do if the base Vijeo Designer setup itself fails?
Reboot first to clear any pending file replacements, close every open installer window, then run the setup again as administrator. If it keeps failing on that PC, try the same software pack on another engineering station: if it installs cleanly there, the media or the download that produced your copy is the suspect, not the sequence. Report a failing original disc or archive to the vendor when you request any replacement.
Can I skip the launch test and run the service pack straight after the base install?
Yes, and the service pack will normally install fine. The launch test is not for the installer, it is for you: it proves the base installation is healthy before the patch goes on top, so a fault that appears later is not misread as a service pack problem. The test takes under a minute, so run it even on a handover day.
How do I keep several engineering PCs at the same service pack level?
Standardise on one level per project, SP10 unless the site requires an earlier one, and record that level with the project files. A project saved at a higher service pack level can open differently or refuse to open on a station still at a lower level, which reads like a project fault but is a version mismatch between engineering stations.
Is the Windows service pack the same thing as the Vijeo Designer service pack?
No. Windows has its own service packs, and some vendors require a specific Windows level before their software installs. NI, for example, documents that its software released after July 1, 2016 needs Windows 7 Service Pack 1 or later. That is a prerequisite on the operating system; the Vijeo Designer service pack updates the Vijeo Designer installation itself. Check both levels when a new install fails.