Issue with AVD User Profile – FSLogix Not Recreating

Try below to fix:

1.    Verify NTFS Permissions
   o    Ensure the user has Full Control on their profile folder path.
   o    Check that the FSLogix service account (if applicable) has access.
   o    Confirm inheritance is applied correctly.
   2.    Check Group Policy / Account Restrictions
   o    Review policies applied to the user: 
       Password complexity and expiration.
       Logon hours restrictions.
       Conditional access rules.
   o    Ensure none of these prevent sign-in.
   3.    Validate Storage Account Integration
   o    Confirm the storage account is joined to AD DS (if using hybrid identity).
   o    Run nltest /dsgetdc:<domain> from the session host to verify domain connectivity.
   o    Test access manually: net use \\<storageaccount>.file.core.windows.net\userprofiles.
   4.    Inspect FSLogix Logs
   o    Located under C:\ProgramData\FSLogix\Logs\Profile.
   o    Look for errors beyond “FindFile failed” (e.g., authentication failures, access denied).
   5.    Clear Residual Profile Data
   o    Remove any leftover registry entries under HKLM\SOFTWARE\FSLogix\Profiles.
   o    Ensure no stale .VHD or .VHDX files remain in the share.
   6.    Test with Another User
   o    Try assigning another test account to confirm if the issue is user-specific or systemic.
   7.    Update FSLogix
   o    Ensure you’re running the latest FSLogix version, as older builds have known issues with Azure Files integration.

FSLogix documentation - FSLogix | Microsoft Learn

Configure profile containers - FSLogix | Microsoft Learn

Store FSLogix profile containers on Azure Files and AD DS or Microsoft Entra Domain Services - FSLogix | Microsoft Learn

Troubleshooting with Logging and Diagnostics - FSLogix | Microsoft Learn

Known Issues - FSLogix | Microsoft Learn

When an FSLogix profile doesn’t recreate after deletion, it usually means the session host cannot create or mount the VHD(X) file. This is normally caused by identity or permission issues rather than FSLogix itself.

The log message indicates that the session host cannot find or create the profile container and that some account restriction is preventing the sign-in operation.

Common causes include:

• Missing NTFS permissions on the profile share. Even if the user has Storage File Data SMB Share Elevated Contributor, FSLogix still requires explicit NTFS permissions. The user must have Full Control at the NTFS level, and the FSLogix service accounts and SYSTEM also need Full Control.
• Kerberos or hybrid identity issues. In hybrid AVD, if the session host is unable to obtain a valid Kerberos ticket for the user, the share cannot be accessed and the VHD cannot be created. Clock skew, sync delays, expired passwords or join issues can trigger this.
• Leftover folders from the old profile. Sometimes a folder with the username or username.sid remains in the share. FSLogix will refuse to create a new VHD if it detects remnants that do not match the expected naming pattern.
• Profile configuration mismatch. If settings changed between Profile and ODFC containers or the naming pattern was modified, FSLogix may be looking for a container that no longer matches the configuration.

Recommended checks:

• Validate NTFS permissions directly on the file share. RBAC alone is not enough for FSLogix.
• Clear Kerberos cache on the host with “klist purge” and check hybrid identity health.
• Remove or rename any leftover folders in the profile path.
• Enable FSLogix verbose logging to see exactly where creation fails.

These steps usually identify why the profile does not recreate after deletion.