FSLogix - Single Profile causes VM to freeze affecting everyone else logged in to it.

Question

Two questions:

1. What are the potential causes of a corrupted profile when using FSLogix?
2. What would cause a WVD VM to freeze when a specific person logs in?

I have seen profiles cause a slowdown or freeze on a physical machine. Delete profile and recreate it fixes it. We have done this with this specific users at least a dozen times in the last 60 days.

Azure WVD running Windows 10 Multi User edition. All objects are in the same zone.
The Host pool has been in production for 9 months with no issues or changes.

Starting 2 months ago, users would complain that the VM is slow or stops responding.  

Long story short, one users profile was causing this.  When he logged in to a VM his profile would become unresponsive and anyone logged in to that VM would also experience the same thing.

The "Band aid" was to delete his profile and let FSLogix recreate it.  But it would continue to happen.  Sometimes it would last a few hours and sometimes a week before having to delete his profile and recreate it.  Like I said that is a band-aid workaround.

On a couple of occasions other users would have their profiles get corrupted causing the same issue.  But they only happen once per user.  This one user has happened a dozen or more times and on different VMs.

On a side note, two of the four VM's have now started to have issues where the Hostpool flags them with an error or warning.  I have gotten the error to go away, only to have it come back after users are logged in.

It has now been about 3 weeks now since the last time this his profile caused a VM to freeze.

Answer 1

I have a ticket open. They are combing through the event logs, a full dump file and the FSLogix log dump.

I just wanted to see if anyone else had this issue, what they found out from it. Bottom line is deleting the users profile everytime is only a bandaid. I want a solution. I need to know what can cause the profile to get corrupted.

I have been looking through the logs myself and noticed issues with the Windows Indexing. And since it is explorer that is the common factor in this (That is the app he was using when everything froze for him and the other users on that VM) I am wondering how to go about preventing that from being corrutped.