I believe that this is the infamous MSI installation issue.
Try removing the cumulitive update patch or try upgradeing to version 2.17, i believe the issue is fixed there.
There is a thread regarding this issue..
Thank you very much for your answer. As we chose Windows 10 Build 1809 July update, I'm afraid it will be difficult for us to uninstall previous patches, which are already embedded into the OS.
I think we have 2 options left:
- Install 2.17 or 2.18 agent in the capture machine.
- Build another capture Machine based on W10 1809 January update - and try to recapture this application.
If you have any other idea, feel free to share with us ;-)
Thank you !
Just a quick feedback here:
We updated our Windows 10 Capture Machine with 2.18 agent, and it solved all the weird problems, such as:
- Installation errors
- Installation slowness when capturing
- BSOD when the capture machine is rebooted
In conclusion, we'll update App Volumes infrastructure to 2.18 as soon as possible ;-)
Yes, that would be my suggestion as well.
Do keep in mind that Appvolumes agent is not backwards compatible (or at least it is not supported).
So you can use Appvolumes manager 2.18 with Agent 2.17, not the other way around. Keep in mind that both versions should not be apart to much.
Regarding the packaging machine. To be honest I haven't seen much issues if you have a working appstack created with a newer agent to work on a machine with an older agent. So my guess is that you will be just fine with this solution
Thanks for the precisions ;-)