Tracker »

Issue 1940 – WinSCP fails to start due to Fabulatech drivers (ftusbprint.dll)

: General
: Unspecified
: Bug
: Medium
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.
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.
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