If users receive "The user profile failed to attach" FSLogix error when logging in, follow these troubleshooting steps.
- Ensure the FSLogix services are running on the WVD session host or dedicated WVD instance
- Ensure your storage for FSLogix profile containers has available storage. In NFA deployments, FSLogix containers are store on the FS01 data disk (E: drive).
- Log into the desktop and wait until you see the above error.
- Press CTRL-SHIFT-ESC to open Task Manager, go to File>Run new task and type in explorer.exe and click OK.
- Using the new File Explorer window browse the the UNC specified in Nerdio Manager for MSP Settings > Integrations page under the FSLogix Profiles Storage location.
- If you are able to browse to the path, try creating a folder in that location. If unable to, then Share or NTFS permissions are incorrectly set.
- Set SHARE permissions to Everyone or Authenticated Users - Full Control
- Set NTFS permissions per Microsoft guidance - https://docs.microsoft.com/en-us/fslogix/fslogix-storage-config-ht
- If you are NOT able to browse to the path then either the path, name resolution or networking is incorrectly specified.
- Verify that you can browse to the path from another computer
- In Task Manager>File>Run new task, type cmd.exe and click OK. Ping the hostname and make sure it resolves and replies.
- If you receive access denied, you likely need to fix or add Shared Contributor SMB role to the user(s) logging in. See "Assign Azure RBAC permission to storage account" here https://techcommunity.microsoft.com/t5/windows-virtual-desktop/fslogix-profile-container-using-azure-files-and-domain/m-p/1311180 if that's the case.
- If you ARE able to browse the path and created a folder then verify that the user's profile VHD(X) file isn't locked by another session. By default, FSLogix profiles are configured to be exclusively locked by the first session that mounts the profile. If a user is already logged into another host pool then the profile is locked. Concurrent access to profiles is supported by FSLogix but there are trade-offs to consider. You can find more information from Microsoft in this KB.
- In addition to browsing the FSLogix logs in event viewer, you can also access the text logs. Either of these locations will give you very helpful error information.
- For the text logs: browse to \\Yourpoolhost\c$\ProgramData\FSLogix\Logs\Profile\ and view the profile*.log files.
- See FSLogix logging documentation for more information.