After cleaning up everything I installed a new v1.4.1 using nRF Connect Desktop - full version not http://developer.nordicsemi.com/.pc-tools/toolchain/ncs-toolchain-v1.4.1-20201215-7ecf886-minimal.zip ( Does it matter other than the time to install?). I did the west update then went to move newtmgr.exe when I notice the path you suggest doesn’t exist. The env.cmd that nRF Connect installed sets the path to tcdir which is (I setup ncs on D: dirve) D:\ncs\v1.4.1\toolchain; the main program folder is:
D:\ncs\v1.4.1\toolchain\opt\bin

For windows they have moved most everything into D:\ncs\v1.4.1\toolchain\opt\bin
D:\ncs\v1.4.1\toolchain\bin is not in the path.

If I run bash from D:\ncs\v1.4.1\toolchain\bin it sets up the bash environment for nRF.
The Windows CMD version D:\ncs\v1.4.1\toolchain\cmd\env.cmd will setup the environment for Windows COMMAND PROCESSOR not PowerShell.
You have to run bash or env.cmd to setup the environment for nRF.
I have ncs at the root of D:
D:\ncs\v1.4.1\toolchain\cmd\env.cmd
OR
D:\ncs\v1.4.1\toolchain\bash
Will setup a Windows for nRF.


    K2AAE you can place newtmgr in any location that is added to the system path. So the bin path within NCS is a good spot.

        jaredwolff That is the issue, toolchain\bin is not in the path set by nRF (env.cmd). If you put newtmgr.exe in /toolchain/bin it will not run unless you prefix it with the path since toolchain\bin is not in the path in Windows.
        Windows toolchain\opt\bin is in the path set by env.cmd and bash uses that path plus \usr\bin
        For Windows you must run env.cmd to set the environment.
        For Windows VSC you cd to the SDK your using then
        \toolchain\cmd\env.com
        code .
        When VSC starts it finds the nRF environment setup.


          Ahh yea you’re right. It blows away anything that was in the PATH. Does the same thing on Mac.

          Terms and Conditions | Privacy Policy