Fences install on VDI seems to lock up all desktop icons

I logged in with my identity and I own a private Fences license I use at home, but this involves a license that my employer license group purchased so to begin with that license is only installed on this one VDI VM computer instance.

So the problem:   The Fences was installed and activated with the license key and the company email and no errors reported.  But having done that even without yet creating a fence, I suddenly cannot move a single icon on the desktop literally moving 3 inches over to an empty spot does the following:  mouse pointer does "busy circle", screen goes black, screen returns with blank blue background, busy circle continues, 10 seconds later all icons return but back in the original position, as if movement was denied.  Then I open customize fences, and remove the "Enable Fences" check and try again and the single icon moves 3 inches successfully.  I then add back the "Enable Fences" and the icon that moved jumps back to the original position.

SO - until I resolve this I have to leave Fences disabled and it is impossible to use.  Details: Fences is 3.1.3.3 and the VDI windows version is Windows 10 22H2.   Is Fences incompatible with these VM installations?  if you need details on the VDI type, I'll have to check with another team for that and the company probably would follow up at that point instead of me.

5,044 views 2 replies
Reply #1 Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 Top

OK - nevermind.  This is strange but the following fixed it.

1. We uninstalled the existing activated Fences software

2. We then re-installed it and again activated with the email and password.

Suddenly nothing is broken.

The only thing I can think of is that the first install we didn't know what email was used by the corporation to purchase this company license, so we did a few unsuccessful activations, but those unsuccessful were followed by learning what email was used and doing a successful activation.  You would not think that would cause a problem but it appears to have "activated" it but in a broken or locked state.