Windows 10 lock screen after connection on mouse move

[Magnus]

Well, i am using UVNC for quite some time now. But now Windows 10 gives me some headache.

I can connect to the host. But as soon as i move my mouse Windows will go back to the user lock screen immediately. There i enter the password and log in again. First move of my mouse and i am back out again.

UVNC was working on Windows 10 but some Update seems to have caused issue.

By the way: Teamviewer has the same issue on the affected systems as there are some on which both is installed.

Any help or has this been fixed in the latest version.

[Magnus]

Well, at least i know now, it is a problem with the user rights. If the domain user has administrative rights on the local PC the problem exists. Downgrading the user rights to a standard user enables VNC.

The domain administrator works fine.

I love Windows security enhancements...

[Magnus]

I have to correct that. It does not matter if the user is an administrator. Right now i have a machine where the domain user is a standard user and it does not work. The domain admin is functional.

[ddbivens]

I ran into this one time before.
If I remember correctly it was when I changed the connection to block remote input (blank screen - show the big green eye).
When I allowed user input - turned off blocking remote user input, it did not happen.
Hope this helps.

[Magnus]

I have the issue on several systems and all of them are patched to the latest Windows 10 updates.

It is weird because it does not only affect UVNC. I tested the systems with TightVNC and even with TeamViewer. All had the same issue.

PS: Where did you change the option (i did not find it).

[ddbivens]

I use the icon (5th from the right) that looks like a monitor. It is named "Toggle Remote Input and Remote Blank Monitor On/Off".

I found the options in "UltraVNC settings" / Input/FileTransfer / "Disable Viewer inputs" and "Enable Blank Monitor on Viewer Request".
I have these settings set as [Disabled] "Disable Viewer inputs" and [Enabled] "Enable Blank Monitor on Viewer Request".
There is another option "Disable Only Inputs on Blanking Request", which I have disabled. I guess this would would leave the monitor active when you click the button to block inputs.

I do remember which system I was having the problem with.
I will try to do more testing in the next few days so I can update this thread with more definitive feedback.

[ddbivens]

I verified the problem and it is repeatable for me.
I am connecting from a Windows 7 Pro/64 bit system using VNCViewer 1.2.1.7. I verified it happens when I connect to Windows 8.1 Pro or Windows 10 Pro PCs (I tested two Windows 8.1 PCs and one Windows 10 Pro PC today). It does not happen when I connect to a Windows XP or Windows 7 PC.
I tested with version 1.2.1.7 and the new beta for 1.2.2.0 on the remote PCs and I got the same results.
When I use the button to "Toggle Remote Input and Remote Blank Monitor On/Off" to activate the Blank Monitor and block user input, then I move the mouse on the screen, the remote PC seems to run the Lock Workstation command.
When I use the button to "Toggle Remote Input and Remote Blank Monitor On/Off" to turn off the Blank Monitor and allow user input, then the problem goes away.
Hopefully, they can find what is causing the issue and will be able to fix it.

[soulraver]

Maybe it helps:

1. run with administrator right - powershell
2. type SECPOL command
3. After the window is opened, find Admin Approval Mode for the built-in Administrator. It's in Security Settings > Local Policies > Security Options
4. Turn on Approval Mode for the built-in Administrator and restart computer
5. Log in and check if it helped

Hope it helps. Cheers