I have now upgraded to 4.1.2 (Build 388) Beta
And now I get [img] a Windows dialog saying "encounterd a problem and needs to close"
This issue is being tracked as well already :-)
- martin
This issue is being tracked as well already :-)
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
This issue is being tracked as well already :-)
- kristianw
Thanks,
I have now upgraded to 4.1.2 (Build 388) Beta
And now I get [img] a Windows dialog saying "encounterd a problem and needs to close"
Kris
I have now upgraded to 4.1.2 (Build 388) Beta
And now I get [img] a Windows dialog saying "encounterd a problem and needs to close"
Kris
- martin
Re: Closing WinSCP does not completly shutdown the program
Thanks for your post. This issue is being tracked already.
- kristianw
Closing WinSCP does not completly shutdown the program
Version : 4.0.7 (Build 370)
Protocol : SFTP-3 and FTP
Interface: Norton commander
Steps
1) Launch WinSCP
2) Connect to a saved session server.
(Once connected)
3) Click the (X) top right hand corner to close the application
(Once closed)
4) Launch task Manager
5) Click on "Processes" tab
I can see the WinSCP process still running.
This prevents Windows XP from restarting. (Until I kill the process)
The problem does not occur if I launch WinSCP and close the "WinSCP login" dialogue, without making a connection.
I also tried, the menu Session/disconnect and then close on the "WinSCP login" dialogue the program still does not terminate.
The only difference is that: the TCP connection via "netstat" changes to "TIME_WAIT", where-as before it would stay at "ESTABLISHED".
So I don't think it is a connection problem.
I turned on WinSCP logging but the last line in the log gives no extra information.
Last line = "Startup conversation with host finished."
I noticed this before in a previous version of WinSCP but only when I used "Open directory/bookmark" so I stopped using it. (Sorry, I can't rememeber the version.)
I have recently change computers because the HDD died.
Therefore, I have now installed the latest version of the program.
Now this problem is happening every time (as you can see from the steps above).
I am on a company network and my profile was restored to the new computer with all may sessions (thanks).
I have local administrator rights, so this is not a permission problem.
I am guessing that WinSCP writes to the registry when it shuts down.
Is it possible that my registry is missing an entry or contains an entry that is preventing WinSCP to shutdown completely?
Also, the HOME Drive/directory is set to a network drive, separating it from the unusual "Documents and Settings\<Username>" directory.
Thanks
Kris
Protocol : SFTP-3 and FTP
Interface: Norton commander
Steps
1) Launch WinSCP
2) Connect to a saved session server.
(Once connected)
3) Click the (X) top right hand corner to close the application
(Once closed)
4) Launch task Manager
5) Click on "Processes" tab
I can see the WinSCP process still running.
This prevents Windows XP from restarting. (Until I kill the process)
The problem does not occur if I launch WinSCP and close the "WinSCP login" dialogue, without making a connection.
I also tried, the menu Session/disconnect and then close on the "WinSCP login" dialogue the program still does not terminate.
The only difference is that: the TCP connection via "netstat" changes to "TIME_WAIT", where-as before it would stay at "ESTABLISHED".
So I don't think it is a connection problem.
I turned on WinSCP logging but the last line in the log gives no extra information.
Last line = "Startup conversation with host finished."
I noticed this before in a previous version of WinSCP but only when I used "Open directory/bookmark" so I stopped using it. (Sorry, I can't rememeber the version.)
I have recently change computers because the HDD died.
Therefore, I have now installed the latest version of the program.
Now this problem is happening every time (as you can see from the steps above).
I am on a company network and my profile was restored to the new computer with all may sessions (thanks).
I have local administrator rights, so this is not a permission problem.
I am guessing that WinSCP writes to the registry when it shuts down.
Is it possible that my registry is missing an entry or contains an entry that is preventing WinSCP to shutdown completely?
Also, the HOME Drive/directory is set to a network drive, separating it from the unusual "Documents and Settings\<Username>" directory.
Thanks
Kris