Screen/PC locked when connecting

[sito]

Hi there,

I have a problem connecting on WIN11 computers. While the connection to WIN7 works fine- when I connect to WIN11 PCs, the target screen is locked and I have to enter the windows logon password. This happens in normal and view only mode...

Version is: 1.4.3.6

How can this be avoided?

Thx
Sito

[Rudi De Vos]

You can auto lock a pc after x time, that's an OS option.
This doesn't look like a vnc settings.

For security reason you should lock your desktop when not in use.
Windows 11 differ from the unsecure win7, auto lock is on by default, but it's an option you can always change the OS behaviour

[sito]

Sorry- i thought it was clear but the behaviour i described occurs while the pc is unlocked.

I found the source of the "problem". I tested it while being connected via rdp session. this does not work any more on WIN 11.

case closed

[Rudi De Vos]

This rdp behaviour exist for a very long time.
MS license doesn't allow multiple connections.
RDP connect -> close concolse
console connect -> close RDP
This how the OS works.

Normal all vnc version connect to the console running as service, and to the current desktop as application.
UltraVNC has the option RDP mode, in that case, running as service he ask what desktop you want to clone.

Just as info

[soc_uvnc_1]

Hello everyone,

This is my first post on the forum, so I hope it's okay to jump into this discussion with a problem similar to what's been described.

I'm running the latest UltraVNC versions on several Windows PCs, all using the UVNC server as a service. Recently, I've encountered a peculiar issue on Windows 10 machines:

Regardless of whether I use Microsoft authentication or the UVNC password, when I attempt to connect with the UVNC viewer to an already open session, I'm only presented with the Windows login screen instead of the active session's shared screen.

To troubleshoot, I enabled the RDP option in the UVNC server settings. Initially, I'm still taken to the Windows login screen, but after the first connection attempt, if I try again with the UVNC Viewer, I'm then presented with the "UVNC experimental server pre-connect window." It's only at this point that I can select the open session and proceed normally.

Post-second attempt, it seems to default to the cloned session until the host is rebooted. I've observed this behavior across domain and non-domain accounts and various recent UVNC versions, with a consistent pattern of initial failure followed by access through the "UVNC experimental server pre-connect window." Notably, this issue does not occur when the UVNC server runs as an application, not as a service.

Could anyone shed light on the potential cause of this problem and suggest how to make the service mode function similarly to the application mode?

Thank you very much for your assistance.

Kevin

[soc_uvnc_1]

Hello Rudi De Vos,
i received an email that tells me that you replied but i can't see it.

I'm missing something?

Thanks

[Rudi De Vos]

*The account is for authentication, not desktop selection.
Using vnc passwd or a user/passwd doesn't make any difference.

It seems that your are using a pc with an rdp remote support connection or an rdp server.

The rdp mode show the active sessions + console.
For a rdp session to be active it need a mstsc active connection (not minimized).

VNC can not open a rdp session, only clone an existing one.

As experiment you can add winvnc.exe to the start of the users (as application) this give access to the running session.

[soc_uvnc_1]

Hello Rudy,

thank you for your reply.

I believe we have identified all the use cases, and indeed, the issue was related to conflicts with already open RDP sessions.
However, the behavior of the “UVNC experimental server pre-connect window” remains peculiar —it only activates after the first VNC login attempt. As the name suggests, this tool looks still in development (experimental), and I’m confident it will be resolved in the future.

Regards.

Kevin