Hi everyone, Has anyone found a solution to the repeated AppX package registration during logon on Windows 11 non-persistent VDIs using FSLogix? Since the AppX registration state is stored at the machine level, FSLogix re-registers around 100 packages at every logon. In our environment, this blocks the Winlogon process for approximately 15–25 seconds. We've tested different FSLogix versions and also tried setting InstallAppxPackages=0, but neither had any noticeable impact on the overall logon time. Citrix UPM already provides a solution for this issue using a persistent AppRepository disk:

With the Enable AppX package load acceleration policy enabled, Profile Management creates a virtual disk container for each machine to store the UWP app registration data. This feature accelerates the loading of UWP apps and prevents data loss on machine restarts.

Reference: Enable UWP app load acceleration | Profile Management 2603 Has anyone encountered the same issue or found a comparable workaround for FSLogix? Any insights or suggestions would be greatly appreciated!

I'm experiencing the same problem on Windows Server 2025. But I haven't found a solution yet.

Remove them all from the image. Job done

But wouldn't removing all AppX packages from the image impact the user experience? What happens if users need apps like Calculator or Photos during their sessions?

Give them OldCalc which restores the Windows 7 one and use something else for Photos or whatever else they want. Removing AppX apps is my goto, they do nothing but make the overall UX suck

I'm with Rankin on this. find alternatives.

would that break Teams?

Teams is probably your only outlier. But I install that after the "get rid of all Appx apps" stage of build. Pre-staging Teams used to be possible but not sure it is with the sh*t new version

I script the install of new teams, and updates monthly.

Same for us, no delay because appx, W25

depends on how scorched earth you want to go. you could just disable appreadiness services. however, you will still need to load up anything cred handling, like AADL, maybe some frameworks. all app-x aren't MS bloat, some are system needed items. as for saving the "install" its tagged to the user/machine in the HKLM keys. so even if you did persist the items from desktop to desktop, and new desktop would run again.