I've never seen this error message but it might be related to using shared drives for the Passolo projects or maybe the user profiles.

You can try and move the projects on a local drive for the VM and see if this helps.

Thank you Adrian. We have used shared drives for the projects for years, but it's only since we switched to WVD that these problems appear, so I think it's the multi-instance use of the app that causes the problem. I'll try moving projects to the VMs, but that's not really a long-term solution as the VMs are in a pool that users get allocated to.

Shared drives or shared resources shouldn't be used for accessing projects or files. Did you ever spend a thought about version management tools? In my opinion this is the most suitable way for a stable work environment with very less data loss.

Can you please attach a screen shot of the error message? It doesn't look like an original Passolo message, maybe it is coming from WVD.

As the tool wasn't explicitly tested and released on WVD it might be something where your IT must introduce measures so that data like registry settings or all the configuration files are kept separate between sessions that run in parallel.

Thank you Achim. Error message below.

I agree that it is likely that we need to reroute the settings, just trying to figure out what exactly.