VMware Horizon Community
jmatz135
Hot Shot
Hot Shot

Agent 2.17 Causes Program Files Directory Issues

On VMs that we put the App Volumes agent 2.17 on after a period of time the Program Files and Program Files (x86) folders end up all kinds of messed up.

pastedImage_0.png

As you can see application directories have been changed to files with no extension and clearly the applications within them no longer work.  These aren't even all applications in appstacks, some of these are applications directly on the VM image itself.  This only happens with agent 2.17 as far as we can tell.  We reverted to the 2.15 agent and everything works fine again (we avoid 2.16 because Visio is broken and other issues make it basically unusable).  Anyone else see anything like this or have any ideas.  Like I said this happens after a period of time after log on so something that is kicking off on the machine is making the app volumes agent go crazy.

Reply
0 Kudos
6 Replies
VDINinja311
Enthusiast
Enthusiast

jmatz135

We saw this exact same issue back on the AV 2.11 agent I believe. It randomly went away, can't remember what version. It seemed random on what folders it did it on too.

Technically we never had an issue with the applications inside of those folders. When we had this issue it was the "C:\Program Files (x86)\Microsoft Office" folder as well but all the office products seemed to not have issues.

Reply
0 Kudos
jmatz135
Hot Shot
Hot Shot

Yes, oddly some applications don't have issues but other just won't launch or throw an error.

Reply
0 Kudos
VDINinja311
Enthusiast
Enthusiast

Have you attempted recreating the appstack with the latest template version?

Reply
0 Kudos
jmatz135
Hot Shot
Hot Shot

I have some done but not all.  I'll try just attaching new ones.

Reply
0 Kudos
jmatz135
Hot Shot
Hot Shot

So I tested it with only one appstack attached that has been created using the 2.17 template and the 2.17 agent to capture.  Still had the issue.  On a side note this happens only after the system is idle for a few minutes so some task that runs during idle is triggering the agent to bork itself.

Reply
0 Kudos
jmatz135
Hot Shot
Hot Shot

So looks like when using Windows 10 1803 this issue does not occur or at least I have not been able to recreate it.  The issue does occur on Windows 10 1703 at the very least.

Reply
0 Kudos