What is the problem?
When copying files from a Box remote to a local Windows filesystem, rclone copy and rclone sync unexpectedly modify filenames.
This only happens during the copy/sync operation.
Example:
Original filename in Box:
＜Test＞.txt
Copied filename:
‛＜Test‛＞.txt
The inserted character is:
U+201B (SINGLE HIGH-REVERSED-9 QUOTATION MARK)
The same issue occurs with other full-width characters corresponding to Windows reserved filename characters.
| Original | Copied |
|---|---|
| ＜ | ‛＜ |
| ＞ | ‛＞ |
| ： | ‛： |
| ？ | ‛？ |
| ＊ | ‛＊ |
| ｜ | ‛｜ |
However, this filename is copied correctly:
！Test.txt
No extra character is inserted.
Environment
- rclone v1.74.2
- Windows 11 Pro 25H2
- Box backend
- NTFS destination
The Box remote uses the default configuration (no custom encoding option).
Steps to reproduce
-
Create a file in Box:
＜Test＞.txt -
Run:
rclone copy "Box:TestFolder" "C:\Temp\Test"
or
rclone sync "Box:TestFolder" "C:\Temp\Test"
- The copied filename becomes:
‛＜Test‛＞.txt
Additional investigation
I performed several tests.
rclone lsfshows the correct filename.- Debug logs also show the correct filename.
- The filename changes only after the local file is created.
- Local → Local copy with rclone does not reproduce the issue.
- Windows Explorer copying from Box Drive does not reproduce the issue.
- PowerShell confirms that the inserted character is actually
U+201B, not just a display issue.
PowerShell output:
‛ U+201B
＜ U+FF1C
...
‛ U+201B
＞ U+FF1E
It appears that only full-width variants of Windows reserved filename characters are affected.
