+15
Under review

Control launches off screen

Dan Belam 12 months ago updated by Charlie Hall 2 months ago 12

I'm a laptop user, and often use a second monitor. Control launches onto the second monitor fine. When I unplug my second monitor, and just use laptop screen, some sessions launch beyond the display size of my laptop, ie where a second screen would be, and you cannot get to the window to move back onto the single laptop screen.

ConnectWise Control Version:
Server Affected:
Host Client Affected:
Guest Client Affected:

Answer

+1
Answer

Hi Cee, thanks for contacting us. Kindly tell us what version are you on?

Meanwhile, you can fix the issue by deleting the user config c:\ProgramData\ScreenConnect Client (xxx)\user.config

I started having this issue after moving from 19.4 to 19.6

Is there a work around for this issue?

+6

You can quickly fix this by deleting or renaming c:\ProgramData\ScreenConnect Client (xxx)\user.config

Had the same problem and I knew the last monitor dimensions were stored somewhere.

I'm having the same issue. If the control window was on my secondary monitor last time it was closed, when I'm using the laptop away from the docking station, it opens the control window offscreen and the usual Shift+Windows+Arrow keys won't work.

On windows 10 I find that if you hover over the taskbar icon you get the small preview screen, you can then right click on it and choose Move to move the active window with the arrow keys back to your laptop screen. Hope that helps.

Is there not a fix for this after 7 months?

Hi Mike B., 

What version are you on? Looks like this was potentially fixed in a 20.1 release. 

I also wanted to comment that I don't think I have had this issue since moving to v20.2 earlier this year. When this happens now the screen appears on my main display, but will be really small and I just have to resize it.

I am experiencing this issue as well. It's a real bugger...

+1
Answer

Hi Cee, thanks for contacting us. Kindly tell us what version are you on?

Meanwhile, you can fix the issue by deleting the user config c:\ProgramData\ScreenConnect Client (xxx)\user.config

FYI - I had this issue today. I was able to resolve it by deleting user.config from: 

C:\Users\*username*\AppData\Local\Apps\2.0\24ZMMT6T.LA0\2GOK2AD8.GW2\scre..tion_b15b0581876c57b7_0014.000a_aad5bdbae25c30a6

Hope this helps for other users in the future. For reference this is for ScreenConnect that is installed via Automate. Still would appreciate if I didn't have to spend an hour figuring this out in the first place though.