Tracker »
Issue 1940 – WinSCP fails to start due to Fabulatech drivers (ftusbprint.dll)
:
General
:
Unspecified
:
NEW
:
—
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.
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.
https://winscp.net/forum/viewtopic.php?t=30359
Emails with Chris Verzulli
Emails with Chris Verzulli
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.dllRegCloseKey HKLM\SOFTWARE\WOW6432Node\FabulaTech\fthook\modules\ftusbprint
For a workaround, see:
https://winscp.net/forum/viewtopic.php?t=30354#104070
https://winscp.net/forum/viewtopic.php?t=30354#104070
The problem seems to be related to Fabulatech ftusbprint.dll driver.