Rclone 1.65.1 runtime exception error - crash immediately after running the command

What is the problem you are having with rclone?

Can't start the command - immediate crash
OS: Windows 7 Pro SP1 32-bit

Run the command 'rclone version' and share the full output of the command.

Can't share 'rclone version' output because of immediate crash
Happens with latest stable version 1.65.1
Last good (working) stable version: 1.65.0
Last good (working) BETA: rclone-v1.66.0-beta.7561

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

Exception 0xc0000005 0x8 0x0 0x0

        runtime/sys_windows_386.s:35 +0x25 fp=0x12fe68 sp=0x12fe64 pc=0x47a535
eax     0x8
ebx     0x36a84ac
ecx     0x0
edx     0x12fe90
edi     0x12fe6c
esi     0x12fec4
ebp     0x12fe6c
esp     0x12fe60
eip     0x0
eflags  0x10202
cs      0x1b
fs      0x3b
gs      0x0


The rclone config contents with secrets removed.

type = drive
scope = drive
token = {}
team_drive = 

type = onedrive
token = {}
drive_id = 
drive_type = personal

A log from the command with the -vv flag

Sorry no logs

welcome to the forum,

i wonder if this is the issue?
Go 1.20 is the last release that will run on any release of Windows 7, 8, Server 2008 and Server 2012.
Go 1.21 will require at least Windows 10 or Server 2016.

here is a similair issue: runtime.asmstdcall + Go 1.211 + windows 7
Due to being compiled with Go 1.21, Syncthing no longer supports Windows 7

Still using Windows 7... I know that sometimes there are reasons for that, but clearly you know that less and less new programs will work on this platform.

Sooner or later you will have to stay on the last version of rclone working on Windows 7 which reached end of life 4 years ago. This is unfortunately how it is.

1.65.0 and 1.65.1 should have been compiled with the same go compiler go1.21.x unless I messed up the point release.

rclone version will say.

So slightly puzzled about the versions...

rclone v1.65.0
- os/version: Microsoft Windows 11 Pro 22H2 (64 bit)
- os/kernel: 10.0.22621.2715 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.21.4
- go/linking: static
- go/tags: cmount

rclone v1.65.1
- os/version: Microsoft Windows 11 Pro 22H2 (64 bit)
- os/kernel: 10.0.22621.2715 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.21.5
- go/linking: static
- go/tags: cmount
1 Like

I have tried on Windows 7 64 bit VM I had in some old archive:

v1.64.2 - works
v1.65.0 - works
v1.65.1 - failed
v1.66.0 - failed

In line what @asdffdsa found go v1.20 is the last version working on Win7. That rclone v1.65.0 still works is probably a fluke ( go1.21.4 vs go1.21.5).

C:\Users\kptsky\Downloads\rclone-v1.65.0-windows-amd64>rclone version
rclone v1.65.0
- os/version: Microsoft Windows 7 Professional Service Pack 1 (64 bit)
- os/kernel: 6.1.7601.24546 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.21.4
- go/linking: static
- go/tags: cmount

C:\Users\kptsky\Downloads\rclone-v1.65.1-windows-amd64>rclone version
Exception 0xc0000005 0x8 0x0 0x0

        runtime/sys_windows_amd64.s:65 +0x75 fp=0x22fca0 sp=0x22fc80 pc=0x474715
rax     0x0
rbx     0x3a298a0

Should we mention somewhere in docs that rclone v1.65.0 is the last one working on Windows 7 platform? I can add "Compatibility" section on download page? Or maybe it exist somewhere already. Any thoughts?

Officially last Win7 working version should be rclone v1.63.1 (last one using go 1.20)

Similarly on macOS:

As announced in the Go 1.20 release notes, Go 1.21 requires macOS 10.15 Catalina or later; support for previous versions has been discontinued.

That is strange. The go team doesn't introduce breaking changes in point releases. Here are the changes for go1.21.5, none of which look particularly relevant.

The code is crashing in runtimeĀ·asmstdcall which is an assembler routine and the way Go calls the Windows runtime.

I don't propose to investigate this further since the Go team have already said go1.21 will require Windows 10 or later so I think filing an issue wouldn't be productive.

Maybe rclone v1.65.0 was working accidentally somehow?

Note that you can compile v1.65.x with go1.21, go1.20 and go1.19

You'll be able to compile v1.66 with go1.22, go1.21 and go1.20

So you'll be able to have the latest rclone for a bit longer on Win 7 if you are willing to compile it yourself.

We probably should be talking about this somewhere...

And yes we should probably state v1.63.1 as being the last version as I don't know why the later ones are working at all, and maybe they will blow up in some different way.

We should probably have a little section in each architecture in the install doc, eg here is the windows install

This could have a little table something like this (probably not correct)

Rclone version Supported Windows Versions
current Windows 10 or later, Server 2016 or later
v1.63.1 Windows 7 or later, Server 2008 or later
v1.XX Windows XP...

We could have a similar table for macOS versions and for linux kernel versions.

To make these tables this will need a bit of software archeology looking up the go release notes and working out which rclone was compiled with which go version.

The download page should probably show a summary table something like this for the latest versions

Required OS versions

OS Minimum Version
Linux 2.6.32
macOS 10.15
Windows 10

I got those figures from the go download page which are for go 1.21

@kapitainsky can you make an issue about this and we can start collecting the data for the various doc sections - thank you :slight_smile:

1 Like

Here you are including relevant "archaeology":

1 Like


Back to your issue.

The last rclone version you can use safely on Windows 7 is v1.63.1.

rclone v1.64.2 and v1.65.0 working is not expected and you risk some other problems using them.

You can make them perfectly safe by building rclone from source and using golang v1.20. You can also compile rclone v1.66.

As soon as rclone moves to golang v1.23 it will be the end of Windows 7 story for rclone (as minimum golang version to compile will be v1.21).

Well , I guess it's really time for me to finally give up Win7. Thank you all for your help :slight_smile: For now I'll stick with the latest working release until I move on to new OS

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.