You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
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...
Walter
Dropbox Staff
Dropbox Staff
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.
- Nancy
Thanks for posting here, Jan_Kreft.
Can you please clarify when exactly you receive this message by Windows Defender? Do you click on something first and then, it appears or does it show randomly?
Dear Nancy, thanks for getting back to me. It appeared after waking laptop from sleep. I did not do anything directly to do with Dropbox or anything I don't normally do after logging in.
- 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.
