0
Not a bug

Moving mouse on screen logs computer out

Loudsy 3 years ago updated by Ben Burner 3 years ago 5

In the last 2-3 weeks, we've found that with certain computers across multiple clients, when we connect and move the mouse even 1 pixel on screen, it takes the user to their login screen. Anyone heard of this? Happens on multiple hosts as well. 

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

Answer

Answer
Not a bug

Good morning,


We've had a few reports of this behavior, and found that the same behavior can occur when connecting to certain Windows 10 machines via other remote support applications as well. Since the Control client code is not responsible for the behavior described in this thread, and is instead an environmental/OS issue, I have marked the topic as "Not a bug".


Regards,

Ben

Waiting for information

Good afternoon,


We've received a couple reports of this behavior, but have so far been unable to replicate it internally. In most cases, rebooting the affected guest machine into safe mode and then back to normal mode appears to resolve the issue on subsequent connections.


That being said, we'd like to understand exactly what's causing this behavior (it's a relatively new phenomenon, and has only been reported in the past couple weeks). If you don't mind, please update this post with answers to the following questions:


1) You mentioned this behavior only started in the past 2-3 weeks: Did you upgrade your Control server immediately prior to the behavior occurring?


2) Have you noticed any commonalities among guest machines on which this behavior occurs? Does it only happen on Windows 10 guests, or does the behavior reproduce on Windows 7/8 guests as well? What "Operating System" text is displayed on the host page for machines on which this occurs, e.g. "Windows 10 Enterprise (10.0.16288)".


3) Have you deployed an app.config to your guest machines? If so, what app.config settings have you enabled?


4) Does the behavior occur if you connect to an affected machine via a support session, or does the behavior only occur when connected via an access session?


Cheers,

Ben

I'm noticed this only a few times in the last 2 weeks.      Both times it has been Windows 10 Pro x64 computers.   No upgrade to control server recently.      There is no app.config applied to guest machines.      I have not been able to test if it happens with a support session as well.

I too have this problem.. We have all Windows 10 pro 64-bit machines..

This has been happening quite for several months now.. Just been dealing with it as having the user reboot seems to resolve it.. It wasnt until a few days ago with I connecting to the same machine and it was doing it again.. So i thought a single reboot resolved it... But now the same machine is doing it again which lead to me knowing this is not a single instance problem.

I have not deployed any app.configs.. being it has been doing this for a while, I cant remember if there was a Control Server update.. Sorry for that..


I also see this post is over 3 months old.. Has there been any more recent discoveries with this problem?

Hello, we are having a similar problem. I did some testing and noticed that it only happens on PC's where a user doesn't have local admin rights on our domain. It works normally when a user has local admin rights. 

Answer
Not a bug

Good morning,


We've had a few reports of this behavior, and found that the same behavior can occur when connecting to certain Windows 10 machines via other remote support applications as well. Since the Control client code is not responsible for the behavior described in this thread, and is instead an environmental/OS issue, I have marked the topic as "Not a bug".


Regards,

Ben

Commenting disabled