Lenry
8 discussion posts
The title basically says everything.
I have a three monitor setup, where my primary monitor is a TV (I play games on it, they always start on the primary screen).
Because of this every newly started software opens a window on the TV which isn't always on. The "move to next window" function is great (it was the main reason I bought DisplayFusion), but it does nothing on windows started with admin rights (for e.g. an installer).
What did I miss?
Windows 10 x64, DisplayFusion Pro 7.3.2 Steam version
Lenry
8 discussion posts
thank you for the reply.
here's the file you asked for
• Attachment [protected]: displayfusion_debug.txt [71,387 bytes]
Thanks! When you start an installer or something that needs admin rights, are you prompted for a user/password, or do you just get the standard Yes/No UAC dialog?
Lenry
8 discussion posts
Just the UAC dialog
sorry, actually none of that. I disabled the UAC prompt.
Jan 5, 2016 (modified Jan 5, 2016)
•
#5
Ok, the troubleshooting info says UAC is enabled. Did you just disable it? If so, have you rebooted since you disabled it?
Lenry
8 discussion posts
no, it's been like this since I've installed Windows 8.1 (from which I upgraded to W10, when it was released)
I set the slider in the User Account settings to "don't bother me with notifications" or whatever the lowest setting is
AFAIK UAC can only be completely disabled from the registry, maybe that's why the dump says it's enabled.
Lenry
8 discussion posts
I found the solution!
It's really embarrassing, because it has nothing to do with DF, but I write it down anyways, maybe it'll help someone else.
So my key combination is Ctrl-Alt-Right for moving windows to the next screen. I assigned this keycombo to one of the programmable buttons of my Logitech MX1000 mouse, through Logitech's SetPoint software, and I use the function with the mouse button all the time, and - silly me - never tried the actual combination on the keyboard. Now I did, and - guess what - it works all the time, also with admin mode windows.
It turned out that SetPoint also needs to run with elevated rights, and then it can correctly do the thing...
Anyway thank you very much for your help, you helped me find the solution.
Jan 7, 2016 (modified Jan 7, 2016)
•
#9
No worries, glad to hear you were able to get it sorted out!
