Problem:
There are no applications mounted in the disk manager
Symptoms:
In order to validate in this case if the issue is similar to the expected error, you can review for this in the FlexApp DIA log.
You first want to have debug mode logging on
See: https://support.liquidware.com/hc/en-us/articles/210632023-Where-To-Find-ProfileUnity-Logs
then obtain a diagnostic in debug.
Once extracted, under the user logs section you'll see a Main FlexApp DIA log.
The logs could show multiple application playback attempts or failures. The below error will show up in the client log indicating and issue accessing the token file.
Virtual Disk will not mount, InvalidOperation, The collection has been modified. The inventory operation might not be performed. is shown in the DIA log:
2025-10-11 09:49:08.533 [6] ERROR - write token error 'C:\FADIA-T\VHDW\7e9dd04001e7dfd8842466939087b999\S-1-5-21-2857351402-2812262531-3171228550-2597642.token', error 'IOException' 'The process cannot access the file 'C:\FADIA-T\VHDW\7e9dd04001e7dfd8842466939087b999\S-1-5-21-2857351402-2812262531-3171228550-2597642.token' because it is being used by another process.', skipping
Resolution:
It is possible that the user has the same application assigned in several different places within the configuration.
Please edit the LwL.ProfileUnity.client.exe.config file. It is a part of the client tools.
Please set the tow below values from True to False.
<setting name="FlexAppNonJitCutReplayInParallel" serializeAs="String">
<value>False</value>
<setting name="FilterParallelEvaluation" serializeAs="String">
<value>False</value>
</setting>
Additional considerations
If you're using a startup GPO that runs LwL.ProfileUnity.Client.Startup.exe from a shared location (typically \\domain\NETLOGON\ProfileUnity), to ensure that your changes to the client tools on the image are not overwritten please follow the below.
-
Backup the current contents of
\\domain\NETLOGON\ProfileUnity. -
Extract the
client-tools.zip -
Edit the
LwL.ProfileUnity.client.exe.configfile. It might be necessary to save the file outside the zip file and copy/replace once edited. Save/close the zip file. Make sure the zip file contains the changed file. Make sure the folder is zippedclient-tools.zip. It should not be left unzipped. Also, the client-tools folder should not be inside the zip folder. For instance, once extracted it should look like- Client.Net\Files vs Client.Net\Client.Net\Files
-
Reboot or force GPO update (
gpupdate /force) on target machines.Important: Always backup existing files before replacing them. Validate the
.configchanges in a test environment before wide deployment. If using both GPO and base image installs, ensure consistency in the config file across both.
Please note, 6.8.7 R2 HF1 has resolved the above issue. It is still advisable to check these settings in case they have been changed in the past.