Why my FSLogix profile is not being created or loaded?

Published 04-13-2020 10:14 AM 8,691 Views

This is Gonzalo and I am one of the Support Escalation Engineers that works supporting FSLogix. Today I want to talk about a common situation that we observe here with our customers: FSLogix profiles are either not created or loaded.

After you successfully configure FSLogix following the Configure Profile Container, you realized that after several attempts FSLogix profile it is not loaded. Pressure to have this completed increases and frustration comes because you are not able to get this properly implemented, especially when it is super easy to configure! At this moment you decide to contact Microsoft Support.

After we collect FSLogix logs, we look at the Profile lo and we found lines like these ones:


[15:44:20.682][tid:00000a64.00001a84][INFO]             Reason set to 3: A local profile for this user exists on this system

[15:44:20.682][tid:00000a64.00001a84][WARN: 00000003]   Local profile already exists. Do nothing. (The system cannot find the path specified.)


This is an indication that a Local profile already exists, and it will take precedence over the FSLogix one and it will result in not having your FSLogix created. This will also impact you when you already have FSLogix profiles and they are not loaded. When this happens, users might complain that they have missing files like report that was created the day before. Since desktop might look similar, that document was stored in the local profile created in a previous session.

When you are already working with FSLogix and suddenly a local profile is created, most of the times it occurs because the location where you are storing your profiles was not reachable at the moment when the user was initiating session. You can observe that behavior looking at the profile log


[17:20:36.873][tid:00000f84.00000c20][ERROR:00000043]   FindFile failed for path: \\fileserver\perfiles\S-1-5-21-323565372-1197129236-3148194589-16601_ana\Profile*.vhd (The network name cannot be found.)

[17:20:36.888][tid:00000f84.00000c20][INFO]             Status set to 1: Cannot load user's profile

[17:20:36.888][tid:00000f84.00000c20][INFO]             Error set to 1064

[17:20:45.952][tid:00000f84.00000c20][INFO]             No user VHD has been attached. This is not a profile we should handle


You can easily look at the profile status in the computer by loading the FSLogix Profile status tool located in C:\Program Files\FSLogix\Apps. Open the frxtray.exe and then double click the icon in the system tray


FSLogix systray iconFSLogix systray icon


If there are any issues with the FSLogix profile, status tool will show a yellow light and inactive status.


FSLogix Profile status toolFSLogix Profile status tool


Clicking the Advanced view button and then going to the profile section you will get the profile log loaded


Advanced viewAdvanced view


If you need to delete a local profile, please do it using the User Profiles window by going Computer properties, Advanced system settings, Advanced and the under User Profiles click settings button. If the user it is not logged you will see that profile type will be listed as Local


User profilesUser profiles


I hope that this blog entry is helpful to you. Let us know what other topics you would like to see.

New Contributor

DeleteLocalProfileWhenVHDShouldApply Reg key is your friend if you want to FSLogix to force delete the profile.



Hi @Chan Nyein Ko Ko 


Thanks for your comment. You are absolutely right about using DeleteLocalProfileWhenVHDShouldApply to delete the profile and actually can also configure PreventLoginWithFailure=1. However, using an automated way to delete Local profiles can be dangerous because end users can be using local profiles without noticing and they could store data there (even in a single session). If you implement DeleteLocalProfileWhenVHDShouldApply you could be potentially deleting important information for the users.

Version history
Last update:
‎May 22 2020 06:57 AM
Updated by: