Forum Discussion

Redlimey69's avatar
Redlimey69
Copper Contributor
Apr 02, 2025
Solved

Recycle Bin Corrupt upon login - shot self in foot :(

In setting up multiple AVD Host Pools (replacing Win10 with Win11) I figured I'd do better in locking down the Storage Account > File Share that's setup to host the FSLogix user profiles. Silly me. Suffice to say, when users log in, they're presented with a corrupt recycle bin message.

My old Win10 environments didn't involve touching the root of the Azure file share volume and I never had such issues. Repeating the same with a new Win11 and applying the steps as documented here: https://learn.microsoft.com/en-us/fslogix/how-to-configure-profile-container-azure-files-active-directory?tabs=adds#set-ntfs-permissions, also does not present the recycle bin issue.

Interestingly, deleting and recreating the File Share (meaning default ACLs), does NOT fix the issue which is rather perplexing. 

 

The hosts for each of these AVD builds reside in our on-prem AD. The GPOs in effect are the same for each, barring the VHDLocation policy.

If I add a user into the "FSLogix Profile Exclude List", they don't have the issue. Remove them and they have the issue. Not that I've touched system drive root perms, but that tells me all is well with the system drive and their respective recycle bin folders.

I increased the logging level to the max, but the Profile log doesn't note any errors. A side-by-side comparison using the same user logging into the 'healthy' environment vs a corrupt bin environment doesn't reveal anything either.

 

I know I've provided very little specifics with the environment settings, but I figured there's something obvious I'm overlooking. I'm ready to be taught a lesson! I'd rather not have to rebuild these 4 environments.

 

Thanks in advance

 

 

  • Turns out there are issues with the FSLogix Agent v25.02. I backed down to 2210 HF4 and the issue stopped. The fact my first lockdown attempts coincided with using 25.02 lead me to think it must have been something strictly with what I was doing, placing too much faith that all underlying components were 100% good.

    I tried to include a link to a justinverstijnen DOT nl blog, but 'content not permitted', so go to that page and look under his AVD postings.

1 Reply

  • Redlimey69's avatar
    Redlimey69
    Copper Contributor

    Turns out there are issues with the FSLogix Agent v25.02. I backed down to 2210 HF4 and the issue stopped. The fact my first lockdown attempts coincided with using 25.02 lead me to think it must have been something strictly with what I was doing, placing too much faith that all underlying components were 100% good.

    I tried to include a link to a justinverstijnen DOT nl blog, but 'content not permitted', so go to that page and look under his AVD postings.

Resources