I tried adding ipfs to path (for running daemon)

[ygboucherk]

I had an error that said daemon wasn't running, so I tried adding ipfs to path for adding it to CLI, but I got this error.

If it's hard to fix, I suggest adding an in-gui method for launching daemon !

Specifications

• OS: win32
• IPFS Desktop Version: 0.9.7
• Electron Version: 6.0.12
• Chrome Version: 76.0.3809.146

Error

Error: spawn powershell.exe ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
    at onErrorNT (internal/child_process.js:456:16)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)

[jessicaschilling]

We'll go over this in our next triage session, but any other details you could provide could be great - namely how you went about adding IPFS to path? What exactly did you do?

[ygboucherk]

I wanted to enable daemon for contributing to IPFS. So I wanted to add ipfs to path for running the ipfs daemon command !

[rafaelramalho19]

@ygboucherk if I understand correctly, you replaced your whole windows variable paths to add ipfs and you removed powershell from it?

It doesn't make much sense that powershell.exe is not available in your windows machine.

Can you specify what steps you followed and what caused this error?

[ygboucherk]

I didn't remove powershell from path, and it's running perfectly from powershell command, and I almost never use powershell (I use CMD)

[ygboucherk]

And I tried adding it to path from GUI button

[ygboucherk]

Without manually editing PATH

[rafaelramalho19]

Alright, thanks for clearing that up. Apparently it can happen that you don't have powershell in the path.

Can you try following these steps and try again?

- cmd+q and search env and hit enter
- click environment variables in the advanced tab
- find Path/PATH variable and click edit
- Click new and paste %SystemRoot%/system32/WindowsPowerShell/v1.0

[ygboucherk]

Okay, thanks

[ygboucherk]

but, what's cmd+q ?
I'm on windows, not on a mac !

[ygboucherk]

Should I edit registry (with regedit) ?

[rafaelramalho19]

Sorry, I meant CTRL + Q (or just press the windows icon for the search to activate)

[lidel]

I am afraid the only fix here is to find IPFS Desktop/config.json and manually set:

"ipfsOnPath": false,

We will be deprecating this feature (#1768), if you want ipfs on your PATH follow https://docs.ipfs.io/install/command-line/