Hi chrisg750,
Can you provide more details about your issues using Ctrl+Alt+Delete? What operating systems are you connecting to, what happens or doesn't happen when you click the Ctrl+Alt+Delete button in the toolbar?
I cannot even find a CTRL-ALT-DEL on an unattended access connection. WHERE IS IT? GotoAssist 4 was fine until it randomly stopped creating sessions. It eventually creates one and works normally, but this is very frustrating!
If you hover over the the top toolbar you will see it. It doesn't work 3/4 of the time for me lately, but the button is there.
If you hover over the the top toolbar you will see it. It doesn't work 3/4 of the time for me lately, but the button is there.
Hi chrisg750,
Digging into this issue further, we have a primary and secondary method of passing the Ctrl+Alt+Delete to the client computer. If the Primary method fails the Secondary method is used. Please check for the following on the Unattended computers.
The first place to look is going to be this file GoToAssistUnattended.srv.log, you will find it in C:\Program Files (x86)\GoToAssist Remote Support Unattended\xxxxxxxxxxx\appdata
Primary method:
Search for CtrlAltDel message received, in case of error you will see:
"Primary CtrlAltDel injection failed with error code:" There should also be an error recorded in GoToAssistTools64/32.log in the same folder.
Secondary method:
Check GoToAssistProcessChecker.srv.log for "Sending CtrlAltDel"
If this log is not present the command was unsuccessful, in this case one of these errors should be seen in GoToAssistUnattended.srv.log:
"Unable to open service control manager"
"Unable to open service"
"Sending service control message 128 failed, with error code"
Hello Glen,
Thanks for the reply!
Connecting to Windows 10 Pro clients via unattended support sessions. When I press the CTRL ALT DEL on the toolbar, nothing happens. It's like if I'm not pressing any button at all. There's no error message or no confirmation of anything. I can move the mouse, but that's about it.
After going through a quick search it seems as though there are other users who also have this issue. The only solution for me thus far, is to open a session with v4 to press CTRL ALT DEL, and then I can carry on with v5. It's an even bigger issue for us specifically because I stopped adding v4 to our new clients months ago. Going to have to start adding v4 to every client from now just in case.
