Forward and back mouse buttons broken when running as Admin

[Greylock]

I didn't want to file this under 'Bugs', as I'm not sure if it is, but when I run (portable) XYplorer as an administrator (xyplorer.exe > Properties > Compatibility > Run this program as an administrator) the back and forward buttons on my mouse stop working, just in XYplorer.

Any ideas whether this might be XYplorer related or just a Windows thing?

[bdeshi]

enter the following into the addressbar of XY when it's running as admin:

Code: Select all

::savesettings; setkey "1", "XButtonSupport", "Settings"; exit "nr";

XYplorer will restart, that's normal. Does it work now?

...only thing I can think of....

[Greylock]

Thanks for the quick reply.

I've just checked in my XYplorer.ini file and XButtonSupport is already set to '1' but I ran your code anyway, just in case, but it doesn't seem to have made any difference.

(I ought to have mentioned that the back/forward mouse buttons do work as long as I don't run XYplorer as an administrator.)

[bdeshi]

Which mouse do you use?

[Greylock]

A Logitech Performance MX

[bdeshi]

Bear with me. Do the buttons work in other apps when they're running as admin?

EDIT: and does the mouse have any companion software? I read on the Logitech site about an app called SetPoint. Do you have this? then what happens when you run SetPoint as admin?

[Greylock]

Good thinking! I've just tried running Chrome as an Admin and the buttons don't work.

I am running SetPoint so I think you might be right that running any app as an admin is preventing SetPoint from interacting with it due to the two programs effectively running as different users.

I'll try running SetPoint as admin now and see what happens (hopefully it won't just reverse the issue!)

[Greylock]

Success!

Closing SetPoint caused the buttons to work in both normal and admin modes so that proved that it was the cause of the issue. So, I ran SetPoint as an admin and voila, wotking back / forward buttons in XYplorer and Chrome as both normal and admin users.

Many thanks for your help!

[bdeshi]

Great!

I assume SetPoint runs at startup. If you're running Windows 8, it (setpoint) won't start up if it's set to always run as admin, via Properties->Compatibility.

[Greylock]

I am, but on Windows 7 so hopefully that won't prove to be an issue.