I had this problem and putting a file in the folder did not resolve it, it immediately re-created the folder after I deleted it from the Finder (Mac 10.13.3). What did work was to choose Pause Syncing from the Dropbox menu bar widget, delete the file in Finder, then create a new folder with the same name (this is what I was trying to do in the first place). After resuming syncing, it left it alone.

I had this problem and putting a file in the folder did not resolve it, it immediately re-created the folder after I deleted it from the Finder (Mac 10.13.3). What did work was to choose Pause Syncing from the Dropbox menu bar widget, delete the file in Finder, then create a new folder with the same name (this is what I was trying to do in the first place). After resuming syncing, it left it alone.

Russell R.1 - Do you really think that we are that stupid?????? we have deleted via the browser, we have unsynced and resynced our devices, we have added a file then tried to delete the folder only for an empty folder to come back, we have done all this in the browser on every machine (across 3 continents!) and still the sub folders reappear. They are not the root shared folder and as the admin of this shared folder I cannot delete and empty the folder (with empty sub folders) on any device or from the browser. I have systematically gone through all the solution over the nine pages of this thread and have found no workable solution. The only thing that save my sanity is that I have selectively unsynced the offending folder from my own devices......but all that does is hide the offender from my sight - it does not solve the problem! Dropbox FFS solve this would you.

When we delete or rename a folder it comes back. It doesn't matter what computer or if we are on the website,  If the folder is renamed, or moved within hours or the next day both the old folder and the new folder reappear.  Or if we simply delete a folder it also comes back. There are hunderes of folders that have been moved, renamed or deleted and keep reappearing. So frustrating and time consuming, how can we stop this from happening?

Hi LisaMVIP,

Let me guess: You try rename/move folders in online only mode...? This is known problem  and you already have done the possible: One more voice!

I'm experiencing this problem as well. 

Hey LisaMVIP & billiesoniq, I have now made sure to move your posts under this ongoing conversation, as the hints we’ve posted here with Walter have resolved the OP’s inquiry. Would you mind checking those out whenever you have a bit of spare time & let us know here if you have any follow-up questions?

Thanks & I’m looking forward to hearing back from you! 

Many thanks to the Dropbox team - especially Walter for helping me resolve this issue. In my case one fo the 9 sharers of a top level folder was adding back a multi layered sub folder, containing no files, each time the administrator attempted to delete it. All sharers told me that they had attempted to delete the reappearing folder........drilling down by the DB team revealed the culprit who hadnt actually made an attempt to delete but merely said he had! Deletion done and all fixed.....woohoo, champagne celebration! but....

How do you fault find without using the DB team in this case? Two options: make use of Event History and Version History. Using event history showed where I had attempted to delete the folder but did not show who added it back. Version history would not have worked as it only applies to actual files and not folders (this folder structure contained no files). I would suggest adding in a file, delete the folder structure, if it all reappears then check the version history of the individual file - it should show you deleting it and then should reveal who is adding it back. Note the use of \"should\"! What seems clear is that there are numerous ways that this \"reappearing ghost\" problem can be solved. Perhaps DB could set up a really detailed help page, that can be easily found, that covers all the myriad permutations of this challenging problem.

Once again - big thank you to the DB team for their prompt and detailed assistance. GuyM