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.
CertFindCertificateInStore failed with: (-2146885628) Cannot find object or property.
This is still happening even after a year of the Dropbox devs "looking into it." It's spamming my Windows logs, and Dropbox is also causing my machine to take 20 minutes to shut down or restart (uninstalling it fixed the issues). Reinstalling it made them all come back. So I have permanently uninstalled this app, and I'm canceling my subscription because the devs can't get their act together.
My Dropbox app is stuck at "Connecting" and I can't use compatibility mode either.
Hello, I have seen numerous/old threads on this "Unable to connect to internet" issue when launching the DropBox client but still no luck after multiple attempts. I use Windows 10 and everything connecting fine to internet. Of course I tried disabling VPN/Firewall and multiple uninstall/reboot/reinstall and nothing helps. I use latest version 211.4.6008 and even tried installing old ones (210.5.4894 and 197.4.7629) and this didn't help either Long time ago, I had this issue and I was told to run DropBox in compatibility mode. This was fine until recently when DropBox said that I couldn't do that anymore and as soon as compatibility mode is turned off, then I can't connect anymore. If I turn on compatibility mode, it connects fine, sync all files and then suddenly tells me that I can no longer run in compatibility mode and I have no other solution than to turn off compatibility mode and then it is no longer able to connect (stuck on "Connecting..."). Maybe this has something to do with SSL/TLS, I tried sniffing the traffic, enable disable IP v6/v4, tried on wifi vs. ethernet, and so on. Still nothing. So how can I use Dropbox on my Windows 10 machine? Is there any setting/registry entry/troubleshooting tool you can suggest? Please help. Thanks. Eric
Windows Server 2019: LTS App Still Shows Unsupported OS Message
I'm using Dropbox on Windows Server 2019, and recently it stopped working, saying, "Support for Windows 7, 8, and 8.1 has ended." They provided a link to download a "Long-Term Support" app, but after installing it, I’m still getting the same message, and it won’t launch. Has anyone else experienced this? It's frustrating, especially since I already installed the recommended LTS app. Any advice or workarounds?
Dropbox unexpectedly quits on Windows 10.
I have 4 sync computers and 1 cell phone It's normal on the website, it's normal on the cell phone, but two computers and two laptops Even if you synchronize, it will end, and it will end even if you delete it and reinstall it where you use it as the main pc. As a result, the folders overlap in duplicate and cannot be newly created with existing folders. The files are kept safe. Restart Dropbox to restart sync and other features. This situation suddenly happened I've reported help with vaccines, security, etc., but even after installing and rebooting, the above will continue to appear
Dropbox desktop app not working on MacOS Sonoma 14.5
my desktop app stopped working, when I click the home icon it continually says "connecting components" without ever getting there. any changes I make to files on my desktop are not visible in the online webpage or on the app on other devices. I have deleted and reinstalled the program multiple times to no avail. I am running macOS Sonoma 14.5 and the current dropbox installation is version 204.4.5420.
Dropbox Sync errors STILL on Windows Search folder
This is a repost of an issue I posted 7 months ago, when it first got on my nerves. "Dropbox Sync errors on Windows Search folder " The reply I got just fobbed me off, saying others haven't reported it - which may be true, but it doesn't answer the question, or address the issue. So not a good reply, was it? This post askes the same question again, clearly indicates the cause of the problem and suggests a solution. Please note the issue does not rely on any product or service other than Windows Search, the DropBox app and the Dropbox sync process. The problem occurs because Dropbox wrongly treats all data in the Dropbox tree as owned by <username>. It does not allow for folders temporarily created and owned by SYSTEM processes, such as Windows Search. Evidence I have relocated all <username> data files to a separate Data Drive D:, just as OEMs have done since Win XP. This is my Dropbox folder path and its contents (on a Win 11 box, tho' this is irrelevant) D:\Users\<username>\DropBox 'owner <username> Folder1... 'owner <username> Folder2... 'owner <username> Search 'owner SYSTEM Data 'owner SYSTEM Temp 'owner SYSTEM USGTHRSVC 'Read Permission is denied to Administrators The Dropbox System Tray window currently reports 46 Dropbox created issues... the Fix button does nothing to help, as all the error files are System files, not accessible to a normal Admin user Suggested Solution I suggest Sync should ignore any folder owned by SYSTEM, and this issue will disappear. NB It seems wrong in principle to copy SYSTEM owned files to any external system apart from a full imaging process initiated by SYSTEM. The above is 100% reproducible - assuming appropriate valid relocation of the DropBox folder Please test for yourselves and report back here. I await an update of the Dropbox app. I am using 211.4.6008 Spilly82
Couldn't start Dropbox on MacBook as I'm getting an error upon startup
I get this message when I try to start Dropbox on my new MacBook: Here is the error code file: bn.BUILD_KEY: Dropbox bn.VERSION: 211.4.6008 bn.constants.WINDOWS_SHELL_EXT_VERSION: 77 bn.is_frozen: True machine_id: e9fbddd8-3af2-522a-a19d-289295cebfd4 pid: 7366 ppid: 1 uid: 501 user_info: pwd.struct_passwd(pw_name='betsy', pw_passwd='********', pw_uid=501, pw_gid=20, pw_gecos='Betsy [removed]', pw_dir='/Users/betsy', pw_shell='/bin/zsh') effective_user_info: pwd.struct_passwd(pw_name='betsy', pw_passwd='********', pw_uid=501, pw_gid=20, pw_gecos='Betsy [removed]', pw_dir='/Users/betsy', pw_shell='/bin/zsh') euid: 501 gid: 20 egid: 20 group_info: grp.struct_group(gr_name='staff', gr_passwd='*', gr_gid=20, gr_mem=['root']) effective_group_info: grp.struct_group(gr_name='staff', gr_passwd='*', gr_gid=20, gr_mem=['root']) DYLD_LIBRARY_PATH: None cwd: '/' real_path='/' mode=0o40755 uid=0 gid=0 parent mode=0o40755 uid=0 gid=0 HOME: '/Users/betsy' appdata: '/Users/betsy/.dropbox/instance1' real_path='/Users/betsy/.dropbox/instance1' mode=0o40700 uid=501 gid=20 parent mode=0o40755 uid=501 gid=20 dropbox_path: '/Users/betsy/Dropbox' real_path='/Users/betsy/Dropbox' mode=0o40755 uid=0 gid=0 parent mode=0o40755 uid=501 gid=20 sys_executable: '/Applications/Dropbox.app/Contents/MacOS/Dropbox' real_path='/Applications/Dropbox.app/Contents/MacOS/Dropbox' mode=0o100755 uid=501 gid=20 parent mode=0o40755 uid=501 gid=20 trace.__file__: '/Applications/Dropbox.app/Contents/Resources/python-packages.zip/dropbox/client/ui/common/boot_error.pyc' real_path='/Applications/Dropbox.app/Contents/Resources/python-packages.zip/dropbox/client/ui/common/boot_error.pyc' not found parent not found tempdir: '/var/folders/6h/96b3td_n1cx_j515t_ckt8_c0000gn/T' real_path='/private/var/folders/6h/96b3td_n1cx_j515t_ckt8_c0000gn/T' mode=0o40700 uid=501 gid=20 parent mode=0o40755 uid=501 gid=20 Traceback (most recent call last): File "desktop/dropbox/fs_api/lifecycle.py", line 235, in client File "desktop/dropbox/fs_api/lifecycle.py", line 283, in _create_thin_client File "desktop/dropbox/fs_api/fs_api_adapter.py", line 50, in __init__ File "desktop/extensions/fs_api/fs_api_python.pyx", line 63, in fs_api_python.FsApiServer.__cinit__ fs_api_python.FsApiError: "Initializing fs api |>> Initializing application filesystem |>> Attempting to initialize dbx cache directory |>> Attempting to create ApplicationFilesystem cache directory |>> mkdirat |>> mkdirat syscall |>> Permission denied" The above exception was the direct cause of the following exception: Traceback (most recent call last): File "desktop/dropbox/client/main.py", line 951, in wrapper File "desktop/dropbox/client/main.py", line 7125, in finish_dropbox_boot File "desktop/dropbox/client/message_queue.py", line 306, in _wrapped File "desktop/dropbox/client/main.py", line 6572, in _init_components_for_account File "desktop/dropbox/client/main.py", line 6493, in create_sync_engine File "desktop/dropbox/sync_engine_boundary/factory.py", line 212, in make_sync_engine File "desktop/dropbox/sync_engine/nucleus/classic_client/sync_engine.py", line 243, in __init__ File "desktop/dropbox/sync_engine/nucleus/classic_client/modern_client/modern_client.py", line 295, in __init__ File "desktop/dropbox/sync_engine/nucleus/classic_client/modern_client/base.py", line 242, in __init__ File "../mac_arm64_dropbox_virtual_env/lib/python3.8/functools.py", line 967, in __get__ File "desktop/dropbox/fs_api/lifecycle.py", line 259, in client dropbox.fs_api.lifecycle.FsApiClientCreationException: "Initializing fs api |>> Initializing application filesystem |>> Attempting to initialize dbx cache directory |>> Attempting to create ApplicationFilesystem cache directory |>> mkdirat |>> mkdirat syscall |>> Permission denied"macOS Open dialog locks up app after installing Dropbox client
After installing Dropbox client on macOS, anytime any app attempts to open the macOS Open File dialog, the app locks up. This is any application with the macOS open dialog. As soon as I trash Dropbox from Applications, everything works again. I believe this has to do with migrating this user account from another Mac, as other user accounts on this computer do not have this issue. I've trashed the .dropbox folder in my home dir and Dropbox dir at ~/Library/Application Support, still have the same issue after re-installing. macOS 15.1I can't log into the desktop app due to "your code may have expired" error.
I have received a new work laptop with Win 11 installed. After installing DropBox on it, I tried to log in, so far quite a few times, but every time, I get a red message that says sorry your code may have expired, even though I enter the code immediately, so the problem is definitely not expiration. Could someone please help me fix this? Thank you
