I have created the oauth authorization for a friend of mine. He's not tech-savy, so he shared his password with me (we are very good friends and in the same Drive organization) and I did a full configuration for a Drive mount for him. Passed him the resulting rclone.conf and a batch file to launch the mount.
Before doing this I tested the mount and I was able, from my machine, to access Drive, copy files, etc.
He copied the files I passed to him, installed WinFsp (Windows 10 machine) launched the batch file and the mount appeared. Files and folders are listed correctly.
But if he tries to access files... either the program accessing them crashes/hangs or the copy dialog appears and never makes any progress. No network traffic, nothing.
The following appears in log after trying to copy a file from Drive to a local drive. I'll provide verbose log if needed but for now this is what I have:
The service rclone has been started.
2020/05/13 16:28:44 ERROR : RANDOMVIDEO.avi: ReadFileHandle.Read error: low level retry 1/10: read tcp 192.168.1.133:56834->184.108.40.206:443: wsarecv: Connessione in corso interrotta forzatamente dall'host remoto.
2020/05/13 16:46:34 INFO : Starting HTTP transaction limiter: max 10 transactions/s with burst 1
Again I stress: the very same .conf file with the same credentials and same mount command line works just fine. We tried disabling the firewall on his PC to no avail (but rclone uses port 443 so I doubt the firewall could be the problem in any case).
What is your rclone version (output from rclone version)
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Windows 10 x164
Which cloud storage system are you using? (eg Google Drive)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
So far the above mounting command was issued through a batch file, on a double click, no admin permissions were requested, hence I guess none were granted. Again: Drive content are displayed correctly on the mount, all directories, all files. The problem comes only when accessing them or trying to copy them locally.
I don't currently have access to the machine where the problem is found but I would suspect it would work correctly, considering that the Q: drive is mounted and its contents displayed correctly in Explorer.