Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

FSLogix profile container not attaching: read the profile log, Status codes and Reason codes

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

When a user signs in and the FSLogix profile container does not attach, FSLogix records the failing step. Two places hold it: the profile log file on the Remote Desktop host, and a set of Status and Reason numbers stored in the host's registry for that user's session. Microsoft documents what each number means, so read them before any setting changes.

Read the profile log for the user's LoadProfile entry, note the Status and Reason, then match them to the table below. A Reason of 3 (a local profile already exists), a Status of 6 or 27 (the container location cannot be retrieved or found), and an error line of "Access is denied" are three of the documented paths, each with its own fix below.

What the error means

Microsoft says the Profile and Office Data File Cache (ODFC) containers set three values that describe the state of FSLogix for the signing-in user: Status, Reason and Error. They are stored per session in the local machine's registry. For the profile container the location is HKLM\Software\FSLogix\Profiles\Sessions\%sid%.

  • A Status is either normal or an error. Status 0 is STATUS_SUCCESS. Status 1 to 28 are errors such as "Can't retrieve virtual disk location" (6), "Can't attach to virtual disk" (12) and "Maximum sessions reached" (25). Status 100 (waiting for the Windows Profile Service), 200 (setup in progress) and 300 (already attached, differencing disks only) are normal.
  • A Reason clarifies the normal Status codes and is not used with the error codes. Reason 0 means "The container is attached".
  • The Error value, and the WARN and ERROR numbers in the log, come from Windows system error codes, because FSLogix made a Windows API call that failed.

Reason codes that explain a container that did not attach:

Reason Name Meaning on Microsoft's page
1 REASON_NOT_IN_WHITE_LIST User isn't a member of the include group
2 REASON_IN_BLACK_LIST User is a member of the exclude group
3 REASON_LOCAL_PROFILE_EXISTS A local profile for this user exists on this system
4 REASON_SHORT_SID Not an appropriate user type
7 REASON_WINDOWS_TEMP_PROFILE Profile is a Windows temporary profile
8 REASON_NOT_WVD_SESSION Session isn't an Azure Virtual Desktop Session
9 REASON_FAILED_TO_LOAD_PROFILE Profile load failed

Likely causes

Cause What you see How to confirm
Profile containers are not enabled, or no location is set No container is attempted when Enabled is 0; Status 6, "Can't retrieve virtual disk location", is the nearest documented code for a missing location Read the Enabled and VHDLocations values under HKLM\SOFTWARE\FSLogix\Profiles
A local profile already exists Reason 3 The Reason value for the user's SID; a profile folder for the user on the host
The user is outside the include group or inside the exclude group Reason 1 or 2 The Reason value; group membership
The share is unreachable or refuses the sign-in WARN or ERROR lines with an Access-is-denied or path-not-found text, and a Status in the error range The profile log lines around LoadProfile
A Windows temporary profile was created first Reason 7 The Reason value; Windows profile events on the host
A sessions limit is reached Status 25, "Maximum sessions reached" The Status value for the user's SID
Share hosting containers not upgraded for the Kerberos default change Access problems on the share after the change Microsoft's notice on the FSLogix pages; the share's Kerberos settings

Microsoft's FSLogix pages carry a notice that a Windows change in the April 2026 Windows Server update moves the default Kerberos encryption type from RC4 to AES-SHA1, and that file shares hosting containers that are not upgraded to AES-SHA1 might have access issues. The page does not describe a symptom or a check, and says customers already on AES-SHA1 are not affected.

Prove the cause before changing anything

Everything in this section reads.

1. Find the log. Microsoft names C:\ProgramData\FSLogix\Logs\Profile\Profile_%date%.log as the file used most when troubleshooting, and says the logging settings must be configured. The defaults on the configuration page are LoggingEnabled 2 (all log files on), LogDir %ProgramData%\FSLogix\Logs, LoggingLevel 1 (INFO, WARN and ERROR) and LogFileKeepingPeriod 2. The last one is the number of daily files kept, with a maximum of 180.

2. Follow one sign-in. Open the latest file and search for LoadProfile: %samaccountname%, substituting the user name, for example LoadProfile: jdoe. Check that the time matches the reported problem and note the process ID, which Microsoft says is used for the whole sign-in or sign-out sequence. Keywords worth highlighting are Begin Session: Logon, Begin Session: Logoff, loadProfile time: and unloadProfile time:. Each line begins with [INFO], [WARN:xxxxxx] or [ERROR:xxxxxx], and warnings and errors have a matching error code.

Microsoft's examples show the format: Status set to 28: No user session config found, Reason set to 0: The container is attached, and an error such as [ERROR:00000005] VirtualDiskAPI::CreateFormattedDisk failed to create vhd(x): ... (Access is denied.). A good sign-in ends with Status 0 and Reason 0. A bad one shows an ERROR line, a Status in the error range or a Reason of 1, 2, 3, 7 or 9.

3. Read the stored values. The cmdlet Get-ItemProperty reads a registry path. To read the user's session entry, find the user's SID with whoami /user in the user's own session, then read the key.

Get-ItemProperty -Path "HKLM:\SOFTWARE\FSLogix\Profiles\Sessions\<SID>"

Microsoft documents whoami /user as displaying the current domain, user name and SID. The Status, Reason and Error values appear in the output.

