I know this is an edge case but am hoping it can be patched rather than convincing my users to stop using // in their file names.

I'm syncing between Google Drive and a Windows 2016 server and have a path that looks like this:
\Audio\Visual Technology\Producer Checklists\Producer Sunday Responsibilities // Template
I receive the following error:
Failed to copy from Google Drive: Cannot create file "\\?\path\to\file\SBSE___.HYF"
I suspect the issue is the way that SyncBack is reading the file name, in the left-hand column of the error report where it lists the file that failed to transfer it has this path:
\Audio\Visual Technology\Producer Checklists\Producer Sunday Responsibilities%20\\ Template
Note that SyncBack has reversed the // to make them into part of the path.
Thanks!
Dave