FileZilla Forums

Hi everybody,

Since 3 days I 've got an error message when I try to drag and drop files on my desktop from filezilla :

In french ; "impossible de déterminer la cibe pour l'opération de glisser-déposer. L'extension du shell n'est pas correctement intallée et vous n'avez pas déposé les fichiers dans une fenêtre de l'explorateur de fichier'.

I read some forums about this problem and tried :
- Reboot a lot of time
- uninstall and re-install filezilla
- start cmd command in admin and start regsvr32 fzshellext_64.dll then reboot

Nothing change.

Any help please.

I am on windows 10 64bits - Filezilla 3.33.0 -

Thank you.

Bug in Windows.

Same problem.
I've found 2 uncomfortable partial solutions:

1) try to drag and drop file from Filezilla local window to Filezilla remote window;
2) try double click on file to transfer: it will be copied in your Windows user path.

It's very frustrating. Can someone tell us if an update will be released next hours?
Thanks.

Can someone tell us if an update will be released next hours?

Microsoft, as it's their bug. And I seriously doubt it, they are masters of procrastination.

Try winscp. Apparently, the windows bug doesn't affect drag and drop operations there.

Edit
See this post viewtopic.php?f=2&t=49039
(I got no email notifications about replies and googled it and found find this post)

Having this issue as well. Also having no success with the regsvr32 fzshellext_64.dll "solution" that's all over the internet.

That's because it isn't a bug in the shell extension, but a bug in the Windows feature the shell extension uses.

Same problem here, please help.

Please fix this issue. I love FileZilla and this is making me crazy. I read that it is Microsoft fault. But please give us a fix. Microsoft maybe will never fix this.

Microsoft did not break the drag and drop. I noticed Fizila developer post about drag and drop issue on MSDN. MSDN replied that iCopyHook is about move, it is not intended to copy. It is the stubborn Filezila developer shifting blame to Microsoft instead of fixing the problem.

I would love to fix the problem if only Windows were open source. But as it is not, only Microsoft can fix this bug.

About the MSDN site you are referring to, only entry level tech support workers reply there, no actual Microsoft developers working on Windows reply there. An actual developer would have explained what has changed and why. The person that has replied doesn't even appear to be a Microsoft employee at all as those are marked as such.

Hi. Huge fan of the software and I created this account to reply.

I have inside information that Microsoft has fixed it in Redstone 5 (Insider Preview & latest incoming Oct update).

Unfortunately Microsoft is also the master of opaqueness so no official bug / fix report.
They had an online bug tracker awhile ago I think but that got hacked.

It's known since weeks now (IIRC I posted about it when the Insider builds fixed it). 1809 is out, so it would be the recommended solution. But, make a backup before upgrading, as it has its own share of bugs (tends to delete all users' files, no biggie... ).