4. Read the settings.

Get-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\Profiles

On the configuration page, Enabled is a required setting (DWORD, default 0: containers disabled, 1: enabled), and VHDLocations is a required setting that holds a list of SMB locations to search for the user's profile VHD(x) file. If none exists, one is created in the first listed location. As a REG_SZ value, several locations are separated by semicolons.

5. Check the event logs. In Event Viewer, Microsoft puts FSLogix events under Applications and Services Logs, FSLogix, in the Admin and Operational logs under Apps. Cloud Cache has its own Admin and Operational logs.

Example (illustrative): on rds01, CONTOSO\jdoe gets a local-looking profile with no container. The user reports it on Monday, but the failure happened on Friday. With LogFileKeepingPeriod at the default 2, only two daily files are kept, and Friday is three days before Monday, so the Friday file is already gone. The Monday sign-in is tested instead and the log shows Reason set to 3: A local profile for this user exists on this system. Keeping 7 files would have held the Friday log for a week.

Fix

Change one thing at a time and sign in again after each.

Status 6 or no container attempted. Set Enabled to 1 and give VHDLocations a valid SMB path, in the policy or the registry, as the configuration page describes.

Disruptive step: enabling profile containers on a host changes how every user's profile loads on their next sign-in. Test with one host first. To back out, set Enabled to 0.

Status 27. Microsoft names it "Can't find virtual disk at the provided location". Check that the path in VHDLocations is spelled correctly and reachable from the host, and that the user's VHD(x) file exists there, using read-only checks first. Correcting the path in policy or the registry is a change. Disruptive step: every user's next sign-in uses the new VHDLocations value, so a wrong value stops profiles attaching for everyone. Back-out: put the old value back; users pick it up at their next sign-in.

Reason 3, local profile exists. Either remove the existing local profile or let FSLogix do it. The setting DeleteLocalProfileWhenVHDShouldApply (DWORD, default 0) set to 1 "deletes local profile if it exists and matches the profile container".

Disruptive step: Microsoft warns that when FSLogix decides a user should have a container and a local profile exists, it will permanently delete the local profile. There is no way back, so confirm that nothing in the local profile is missing from the container, and back up the profile folder first.

Reason 7, Windows temporary profile. The Reason says the profile is a Windows temporary profile, so read the Windows profile events on the host. The archived Windows event 1511 page ("Windows cannot find the local profile and are logging you on with a temporary profile") lists a corrupt local profile, lost permissions to the profile folders, a profile deleted by hand that left its SID in ProfileList, and antivirus scanning during sign-in. To stop users working in a temporary profile, FSLogix offers PreventLoginWithTempProfile (default 0). When set to 1 it loads the FRXShell and the user's only option is to sign out.

Risk: setting PreventLoginWithTempProfile to 1 stops every affected user from working at all until the cause is fixed, because they can only sign out. It protects them from saving into a profile that disappears. To back out, set it to 0.

Reasons 1 and 2. The user's group membership decides this. Correct the membership or the include and exclude group configuration.

Risk: a membership or group-configuration change decides whether a user gets a container at the next sign-in, and it applies to everyone in that group. Impact: a wrong change moves other users into or out of FSLogix. Back-out: write down the current membership and the include and exclude settings first, and restore them if the result is wrong.

Access denied or path not found. Check the share and folder permissions for the account named in the log line, and the path in VHDLocations. Microsoft's example for access denied shows the failing path, so test the same path from the host.

Risk: if you change a permission on the share, you change who can open every user's container there. Back-out: record the existing permissions first and put them back if the sign-in does not improve.

Status 25. Microsoft names it "Maximum sessions reached" and the page gives no further detail, including which limit applies. Read the lines around it in the profile log before changing anything.

Confirm the fix

Sign in again as the same user and read the new LoadProfile entry. A fixed attach ends with Status 0 and Reason 0 ("The container is attached"). Read the Sessions key again for the same values, and check that the container's VHD(x) file now exists in the first location listed in VHDLocations.

Check a second user and a user who signs in after the first signs out, so the fix is proven for more than one sign-in.

What to watch afterwards

  • Raise LogFileKeepingPeriod so a failure is still on disk when someone investigates it. Risk: more daily log files stay on each host's disk; to back out, set the value back to 2.
  • Set LoggingLevel to 0 (verbose) only for a short investigation. Risk: verbose logging writes more data on every sign-in; to back out, set it back to 1.
  • Moving the logs with LogDir needs a reboot of the host or a restart of the FSLogix service, according to Microsoft. Disruptive step: that restart affects users signing in meanwhile; do it when no one is signing in, and back out by setting LogDir back and restarting again.
  • Count Reason 3, Reason 7 and Status 6 across hosts after a change, using the same search text in each log.
  • Watch for access problems on the share around the Kerberos change that Microsoft's notice describes.

Risks and limits

These commands have not been run or lab-tested. The codes covered are those Microsoft publishes; container locks, container size and storage performance are separate faults and are not covered. Microsoft's page states that Event Trace Logging files are for Microsoft internal use only.

Microsoft's logging page does not list event IDs, so none are quoted here. The codes in the log lines come from Windows, and the page links its own guide for decoding a system error code. Deleting a local profile and enabling DeleteLocalProfileWhenVHDShouldApply cannot be undone.

Sources