Insync slows down and crashes Windows Explorer + other Bugs

Bugs and issues Windows
#2

Try this for at least a temporary workaround:

  • Uninstall Insync
  • Reinstall Insync, BUT when the installer asks for admin privilege, deny it.
  • Insync will then tell you it can install without admin privilege (but some features will be limited), accept this option.
  • Continue to install and run Insync

Insync needs admin privilege to interact with Windows Explorer, to show overlay icons and add entries to context menu etc. Without it, Insync shouldn’t interfere with Windows Explorer.

It’s odd that you’re having these problems even on new Windows machine though. I’m not having such problems on Win 7 or Win 10. Could it be that another program is in conflict with Insync?

#3

Hey @JohaWeber!

Apologies for the delay. Tagging our Windows engineer @Rajat o take a look again at the issue. :slight_smile:

#6

Thank you for the tips! But sadly, I already tried to use and install Insync with and without administrator permissions… Always the same problem.

I don’t think, that another program could be in conflict with it - because it also happens if nothing is installed on a fresh windows installation than insync.

#7

Now, out of nowhere, today Insync tells me that a lot of stuff got removed although I DID NOT REMOVE any of those files nor did any of my coworkers!

Insync_2018-09-16_13-15-43
Insync_2018-09-16_13-15-43.png800×589 57 KB

I checked some of the notifications and it seems to affect both my personal Google account as well as the G Suite account of my company. BUT: when checking all the files online - everything is still there and in the Insync UI those folders are set to be synced but when checking the synced folders on the computer, those files and folders are actually removed!!! I repeat myself: Nobody did remove those files! There are a lot of team drives and folders of projects that no one is working on since … the upload of those files!

EDIT: About 50GB of data were actually moved (by insync!) in the related .insync-trash folders of the affected team-drives and at this moment Insync starts to recreate all those folders… and hopefully redownloads the files. that are still available online… wtf… I never deleted those folders/files!

#8

I experienced similar problems when testing an early test build of 1.5. In all occurrences, files remain in the cloud. So you probably don’t need to worry too much.

I do think Insync released 1.5 too early. Some more beta testing seems necessary.

#9

@JohaWeber Please send the Insync logs and dbs to us so that we could look into this. Create a copy of the “dbs” folder (present next to the logs.db file), compress it and send it to us along with the log.db file at support@insynchq.com.

1 Like
#11

Any updates on this one? I have already sent the logs…

#12

Hey @JohaWeber,

I’ll follow this up again. :slight_smile:

#13

It’s now almost a week ago and I did not even get a “guess” of what could be the problem. Still a lot Errors with “can’t start a new thread”, failed access of accounts, missing folders and files, problems with the Windows Explorer and so on…

#14

Also when right-clicking on a folder or a file in the Insync UI and choosing “View on Drive Web” - there’s a 50% chance of Insync crashing and shutting down. I then have to manually restart the program…

#15

Hey @JohaWeber,

We’re been taking a look at the issue and have replied to your email. :slight_smile:

#16

@dipesh @Gregory and people that stumble across this issue and have the same problems: After unsyncing some of the folders with either lots of files (100+) or few very big files (1GB+) the windows explorer works properly again.

This temporary solution until the real issue is solved was brought to me by Insync’s support-team (just for the record).

#17

Problems still persist in the version 1.5.4

#18

There are certainly at it will manage the part for the valuable part in sync slowing down it where the crashed windows explorer and other which canon error b200 will be going it for the process to catch it.

#19

@david_brat I don’t really get your message/point - sorry! :frowning: Perhaps you can explain it further? :slight_smile:

@Gregory Still a lot of important files that get removed only on my machine (not online) and then resynced when opening the folder on drive.google.com - very frustrating! And it drives one insane when you think “I absolutely know I put the file in this folder and Insync is done with its syncing stuff and every folder and team drive and file has a green check mark on it in the UI” and then: WHOOPS! Nothing there! Taking a look at drive.google.com then shows the file in the right location. And the big resync-and-opening-files-and-folders-game starts again just to trigger Insync to download the stuff properly… Which I thought is the whole point of having insync!? To not have to worry about syncing processes? :triumph::rage:

#20

Thank you for the information.

#21

It’s possible that an earlier faulty version of Insync corrupted your sync database (specifically selective sync settings), leading to the file loss you’re experiencing now. It’s not necessarily the fault of the current Insync version.

I had confirmed similar experiences with an early test build of 1.5, and unconfirmed suspicion of a 1.4.x build. I was able to fix the problem using a custom script (playing around with GD API and SQL query) to fix all the selective sync settings in the database.

@dipesh any thoughts? Any plan on releasing tools / features for users to refresh / verify / fix their Insync database?

1 Like
#22

@hawk that sound like a possible error! Any way to get this custom script?

@dipesh a function to fix / verify / refresh insyncs database would be more then helpful…

#23

The script is something I wrote myself. I don’t seem to have saved it. It’s very user-unfriendly anyway.

What it does to the database is very simple, just find the file_id of all the files & folders you want synced, and set their corresponding value to “S” (sync) in the table responsible for selective sync settings.
The difficult part is getting all the file_id’s. The most powerful method is of course playing around with GD’s public API directly, but it’s quite messy. Some tools that can probably help ease the pain are gdrive and rclone.

A caveat is that, while I’m sure this process can help prevent future file loss, I’m not sure if it can trigger a resync for files that are already unsynced.

1 Like
#24

All Problems still persist/occur.