Problems with FSLogix 3.26 - W11 MU - 10 users per Vm
Scenario Overview We are documenting a recurring intermittent Denial of Service (DoS) regarding user profiles in an AVD multi-session environment using Azure Files Premium (SMB). The issue consistently surfaces after updating to the FSLogix 3.26 branch (v3.26.126.19110). Root Cause Analysis (Failure Logs) Through deep log analysis, we identified a "driver poisoning" pattern unique to version 3.26: SMB/Kerberos Handshake Sensitivity: Under varying storage response times (latency spikes of ~350ms vs. the usual ~40ms), version 3.26 triggers an intermittent 1326 error (Logon failure: unknown user name or bad password). Driver Execution Flow Corruption: Unlike previous versions, after this initial network/authentication glitch, the 3.26 driver fails to release execution threads or volume handles properly. Catastrophic Failure (Error 267): The system attempts to access the SecuredProfileRegData path within the mounted VHDX, but the driver returns Event ID 26: "0x10b - The directory name is invalid". Unrecoverable "Zombie" State: Once Error 267 occurs, the VM becomes "poisoned." It blocks all subsequent login attempts and even prevents a clean uninstallation of the agent (MSI Error 0x80070643 due to files being "in use"), necessitating a full VM reboot or redeployment. Has anyone else been through this? My first step was to go back to Agent Version 2506 (2210 Hotfix 4) Evidence of Success with Version 2506 (2210 Hotfix 4) After performing a clean deployment and reverting to version 3.25.626.21064, metrics from April 24, 2026, show absolute stability on the same infrastructure: Consistent Logon Times: Average profile load time of 1.6 seconds across multiple concurrent users Storage Efficiency: FindFile response times remained stable between 39ms and 45ms, with the agent successfully retrying any momentary delays. Error Resilience: Unlike v3.26, if this version encounters an authentication glitch (e.g., on a local service account), it bypasses the error and remains functional, allowing domain users to log in without collateral blockages. Concurrency Support: Seamlessly managed over 20 simultaneously mounted volumes without pointer collisions or kernel hangs.
FSLogix Version Compatibility
Hi, We are using FSLogix on a Windows Server 2025 RDS farm and are looking to update FSLogix version from 2.9.8884.27471 to the latest version. Is to ok to update one or two of the RDS hosts at a time to make sure there are no issues, or is it required to update all RDS hosts at the same time for profile compatibility. Thanks!
Issues with FSLogix Profiles on Win11 25H2 Multiuser sessionhost's
Hey guys we have currently lot of issues with AVD and FSLogix 26.01. There seems to be an issue that the profile container isnt't unmounted correctly. We have lot's of users who are not able to login correctly because the profile can't be mounted because its already in use by another process. I'm currently looking what could cause that. We use a Azure files storage were i don't see any issues. It looks like a process within the userprofile is blocking the unload of the profile. Should i be able to see in the logs of FSLogix which process is causing this. Or what is a effective way to troubleshoot that? Thanks for any help Best regards Marc
Issue with AVD User Profile – FSLogix Not Recreating
Hi all, We have a user who has repeatedly reported that their settings and favorites are not loading in AVD. To troubleshoot, we deleted the user’s FSLogix profile from our storage account to allow it to recreate automatically. However, the profile is not being recreated. We are operating in a hybrid environment, and the user is part of a group assigned the Storage File Data SMB Share Elevated Contributor role. From the profile logs, we found the following error: FindFile failed for path: \\<redacted>.file.core.windows.net\userprofiles\<redacted>\Profile*.VHD (Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.) What are some likely causes and additional troubleshooting steps we should take?
FSlogix Profile Disconnects
Hi, Just wondering has seen this issue with their AVD instances and FSlogix in regards to profile container disconnects. We have version 3.25.822.19044 and my theory is that computers that go into sleep mode (due to power timeouts) are not cleanly triggering the disconnect procedure for the container to be cleanly disconnected. We have noticed this by the users .VHDX.metadata file not deleting on their log off. It's also not releasing the Handles and Leases for their containers, making them sign in with a temp profile if they try again. We are just running a standard regedit profile setup based on this page, https://learn.microsoft.com/en-us/fslogix/concepts-configuration-examples Just seeing if anyone else has any fixes in place? Or is this a known issue. Thanks Josh.
AVD with FSLogix - profiles not loading
Setup AVD with FSLogix several months back and profiles had been loading fine. About a month ago, profiles stopped loading and the logs show "Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced." This is in regards to connecting to the profile share path. If I manually try to go to that path, I receive the same error. The accounts do have a password, so it shouldn't be anything to do with a blank password. There are no sign-in time restrictions enforced on these accounts. What's left is a "policy restriction", which is kind of vague. Things I've tried: update to latest FSLogix verify permissions on profile storage enabled these in local policy: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options ‘Accounts: Limit local account use of blank passwords to console logon only‘ = disabled Computer Configuration > Administrative Templates > System > Credentials Delegation ‘Restrict delegation of credentials to remote servers‘ = disabled I have a ticket open with MS support for 3 weeks now, but thus far they've been completely useless.Old file server still present in registry on user profiles
We are running FSLogix 2.9.8884.27471 on Server 2022. Our domain controllers are all Server 2022. We just migrated to a new file server. The Citrix profiles are stored on a completely different server; we have not changed the Citrix profile file server. We only changed/migrated the general file server used for general file storage. After we powered off the old file server, Citrix users complained of "slowness" when using File Explorer. We discovered that there are a bunch of references to the old file server in each user's FSLogix profile registry. If we mount the FSLogix profile, when a user is logged out, and delete the references from a user's profile registry, the "slowness" issues with File Explorer, are resolved. The registry entries that seem to be present in each user's profile are located in the following: HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints 2 (there are a couple mount points still present for the old file server) HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders (we use GPO to redirect a users "Favorites" folder - the old file server is still listed in the "Favorites" registry entry, even though the GPO is setup to point to the new file server) HKU\FSL.VHD.****\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders (we use GPO to redirect a users "Favorites" folder - the old file server is still listed in the "Favorites" registry entry, even though the GPO is setup to point to the new file server) When we delete the "Favorites" entries, we find that after a user logs in/out, the "Favorites" entry updates properly to the new file server path. We can also remedy the File Explorer "slowness" by simply powering on the old file server. Again, all of the sharing on the old file server has been disabled. So it seems like as long as a user can "ping" the old file server, then that's all FSLogix needs to ensure that File Explorer works. This issue does not occur on physical Windows computers/servers- only with with FSLogix profiles. Instead of either leaving on the old file server powered on, or manually editing the registry in each user's profile, is there a way to remove (or update) these registry entries that point to the old file server?
