FSLogix and Memtime: Enable "Wait for Profile" Option

This guide explains how to ensure that Memtime starts only after the FSLogix user profile is fully attached.
This prevents issues with missing data, incorrect paths, or multiple sessions on RDS or terminal servers.

Background

In environments using FSLogix, the user profile is attached after logon.
If Memtime starts too early, it may:

1. Start before the profile is available
2. Use incorrect paths
3. Create temporary local data
4. Cause conflicts in multi-user environments
   
   

To avoid this, Memtime must start only after FSLogix confirms that the profile is ready for the current user.

This option blocks the user login until the FSLogix profile is fully loaded.

Registry path:

HKLM\SOFTWARE\FSLogix\Profiles

Required values:

1. Enabled = 1

2. PreventLoginWithFailure = 1

3. FlipFlopProfileDirectoryName = 1

4. WaitForProfileTimeout = 60 (seconds)

Result:

1. Explorer and autostart applications only start after the profile is mounted

2. Prevents empty or incomplete AppData folders