asked on September 22 Show version history

Note:  This problem was solved by Bruce Green, MultiMed Billing Systems, LF Wizard Extraordinaire. Hopefully this helps someone if they encounter this issue.


Running LF Win Client 10.4 in an AVD environment, we found that one user was unable to load the exe successfully.  All other users were unaffected.  Moreover, this started in the middle of the day - in the morning this user had no issues.  When she the clicked the icon, the client did not display itself, nor did an icon appear on the Taskbar. There was an instance of LF.exe in the process list, but it only shows 2.680K of RAM, and the instance was taking no CPU.



Turns out the LF Client had crashed, and it left temp file paths in the registry, pointing to a local copy of the user profile that was created by FSLogix at login, destroyed at logoff, and recreated under a different name at next login. Removing the temp file paths allowed LF to load properly.


If the above does not work, here is the initial debugging process from Ray Cruz, LF Support:

1. Are they (Azure Devops) logging the problem virtual desktop? If so, can we get those logs?
You'll need to get the DevOps to set it up. Once that is set, reproduce the issue and let us know what you find.
2. Get a list of installed applications on the Virtual Desktop.
Step 1: Open command prompt with admin rights. That is, type in cmd either in Start menu search box or in Run dialog box and hit Ctrl + Shift +Enter to open the command prompt with admin rights. Alternatively you can also go to All Programs > Accessories and right-click on Command Prompt and select Run as administrator.
Step 2: Click continue button if you get User Account Control (UAC) Prompt.
Step 3: In the Command Prompt, type "WMIC" and hit enter. Once you type hit enter
Step 4: Next, you need to type the following command and press Enter key to execute the same.
/output:C:\Users\Public\InstallList.txt product get name,version
Where "C" is the drive letter where Windows will store the installed applications list. You can also change the name of the output file and drive letter if you want to modify the output location. Also note that this should work in Windows 2000 & XP operating systems without problems.

2 0