FSlogix Profiles Not Loading

Question

FSlogix Profiles Not Loading

Manoj Chauhan 65

Hi Team,

I have created a new host pool with 5 VMs with Windows 11 Multi-Session OS.

FSLogix is installed and also edited the relevant registry setting's.

The VMs are domain joined but whenever a user is logging in, a local profile is created instead of the once from the FSlogix user profile containers.

The users accessing the said host pool have the remote access permissions and also have access to the SMB Shares, Please find the attached screenshot below: Error_snap

Please help !!

Regards,

Manoj.

Adam Zachary 2,255 Reputation points

2025-12-08T20:52:24.03+00:00
I’ve seen this exact situation a few times when teams deploy new host pools. Everything looks right, FSLogix is installed, registry keys are there, shares are accessible, but users still get a local profile. Every time, it came down to one of a few missing pieces that FSLogix is very picky about.

First thing to check is whether Enabled=1 is actually being applied under HKLM\SOFTWARE\FSLogix\Profiles. I’ve had customers push the setting through Intune or GPO, but the VM ended up with conflicting registry values in another path. The setting must only exist under the Profiles key.

Second, make sure the VHDLocations path is reachable from SYSTEM, not just the user. This is a common trap. If the host pool VM can’t access the share as the machine account, FSLogix silently falls back to a local profile.

Finally, confirm the user is in "FSLogix Profile Include Group" or that you haven’t accidentally enabled the exclude mode. One of my customers hit that recently and it looked exactly like what you’re seeing.

Typically, when FSLogix installs fine but loads a local profile, it’s almost always one of three things:

Wrong registry path

Machine account not having storage permissions

Or include/exclude settings blocking the user.

Check it out and let me know please
Manoj Chauhan 65 Reputation points

2025-12-09T12:25:21.8433333+00:00
@Adam Zachary Thanks for the quick response. All the parameters seem to be correct in my case but still facing issues.
Manish Deshpande 1,330 Reputation points Microsoft External Staff Moderator

2025-12-09T19:16:48.9433333+00:00

Hello Manoj Chauhan

Could you please provide the details i have requested over the private chat pls?
Manoj Chauhan 65 Reputation points

2025-12-10T00:11:10.0166667+00:00

@Anonymous Seems like adding the regkey DeleteLocalProfileWhenVHDShouldApply=1 under HKLM\SOFTWARE\FSLogix\Profiles is working, now i can see my fslogix profile loading.

1 answer

Your answer

Adam Zachary 2,255 Reputation points

2025-12-08T20:52:24.03+00:00

I’ve seen this exact situation a few times when teams deploy new host pools. Everything looks right, FSLogix is installed, registry keys are there, shares are accessible, but users still get a local profile. Every time, it came down to one of a few missing pieces that FSLogix is very picky about.

First thing to check is whether Enabled=1 is actually being applied under HKLM\SOFTWARE\FSLogix\Profiles. I’ve had customers push the setting through Intune or GPO, but the VM ended up with conflicting registry values in another path. The setting must only exist under the Profiles key.

Second, make sure the VHDLocations path is reachable from SYSTEM, not just the user. This is a common trap. If the host pool VM can’t access the share as the machine account, FSLogix silently falls back to a local profile.

Finally, confirm the user is in "FSLogix Profile Include Group" or that you haven’t accidentally enabled the exclude mode. One of my customers hit that recently and it looked exactly like what you’re seeing.

Typically, when FSLogix installs fine but loads a local profile, it’s almost always one of three things:

Wrong registry path

Machine account not having storage permissions

Or include/exclude settings blocking the user.

Check it out and let me know please
Manoj Chauhan 65 Reputation points

2025-12-09T12:25:21.8433333+00:00

@Adam Zachary Thanks for the quick response. All the parameters seem to be correct in my case but still facing issues.
Manish Deshpande 1,330 Reputation points Microsoft External Staff Moderator

2025-12-09T19:16:48.9433333+00:00

Hello Manoj Chauhan

Could you please provide the details i have requested over the private chat pls?
Manoj Chauhan 65 Reputation points

2025-12-10T00:11:10.0166667+00:00

@Anonymous Seems like adding the regkey DeleteLocalProfileWhenVHDShouldApply=1 under HKLM\SOFTWARE\FSLogix\Profiles is working, now i can see my fslogix profile loading.

Answer 1

@Manoj Chauhan - Thank you for reaching Microsft QnA support

From screenshot the two required registry values exist under HKLM\SOFTWARE\FSLogix\Profiles (Enabled=1 and a VHDLocations UNC)

Microsoft’s documented requirements for profile containers - Configuration Setting Reference

C:\Program Files\FSLogix\Apps\frxtray.exe shows a green status and the user as “Logged in – Profile” rather than “Inactive”.

The share path in VHDLocations is reachable and browsable from that host under the user’s context (use runas /user:domain\user "explorer.exe" or log on with a local profile and test)

Store FSLogix profile containers on Azure Files and Active Directory Domain Services or Microsoft Entra Domain Services - Store FSLogix profile containers on Azure Files and Active Directory Domain Services or Microsoft Entra Domain Services

If frxtray is inactive or the share is not reachable from that user context, FSLogix will skip attaching and Windows will create a local profile -

Why my FSLogix profile is not being created or loaded?

FSLogix will not attach a container if a standard local profile is already present for that user.

We can suggest trying: Delete the user’s local profile via System Properties > Advanced > User Profiles (do not just delete the folder) and log in again.

Optionally set DeleteLocalProfileWhenVHDShouldApply=1 under HKLM\SOFTWARE\FSLogix\Profiles so FSLogix automatically removes any matching local profile when it should attach a container

If you use FSLogix Profile Include List / Exclude List (Group Policy or registry), make sure the users or groups are in the Include list (or those settings are not configured at all) and if an exclude list applies, FSLogix will intentionally skip the user, and you will see only a local profile

Even if users can browse the share from another machine, the session host’s computer or you may not actually have NTFS and share rights required for container folders and VHDX creation.

For domain‑joined AVD with Azure Files: Microsoft requires at minimum:

Share “Storage File Data SMB Share Contributor” (or equivalent) for the user/group.

NTFS: User has Full Control on their own profile folder; at root, typically “Creator Owner – Full control (subfolders and files only)” and users are not granted list access to other users’ folders. Re-test by creating a folder and a dummy file in the exact path under the affected user account.

AVD + domain join vs Entra‑only:

Since your VMs are classic domain‑joined, should follow the “FSLogix with Azure Files and Active Directory” guidance; please check you are not mixing in the Entra‑only configuration (which uses a different auth path).

Prerequisites for Virtual Desktop

Microsoft Entra joined session hosts in Azure Virtual Desktop

Regards

Himanshu

Manish Deshpande 1,330 Reputation points Microsoft External Staff Moderator

2025-12-10T19:18:47.25+00:00

Hello Manoj Chauhan

Thanks for update Manoj Chauhan, As the issue was resolved. Could you please accept the answer and upvote it. So, it will be helpful to community members.

Share via

FSlogix Profiles Not Loading

1 answer

Your answer