C:\SnapvolumesTemp\Writable location not available

[balagbm2017]

Hello

I have created and assigned writable volumes for one users. I can see the writable volume is attached successfully when I try to browse the writable volume folder I got the below error. Can you advise me how to resolve this issue

[balagbm2017]

[Lakshman]

The syntax "C:\snapvolumestemp\writable" is not correct. Please use "C:\SnapvolumesTemp\MountPoints" folder and you will see a GUID for the writable volume disk.

What is the version of App Volumes? In the latest versions 2.13.1 and 2.13.2, there is a known issue in browsing to the mountpoint folder.

AV 2.13.1: Can no longer see C:\SnapVolumesTemp after updating to 2.13.1

[balagbm2017]

Thanks Lakshman for your quick response.

I was following only VMware blogs and KB

Managing OST Files with App Volumes & User Environment Manager

VMware Knowledge Base

Microsoft Outlook Search Indexing With VMware App Volumes - YouTube

To make support customer use case - outlook search & indexing also OST in the writable volume . As per your advise I will make the necessary changes and keep you update.

I am currently using App volume version 2.13.

[fdrietatns]

Yes, see AV 2.13.1: Can no longer see C:\SnapVolumesTemp after updating to 2.13.1

I have to roll the agent back to 2.12.1 in order to correct this issue and various other issues this condition creates.

Thanks..

[balagbm2017]

I have rolled back to 2.13.1 the problem is resolved.

[Lakshman]

I guess the issue still remains in 2.13.1. Have you rolled back to 2.13.1 or 2.12.1?

[balagbm2017]

Again rollback required to 2.12.1??? . 2.13.1 solved logon slowness after attached appvolumes, OST files are persistent each login/logout.. Can we expect any other issues to come...? As of now VMware support team confirmed to roll back to 2.13.1 . Might be next call they may say to go back to 2.12.1 .....:)

[Lakshman]

No need to rollback again Happy to hear that 2.13.1 resolved the issue

[balagbm2017]

Dear Lakshman

We tried with all the versions, however, search and indexing features is working on 2.13.1 however we can experience lot of CPU (100%) only when we attach app volumes(writable-UIA plus profile) . The following services we have noticed during 100% CPU

Windows defender  services also contributing high CPU

during the high CPU period, end users windows search on the task bar is not working.

Do you have any reference from VMware on which version of App volumes outlook search & indexing works with out any issues .

[Lakshman]

When i searched for wsappx process, there are many posts related to high CPU usage. Below is one from Microsoft community:

wsappx process takes more CPU usage - Microsoft Community

As other users who are not using App Volumes face similar issue, i guess it may not related to writable volumes.

[balagbm2017]

Temporarily the problem has been fixed by VMware SE with the help of https://kb.vmware.com/s/article/2149795