We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Firewall blocking dropbox.exeexe
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 w...
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
Dropbox Staff
Dropbox StaffNo I can't, due I denied the connection to this suspictious file and the message it didn't appears anymore
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
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.
I have got this same error today, 17 June 2023. Previous posts are 1-2 years old but the issue is the same. I could not find an answer to the previous posts.
The file dropbox.exeexe does not exist in the folder, but the expected dropbox.exe does exist in that place.
- 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.
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.
