Share via

FSlogix Not Recreating Profile After Deleting Corrupt One

John Blobacus 0 Reputation points
2025-04-30T19:47:05.4433333+00:00

I have a situation where a user was getting forced to use a temp profile while signing in. I found that the profile was having issues all over so i deleted it in the az fileshare we use to house the profile disks. But now for some reason the user signing in wont trigger FSlogix to recreate the profile, It just sits on a black screen saying "please wait" This is inspite of doing this successfully with another user today, deleting the profile and having fslogixs recreating it successfully

if i could get some help, id sure appreciate it

Thanks

Windows for business | Windows Client for IT Pros | User experience | FSLogix
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Daphne Huynh (WICLOUD CORPORATION) 160 Reputation points Microsoft External Staff Moderator
    2025-07-24T11:05:02.46+00:00

    Welcome to the Microsoft Q&A Platform and thank you for your question in here!

    Based on your description, it seems you are encountering an issue where FSLogix is not recreating a profile for a user after manually deleting the profile disk from the Azure file share. Instead of triggering FSLogix to generate a new container, the session gets stuck on a black screen with a "Please wait" message.

    This behavior typically suggests that FSLogix is encountering issues during the profile creation or mounting process. Since it worked successfully for another user, the problem may be user-specific or related to remnants from the previous profile.

    I would like to recommend a few troubleshooting steps that may help fix the issue.

    1.Ensure Local Profile Is Removed Completely

    Verify that the local copy of the profile (under C:\Users) for the affected user has been deleted.

    Also, check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList in the registry and remove any stale entries associated with the affected user’s SID.

    2.Check FSLogix Logs

    Review the FSLogix logs located at: C:\ProgramData\FSLogix\Logs\Profile Look for any errors or failed mount attempts that might explain why the profile isn't being created or attached.

    3.Verify Share Access

    Log in to the session host as the affected user (or an admin) and test access to the profile share: \<fileserver><profileshare> Ensure the user has both read/write NTFS permissions and Full Control share permissions.

    4.Confirm “Delete Local Profile When VHD Should Apply” Policy

    Make sure this policy is enabled to avoid local profile conflicts:

    Computer Configuration > Administrative Templates > FSLogix > Profile Containers > Delete local profile when VHD should apply: Enabled

    5.Check Profile Storage Quotas or Locking

    Ensure the user’s VHD(x) isn’t locked by another session or blocked due to storage quotas.

    Please let me know how it goes, I am happy to assist further if needed. Wishing you a successful resolution and a great day!

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.