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
Drop box is stuck at "Starting..." but files are being synced
The box icon on system tray stays at gray and says "Starting...". But, when files are changed on another computer, they are being synced. Should I be concerned? Is there a fix? Thanks.
Hi again to all,
This should be resolved now. Please restart your Dropbox desktop or mobile app and try again.
Let us know if you are still receiving an errors or you're experiencing anything out of the ordinary & we can look further into it.
Thanks to everyone for your reports & happy Dropboxing ahead!
Same problem here (sync working, but showing "Starting..." on menu bar). Using MacOS High Sierra, and latest Dropbox (55.4.171). I wasted my time re-installing and re-syncing everything - it is obviously a Dropbox issue, so let,s just sit tight and wait for a fix.
Adding my voice here.
I'm seeing the same thing across 3 computers: two Windows 10 PCs, one MacBook Pro.
Symptoms began around the same time on all 3 machines, which was some time last night, August 13th, between 19:30 and 22:30 ET.
All 3 show "Starting..." as the status from the Dropbox taskbar icon/flyout. (Previously "Indexing..." before I closed and restarted Dropbox on each).
The two Windows machines show the Recent Files history in the flyout, and the Notifications tab and the 3 Dropbox Paper / Dropbox Folder / Dropbox.com icons are accessible.
The MacBook shows a blank flyout (with a "Dropbox is starting...." message only) and the Dropbox Paper / Dropbox.com icons are greyed out.
All 3 machines have had Dropbox closed/restarted (multiple times) and have been completely rebooted without change.
Files and folders do appear to be syncing successfully between all 3 machines (and other devices) successfully, regardless of the erroneous "Starting" messaging, so this isn't actually a service-impacting bug, only a display issue.
