nRF Connect for VS Code - SDK not recognized and west exits with code -2 after update to v2026.3.1484

[Bill]

After updating from v2026.1.1327 to v2026.3.1484 on Linux, all previously installed SDKs disappeared from the Welcome view — the extension no longer recognizes them. Attempting to update west from within the extension fails immediately with exit code -2. No changes were made to the environment between the two versions.

It seems that in v2026.3.1484, `toolchainInstallDir` reads `nrfutil-sdk-manager config show --json` output as `JSON.parse(e)?.install_dir`, but the actual JSON structure nests it under `default.install_dir`, so it always falls back to `~/ncs` regardless of configuration.

Verified workaround: rolling back the extension to 2026.1.1327 immediately fixes the issue.

Another workaround (which defeats the purpose of having a setting for selecting a different folder): create a symbolic link from the actual`ncs` foldet to `~/ncs`.

[Benjamin]

Hi,
Thanks for reporting. There have been reports of similar issues, we are investigating and I will come back to you with an update.

Regards,

Benjamin

[longo92]

Also on windows have similar issues. Any news on when a bugfix update will be release?

[longo92]

I have the same error message in devzone.nordicsemi.com/.../nrf-connect-vscode-extension-can-ignore-toolchain-manager-install-directory-user-settings, so:

[west]: exited with code -4058.

I did not try the fix you suggest.

I keep still use previous version until is fixed.

[Elfving]

Understood. I'll keep you posted.

Thanks for pitching in guys, and let us know if there is anything else.

[longo92]

A new release has been dropped..the relase target those fixes?

[Elfving]

Unfortunately not, as the team hasn't been able to reproduce it. Does the problem present itself in any different way when using it for you?

Regards,

Elfving

[Bill]

Please, have a closer look at the original post of this topic, everything is explained, including a possible reason for the failure.

To reproduce it's enough to have the Nordic SDKs and toolchains in a folder different from the 'canonical' one (`$HOME/ncs`) and then set the path in the VSCode extension setting parameter (`nrf-connect.toolchainManager.installDirectory`).

Note that many people prefer not to use the canonical folder in order not to clutter the home folder, but keeping things nicely organized.

BTW, I confirm the new version still has the same issue, so we need to stay at the version from 2 months ago.

[Elfving]

Once again, thanks for everyone's patience here, as well as your input on this problem.

I believe we've reproduced it now! 

The bug might not be connected to the extension per se, so I am not certain yet as to how quickly we'll get it solved, but we are working on it!

Thanks again!

Regards,

Elfving

[longo92]

Thank you Elfving  for the update.

Just for our understanding: can you point which is the source of the issue or give us some details (maybe we can also help you...)

Thanks,

Alessandro

[Elfving]

It is related to the sdk-manager. But no worries, we're working on the fix. 

[longo92]

 Elfving  with the the yesterday extension update(i.e., 2026.4.1637) is resolved.

I see from bug fix.es changelog the related issuse (at least in my case).

[Elfving]

Great! 

Does it work for you as well Bill ?