Dexpot Forum

Hi!

Yesterday I let the system upgrade my Dexpot to the latest version.
After this upgrade, Dexpot and synergy no longer work.

I run a synergy server on another machine, whose keyboard and mouse is shared to my Win7 64bit machine (a laptop) which is running Dexpot.

Win7 and Dexpot starts as usual and I can move the mouse pointer from my other machine's screen into the Win7 desktop. So far everything is fine. But...
As soon as I change the desktop (or do anything that has to do with Dexpot, like right-clicking on the tray icon), the remote mouse and keyboard immediately stop working.
I have to switch to the local mouse and keyboard on the Win7 machine itself to continue, and once I have pressed some keys and used the mouse, the remote keyboard and mouse start working again within this desktop. When I change from this desktop (or click the Dexpot tray-icon), again the remote keyboard and mouse stop woring.

Dexpot has been running fine with synergy for years, so someting has changed in this latest update.
Can you please investigate?

Do I really have to install it in a non-default location, or do you think you can correct the problem instead?

Do you already know what is happening and what the problem is?



The only time anything simillar is happening (loosing contact witht he remote kbd/mouse) is when I start an application as another user (usually Administrator). When this new window has focus, synergy don't work, forcing me to use the local kbd/mouse when confirming and doing stuff as Administrator. As soon as a process that I own myself, remote kbd/mouse work fine.

Perhaps the new version of Dexpot is calling some function that is not in my own user context, and therefore synergy stop working?

Exactly, it's a UAC security "feature". When installed to Program Files, Dexpot now runs with something called UIAccess. That's basically an "administrator light" mode that allows us to manage windows of other applications running elevated. It also has all sorts of ridiculous side effects, like blocking mouse hooks of other applications, which is what's happening here. We'll probably remove it again in the next version, but until then your best option is to move Dexpot out of Program Files.

Thanks for the swift response.

Nice to know that you're already ontop of the problem.

I'll reinstall Dexpot, pending the next version.

Thanks for the updated version without UIAccess. It's working fine.