WinSCP script "hangs" when wrong .ini session password used

Hi!
I'm facing the same problem as in:
https://winscp.net/forum/viewtopic.php?t=1859

I have a script that uses a .ini stored session and when the stored password is wrong for some reason (e.g. expired, changed), the script "hangs" since WinSCP prompts for a new correct password.

Is there any "winscp" scripting solution to this problem?

My script:
The last line in the log file:
One possible solution is that I introduce an own timeout in my program that execute the WinSCP script. But I would like to have a more generic solution.

Thanks in advance
/Christian

What version of WinSCP are you using?

Sorry, latest version, 4.05 (Build 354).

Additional information:
To simulate wrong password/force error, I modified the Password field in the winscp.ini file (removed one char) for the Session I'm using in the script.
The password has not been changed on the remote server.
I did this for testing purpose.