The first launch of any application presented via App Volumes is slower than locally installed applications. However, after the first launch the launch time is normal. The environment is as follows:
App Volumes 2.15
OS Windows 10 1803
I had the same behavior with previous versions of App Volumes (2.14) and UEM (9.4 and 9.5). I have tried both user and machine assigned App Stacks with the same result.
Take a look at this, I think reverse replication is enabled by default in newer versions
I saw this KB article, and have verified that those changes are in place on my app stacks. As you said, this appears to be the default with newer versions. What I am seeing is a 5 - 6 second delay before the application launches the first time. After that launch, it is instant.
Is there something unique about the first launch of an application? I was under the impression that any registry injection, etc. happened at the time the volume is attached.
Is it the first time no matter how long you wait, or after connecting a few minutes later. I'm still on 2.13 and I'm not see that, but I've see people report this before in some applications, and they add there own reverse replication entries to the snapvol.cfg. I'd open a support ticket if it seems like its all applications not matter how long you wait after logon.
I thought that maybe there was some activity in the background. So, I logged on and left the VM idle for several minutes before launching the application and got the same result. I have already opened am SR and am waiting for a response. I was just curious if any others had seen this behavior.
I know this thread is a bit old, but did you ever get this resolved? I have also been dealing with this issue.