Command prompt closes immediately on connecting

[Jimz18 · Accepted solution]

Pressing F5 to refresh screen (Connection closed.) fixed for me.

[Verricom]

Well what do you know, Jimz18 might have fixed it for me.

So far so good, any "connection closed" screen works when I hit F5 to refresh, not ideal if I am piping script into the remote prompt via an automation tool but at least it works for manual typed connections again... so far at least!

[paulquevedojdrf]

F5 works for me as well

[AshC]

Hi, all.  

We re actively investigating this behavior and should have some answers soon.  

[AGJL]

Too bad LogMeIn isn't a mainframe system, then F5 would actually be a fix rather than a workaround.  BTW, F5 gets me connected to the CLI as well.  Good catch Jimz18!!!

[AGJL]

UPDATE:  Can anyone at LMI give us an update for when this issue will be resolved?  We're quickly approaching the end of month 3 since it was reported and it is still happening as of a minute ago. 

[AshC]

Thanks for your patience.  We are actively investigating the cause of this problem.  I hope to have more information soon. 

[egrylls]

It might be because its opening POWERSHELL instead of a COMMAND PROMPT.  Have your devs look at that.  Seems someone changed something in the client or exe being called and now it's a different executable being brought to bear.

[jowsr]

Hi Team,

It looks like someone has made this worse. Now I get two 'connection closed' messages and the f5 refresh no longer works......

[AshC]

@jowsr   There should be a permanent fix in an upcoming release.  I will have an ETA soon.