AppVolumes 2.13.2.13 - Cannot Open files when "Cloud Volumes" Service in enabled

[danielkrause]

We have some applications local installed on the golden image (win7 x64):

- VLC

- Office 2010

- ERP

We are using appvolumes 2.12.2.13 on our system to publish specified apps.

Now we realized a problem:

If a user want to open a document/file from the ERP system in VLC or Outlook (using a specified CMD command) its not possible if the "Cloud Volumes" Service is enabled wherever a appstack is attached or not.

First i was thinking i could make some changes in the snapvol.cfg, but if no appstack is connected the error also occurs. It worked with the old version of appvolumes 2.12.

if i stop the "cloud volumes" service all commands working fine.

Any ideas how to fix this issue?

[Lakshman]

Not sure why it doesn't work in 2.13 if it worked in 2.12. Have you tried with the latest 2.13.3 version?

[danielkrause]

I installed the 2.13.3 Agent on Windows 7.

Also not working.

The same commands also not working on Windows 10 by the way when the App Volumes services is running.

[Lakshman]

Could be a regression issue (not 100% sure) as it worked in 2.12. Please file a SR with support.

[techguy129]

Even if no appstacks are connected there is a local system appstack that is under C:\SVroot. Try stopping the app volume server, delete the contents of SVroot and start the service. See if it works after that?

More then likely there is an issues with the 2.13 version and support will need to fix the bug.

[danielkrause]

i tried to remove the content of the c:\svroot dir, but even when the appvolume service is disabled i cannot delete the hole directory because some files in c:\svroot\windows are still in use.

After starting " same issue"

[danielkrause · Accepted solution]

Here is the solution by the VMware Support:

>>>>>>

Change the following registry value on the master image.

  Key  
HKLM\SYSTEM\CurrentControlSet\services\svdriver\Parameters

  Value  EnableHookInjection
Data   1 <<<   Here it needs to be changed to 0.

It can also be done using the command line.

  reg add HKLM\SYSTEM\CurrentControlSet\services\svdriver\Parameters /v
EnableHookInjection /t REG_DWORD /d 0 /f

Once done , Reboot the Agent VM and try the Outlook test again.  If
you are using Instant Clones, or Linked Clones with refresh at logoff, you may
need to create a new base image in order to test.