Has anyone come across this error? FSLogix 2210 hotfix 3 on WS2022

This is a known issue on WS2019, but not on WS2022. Try to execute the following code via Remote PS in your Image: $AllUserInboxAppsKey = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\InboxApplications" $AllUserApps = Get-ChildItem -Path $AllUserInboxAppsKey ForEach($Key in $AllUserApps) { Add-AppxPackage -DisableDevelopmentMode -Register (Get-ItemProperty -Path $Key.PsPath).Path } $AllUserAppsKey = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Applications" $AllUserApps = Get-ChildItem -Path $AllUserAppsKey ForEach($Key in $AllUserApps) { Add-AppxPackage -DisableDevelopmentMode -Register (Get-ItemProperty -Path $Key.PsPath).Path } https://learn.microsoft.com/en-us/fslogix/troubleshooting-appx-issues

@Balint Oberrauch We've contacted Sentinel One and are waiting to hear back.

i am having the same issue. it seems to work on the master image but not the clones. are you saying it AV related?

Can you elaborate on "it works on the master image"? The anomaly occurs after the second connection and the user must have an active FSLogix profile.

it works on the master image after the second connection by the user

You apply the same AV policy?

@Balint Oberrauch did this really work for you on w2k22?https://learn.microsoft.com/en-us/fslogix/troubleshooting-appx-issues