Google Drive for Desktop Syncing - strange syncing issue

As those of you who have helped me previously will know, we have four near-identical Windows 10 computers, all HP Elite 8000 series, all running Win 10 22H2 64 bit

We have Google Drive for Desktop installed on all of them, all connected to a common Google Drive account. When we upload photos to Google Drive, three of them automatically download the files to their respective Virtual Drives in ThisPC, but one of them I will call it "Computer A", always requires manual downloading by pausing and restarting syncing. It doesn't seem to matter how long I leave it, this one computer will not fetch changes automatically. Storage is not an issue, as we are never using more than 3-4 GB of the 15GB allowance.

Curiously, when I delete a folder already in the Virtual Drive, it successfully reflects the changes online, and subsequently, in the other three computers' Virtual Drives. Furthermore, if I have a folder of files in Google Drive on line, and I delete a folder in the Virtual Drive on Computer A, it does not download the online folder. I would have thought that deletion would trigger the syncing and download the folder, but it doesn't.

To me, this seems that is it checking for changes on the computer itself, but not on the drive online.

Here is what I have tried so far to resolve this issue.

1. Restart Computer

2. Quit and restart Google Drive for Desktop

3. Quit and disconnect account and then restart Google Drive for Desktop and go through setup again

4. Quit and uninstall Google Drive for Desktop. Download the latest version and set up again

5. Restarted our internet modem.

6. Temporarily turned off the firewall (to see if Google Drive was being blocked)

ETA: 7. Tried running Google Drive as Administrator.

Its possible that there was something that was not uninstalled or removed, such as a setting or a registry entry when I uninstalled Google Drive for Desktop (though I did delete the "Drive File Stream" folder from Program Files>Google before reinstalling)

My next step ought to be to completely remove all traces of Google Drive for Desktop from the computer, before reinstalling, but I don't know how to do that.

Anyone have any other ideas as to what I could try?

Capture Google Drive for desktop logs for support - Google Workspace Admin Help

bro67 said:

Capture Google Drive for desktop logs for support - Google Workspace Admin Help

Yeah, I've given up hope of getting any support from Google. They are worse than useless.

It is obvious that you did not even go to the link I posted to find out how to generate the logs.

bro67 said:

It is obvious that you did not even go to the link I posted to find out how to generate the logs.

Let me make this clear. I had already done what you suggested before I even posted here.

My post requesting help at the Google Community is still unanswered after.... five weeks
------------------------------------------------------

In the end, I have fixed this myself. Here is what I did...

1. Uninstall Google Drive for Desktop.
2. Restart the computer.
3. Download Glary Utilities and use its Registry Repair function to list all invalid registry entries.
4. Search through the list and delete all entries that appear to be related to Google Drive.
5. Restart the computer.
6. Re-install Google Drive For Desktop, but log into my personal Google Drive account, a different account, which I use on my home computer.
7. Tested and it worked fine.
8. Uninstalled Google Drive for Desktop.
9. Restart the computer.
10. Use Glary Utilities Registry Repair function to list all invalid registry entries.
11. Search through the list and delete all entries that appear to be related to Google Drive.
12. Restart the computer.
13 Re-install Google Drive For Desktop, and logged into the regular work Google Drive account.

This fixed the problem. I figured the cause was possibly one or both of two issues.

1. One or more registry entries that were not being removed when I was uninstalling GDFD (I do wish developers would design their uninstallers to remove everything they install).

2. Some config setting that had become corrupted and was not being removed on the uninstall. By logging into the different account, that config might be overwritten. If so, then by logging back into the original account, the config would be overwritten again with the correct data for that account.