In your User Guide there are several ways to update a package:
1) Re-packaging the latest version: you can always re-capture the latest version of the software. As long as the package keeps the same AppID, running the package will automatically patch any existing binaries and registry keys before running, without affecting user-created data files. This method works for all update types. 2) Using the -Patch parameter on the virtual package (see Virtual package command lines). This method is mostly recommended for update type #2.
I don' understand well the first method: what does it mean "re-capture the latest version of software"? If I must to execute an update file how can I do this?
The second method also is not so clear for me: can someone explain me better? It exists a video that show this method?
If the activation process involves taking a hardware fingerprint, then in all likelihood, you will have to activate it on each machine. If no such fingerprint is taken, then capturing the activation process may work for the same package on different machines. I have seen both. This depends more on the program you wish to package than on Cameyo.
For minor updates, i.e. not full version numbers, using -Patch parameter is a good place to start. Download your executable, drag your package to the command prompt, add a space, type -Patch, add a space, drag your executable to the command prompt, and <Enter>, e.g. appname_1.05.cameyo.exe -Patch update_1.07.exe
For major updates, e.g. going from version 1.05 to 2.0, it is recommended to build the package anew in your clean virtual machine. As long as your Application ID and Data storage are the same between the original package and the newly built package, you can run the new package on your system without affecting user-created data.