FSLogix keeps creating new profile container (Create Formatted Disk) after nightly reboot – only for one user

FSLogix keeps creating new profile container (Create Formatted Disk) after nightly reboot – only for one user

Post:

Hey everyone,

I’m running into a strange FSLogix issue and wondering if anyone has seen this before.

Environment:

• FSLogix Profile Containers on Windows Server 2022 RDSH

All other users work fine, containers are mounted normally (AttachVirtualDisk success).

For one user everything works fine during the day, but after the nightly server reboot (03:00), the next logon shows this in Profile-*.log:

[08:41:57.152] Profile VHD not found. Creating new VHD.
[08:41:57.465] Created vhd(x): \\<server>\FSLogix_Profiles$\<user>_...\Profile_<user>.VHDX
[08:41:57.871] Create Formatted Disk
[08:42:00.621] Format complete
[08:42:01.746] Attached vhd(x) successfully
[08:42:02.294] Mounted: ...Profile_<user>.VHDX
[08:42:02.465] User Profile Path: C:\Users\<user>.FSL0

After that, the user gets a completely fresh profile. At logoff, FSLogix also logs that it removes the local profile:

[09:01:49.277] Directory removal queued: C:\Users\local_<user>
[09:01:49.277] Profile removed for sid ...-5762

Additional context:

The AD user account was recently re-created.

Share and NTFS permissions are correct (user + SYSTEM + session hosts = Full Control)

DeleteLocalProfileWhenVHDShouldApply = 1 (default setting)

No .lock file left behind

No issues for any other users

So essentially, every time the servers reboot at night, FSLogix creates a completely new container for this user instead of attaching the existing one.

Question:

Has anyone seen FSLogix do a full “Create Formatted Disk” on every logon like this?

Any tips on what else to check when it only affects a single user?

Thanks in advance!FSLogix keeps creating new profile container (Create Formatted Disk) after nightly reboot – only for one user

Post:

Hey everyone,

I’m running into a strange FSLogix issue and wondering if anyone has seen this before.

Environment:

FSLogix Profile Containers on Windows Server 2022 RDSH

All other users work fine, containers are mounted normally (AttachVirtualDisk success).

For one user everything works fine during the day, but after the nightly server reboot (03:00), the next logon shows this in Profile-*.log:

[08:41:57.152] Profile VHD not found. Creating new VHD.

After that, the user gets a completely fresh profile.
At logoff, FSLogix also logs that it removes the local profile:

[

Additional context:

The AD user account was recently re-created.

Share and NTFS permissions are correct (user + SYSTEM + session hosts = Full Control)

DeleteLocalProfileWhenVHDShouldApply = 1 (default setting)

No .lock file left behind

No issues for any other users

So essentially, every time the servers reboot at night, FSLogix creates a completely new container for this user instead of attaching the existing one.

Question:

Has anyone seen FSLogix do a full “Create Formatted Disk” on every logon like this?

Any tips on what else to check when it only affects a single user?

Thanks in advance!