Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config file version (37) is newer than supported version (35) #784

Open
31bado opened this issue Aug 26, 2023 · 9 comments
Open

config file version (37) is newer than supported version (35) #784

31bado opened this issue Aug 26, 2023 · 9 comments

Comments

@31bado
Copy link

31bado commented Aug 26, 2023

I'm getting the following error "Failed to initialize config: config file version (37) is newer than supported version (35). If this is expected, use -allow-newer-config to override." on WIN 11 - Home - 22H2. I'm using the latest versions of syncthing and synctrayzor.

How to use the command "-allow-newer-config to override"?

Can you help? Thanks in advance.

@as-loan
Copy link

as-loan commented Aug 26, 2023

I had this exact same issue. The problem was that I had launched the base Windows syncthing install prior to using synctrayzor. The synctrayzor install uses an older version at first launch, then updates to the latest version after starting. I fixed the issue by deleting the C:\Users<username>\AppData\Local\Syncthing folder and relaunch synctrayzor. When it launches, it will repopulate the syncthing folder.

@31bado
Copy link
Author

31bado commented Aug 26, 2023

I had this exact same issue. The problem was that I had launched the base Windows syncthing install prior to using synctrayzor. The synctrayzor install uses an older version at first launch, then updates to the latest version after starting. I fixed the issue by deleting the C:\Users<username>\AppData\Local\Syncthing folder and relaunch synctrayzor. When it launches, it will repopulate the syncthing folder.

Hi as-loan. Ok, I'll try this solution and see if it works for me.

Thanks!👍

@Fuger2021
Copy link

I had this exact same issue. The problem was that I had launched the base Windows syncthing install prior to using synctrayzor. The synctrayzor install uses an older version at first launch, then updates to the latest version after starting. I fixed the issue by deleting the C:\Users\AppData\Local\Syncthing folder and relaunch synctrayzor. When it launches, it will repopulate the syncthing folder.

bro you are my hero 👍

@jikaczmarski
Copy link

jikaczmarski commented Nov 14, 2023

Just want to confirm that this still works. I'm not sure what a possible code solution would be to this. More of a wiki entry in my opinion.

@31bado
Copy link
Author

31bado commented Nov 14, 2023

Hi Jesse. I upgraded to last version of Syncthing, didn't modify synctrayzor and, till now, it's working.

@jikaczmarski
Copy link

Oh sorry, I seem to have been a bit ambiguous. I meant to say that the solution of deleting the original Syncthing folder from AppData was a solution that still works. It's how I fixed my install last night.

@31bado
Copy link
Author

31bado commented Nov 14, 2023

Ok! Got it. 👍

@jonahquark81
Copy link

Alternative is to use the command line option as indicated in the error message.

Open settings (on the right side, toward the bottom)
Switch to syncthing tab
Open advanced section
add -allow-newer-config into the command line parameters box

Now restart syncthing. It will start, then upgrade to the latest version.

Once it has started OK, go back into the settings and remove the option. It will prompt to restart syncthing.

I suspect the option exists to provide this upgrade route without losing any config. It's not clear how much syncthing actually tries to do with the config before it switches to the new version. The syncthing site says

--allow-newer-config
Try loading a config file written by a newer program version, instead of failing immediately.

As the config is an XML file I expect (providing they do not introduce some change in the xml layout that breaks older code) it will load and the autoupgrade function will kick in before it does anything else.

@Rayisabc
Copy link

I had this exact same issue. The problem was that I had launched the base Windows syncthing install prior to using synctrayzor. The synctrayzor install uses an older version at first launch, then updates to the latest version after starting. I fixed the issue by deleting the C:\Users\AppData\Local\Syncthing folder and relaunch synctrayzor. When it launches, it will repopulate the syncthing folder.

It works!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants