FSlogix 2210 HF1 ignoring InstallAppxPackages registry setting?

[Rian_Devereaux]

Using the latest FSlogix 2210 HF1 (2.9.8440.42104) and I've noticed on logging on the wsappx service uses loads of CPU for around a minute or so. Having checked further into the logs, it shows a lot of AppX packages being checked on login, which is odd as I set the InstallAppxPackages dword registry key to 0 which should prevent this behaviour, but it appears it does not. Is this a known issue? Do I have to use group policy instead? Anyone else have this behaviour?

Really appreciate an answer to this as this creates quite an impact during early morning login storms, which in conjunction with the autoload of the abomination that is Teams, is causing me a real headache.

Just to add we're running VMware Horizon with Instantclones, and using both the profile, container and app masking components of FSlogix.

Cheers JD

[#2]

Me too.

I've read somewhere else that this is broken so I'm waiting for the next version to get it fixed

Regards

Ken Z

[#3]

I join the club with this issue. I just received the case (but customer is waiting for a resolution since over 2 months), they can work on similar environment where apparently the same patch level / FSLogix Agent / Citrix VDA and policies are the same. But on this small citrix delivery groups of 5 VMs (single-session, persistent), users must wait 10 minutes during logoff, and if they try to reconnect before 10-12 minutes, things get ever more messed up and Service Desk will need to intervene.

I can reproduce the problem, brand new test user and deleted all data on ProfilesList and c:\users.

Login is successful with clean status on FSLogix. 
Citrix Team was aware of the issue (FSLogix as well apparently since per default this option now is disabled) with the , but if set not configured, enabled or disabled, it seesm FSLogix try to execute it regardless. Checking at the same time the Application and System logs, I can confirm those 10 mins stalled are caused from this error, executed during EndShell.

FSLogix log:


[13:12:44.709][tid:000014a4.0000347c][INFO] ===== Begin Session: EndShell
[13:12:44.709][tid:000014a4.0000347c][INFO] User: S-1-5-21-1317981365-2265402352-3931857092-21215 (testuser)
[13:12:44.709][tid:000014a4.0000347c][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\LogonSyncMutexTimeout. Using default: 60000
[13:12:44.709][tid:000014a4.0000347c][INFO] Acquired end shell lock for user testuser (SID=S-1-5-21-1317981365-2265402352-3931857092-21215) (Elapsed time: 0)
[13:12:44.709][tid:000014a4.0000347c][INFO] Session configuration read (REG_SZ): SOFTWARE\Policies\FSLogix\ODFC\Sessions\S-1-5-21-1317981365-2265402352-3931857092-21215\ActivityId = '0337f8c0-880b-4a0d-9b37-ac823f7f2fa1'
[13:12:44.709][tid:000014a4.0000347c][INFO] Session configuration read (DWORD): SOFTWARE\FSLogix\Profiles\Sessions\S-1-5-21-1317981365-2265402352-3931857092-21215\LogonStage = '3'(EndShell)
[13:12:44.709][tid:000014a4.0000347c][INFO] Session configuration read (DWORD): SOFTWARE\FSLogix\Profiles\Sessions\S-1-5-21-1317981365-2265402352-3931857092-21215\InstallAppxPackages = '0'
[13:12:44.709][tid:000014a4.0000347c][WARN: 00000002] Failed to remove AppxPackage file: C:\Users\testuser\AppData\Local\FSLogix\AppxPackages.xml (The system cannot find the file specified.)
[13:12:44.709][tid:000014a4.0000347c][INFO] Session configuration read (DWORD): SOFTWARE\FSLogix\Profiles\Sessions\S-1-5-21-1317981365-2265402352-3931857092-21215\CleanupRecycleBin = '0'
[13:12:44.802][tid:000014a4.0000347c][INFO] ===== End Session: EndShell

I need to fix this Issue ASAP.

Since I got a test environment I can try to downgrade to FSLogix 2201 Hotfix2, but this will be a kinda big downgrade loosing other features maybe in use or with bugs solved in 2210 causing me even more problems.

If I  understood correctly if I want to "fix" this issue I need to re-register all apps?
Issues with AppX, MSIX or Microsoft store applications - FSLogix | Microsoft Learn


I didn't installed yet FSLogix 2210 Hotfix2, where the Group Policy template were updated. Maybe this will fix the issue too?

It would be of great help if anyone experiencing this issue could share their experiences to know in which direction should I move to fix (or wokaround) the issue.

Best Regards,