Issue activity log

2021-01-07 12:40 Created WinSCP fails to start due to Fabulatech drivers (ftusbprint.dll)
Component General
Severity Bug
Comment We got few reports recently about WinSCP failing to start in VMware or Microsoft Terminal Server.

The problem seems to be related to Fabulatech ftusbprint.dll driver.
2021-01-07 12:41 Comment
2021-01-07 12:42 Comment Emails with Mon Sam:
While working with VMware support they suspected the following...
"There might be a problem with Fabulatech hooking DLLs"
As a test, I install the VMware agent minus "Scanner" and "Serial Port" redirection. This allowed for WinSCP to start successfully.
2021-01-07 12:43 Comment
Emails with Chris Verzulli
2021-01-07 13:04 Comment When debugging the process start with the Process Monitor, one of the last real actions before the process fails are:
CloseFile C:\Windows\SysWOW64\ftusbprint.dll
RegCloseKey HKLM\SOFTWARE\WOW6432Node\FabulaTech\fthook\modules\ftusbprint
2021-01-15 09:20 Comment For a workaround, see:
2021-04-09 13:02 Comment
2021-11-23 10:17 Comment
2022-01-20 12:02 Comment