So after many attempts on Intercom and after the sending of multiple logs and dbs and no real helping answer up until today and after multiple version incrementations which did not fix the issue:
On v1.5.1 Insync still crashes Windows Explorer and slows it down significantly. It crashes when trying to create a new folder, rename files or just right-clicking anywhere on the desktop or inside the windows explorer as long as Insync is sitting in the task bar - syncing or not syncing, that does not matter: its simple presence is sufficient to create problems. I tried multiple weekends to narrow the problem down to insync and try to start and restart and quit other programs, try different physical drives as the location where the files downloaded to/synced from, multiple clean windows installations, heck I even bought a new computer.
It tried everything to solve it on my own. Problem always did reoccur. So whenever I quit Insync… my machines run well and windows behaves as it should.
A screenshot of how the windows explorer behaves: Not loading properly when starting/opening it, the green loading bar then moves extremely slowly over multiple hours to the right and nothing happens if you click anywhere. Frustrating. To create a new folder I have two options: Quit insync, create folder, restart Insync. Or just attempt to create a folder and see windows crash immediately and let it restart the windows explorer, navigate where I wanted to create the new folder in a new explorer window and then find a new folder labeled “New Folder” and then attempt to rename it - hitting enter after the renaming then results in another crash so I repeat the step with the navigation in a new explorer afterwards. Yeah. So therefore the best option is to work, without insync enabled and sync stuff at the end of the day after starting the client. Guess what? My coworkers hate me! Because no files are synced up until the end of the day! Nice! …not.
As a bonus: I get multiple “Can not sign into account blabla…” errors during the day and a lot of “Can’t start a new thread” errors although the corresponding files seem to be fine. Sometimes a restart of Insync helps, sometimes it doesn’t. Sometimes a computer restart helps, sometimes it doesn’t…
inb4: All types of drives/discs I was using were partly factory new products or not that old and read perfect health status via S.M.A.R.T. All drivers and versions of windows where updated to the latest versions. The old computer was an Intel, the new computer an AMD. Both with absolutely stable RAM-Configurations, enough computing power and stress tested for at least 2 hours on heavy load on all components with no error occuring.
PLZ HELP. I’m driving crazy and my last resolution would be calling the police.