FsLogix not creating User VHD

Question

I am currently in testing mode of AVD. I have 2 VMs in the hostpool which are Entra Joined (No Directory Services only Entra ID joined). We have installed the applications which are available for all the users. Now we want to implement FSLogix so that the user's profile and data can travel between the sessions. I have installed and configured the FSLogix but unfortunately it is not behaving as it should be. I am also attaching the log file of fslogix.Profile-20250605.log

Your kind help will be highly appreciated.

Regards,

Tariq Ghouri

Answer 1

Hello,

Your logs show multiple entries with the message "Local profile already exists, no action required." During the profile loading process, this likely indicates that the FSLogix Profile Container failed to mount correctly, causing the system to fall back to using a local profile.

Root Cause Analysis

1. Core Issue When a user logs in, FSLogix is expected to mount a remote VHDX container as the user’s profile storage. If this warning appears, it means:
   • FSLogix failed to mount the VHDX container
   • The system reverted to a local profile in C:\Users\<username>
2. Common Triggers
   • Permission Issues: User/computer lacks access rights to the shared storage.
   • Network Issues: Unable to reach the SMB share path.
   • Misconfiguration: The VHDLocations registry key points to an invalid path.
   • VHDX File Conflicts: Existing VHDX file is locked or corrupted.

Troubleshooting Steps

1. Verify If FSLogix Attempted to Mount the Container

• Check Log Entries Examine %ProgramData%\FSLogix\Logs\Profile\<username>.log for keywords:

  
    [Warning] Failed to attach VHD (Mount attempt failed)  
  
    [Error] Access is denied (Permission issue)  
  
    [Info] VHD located at \\path\file.vhdx (Verify path)  
  
  

  If no mount attempts are logged → Check registry settings.

2. Validate Shared Storage Accessibility

• Manual Mount Test On the VM, run as the test user:

  
    net use * \\storageaccount.file.core.windows.net\share /u:AZURE\storageaccount <StorageKey>  
  
  

  If failed → Check:
  • Storage account firewall rules (Allow AVD subnet/IP).
  • DNS resolution of the storage endpoint.

3. Check Registry Configuration

• Critical Registry Keys On the VM, verify (Path: HKLM\SOFTWARE\FSLogix\Profiles):

  
    Get-ItemProperty 'HKLM:\SOFTWARE\FSLogix\Profiles' | Select-Object Enabled, VHDLocations, VolumeType  
  
  

  • Enabled should be 1.
  • VHDLocations must point to a valid SMB path (e.g., \\storageaccount.file.core.windows.net\share).
  • VolumeType should be VHDX (unless otherwise specified).

4. Check Existing Profile Status

• VHDX File in Shared Storage Navigate to the share and confirm if the VHDX exists:

  
    \\storageaccount.file.core.windows.net\share\<user-SID>\  
  
    └── Profile_<username>.vhdx  
  
  

  If present but unmountable → Rename the old file and test with a new profile.

5. Deep Permission Check

• Storage Account Permissions
  • Computer Objects: Each AVD VM’s computer object needs access (Check in Entra ID).
  • User/Group: Test user’s group must have permissions (Use security groups).
• Share-Level Permissions Right-click the share → Configure permissions → Ensure:
  • Share-Level: At least Read/Write.
  • NTFS-Level (if applicable): Full Control (Verify via icacls).