Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

An error occurred when trying to connect.

See original GitHub issue

Please describe what you were doing when this error happened.

Specifications

OS: win32
IPFS Desktop Version: 0.8.0
Electron Version: 5.0.2
Chrome Version: 73.0.3683.121

Error

Error: spawn powershell.exe ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:246:19)
    at onErrorNT (internal/child_process.js:429:16)
    at processTicksAndRejections (internal/process/task_queues.js:81:17)

Issue Analytics

State:
Created 4 years ago
Comments:11 (6 by maintainers)

Top GitHub Comments

1reaction

shaswata56commented, Sep 6, 2019

Found it! Actually, C:\Windows\System32 is not in my PATH.

It’s a bit odd not to have C:\Windows\System32 though. I don’t know why that might have happened. Perhaps a corrupt PATH.

Idea(2) is good. It’ll not gather useless bug reports.

That’s what I’ll do 😃

Mistakenly I’ve cleared PATH from my system a week ago. Then rewrote the path. But I didn’t notice that system32 was missing from there.

1reaction

shaswata56commented, Sep 6, 2019

Is it on the PATH? I haven’t been able to reproduce this on any Windows 10 machine I’ve tried on…

Currently I’m in Manjaro, I’m replying soon after checking my PATH.

Found it! Actually, C:\Windows\System32 is not in my PATH.

Anyhow, just to let more information here:

By default we add ipfs to the PATH if it not exists. For that, on Windows, we use PowerShell.

I will hide this error when it’s caused by an automatic action. If the user decides to check this option on the settings and it fails, they’ll get an error message. Otherwise, it will fail silently.

Idea(2) is good. It’ll not gather useless bug reports.