I am getting the following error when I start Atom with Juno installed: We tried to start Julia with the `powershell` wrapper but could not find `powershell` or `where` on your `PATH` . Please make sure `%SYSTEMROOT%\System32\WindowsPowerShell\v1.0` and `%SYSTEMROOT%\System32` are on y…

Does where powershell work in a cmd prompt?

Nope, do you know why this can be the case and how I can fix this? C:\Users\Username>where powershell INFORMATION: Es konnten keine Dateien mit dem angegebenen Muster gefunden werden.

So if you’re certain that C:\Windows\System32\WindowsPowerShell\v1.0 is on your PATH – is there a powershell.exe in there?

[grafik] And yes, there is a powershell.exe there

[grafik] That path needs to be in a env variable called Path (or PATH or whatever, it seems to be case insensitive), not in one named Powershell1 or anything else.

If this information is any useful, Julia starts and works normally inside VSCode.

Not really :slight_smile: Juno should work fine if you disable the powershell wrapper, I think, but it’d still be interesting to figure out why where powershell doesn’t work for you. Do any of the following work? C:\Users\you>where powershell C:\Windows\System32\WindowsPowerShell\v1.0\powershell.e…

Only where powershell does not work, the other two work as in your example.

And can you execute C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe?

Strange Powershell related error

General Usage

IljaK91 April 12, 2019, 1:15pm 15

Nevermind, for some reason “where powershell” works now as expected and Julia starts normally after updating Atom to 1.36 (probably unrelatedly).

Topic		Replies	Views
[solved] Julia throws "PowerShell version < 3" error, when PowerShell is >3 New to Julia question	3	1236	July 12, 2017
Running .jl file from PowerShell New to Julia question	5	1763	June 23, 2021
Julia can not start inside Atom Juno	45	16319	October 6, 2021
Julia 1.5 on Windows Terminal General Usage windows	3	1902	August 3, 2020
Julia doesn't start in Atom with Juno New to Julia	4	2170	October 12, 2018

Strange Powershell related error

Related topics