Anyone have a solution for FSLogix not being able to attach the profile, when connecting via eSSO in workspace app (cr) on 24H2 Win11 with EnableMPR = 1? I'm asking in this channel and not the fslogix channel, because it works fine if we: a) do not use sso in the workspace app and provide username + password manually b) use the storefront website c) downgrade the client to 23H2 The VDA is Windows Server 2022 with Citrix VAD 2503 and FSLogix 3.25.626.21064. It all does not matter though, because we also see the same problem with CVAD 2407 or older FSLogix versions. Enhanced SSO is enabled on the client via Group Policy. FSLogix Error in the screenshot basically says "could not connect to a domaincontroller". VDA throws a bunch of LSA 40970 and 40960 errors during the error, stating "authenticationfailure for server cifs/domaincontroller" and "not enough systemressources to complete the API call (0xc000009a)".

Did you try this one: Windows Registry Editor Version 5.00 ; ------------------------------ ; FSLogix Profile Container Settings ; ------------------------------ [HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles] ; Wait for the network to be available before attempting to attach the profile "WaitForNetwork"=dword:00000001 ; Ensure the User Profile Service is fully initialized before FSLogix starts "WaitForUserProfileService"=dword:00000001 ; Increase the number of retries FSLogix will attempt to locate and attach the VHD "ProfileRetryCount"=dword:00000014 ; 20 retries ; Time (in seconds) between each retry attempt "ProfileRetryInterval"=dword:00000005 ; wait 5 seconds between retries ; ------------------------------ ; FSLogix Office Container Settings (optional – if used) ; ------------------------------ [HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\ODFC] ; Apply same wait logic for Office containers if enabled "WaitForNetwork"=dword:00000001 "WaitForUserProfileService"=dword:00000001

The issue only happens, when the ClientOS is Win 11 24H2. It does not happen with Win 11 23H2.

Thanks @Arthur. We can try the waitfornetwork and waitforuserprofileservice settings -maybe that helps. As @Marco Hofmann stated, it only happens with Client OS Win 11 24H2 and should not need such settings. We never used them at our customers; same for the retry settings. Our experience showed, that FSLogix either works and the profile attaches, or it doesn't. If it does not attach, then retries won't help, because theres something fundamentally broken that needs to be fixed.

Report it to vendor - Microsoft 😉

you'd have better luck telling copilot