Corruption of Windows 10 Start Menu - Issues with FSLogix and Citrix WEM ? RRS feed

  • Question

  • We recently deployed FSLogix App (v2.9.7117.27413) in our Windows 10 pooled VDI environment using both Profile and O365 Containers. This has been working very well, but we have noticed issues once we install Citrix Workspace Environment Manager (v1906).

    The start menu goes back to Windows internal shortcuts only. Stopping & starting explorer.exe temporarily resolves the main issue, and other applications then appear as new items in the start menu, and the pin items to Start option is restored.

    Currently we have no policies setup / applying in Citrix WEM.

    We built in a delayed explorer.exe stop/start into the user logon to get around the issue.

    Citrix WEM installed on a machine without FSLogix doesn't appear to have this problem. Similarly a machine with just FSLogix works fine.

    Is anyone else aware of this problem, or have any suggestions to resolve this apparent conflict between the two programs ?


    Friday, August 23, 2019 2:01 PM

All replies

  • Hello,

    Have you created a ticket about this issue? I think we will need to look into the logs with the support tool more to figure out what is going on. Here is where you can create ticket if you have not done so already please Open an FSLogix ticket.

    If this issue is happening even without FSLogix, you will need to Open a Citrix ticket.

    Wednesday, August 28, 2019 12:49 AM
  • After some trial and error it seems like this might be to do with the Citrix WEM agent not being linked/configured. Once we configured the agent and linked it to the WEM Infrastructure server we saw the Windows 10 Start Menu being presented consistently. Checking against Win10 v1709 & Win10 v1809 configurations.

    David Lock

    Wednesday, August 28, 2019 8:22 PM
  • Did you find the root cause? I have the same problem but my WEM is configured
    Tuesday, December 8, 2020 7:58 AM
  • We continued to use a delayed explorer.exe stop/start during the user logon to get around the issue.

    We will revisit again now we are moving to Win10 v1909 and have upgraded our WEM infrastructure and agent (v2009). Initial testing that our original issue has gone with this setup.

    David Lock

    Tuesday, December 8, 2020 9:00 AM