Firewall blocking dropbox.exeexe

[Pinkysnickers]

Hi community,

Can anyone tell me why Windows Firewall is blocking C:\program files (x86)\dropbox\client\dropbox.exeexe? Note the double exe at the end. It's that that is confusing me, otherwise I would just allow access, but I'm not sure if this is something fishy!!?

[Walter]

Hey @Pinkysnickers, sorry to hear about this.

Could you try installing the latest, stable version of our desktop app from this page?

If you still get the same error, please send us a screenshot so that we can have a visual too. 

Thanks!

[mp3man]

I've recieved this morning the same firewall alert too, including the same file with .exeexe extension and this is very suspictius. What should I do? Uninstall forever dropbox client? Thanks

[Walter]

Hey @mp3man, thanks for the nudge here.

If you're still getting this message from your firewall, could you send us a screenshot to have a better look into this?

[mp3man]

No I can't, due I denied the connection to this suspictious file and the message it didn't appears anymore

[gales81]

It's a weird thing, because it points to the dropbox directory, but there's nothing there. Not sure what to think about it. But I start to be suspicious, because I already have one blocked on the chrome - chrome.exe.exe. After blocking it both apps work well

[cs1970]

I've gotten this today:

The dropbox application folder has a "Dropbox.exe" file but no "dropbox.exeexe" file so I dont know if that is a Windows Defender issue incorrectly appending 'exe for some reason or if perhaps this is the name of a temporarily installed program that carries out autoupdates considering that there re two subfolders named "152.4.4880" and "PackageAssets" present which have modified date/times that coincide with the appearance of this dialog.

If it is your update/install process, it really shouldnt be presenting users with a security alert about a file with such an unconventional name.

[Walter]

Thanks for your feedback on this @cs1970 - we've passed it on to the team.

Let us know if you have anything else to add. 

[cs1970]

A few days after I posted the above example, Windows Defender Firewall interrupted a Chrome update with a similar notification referring to "chrome.exe.exe" so I think the finger can likely be pointed at Microsoft here for the spurious suffix at least, whatever about validity of the alert being raised in the first place.

[Walter]

In that case, you may want to flag this with Microsoft directly as well @cs1970 

Cheers!