Unable to install nRF Connect SDK to a non-default location on Windows 11

[r0n9]

Hello,

I am trying to install the nRF Connect SDK v3.0.1 on Windows 11 (version 24H2 build 26100.4061). In the VSCode -> nRF Connect(the plugin) -> Manage SDKs

I can successfully install the SDK using the default location (c: ncsv3.0.1). However, if I try to install it on d: ncsv3.0.1 or e: ncsv3.0.1, the installation will fail with error code -4058.

[22:57:56] nrfutil-sdk-manager sdk,install,v3.0.1,--sdk-path,d:\ncs\v3.0.1: Calculating SDK checksum

[22:58:02] nrfutil-sdk-manager sdk,install,v3.0.1,--sdk-path,d:\ncs\v3.0.1: Verified previously download file: success

[22:58:02] nrfutil-sdk-manager sdk,install,v3.0.1,--sdk-path,d:\ncs\v3.0.1: Unpack SDK v3.0.1

[23:00:55] nrfutil-sdk-manager sdk,install,v3.0.1,--sdk-path,d:\ncs\v3.0.1: Unpacked SDK tarball: success

[west]: exited with code -4058.

[00:17:10] nrfutil-sdk-manager sdk,install,v3.0.1,--sdk-path,e:\ncs\v3.0.1: Calculating SDK checksum

[00:17:16] nrfutil-sdk-manager sdk,install,v3.0.1,--sdk-path,e:\ncs\v3.0.1: Verified previously download file: success

[00:17:16] nrfutil-sdk-manager sdk,install,v3.0.1,--sdk-path,e:\ncs\v3.0.1: Unpack SDK v3.0.1

[00:20:10] nrfutil-sdk-manager sdk,install,v3.0.1,--sdk-path,e:\ncs\v3.0.1: Unpacked SDK tarball: success

[west]: exited with code -4058.

Any suggestions to fix the error? I have limited space in the C drive, and would appreciate installing the SDK on another drive. Cheers

[Øyvind]

Hello, 

Could you please test using e.g. nrfutil sdk-manager install v3.0.1 --sdk-path e:\ncs\v3.0.1 --install-dir e:\ncs?

Kind regards,
Øyvind

[Al.]

Despite my doubts (see comment below), I did try this. (nrfutil sdk-manager install .....) but with current version (v3.1.1) and my path (d:\data\programfiles\nordic\ncs.

It appeared to download and unpack successfully - the resulting ncs directory is 10GB! But how does haveing done this relate to or effect the extension for nRF development in VSCode? VSCode still shows no extensions installed. I'm guessing if I go to install the extension from within VSCode it will go through the process exactly as before, and assume the install-dir is c:\ncs.

Now that (hopefully) the sdk and toolchain is installed via the command line, how to sync this with VSCode?

[house_tiger]

not sure if you already found a resolution to this, but I encountered the same issue and found a workaround.

• close VS Code if it's open
• open the file "config.json" located here: C:\Users\<your username>\.vscode\extensions\nordic-semiconductor.nrf-connect-2026.1.1327-win32-x64\platform\nrfutil\config\nrfutil-sdk-manager\config.json
  • your extension version may be different from mine so check the .vscode\extensions folder for the exact version you have
• update the "install_dir" property from "null" to your desired path, in my case "d:\\ncs"
  

  {
    "default": {
      "install_dir": "d:\\ncs",
      "toolchain_index": null,
      "sdk_index": null
    },
    "toolchain_indexes": {},
    "sdk_indexes": {}
  }

• open VS Code, select the nRF Connect tab, click "Install SDK", and now you can provide a path for the SDK on the same drive as "install_dir", such as "D:\ncs\v3.2.1" and the process will finish successfully. all SDK and toolchain files will be installed on the D: drive

I couldn't find a setting in the nRF Connect extension which would let you change this in a more user-friendly way. I set up a Dev Drive in Windows and thus I wanted the SDK, project files, and everything on that second partition.