This issue has been solved in the newest release of FSLogix 25.04: https://learn.microsoft.com/en-us/fslogix/overview-release-notes
Please use this newer version instead of version 25.02. This fixes the bug in this article without any change in policies and settings.
The problem/bug described
When testing the new FSLogix 25.02 version, I came across a very annoying problem/bug in this new version.
“The Recycle Bin on C:\ is corrupted. Do you want to empty the Recycle Bin for this drive?”
I tried everything to delete the folder of the Recycle bin on the C:\ drive but nothing worked. Only warnings about insufficient permissions and such, which is good but not in our case. This warning appears everytime you log in to the hostpool and every 2 minutes when working in the session. Something you definitely want to fix.
Table of Contents
- The problem/bug described
- How to solve the problem with GPO (1)
- How to solve the problem with a registry key (1)
- How to solve the problem – Profile reset (2)
- Summary
📖 Estimated read time: 4 minutes
🔄 Page last updated on: July 14, 2025 🆔 Post ID: 1312How to solve the problem with GPO (1)
To solve the bug, you have to disable the Recycle Bin roaming in the FSLogix configuration. You can do this by going to your FSLogix Group Policy and open it to edit the settings. Make sure you already updated the FSLogix policies to this new version to match the agent and policy version. I also addedd a fix for using the Windows registry.
Go to the following path:
Computer Configuration -> Policies -> Administrative Templates -> FSLogix
Here you can find the option “Roam Recycle Bin”, which is enabled by default -> even when in a “Not Configured” state. Disable this option and click on “OK”.
After this change, reboot your session host(s) to update the FSLogix configuration and after rebooting log in again and check if this solved your problem. Otherwise, advance to the second option.
How to solve the problem with a registry key (1)
When using Registery keys to administer your environment, you can create the following registery key that does the same as the Group Policy option:
HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Apps\RoamRecycleBinThis must be a default DWORD;
- 1: Enabled (which it is by default)
- 0: Disabled (Do this to fix the issue)
After this change, reboot your session host(s) to update the FSLogix configuration and after rebooting log in again and check if this solved your problem. Otherwise, advance to the second option.
How to solve the problem – Profile reset (2)
If disabling the recycle bin did not fix your problem, we have to do an extra step to fix it. In my case, the warning still appeared after disabling the recycle bin. FSLogix changed something in the profile which makes the recycle bin corrupt.
We have 2 options to “fix” the profile:
- Backup all of your data in the profile and delete it. Then let FSLogix regenerate a new profile
- Restore a backup of the profile, before the FSLogix update to 25.02
After logging in with a new or restored profile, the problem is solved.
Summary
This problem can be very annoying, especially when not wanting to disable the recycle bin. This version seems to change something in the profile which breaks usage of the the recycle bin. I did not manage to solve it with a profile that had this problem.
In existing and sensitive environments, my advice is to keep using the last FSLogix 2210 hotfix 4 version. As far as I know, this version is completely bug-free and does not have this problem.
After some more research, I came across a page of Microsoft about a lot of features deprecated in this version of FSLogix. Be aware of those changes before they might impact your environment: https://learn.microsoft.com/en-us/fslogix/troubleshooting-feature-deprecation
If I helped you with this guide to fix this bug, it was my pleasure and thank you for reading it.
End of the page 🎉
You have reached the end of the page. You can select a category, share this post on X, LinkedIn and Reddit or return to the blog posts collection page. Thank you for visiting this post.
- Azure Master Class (12)
- Azure Virtual Desktop (22)
- Flying (16)
- Intune (6)
- Microsoft 365 (13)
- Microsoft Azure (33)
- Microsoft Defender XDR (4)
- Microsoft Entra (12)
- Networking (5)
- Powershell (20)
- Uncategorized (1)
- Windows 365 (3)
- Windows Server (14)
If you think something is wrong with this post or you want to know more, you can send me a message to one of my social profiles at: https://justinverstijnen.nl/about/
If you find this page and blog very useful and you want to leave a donation, you can use the button below to buy me a beer. Thank you in advance and cheers 🙂
The terms and conditions apply to this post.
Page visitors: No page-counter data available yet.
16 Comments
여성전용마사지 · July 31, 2025 at 05:31
thanks for this solution
skadann · June 23, 2025 at 00:13
HA! I didn’t know about these workarounds. I rebuilt all my images thinking the problem was my image update process. This is fantastic 🙂
Justin · June 25, 2025 at 18:55
Thank you! Yes, I experienced the same. In my case it was only an update and i immediately got it. Then went on searching for solutions but couldn’t find it at the time.
emoryayers · June 2, 2025 at 11:52
great guide, helped me out a lot
Lucero · April 8, 2025 at 10:48
How to solve if not using GPO (cloud native FSL) – registry key perhaps?
Justin · April 8, 2025 at 18:21
Dear Lucas,
I added a part to the page which includes the change by creating a registry key: https://justinverstijnen.nl/solved-fslogix-update-25-02-breaks-recycle-bin-bug/#solve-problem-registry
Kind Regards, Justin
Stuart · April 3, 2025 at 22:43
Thanks for this! I was going insane questioning my sanity. It was compounded by me actually locking down the root of the Azure File Share in my most recent AVD deployments (rather than just accept the defaults, which I’d done in earlier Win10 deployments) and thought that was the reason for my issues.
Anyway, I decided to downgrade to 2210 HF4 and the issues immediately went away.
Justin · April 6, 2025 at 14:56
Dear Stuart,
Thank you for replying. I am glad that I helped you solving this issue 🙂
Kind regards, Justin
Arthur · March 27, 2025 at 01:56
What a life saver you are. disable the roam recycle bin fixed our issue.
Justin · March 27, 2025 at 22:15
Dear Arthur,
Thank you for replying. I am glad that i helped you solving this issue, which maybe really simple but can be challenging in bigger environments.
Kind regards, Justin
Prajwal K V · March 21, 2025 at 05:57
I also faced this issue in our environment but how we can resolve for pooled host pools ?
Justin · March 25, 2025 at 18:24
Dear Prajwal,
With Pooled hostpools this article exactly describes how to fix it. When using personal hostpools in combination with FSLogix the fix will also be the same.
Kind regards, Justin
Hans · March 18, 2025 at 20:41
Very helpful…got this issue on my environment too and solved it
Edwin · March 19, 2025 at 11:12
Hello Hans, Which solution did you choose?
Hans · March 19, 2025 at 14:38
Hello Edwin, i have disabled the recycle bin in solution 1 and after that restored the profile like in solution 2
Justin · March 19, 2025 at 22:59
Dear Hans, thank you for replying to my page.
I am glad I helped you solving this issue.
Kind regards, Justin