Troubleshooting
When an HMI project fails to open: recovery and backup
Short answer
A Vijeo Designer project that no longer opens is recovered from the editor's local project storage on the PC, not from the panel. Save never creates a portable backup: close the project in the manager, export it and keep that export as a zip after every working session, then prove the zip by importing it into a clean editor and building.
On this page
- Why won't my HMI project open after I saved it?
- Where does Vijeo Designer store projects on the PC?
- How do I recover a Vijeo Designer project that will not open?
- Why isn't saving enough of a backup?
- How do I export a Vijeo Designer project as a zip backup?
- Can I pull the program back off the panel when the PC copy is gone?
- How do I prove a zip backup is good before I need it?
- Questions asked
An HMI project that fails to open is recovered from the editor's local project storage on the PC, because the panel holds only the downloaded runtime and a Save never created an independent copy of anything. Preserve the files in the editor's managed storage folder, then open a preserved copy or your most recent export. After that, make the loss impossible to repeat: at the end of every working session, close the project in the manager, export it, and keep that export as a zip archive stored outside the engineering PC. The sections below walk the recovery in order, show where Vijeo Designer actually keeps projects, explain why Save alone stranded you, give the export routine, and set out the drill that proves a backup before you ever need it.
Why won't my HMI project open after I saved it? #
Because pressing Save only writes your work into the editor's own managed folder on the PC — it never creates a portable backup — so when that folder or its files are damaged, moved or half-copied, the project fails to open and the panel cannot hand you an editable copy.
Two artifacts are in play, and only one of them is on your side of the cable. The panel holds the runtime application that was downloaded to it; the PC holds the engineering project the editor needs in order to open, edit and rebuild the screens. A project that will not open is a fault in that PC-side artifact — its folder, its files, its version match or its access rights — and nothing you re-save during a working day changes what the panel holds.
The first move is restraint. Close the editor without saving, and stop clicking Open on the broken project: a failed attempt that ends in a save can overwrite the last good internal state. Everything from here happens on copies.
Then read the exact error before theorizing, because refusals to open are not all corruption. Some editors refuse a project because a required server license is missing or another running instance holds it, and a project can also fail purely because files went missing — fixing an HMI project that fails after a Git clone documents that failure pattern for version-control mishaps.
The decision: treat an unopenable saved project as a local-storage fault, freeze the original, and recover from a preserved copy or an export.
Where does Vijeo Designer store projects on the PC? #
For Vijeo Designer 6.2 the vendor documents the working folder as C:\Users\Public\Documents\Vijeo-Designer 6.2\Vijeo-Manager on Windows 7 and Windows 10, navigated as This PC > C: > Users > Public > Documents > Vijeo Designer x.x > Vijeo Manager with the folder's version number matching your install.
Saving never asks for a location — unlike most PLC software, which asks for a save path, there is no file dialog — so every Save lands inside that managed tree, and an ordinary, error-free session can still leave you with exactly one copy of the project, in a folder you may never have opened. The storage-and-export workflow described in this article was identified for Vijeo Designer 6.2 and Vijeo Designer Basic 1.1; newer Vijeo software has been reported to store projects differently, with no exact version pinned down, so do not apply this layout blindly. On Windows XP the documented working folder sits under C:\Documents and Settings\All Users\Documents instead.
If the folder exists but looks empty, do not conclude the projects are gone. Open the editor's project manager and let it show you where its active storage sits, then compare that path with the folder you found before copying anything.
The decision: locate the real storage folder first and copy from there; nothing inside it gets moved, renamed or deleted while you diagnose.
How do I recover a Vijeo Designer project that will not open? #
Recover it from the files on the PC, in this order: preserve the storage folder untouched, prove the editor itself works, then open a preserved copy or your newest export — and never rename, delete or repair anything inside the live storage folder.
Run the sequence in this order and stop at the first step that changes the picture:
- Close the editor without saving, so the storage folder stops changing while you work.
- Copy the entire project folder out of the managed storage to a separate recovery location, and confirm the copy shows the same files and subfolders before anything else.
- Launch the editor without opening the affected project; if the editor itself will not start, the fault is the installation or its environment, not your project.
- Open a known-good project. If it opens, the problem is inside the affected project's files or storage; if every project fails, repair the editor or fix file access first.
- Read the complete error text and note which action triggers it — locating, opening, importing and converting are different failure paths with different fixes.
- Check access at the Windows level: the drive is online and your account can read the files. An error naming a missing file points at that exact item in the preserved copy.
- Hunt for older copies — previous exports, zip archives, the other PC that last edited the project — record their dates and locations, and always test a duplicate, never an original.
- If the editor offers a conversion on import, keep the pre-conversion copy, and make the converted project the working copy only after it opens and builds.
The symptom in front of you narrows the search:
| What you see | Where the fault lives | Next move |
|---|---|---|
| Project absent from the manager, files present on disk | Workspace pointed at the wrong storage location | Compare the editor's active storage path with the preserved folder |
| Project listed but fails while loading | Damaged files, version mismatch or a missing dependency | Read the full error, then open a preserved copy or the latest export |
| Known-good projects fail too | Editor installation or file access | Repair the installation or fix read access before touching any project |
| An export imports and builds | A usable recovery candidate exists | Make it the working copy and start the export routine below |
The decision: recovery happens on duplicates. The first intact copy you make is the recovery point; the original stays sealed until a copy proves itself.
Why isn't saving enough of a backup? #
Because Save and Export write to different places: Save updates the managed folder the editor controls, while Export produces a portable copy you can zip, move to another drive and import again later — and only the second one survives damage to that managed folder.
Vijeo Designer saves silently by design: no dialog, no destination, no copy count. A successful Save proves the session was written into the folder the editor controls and nothing more, so if that folder is what gets damaged, half-copied or swept up in a disk cleanup, the saved work disappears with it.
Export is the step that leaves the editor's control. It writes a portable copy to a destination you choose — another drive, another machine, a network share — places the managed folder's problems cannot reach. Whichever edition you run, confirm where Save lands and where Export writes its output before you trust either one.
The decision: Save exists to continue work and Export exists to keep it. A session that ends at Save still leaves the work with exactly one copy.
How do I export a Vijeo Designer project as a zip backup? #
Close the project in the manager first, then right-click it and run Export to write a portable copy to a destination outside the managed folder, and keep that output as a zip — stored this way, it exports cleanly from the zip later and imports cleanly back into Vijeo.
Work the export in five moves:
- Save the session and confirm it completes without an error.
- In the project manager, right-click the project and choose Close, then confirm the project actually closed before continuing.
- Run Export and pick a destination outside the managed storage — a second drive, a network share or removable media.
- Wrap the export in a zip and label the archive with the project name, the editor edition and version, and the date.
- When the day comes to use it, copy the zip first and import from the copy, so the archive itself is never your only instance.
Keep the archive's internal structure exactly as the export produced it. An archive that wraps the project one folder deeper than the importer expects fails for purely structural reasons — a failure mode documented for another platform in fixing Ignition project import nested ZIP folder errors — so re-zip nothing by hand and rename nothing inside.
The decision: export after every working session and store the zip off the engineering PC. The most work you can ever lose is one session.
Can I pull the program back off the panel when the PC copy is gone? #
Usually not — a downloaded panel application is runtime files that execute the screens, and the editable engineering project normally exists only in the editor's local storage, so treat upload as a per-model exception to verify in the panel's documentation, never as your backup plan.
The running screens prove only that the panel's runtime files are intact. An application downloaded to a panel executes the interface; the engineering project contains what is needed to change and rebuild it, and that lives in the editor's storage. Sending an application to a panel says nothing about getting editable source back off, so before relying on upload, find your panel model's documented upload operation and what it says the panel retains. Some transfer tools return an application, a few configurations retain source, and the rest leave you with working screens and nothing editable behind them.
If the panel will not boot at all, panel recovery is its own documented procedure: for the HMIST6, power the panel off, power it on, and click Yes at the prompt shown during boot to enter recovery mode. That restores a serviceable panel and still returns no source. Power a panel down and up only with the machine in a safe state, because the operator interface going dark is a change to running equipment.
An older terminal adds one more dependency: holding the correct firmware file, which getting the right firmware file for a legacy HMI panel sorts out for legacy hardware.
The decision: assume the panel copy is runtime-only until your model's documentation proves upload retains editable source. The backup plan is the zip on the PC, not the panel.
How do I prove a zip backup is good before I need it? #
Import the zip into a clean editor, open the project and build it — for an illustrative 1,462-file, 512 MB project whose export is a 96 MB zip, the whole drill takes under 20 minutes and turns 'I think I have a backup' into a verified one.
Worked example — the counts and sizes are illustrative, so substitute your own. The project folder in the managed storage holds 1,462 files totalling 512 MB, and the export you just made is a 96 MB zip. Run four checks, immediately:
- Count entries: the zip lists 1,462 file entries against 1,462 files in the folder, so 1,462 - 1,462 = 0 files were left out.
- Sanity-check the size: 96 MB / 512 MB = 0.1875, so the archive holds about 19% of the source, which is normal for project data that compresses well; compare it against your previous export, because a sudden jump either way means the content changed.
- Import and build: open a clean copy of the editor, import the zip, open the project and build it — about 15 minutes on this example.
- Label the result: project name, editor edition and version, date, and the entry count it passed with.
The arithmetic of the habit is small: 2 minutes to export, 1 minute to copy the archive off the PC, 15 minutes to import and build — 2 + 1 + 15 = 18 minutes, call it 20, added to the end of a session. A backup that has never survived an import is a hope, not a backup.
The decision: a zip counts as a backup only after this drill passes on it, and the drill runs immediately after each export, not on the day the project refuses to open.
Questions asked
Do other HMI and SCADA editors have the same save-versus-export problem?
Yes. Most editors keep the working project in a managed folder and need an explicit command for a portable copy. TIA Portal puts Archive on the Project menu and can reorganize during a Save As, and FactoryTalk View Site Edition documents a separate backup-and-restore procedure for applications. The habit is identical everywhere: archive or export after every session and store the file off the engineering PC.
What should I check first when a project opens on one PC but not another?
Compare the editor edition and version that last saved the project with the one installed on the failing PC, and read the full error before changing anything. A project last saved by an older edition may need that edition or a documented conversion, and version mismatches usually announce themselves during import or conversion. Test on a duplicate copy and keep the pre-conversion file.
How much work disappears if the storage folder is damaged between exports?
Everything saved since the last verified export. Save writes into the same managed folder that failed, so it adds no protection; the export is the only independent copy. Export at the end of every session and the worst case is one session; export once a week and a Friday failure costs the whole week. The interval you choose sets the loss.
Where should the exported zip archives live?
In at least two places, one of them off the engineering PC entirely — a network share or removable media. Damage that hits the machine can hit every drive attached to it, so the archive that saves you is the one the machine cannot touch. Keep the two most recent exports of each project and delete older ones only after the newest has passed the import-and-build drill.
How do I find out which editor edition and version I am running?
Read the product name and version from the editor's software information screen before choosing a recovery path. The edition matters because Vijeo Designer and Vijeo Designer Basic keep projects in the same managed-storage style, while newer releases have been reported to store projects differently. Write the edition and version on every backup label so a restore years later starts with the right editor.