Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logon prompt does not appear after ctrl-alt-delete on Windows Server 2019 #186

Open
fkamp opened this issue Mar 22, 2024 · 2 comments
Open
Assignees
Labels
Rudi Rudi answer is needed

Comments

@fkamp
Copy link

fkamp commented Mar 22, 2024

I ran into an issue where all our Windows Server 2019 installations dont work with UltraVNC anymore. Establishing the VNC session works fine, however, after sending ctrl-alt-delete for SAS, the login prompt does not appear. It only shows a blue screen. After some time, it will revert back to showing "Press ctrl-alt-delete to unlock".

Windows Server 2019 Standard
OS build 17763.5576

UltraVNC 1.4.3.6

Does anyone have an idea?

Here is an excerpt of the logfile:

Fri Mar 22 16:55:55 2024
vncDesktopThread::run_undetached : Hook changed 
 --The requested resource is in use.
Fri Mar 22 16:56:00 2024
vncEncodeMgr::SetEncoding : unknown encoder requested: 24
vncEncoder::SetTranslateFunction : only 8, 16 or 32 bits supported remotely - 0 requested
Fri Mar 22 16:56:04 2024
 keysym 0xffe9vncMenu::~vncMenu : vncmenu killed
 --The requested resource is in use.
WinVNCAppMain : ################## Closing Imp Thread
imp_desktop_thread : OpenInputdesktop OK
imp_desktop_thread : SelectHDESK to Winlogon (4f4) from 100
imp_desktop_thread : Username SYSTEM 
vncMenu::vncMenu : vncmenu(server)
 keysym 0xff09Fri Mar 22 16:56:05 2024
 keysym 0xff09 keysym 0xffe9Fri Mar 22 16:56:20 2024
vncMenu::~vncMenu : vncmenu killed
 --The requested resource is in use.
WinVNCAppMain : ################## Closing Imp Thread
imp_desktop_thread : OpenInputdesktop OK
imp_desktop_thread : SelectHDESK to Winlogon (460) from 100
imp_desktop_thread : Username SYSTEM 
vncMenu::vncMenu : vncmenu(server)
Fri Mar 22 16:56:29 2024
 keysym 0xffe3 keysym 0xffe9 keysym 0xffff keysym 0xffff keysym 0xffe9 keysym 0xffe3Fri Mar 22 16:56:37 2024
vncMenu::~vncMenu : vncmenu killed
 --The requested resource is in use.
WinVNCAppMain : ################## Closing Imp Thread
imp_desktop_thread : OpenInputdesktop OK
imp_desktop_thread : SelectHDESK to Winlogon (434) from 100
imp_desktop_thread : Username SYSTEM 
vncMenu::vncMenu : vncmenu(server)
Fri Mar 22 16:56:53 2024
vncMenu::~vncMenu : vncmenu killed
 --The requested resource is in use.
WinVNCAppMain : ################## Closing Imp Thread
imp_desktop_thread : OpenInputdesktop OK
imp_desktop_thread : SelectHDESK to Winlogon (410) from 100
imp_desktop_thread : Username SYSTEM 
vncMenu::vncMenu : vncmenu(server)
@RudiDeVos
Copy link
Member

RudiDeVos commented Apr 3, 2024

Is vnc running as service ? Only a service can use SAS.

Please verify, on some systems this is not enabled

Enable-CAD-Prompt-for-UAC-Windows-10-Tweak

On some system the software ctl-alt-del is disabled
Using gpedit.msc

Search EnableSecureCredentialPrompting on google for it

@fkamp
Copy link
Author

fkamp commented Apr 3, 2024

Is vnc running as service ? Only a service can use SAS.

Please verify, on some systems this is not enabled

Enable-CAD-Prompt-for-UAC-Windows-10-Tweak

On some system the software ctl-alt-del is disabled Using gpedit.msc

Search EnableSecureCredentialPrompting on google for it

I should have mentioned that it worked when the server was set up initially. VNC runs as a Windows Service. The blank blue screen comes after sending ctrl-alt-delete. So yes, the SAS prompt is enabled. Thanks for the tip anyway.

@Neustradamus Neustradamus added the Rudi Rudi answer is needed label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Rudi Rudi answer is needed
Development

No branches or pull requests

3 participants