PuTTY bug vista-update-breaks-config

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Snapshot | Docs | Changes | Wishlist

summary: Windows Vista update KB3057839 breaks PuTTY configuration dialog
class: bug: This is clearly an actual problem we want fixed.
priority: high: This should be fixed in the next release.
present-in: 0.52 0.53b 0.54 0.58 0.60 0.63 0.64 2015-06-09
fixed-in: 2015-06-19 6163710f043fb58fc80f6b45c14a92f7036bde75 0.65

Many people have reported that on Windows Vista (but not Windows 7), after the Windows security update KB3057839 (part of the update MS15-061 published on 9 June 2015), the PuTTY configuration window does not display. Only a taskbar icon is visible. The window is in fact present, but invisible; keyboard input and even blind clicking on the invisible configuration window still work. (Some public reports: one, two, three.)

The PuTTY terminal window works when launched from the command line (putty -load sessionname, putty -ssh hostname.full.domain -l username). Other PuTTY suite programs such as PuTTYgen work.

Uninstalling the KB3057839 update is reported to restore PuTTY to a working state; however, since that's a security update, that's not an ideal solution. (One correspondent reported that uninstalling KB3058515 also worked.)

We asked on Microsoft's forum; this has yielded another program (dBpoweramp) suffering from what sounds like the same symptom.

One correspondent's experience suggests that the window is present but invisible (transparent); they've also posted publicly. They can restore visibility with an AutoHotKey script containing the following:

WinWait, PuTTY Configuration
WinSet, Transparent, 255

It's also been reported that hiding and showing the window with ShowWindow() (by hacking the PuTTY source, or externally from PowerShell) makes the window reappear.

Another perturbation that makes the symptom go away is mucking around with SetWindowLong(). It's not clear why, but it has made us a bit suspicious of our use of that family of functions.

Another correspondent reports that setting the Windows properties 'Disable desktop composition' or 'Run in 256 colors' on putty.exe (in the Compatibility tab of the file properties?) avoids the issue. Others report that disabling desktop effects entirely (by selecting the "Windows Vista Basic" colour scheme) also works, although that's a sledgehammer to crack a nut. Presumably all these methods work by removing the possibility of transparency.

None of PuTTY's settings appear to have any effect on this behaviour (which is as you'd expect, since the configuration dialog is itself not configurable); at least, many people have tried erasing their saved sessions, uninstalling, using -cleanup etc with no improvement.

Update, 2015 Jun 18: we think we've found the root cause of this. It was apparently only by luck that the configuration dialog appeared at all, on any version of Windows (gory details in the commit message).

The bug we've found is fixed in development snapshots dated 2015-06-19 or later. It made the symptom go away on our test machine, and on those of all who originally raised the issue and reported back to us after testing the update.


If you want to comment on this web site, see the Feedback page.
Audit trail for this bug.
(last revision of this bug record was at 2016-12-27 11:40:22 +0000)