High CPU usage even when not syncing or indexing

Hi Walter 

Everything that is mentioned in that article is not the case for me (and most others). Also, by the answers just in this thread all off the discussed "problems" can be outruled.

But just to summarize it again:

1. Dropbox is syncing a large number of files
   Simply.....NO! I have way fewer files in my Dropbox than compared to 2019 for instance. Also, I'm only synchronizing the absolute bare minimum with my computer. Right now due to cooperation works around 223k files. At peak times in 2019 I synced my whole Dropbox to my PC, resulting in way over 4 Million files. Never caused any trouble back than.
   I do get high CPU and RAM loads while Dropbox is idlying (according to the client, but not according to the windows task manager). But the truth is, since Windows 10 got the update on the Explorer and the usage of symbols in the explorer, Dropbox Client goes mayham and is battling with the search indexer, MS antivirus etc.
   
   How do I know? Well....as soon as the Dropbox client is "idlying" one of the mentioned MS processes checks on what Dropbox has done to the files and updates the symbols. Once they are finished, Dropboxs' cpu and ram load skyrockets and from the task manager I can see my hard drive is being actively used by dropbox processes. Once the dropbox processes calm down, the MS processes take over again and the cycle starts all over again. I watched this circle for a total of 4 days straight! The computer was running round the clock, I haven't touched the mouse or keyboard once in that time!
   
   I already tried anything I could find in this forum, this includes re-installing the dropbox client, reducing the number of files, deactivating the MS indexer (which is a nightmare when you need to access files frequently) and antivirus (if I have to explain to you why this is bad I'll immediately cancel my dropbox subscription).
   
   So for fun and giggle.....I did some experiments. W10 in a virtual machine, Linux Mint on a second hard drive with own Dropbox folder (not official client I believe). And well.....Linux Client works like a charm, after syncing 0% CPU load....as it should be. But the CLEAN freshly installed W10 in the VM......after syncing the CPU loads are still trash. Exactly like on my regular W10 installation.  
2. Other apps interfere with sync
   The only other "PROGRAM" that is connected to dropbox is Microsoft Office. But even this is not running for the majority of time. because....you guess it: It causes high cpu loads. Currently....I CAN'T work with Dropbox client running and MS Office....because when the Dropbox Client is gulping on my CPU my Office completely freezes, typing only 1 letter every ~10seconds. I reinstalled Dropbox Client and Office already....nothing helped.
   I also turned off my Phone to prevent a secondary device causing trouble...again, nothing changed.
   
   And final note to that point: I don't run any programs that are being installed in Dropbox, so no temporary files causing issues. Everything is just data files of various types.
3. Files in your Dropbox folder have the wrong permissions
   Windows file permission handling might be a mess, but this is one thing that hasn't changed in W10 at all if I remember correctly. The dropbox client (and my windows user account on the local machine) have full access to the dropbox files that are synced to my drive. No permission violations or anything, not even an entry in the event-manager about wrong permissions.
4. The Dropbox folder is installed on a NAS device
   Nope. Regular SSD in my computer.
5. Your device doesn’t support extended attributes
   Nope. Since I'm running the regular client on my Windows installation, the file system is NTFS as requested. 

So.....after this is answered back to the topic:

The issues came with the Windows explorer update and symbol handling. Ever since the dropbox client is running in circles with the MS processes.

I worked/work with many different cloud services, some with/without clients, some only available under Linux etc etc.....you get the point. But the dropbox windows client is without a doubt the most un-optimized and problem causing client I've ever used at this point. It has nothing to do anymore with it's previous glory from 2019 where it just worked and where you would only get CPU load when the client was actually syncing files. As I mentioned, the issues were caused by MSs changes in the explorer......but this is how W10 and W11 are now working, this won't change. What's missing is your adaption to the problem.

But I guess not enough users are complaining about this sh** because they just assume their PC is either not powerfull enough or they don't care about how well their PC is running. But honestly.....I don't see myself working with Dropbox in the future with these rising problems.