Troubleshooting
Cleaning EasyBuilder Pro AppData CloudHMI Files Safely
Short answer
Treat the Weintek CloudHMI xob tree under AppData\Roaming as application-managed data, not confirmed temporary cache, because no vendor documentation marks it disposable. Copy the whole tree to storage outside the VM, verify the copy, then remove the guest contents as a controlled test after closing EasyBuilder Pro. Deleting the roughly 1 GB frees guest space only; the host virtual disk shrinks after the hypervisor's documented space reclamation runs.
On this page
Do not delete the contents of AppData\Roaming\Weintek\CloudHMI\xob on the assumption that they are temporary files the software rebuilds. No documented statement from the vendor identifies these identifier-named folders or their project.encrypted files as disposable cache, so the roughly 1 GB they occupy on your engineering VM is application-managed data until a controlled test shows otherwise. The working answer: copy the complete tree to storage outside the VM, verify the copy, close EasyBuilder Pro, remove the guest copy, and validate the software before you call the space reclaimed.
One further fact decides whether the cleanup even pays off. Deleting files inside the guest frees space in Windows immediately, but the virtual-disk file on the host usually keeps its size until you run the hypervisor's documented space-reclamation step.
What the path establishes, and what it does not #
| Observed item | What it establishes | What to check next |
|---|---|---|
AppData\Roaming |
User-scoped application storage in Windows; the location says data, not temporary | Which Windows account runs EasyBuilder Pro, and its real profile path |
Weintek\CloudHMI\xob |
An application-specific tree created by Weintek's EasyBuilder Pro | Whether any process holds it open after the software closes |
A folder named 63a514c7-9cf7-4939-8be1-312bbbf2976b |
An identifier-named object container, not a readable description | Which operation creates or reads it |
project.encrypted |
Encrypted, project-related content, unreadable by inspection | Its dependency, by access monitoring and removal test |
| About 1 GB total | A real cleanup target, not evidence the data is orphaned | Allocated size versus logical size, and guest free space |
The confident answer sometimes given, that these are temporary files left behind when the program closes and safe to remove, is an unverified guess rather than a documented property of the software. Encryption closes the usual shortcut: you cannot open project.encrypted, look inside, and decide. The decision has to come from behavior.
Find out whether anything still uses the directory #
- Confirm the real path for the account that runs EasyBuilder Pro. A written
User\Nameis a location description, not an account name; open the actual profile directory and work from theWeintek\CloudHMI\xobtree you find there. - Record the total size, allocated size, subfolder count, and modification times of the tree. Save the listing outside the tree so it survives the test.
- Close EasyBuilder Pro normally, then check for remaining Weintek processes and for open file handles on the path. A background process still holding the directory changes the plan.
- Run a file-access monitor filtered to the path. Launch the software and repeat the operations your workflow actually uses: opening a project, downloading to a panel, and, because the directory name references cloud functions, any EasyAccess 2.0 remote-access or cloud workflow you use.
- Correlate what you did with what changed. New folders, changed timestamps, or reads of existing files point to an active dependency. A file untouched at startup can still serve a rarely used function, so monitoring narrows the question without finishing it.
Back up the tree before anything is removed #
- Save open work and make your normal project backups first, then verify HMI project data is inside your platform backup so your recovery path does not depend on this directory.
- Copy the complete
xobtree to storage outside the VM: host disk, network share, or external drive. Preserve folder names and file contents exactly. A partial copy of HMI data is a recognized failure mode, the same one behind fixing an HMI project that fails after a Git clone, so copy everything rather than a sample. - Verify the copy by comparing structure, file counts, and sizes between guest and backup; comparing file hashes is the stronger check.
- Do not decrypt or edit
project.encryptedat any point in the process. - Treat a VM snapshot as a rollback aid, not as this backup: snapshots retain the old disk blocks you are trying to free and can grow host consumption while they exist.
Run the removal as a test, not as a guess #
- Close EasyBuilder Pro and finish the handle check. If a related process still touches the path, identify it before deleting anything beneath it.
- In a maintenance window, remove the backed-up contents from the guest. Record exactly which folders were removed so a restore puts them back in the same places.
- Watch the Recycle Bin: files sent there still consume the space you are reclaiming. Empty it only after the external backup is verified.
- Restart EasyBuilder Pro and run a validation sequence: open an existing project, create and download a test project to a panel, and exercise any remote-access workflow you use.
- If anything fails, close the software, set newly created files aside separately, and restore the saved tree to its original path.
The application may recreate an empty xob directory on startup. That proves nothing: an application can rebuild a folder while the content that lived in it stays gone. The functional result of step 4 is the evidence that counts.
Why deleting 1 GB may not shrink the VM disk #
Guest free space and host storage are different measurements. Deleting the tree raises free space inside Windows, but the virtual-disk file on the host keeps its allocated size until the hypervisor reclaims the blocks, and a snapshot chain can keep the old blocks alive regardless.
Illustrative example with round numbers, not measurements from your VM. A thin-provisioned virtual disk of 60 GB; before cleanup the guest reports 8.2 GB free and the virtual-disk file occupies 52.4 GB on the host datastore. You remove 1.0 GB of xob contents and empty the Recycle Bin:
- Guest free space: 8.2 GB + 1.0 GB = 9.2 GB, available immediately.
- Host virtual-disk file: still 52.4 GB, unchanged by the deletion itself.
- After the guest passes its functional checks and you run the hypervisor's documented reclamation, guest TRIM or UNMAP plus the hypervisor's own compact or shrink procedure, the file drops to 52.4 GB − 1.0 GB = 51.4 GB.
| Measurement | What it answers | Where to look |
|---|---|---|
| Guest volume free space | Can Windows and EasyBuilder Pro allocate more files | Inside the VM |
| Virtual-disk file allocation | Has host consumption actually fallen | Host datastore and hypervisor storage view |
| Snapshot storage | Are earlier disk blocks still retained | Hypervisor snapshot management |
Never reclaim host space by deleting virtual-disk or snapshot files by hand from the datastore: that loses the VM, not the gigabyte.
The decision, case by case #
- The software passes the full validation sequence on the cleaned directory: the deletion stands. Keep the external backup through at least one complete project cycle that includes every workflow you tested, then retire it. The 1 GB stays reclaimed.
- Any function fails without the directory: restore the tree, leave it in place, and recover capacity elsewhere. On that installation the directory is load-bearing, whatever the filenames suggest.
- You need host capacity, not guest capacity: do the guest cleanup first, then the hypervisor's documented reclamation, and expect the host gain only after that step and only once snapshots are gone.
- You cannot take the outage now: leave the directory untouched. Renaming it within the same guest volume tests dependency cheaply but reclaims nothing, so it is a diagnostic, not a cleanup.
Questions asked
Are the project.encrypted files safe to delete because they are just cache?
No vendor documentation marks them as cache, so treat them as application-managed data. The encryption also removes the usual shortcut of opening a file to judge its importance. Delete only after the external backup and the controlled removal test pass, and keep the backup until the software has run a full project cycle without the directory.
Will EasyBuilder Pro rebuild the xob folder by itself after I delete it?
Possibly as an empty directory, and that proves nothing. An application can recreate a folder while the content that was inside it stays gone, so successful recreation is not evidence of a safe deletion. The evidence that matters is functional: projects open, downloads succeed, and any remote-access or cloud workflow still works after the contents are removed.
Is a VM snapshot enough protection before I clean the directory?
As a rollback aid, possibly; as a backup, no. Snapshots retain the disk blocks you are trying to free, so host consumption can grow while the snapshot exists, and a long snapshot chain complicates the reclamation you are doing this for. Copy the tree to storage outside the VM and verify it; treat any snapshot as separate.
I deleted the folder and the host disk did not shrink. What now?
That is expected behavior, not a failed cleanup. The deletion raised free space inside the guest operating system; the virtual-disk file keeps its size until the hypervisor reclaims the blocks. Run the hypervisor's documented space-reclamation or compact procedure with the guest able to issue TRIM, and remove snapshots per your rollback plan; only then does the host see the reduction.
Can I open or decrypt project.encrypted to check what it is before deciding?
Leave the file intact. No documented EasyBuilder Pro workflow opens or imports these files, so there is nothing to learn that way, and editing an encrypted application file risks corrupting data the software may need. Answer the dependency question with access monitoring and the removal test instead of reading the file.