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.
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?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.How to fetch username or userEmail from userprofile details of FSLogix
Hi I am trying to fetch several details from FSLogix userprofile like disk size usage , last accessed date. I need to get user details as well like Username or UserEmail. Below is the PS Snippet that I am using. $Profiles = Get-ChildItem -Recurse -Path $FileSharePath -Filter "*.VHDX" -ErrorAction Stop | ForEach-Object { [PSCustomObject]@{ UserGPN = ($_.Name -split '_')[1].Split('.')[0] FileShareName = ($_.FullName -split '\\')[3] FileName = $_.Name TotalSizeInGB = $DriveSizeGB ConsumedSizeInGB = [math]::Round($_.Length / 1GB, 2) FilePath = $_.FullName CreationTimeUtc = $_.CreationTimeUtc.ToString() LastAccessTimeUtc = $_.LastAccessTimeUtc.ToString() LastWriteTimeUtc = $_.LastWriteTimeUtc.ToString() } } How can I get that ? Kindly help! Thanks Hirdesh
FSLogix Error 1326 The username or password is incorrect
Hi all, I need your help with this one. I am currently implementing FSLogix in an AVD environment, as I did dozens of times before. But this time I ran into a strange Issue. The error I am getting is: My current setup is: - Hybrid joined VMs - Storage account joined to OnPrem - Active Directory Domain Services (AD DS) Identity is enabled on the storage account via Terraform - All Users and Groups are hybrid - Azure Infrastructure is deployed with Terraform - Hosts and Users are managed via GPOs I already found this Tech Community Post, but the suggestions there unfortunately did not help me. My troubleshooting steps up until now where: Redeploying the storage and the VMs Checked FSLogix, NTFS and IAM settings Deploying an Microsoft Entra Kerberos authentication enabled storage account -> same issue Checked that the Kerberos encryption algorithm of the client and the storage match -> client allows all algorithms, storage is set to max compatibility Created a new computer object in the domain and used it for the domain join via Terrraform Checked that storage account is joined to AD -> here I got an interesting find: Here the AccountType and SamAccountName are missing, I checked this in another environment, there they are displayed correctly BUT this does not explain to me why the Entra Kerberos enabled storage account got the same error Many thanks for reading all of this. Do you guys have any ideas and suggestions what I could try?FSLogix Blog Update: FSLogix release changes and Windows multi-session updates in Azure Marketplace
Tired of checking and installing FSLogix after deploying your Session Hosts with a Windows multi-session image from the Azure Marketplace? As of August 8th, 2023 (patch Tuesday), these images will come with the latest version of FSLogix already installed. This means that you can skip the hassle of installing or updating FSLogix on your virtual machines and enjoy it's amazing features right away. Read the full post on the FSLogix Blog!
FSLogix Event ID 26
FSLogix Error 26 Failed to run export action on OneNote registry for file eula.reg (The system cannot find the file specified.) Has anyone ever found a fix for this? Disabling OneNote integration gets rid of the first error of course...but at what cost? I don't know any fix for the second one.
