I have been running rclone with OneDrive since about 2 years.
Recently i updated my Windows Server 2025 to the May update. Reverting back to March didnt help.
Since then sometimes my OneDrive mount (D:\ just stops working. I have to restart the Rclone service (Rclone is configured as a Windows service) - after that the mount works again.
Between 2-5 days the mount works without any problem.
Run the command 'rclone version' and share the full output of the command.
rclone v1.69.3
os/version: Microsoft Windows Server 2025 Standard 24H2 24H2 (64 bit)
os/kernel: 10.0.26100.4061 (x86_64)
os/type: windows
os/arch: amd64
go/version: go1.24.3
go/linking: static
go/tags: cmount
I use WinFSP 2025 update. Same error appears with 2023 and both 2024 betas.
All Windows drivers are up-to-date. No network errors/timeouts/outage.
Which cloud storage system are you using? (eg Google Drive)
OneDrive for Business (Azure cloud app is configured)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.
[Backup]
type = crypt
remote = OneDrive:Backup
password = XXX
[OneDrive]
type = onedrive
auth_url = Sign in to your account
token_url = Sign in to your account
access_scopes = Files.Read Files.Read.All Sites.Read.All offline_access
token = XXX
drive_id = XXX
drive_type = business
A log from the command that you were trying to run with the -vv flag
2025/06/16 22:17:58 CRITICAL: Fatal error: failed to mount FUSE fs: failed to retrieve mountpoint path information: CreateFile D:: The I/O operation was aborted due to thread termination or application request.
It seems like a strange error you are having, with it working for a few days then stopping. I am not the most technical but I will try help!
Could it be Windows killing the service via the service manager?
Could you be running out of disk space? You could trying running with vfs-cache-mode writes instead of full if that works for your use case as that will use less disk space.
It would also be worth adding --log-level DEBUG instead of ERROR and posting the output here as this will show us how rclone is trying to interpret your command.
the Windows Service is still running - the Windows event log shows:
The time limit (30000 ms) was reached while attempting to connect to the Rclone service.
Disk space is not the problem. Always more than 700GB free. "Write" will not work since i need to read and write (= full) all day long (encrypted backup of my work).
I will change to DEBUG. Do you need the output when my mount crashes or...