Visual Studio Code Version : 1.18.0 Insiders
Code Settings Sync Version : 2.8.5
Operating System : Windows 10
Occurs On: VSCode Start and Download
Proxy Enabled: No
GIst Id: It is a private gist.
What I did was install VSC, Install the sync plugin, and then I added my token and then I edited my user settings and told it to use my existing gist. (sidenote, I think the app should ask you if you want to use an existing gist or create a new one. Getting a fresh install of VSC up and running is not a friendly experience.)

Remove the sync.version from settings.json and try.
Did you install Settings Sync first time ? or updated / reinstalled after a long time ?
As this key is removed from settings.json
@shanalikhan I installed the normal non-insiders build and everything is working.
It appears your extension is broken on the insiders build of Visual Studio Code.
Didn't mean to close this. Re-opened.
What is the exception on insiders
Error: Unable to write to User Settings because sync.version is not a registered configuration.
/resources/app/out/vs/workbench/workbench.main.js:10
Have u tried removing sync version key from settings in insiders build?
Or is it occuring everytime even after removing that key from settings json
That key does not exist. I think that is what the error is saying. It's
saying it can't find that key.
On Nov 8, 2017 9:25 AM, "Shan Khan" notifications@github.com wrote:
Have u tried removing sync version key from settings in insiders build?
Or is it occuring everytime even after removing that key from settings json
โ
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/shanalikhan/code-settings-sync/issues/444#issuecomment-342851653,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACzG65MlffKXHl0hDeeHbGNN1KRrFEGHks5s0cgBgaJpZM4QVz1D
.
It does happen in the stable release of VS Code (1.18). And I could not find sync.version in my User Settings. There is a "version" key which should appear in syncLocalSettings.json
This error message comes from https://github.com/Microsoft/vscode/blob/06d659f33fa4aaacc1ac874417d898f00acef216/src/vs/workbench/services/configuration/node/configurationEditingService.ts#L281
And the meaning of this error code:
Error when trying to write a configuration key that is not registered.
The trace shows that it is caused by calling writeConfiguration. Apparently this method is still deeply inside VS Code API, so I could not find the real cause.
PS. The file onfigurationEditingService.ts I mentioned above has changed in last few days. The most recent change happened 2 days ago. The history: https://github.com/Microsoft/vscode/commits/master/src/vs/workbench/services/configuration/node/configurationEditingService.ts
i will need your GIST ID in order to reproduce at my end.
Also check either you have saved sync.version in settings.json inside your GIST.
If Gist contains it, remove this from gist from github and then download the gist again and let me know
It seems that as soon as I have upgraded to 1.18 it triggered this error. I have tested on 2 computers and it worked fine on 1.17, but after the upgrade this error showed up.
@danutzcodrescu does your gist have sync.version in settings.json file ?
@shanalikhan I do not have a sync.version any more and I still get the error. I have deleted the sync.version prop as soon as I have upgraded to 1.18 both in the settings.json and in the gist. However, the error still shows up. I have even tried with a clean new installation and a new gist.
Have the same issue with ubuntu:
Visual Studio Code Version : 1.18.0
Code Settings Sync Version : 2.8.5
Operating System : Ubuntu 16.04
Occurs On: VSCode Start and Download
Proxy Enabled: No
GIst Id: It is a private gist.
Have the same issue on Manjaro Linux
Visual Studio Code Version ๐ 1.18.0
Code Settings Sync Version ๐ 2.8.5
Operating System ๐ Manjaro Linux 17.0.2
Occurs On ๐ VSCode start new window
Proxy Enabled ๐ No
GIst Id ๐ It is a private gist ๐
Have this issue too. sync.version does not exist in my settings.json. Attempting to add it also yields a warning/error that it is not a valid key anyway.
Same Problem here,
Visual Studio Code Version ๐ 1.18.0
v2.8.6 release fixing this.
Let me know if anyone have still problem.
same here
Most helpful comment
v2.8.6 release fixing this.
Let me know if anyone have still problem.