https://devzone.nordicsemi.com/f/nordic-q-a/124656/vs-code-can-not-recognize-sdk-and-toolchain-after-moving-the-ncs-sdk-from-c-drive-to-d-drive-of-windows-pcHi Support Team Due to there is very little space of C: drive of computer, so I moved the NCS SDK from C: drive to D: drive. The VS code can&#39;t recognize the SDK and toolchain anymore. Do you have any approach to make the VS code recognize the SDK anden-USTelligent Community 13Tue, 30 Sep 2025 22:32:00 GMThttps://devzone.nordicsemi.com/thread/550270?ContentTypeID=1Tue, 30 Sep 2025 22:32:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3dd3bb25-6b8f-4954-81a6-8dc42b8e1978crzyrndm<p>I have a very similar / the same issue setting up a new PC. Attempting to install to D (but otherwise default path)</p> <p><img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-2025_2D00_10_2D00_01-112852.png" /></p> <p>The toolchain install goes as expected (if incredibly slowly? 55 minutes for the 2.7.0 toolchain download and install?) but the SDK install that follows uses the default C drive path and then fails with this error</p> <p><img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-2025_2D00_10_2D00_01-113130.png" /></p> <p>It also appears to have installed the toolchain in the C drive anyway</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/550001?ContentTypeID=1Mon, 29 Sep 2025 10:50:10 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a247ae7b-6576-431e-96c0-127893c6baa4Benjamin<p>Hi,<br />Could you share any error messages if you got them?<br />Did you install NCS from scratch and how did you specify installation path?<br /><br />Regards,<br />Benjamin</p><div style="clear:both;"></div>