Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I just got a new computer with Windows 7 (64 bit), installed the latest version of Putty, and find that Putty always locks up once I disconnect an SSH session or when I get disconnected (e.g. when the server reboots).

Putty works great until that point and hangs every time on disconnect.

The only way I found to terminate Putty at that point is to kill it through the task list.

Anyone else seeing that? Any known fix?

share|improve this question

closed as too localized by random Jul 25 '12 at 0:25

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

Putty for me hangs when exiting in Windows XP on some computers for me. Are you by any chance running Macafee? –  TheLQ Aug 5 '10 at 16:39
We're running ESET Smart Security 4. –  Eric J. Aug 5 '10 at 17:44
What version did you download? I ask because I have this EXACT SAME ISSUE. And the strange thing is, on my HP HDX18T notebook where I have this problem, I am running the x64 version v0.60. I am running the exact same version on my desktop computer, and it doesn't lock up there. This leads me to believe there is a little something more to this than just version. There is something hardware related here that is impacting this. Both setups run Win 7 Ultimate, x64, 8GB RAM. –  user51676 Oct 7 '10 at 20:10
I dont know about hardware being a cause, but there's something going on. On my main computer, Win7 x64, it works fine... On my new laptop, HP Elitebook 8440p running Win7 x64, it doesnt. And yes, this is the latest 0.60...a very annoying problem. –  J Sidhu Oct 30 '10 at 18:24

6 Answers 6

Hmmm... I haven't quite figured out how I can answer my last post (Nov 21 at 12:05). Anyway, I have put putty in xp-mode now and I haven't had a problem since and this is almost 3 weeks ago.

If I remember correctly you have to put the putty connection manager into xp-mode aswell in order to be able to use them with each other. Works like a charm now.

share|improve this answer

There is an X64 build of Putty for AMD64 architectures at http://www.kelley.ca/amd64/

share|improve this answer
up vote 0 down vote accepted

I just downloaded the latest Putty build and this problem seems to be gone.

share|improve this answer

Unforunately I have the same problem and did not realise that putty was causing this until recently. I was almost ready to send my new Laptop from Dell (also Intel i5 and windows 7) back. I also have the latest version (0.60) of putty. Hopefully the makers of putty will release a new version soon as this is causing me to restart my computer at least once a day! The problem is that I cannot even use the task-manager to kill the process. I have noticed though that the problem seems to be less evil if you start the putty sessions within the "Putty connection manager", as I can then at least close the putty session by clicking on the 'x' within that program.

share|improve this answer

What worked for me was right-click on Putty, Properties, Compatibility Tab, Run As Administrator. I can deal with the single Cancel or Allow popup & it works even better when you switch Putty to "Close window on exit: Never".

share|improve this answer
Responding to Eric J's answer: for me the latest build solved the problem when I closed the connection, but whenever the server disconnected (timeout, etc), it still locked up, until I switched to runing putty as admin. I have Windows 7 64-bit on an HP dv6tse. –  Wick Dec 5 '10 at 7:59

See if forks like KiTTY exhibit the same effect.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.