Dropbox.exe Download

[Robinette Ith]

Did this post help you? If so, give it a Like below to let us know.

Need help with something else? Ask me a question!

Find Tips & Tricks Discover more ways to use Dropbox here!

Interested in Community Groups? Click here to join!

Hi Hannah, sorry for the delay. I have been trying to take a screenshot and send it to you with Screenshot Captor, but due to my inability to understand these programs I seem to keep messing things up. I am no longer sure if what I was doing was right and I couldn't work out how to send it to you. These 7 dropbox.exe were all running in Process Explorer and that is what I was trying to capture and send. Thanks for any help, Olddog76.

Also, I would like for you to locate your Dropbox icon. It would be on the task bar, next to your WiFi. Once you do this, could you hover your mouse there and let me know what the status and version of the Dropbox Desktop application?

I just had MBAM Premium detect a DropBox Windows HKLM Registry Key as Ransomware. I was moving files around inside my DropBox folder when this happened, so MBAM probably picked up on the DropBox.exe process "modifying" (AKA Syncing) these files to the cloud en masse, killed the process, and blocked it from executing. I'd like to first say amazing job at blocking Ransomware in its' tracks - um... if it was actually Ransomware.

To clarify, I was moving things in a folder in my DropBox on my computer, which is a folder I share with other users in the office. This detection occurred on one of the workstations at the office running their own company DropBox account that has access to my shared folder.

I don't know if their installation of MBAM was up-to-date or installed properly when this detection occurred, since they had another "computer expert" come in to fix some things while I was away over the weekend. le sigh When I checked their programs in appwiz.cpl, a lot of programs had different install dates than when I had installed them, including MBAM, so hopefully this computer guy didn't break things and I'm not wasting anyone's time with this issue.

Hi, I just had MBAM Premium detect a few Dropbox files as Ransomware several minutes ago, as well. I am unable to find the folder C:\ProgramData\Malwarebytes\MBAMService\logs\ to attach, but here's image of the Quarantine Results. Is this a false positive or a real threat?

Hi, again, So, Dropbox disappeared from my system. So, I reinstalled it and added the C:\Program Files (x86)\Dropbox\Client\Dropbox.exe file to my Exclusions. I began working in Dropbox again and all of a sudden, it got Quarantined again (along with all the Registry Value and Registry Key Types as in the image above), and it was taken off my system. This is a bit of a problem for me, since I backup my work constantly to Dropbox and need to have reliable access to it. I checked for updates to MBAM and the check came back that I was up-to-date. Is there a fix in the works or is there something else I should do? Thank you.

Just happened to me also. I restarted my PC and shortly after Dropbox started indexing, as it always does, I got a pop-up at the lower right of my screen saying Ransomware had just been handled and it showed the path for dropbox.exe. I checked and sure enough, dropbox.exe is gone. Nothing shows in the quarantine or anywhere else I can see on Malwarebytes. Log attached.

Miekiemoes, that is not correct. Dropbox does get deleted. It is not just the process being stopped. This has been posted several times, yet you continue to insist it is not happening. My dropbox was deleted early this morning. It's gone. I attached my log above.

Your log doesn't indicate it has deleted it - only that it had killed the process. I am not saying you are wrong here, I am just looking at the information that is present in the log, as I can't reproduce it either where it deletes dropbox.exe.

Just to add to my information in case it helps the developers working on it: I do not have C:\Users\\AppData\Roaming\Dropbox\bin\Dropbox.exe anywhere on my system- (Dell Laptop). I have a Dropbox folder under Users, but it does not have any .exe files within. And where my .exe Dropbox file "used to be" was under C:\Program Files (x86)\Dropbox\Client\Dropbox.exe - which is what I added to MBAM Exclusions, and was later Quarantined as ransomware anyway. It still shows up on the Quarantine window of MBAM, but C:\Program Files (x86)\Dropbox no longer exists on my computer, though I never chose what to do with it on the Quarantine page.

Also, I found the file for the MBAM service logs after doing a search on my computer and it was not in the Malwarebytes folder, it was just on my C:\ drive. Weird. I've attached it here. Thanks again.

I will roll back to the good and simple version 2.21 (which requires a clean uninstall to eliminate the required update nag dialog to version 3). You should continue to offer 2.2.1 with a big warning on your sales site, especially for those of us who are Premium paid customers. For the benefit of others suffering from this bug, please see instructions I received from Malwarebytes support below:

Unfortunately we do not currently have a fix for the bug you are experiencing. Our engineers are hard at work to track down and fix most critical issues since the release of Malwarebytes 3.0. In the meantime we are advising users with the option to revert back to version 2.2.1 until we have a formal fix for these bugs.

I am not sure what version I have: the Dropbox icon does not appear in the tray, so I am not sure how to check it. Any suggestions? I have also tried to install new version, but the icon is still not appearing in the tray. Otherwise, the task manager shows that Dropbox is running.

I have 3 dropbox.exe running, across 3 OS user accounts (win7), one on a limited account, one on the Administrator account, and one on the active account (being in the administrators group).

The active account runs dropbox.exe normally.

The other two accounts dropbox.exe launch via the win7 RUNAS.EXE command launching under the profile of the dropbox.exe install being run. (so same as fast user switching)

Question, as I dont know the underlying mechanics of what your doing, Ill ask, will Boxifier suffer under high file loads? aka we have around 300K files, but expect to raise to 500K soon, and the DB app is already gagging on the number.

The protected folders feature is experimental. The main reason it was introduced is to be able to backup folders to Dropbox without worrying that the DB app might suddenly decide to delete those files.

@Dave, I just checked the latest stable build of the Dropbox desktop client (2.10.42) and the file path limit is still there. However, it continues to be removed in the latest experimental build of the Dropbox desktop client (2.11.29) so probably we will soon see it in the stable build.

Issue to be solved: Software Inventory (which is really FILE inventory) you've noticed takes FOREVER when you define a rule like "dropbox.exe on c:\users\", the clients take several minutes to run that query. and the more rules you make, the longer it might take your clients to run software inventory.

Resolution: whenever possible, forget creating software (file) inventory rules. This blog post will show how to setup a rule looking for dropbox.exe on c:\users\, and you can get back File Version so you can run reports.

Why I used dropbox.exe... dropbox.exe may not be listed in Installed Software, nor in Add/Remove Programs. It might be listed in ccm_recentlyusedapps. Using this as a sample, after you've deployed this, run this .sql query to see which computers, the version, and path.

One interesting caveat: every time you change a ConfigItem (add something) the vDCMDeploymentNonCompliantRuleDetailsPerClientMachine will "reset", so if you don't want to "lose" history, you'll want to likely simply make more CIs. Not edit existing ones.

This sample was to show you can get version of any dropbox.exe file, for reporting purposes. If, for example, what you really need to be able to do is create a collection of "machines where widgets.exe located in c:\program files\widgets is less than version 5.4.3.2", then make a ConfigItem for widgets.exe, in that folder, and "compliant" means version is greater than or equal to 5.4.3.2. You can then easily right-click the CI and make a collection of Non-Compliant machines.

3a8082e126