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.]

I have the same problem trying to install sdk from within VSCode (for me, sdk v3.1.1, 2025-11-20); . More detail: the following error message also displays, along with error code -4058:

Error: The configured `install-dir` directory (C:\ncs) and the `--sdk-path` directory (d:\Data\ProgramFiles\Nordic\ncs\v3.1.1) are on different drives. The installation requires directories on the same drive. Use the `--install-dir` flag to specify a directory on the same drive as for `--sdk-path`. Caused by: Provided path are from different drives

Clearly the VS code integration is failing to offer user ability to specify install-dir. And is then making the faulty assumption to use a hard-coded location instead of the same location as sdk-path.

Like rOn9, I need to conserve disk space on C: drive, so installation in default location is a no-go.

[Al.]

I'm not sure that would be a long-term solution ... what would happen the first time there is an update applied from within VSCode? Won't it go looking for the install-dir on C:, since this update process is happeng from inside VSCode, where the correct path can't be specified?

[Al.]

I've tried all that, at least all files at all locations I know of. I've also scanned the registry for zombie entries to remove. I haven't (and can't) try on a virgin machine. 

Are you suggesting that the tool using c:\ncs for install-dir is a "memory" from an earlier install? I think it is just the tool's default, which can't be overriden in the VSCode interface.

[Øyvind]

Hello, please open a new ticket with your issue and provide details about your development environment and the problem you are having.

Thanks.
Kind regards,
Øyvind