Ah, sorry, that path you can’t find is actually only connected to Particle Dev, so you won’t need it.
But these parts of your PATH might be a clue for your problem.
You have got C:\Program Files\nodejsandC:\Particle\Tools\NodeJS.
Any reason why you’ve got two sets of nodejs?
And I can’t see the %appdata%\Roaming\npm in your PATH, can you check if it exists?
This directory should actually contain the particle-cli module.
If this directory exists, try adding it to your PATH manually (and remove the second NodeJS from it).
What does npm version report (maybe executed from within both of your directories)?
two node js because i had installed it and forgot to take it off of the toolkit installation. and npm version outputs: http://prntscr.com/8yt413. and particle-cli is in the npm-cache.
I’ve run out of ideas, but I’ve asked some of the more brilliant people to have a look into your problem.
I had thought of offering a TeamViewer session to just play through what I’d do if my machine would not work (providing you’d trust me enough to let me fiddle on your machine).
But let’s wait first if someone has got the right idea.
How would PuTTY help installing CLI?
Or do you mean you got around the need for CLI by using another aporach - e.g. for setting WiFi credentials?
If that, then asking the correct question would have safed you a lot of trouble
I recently had problems reinstalling particle-cli (failure at serialport) but then I found these posts:
and
I followed the suggestion to do the npm install from the Visual Studio Command Prompt:
Try running the npm install commands from a MSVS command prompt.
Find it at Start menu > Microsoft Visual Studio 201X > Visual Studio Tools > Open Visual Studio 201X Tools Command Prompt or run the <Program Files>\<VS dir>\Common7\Tools\VsDevCmd.bat from a command prompt.