• State Not Answered
  • Replies 9 replies
  • Subscribers 88 subscribers
  • Views 1508 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 345961
Options

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
Parents
  • 0

    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.

Reply
  • 0

    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.

Children
Related
Terms of service