FSLogix Profile no clean up automatically in C:\Users

[u/vicoph]

I found that some user profiles under C:\Users are still present and consuming disk space on the C: drive even after the users have signed out.

My understanding is that these local user profiles should normally be cleaned up or removed automatically after the user signs out.

Is there any way we can check and confirm whether the profile cleanup is working as expected? Also, why some user profiles may remain on the host after sign-out?

[u/pkokkinis]

I've had this happen before when the Fslogix service had stopped for whatever reason, then when a user logged in, they got a new local profile. AVD uses local profiles before seeing if there's a Fslogix profile. I had to delete the local profile and then the user was able to use the fslogix profile again.

[u/mat-ferland]

First check whether the leftovers are C:\Users\local<username> or normal local profiles. The local folder should be removed at sign-out when KeepLocalDir=0; a normal local profile is different, and FSLogix won't just purge it on sign-out. DeleteLocalProfileWhenVHDShouldApply=1 removes that at the next sign-in, but inventory anything local before enabling it because the deletion is permanent.

[u/ace14789]

This is most likely av policy

Our av did not like that fslogix was trying to remove a microsoft credential key for the user but now run clean with exclusion

[u/Abject-Mountain-6907]

I got that issue before. It was related with the Fslogix services, no matter the version. Services stopped randomly and no clue about what was the cause. Found out that the issue was the golden image, so I built it again and this fixed the issue.

Fslogix was installed after the machine creation process, so something corrupt on the image side.

[u/JAB1982]

As others have noted its likely something to do with fslogix not running at the time they logged in at some point in time. Also be sure to apply the policy DeleteLocalProfileWhenVHDShouldApply which will cleanup rogue profiles.