# Having installed several versions of Julia on machine. How to open a specific version of julia from PowerShell?

**URL:** https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134
**Category:** General Usage
**Tags:** question
**Created:** [March 19, 2022, 3:52pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134 "2022-03-19T15:52:23Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![Amro](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@Amro](https://discourse.julialang.org/u/Amro)
#### Post date: [March 19, 2022, 3:52pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/1 "2022-03-19T15:52:23Z")

</div>

I have two versions of Julia installed on my machine `1.6.3` and `1.8.0-beta 1`. When I write `julia` in the PowerShell, it opens `1.6.3`, how can I select the demanded version? I tried something like below, but it didn’t work

```julia
C:\> julia-1.8.0-beta1

```

---

<div class="post-metadata">

### Author: ![feanor12](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/feanor12/32/8212_2.png) [@feanor12](https://discourse.julialang.org/u/feanor12)
#### Post date: [March 19, 2022, 4:02pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/2 "2022-03-19T16:02:42Z")

</div>

You can call the binary for the different installations by using the full path.  
julia alone opens the binary that is available using the PATH environment variable.

I usually setup a custom shell in the new [windows](https://en.wikipedia.org/wiki/Windows_Terminal) terminal to start a specific version.

---

<div class="post-metadata">

### Author: ![Amro](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@Amro](https://discourse.julialang.org/u/Amro)
#### Post date: [March 19, 2022, 4:07pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/3 "2022-03-19T16:07:39Z")

</div>

Thank you very much.

Another issue, I have many packages installed in `1.6.3` how can I made them installed also in `1.8.0-beta 1`, such coping some files…

---

<div class="post-metadata">

### Author: ![feanor12](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/feanor12/32/8212_2.png) [@feanor12](https://discourse.julialang.org/u/feanor12)
#### Post date: [March 19, 2022, 4:13pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/4 "2022-03-19T16:13:22Z")

</div>

I usually place a `Project.toml` or even manifest file in my project directories.

To generate them just activate the project directory in the package mode and then add the required packages. I think julia can then also use already installed packed without reinstalling.

In case you already have a `Project.toml` you can call instantiate in the pkg mode of the REPL to force an installation.

I usually only have very few packages installed in the default environment.

If you don’t want to use Project files you can also activate named environments by using `pkg> activate @myname`. I don’t know if they are available between version though.

---

<div class="post-metadata">

### Author: ![feanor12](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/feanor12/32/8212_2.png) [@feanor12](https://discourse.julialang.org/u/feanor12)
#### Post date: [March 19, 2022, 4:17pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/5 "2022-03-19T16:17:22Z")

</div>

The packages for the default environment are also stored in a Project.toml file.  
You can find it by calling status

```julia
(@v1.7) pkg> st
      Status `~/.julia/environments/v1.7/Project.toml`
  [6e4b80f9] BenchmarkTools v1.3.1
  [c3e4b0f8] Pluto v0.18.1
  [b8865327] UnicodePlots v2.9.0

```

---

<div class="post-metadata">

### Author: ![Amro](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@Amro](https://discourse.julialang.org/u/Amro)
#### Post date: [March 19, 2022, 4:30pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/6 "2022-03-19T16:30:12Z")

</div>

Thank you very much.

---

<div class="post-metadata">

### Author: ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)
#### Post date: [March 19, 2022, 4:34pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/7 "2022-03-19T16:34:17Z")

</div>

You can also use `juliaup` for this scenario, see [Julia in the Windows Store | David Anthoff | JuliaCon2021 - YouTube](https://youtu.be/rFlbjWC6zYA). Just make sure you uninstall your other Julia versions before you switch over to using `juliaup`.

---

<div class="post-metadata">

### Author: ![feanor12](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/feanor12/32/8212_2.png) [@feanor12](https://discourse.julialang.org/u/feanor12)
#### Post date: [March 19, 2022, 4:38pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/8 "2022-03-19T16:38:08Z")

</div>

I am not sure if it is possible, but can the Windows store version also ship with custom profiles for the Windows terminal? 😃

---

<div class="post-metadata">

### Author: ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)
#### Post date: [March 19, 2022, 5:41pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/9 "2022-03-19T17:41:28Z")

</div>

It does 🙂

---

<div class="post-metadata">

### Author: ![song](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/song/32/204932_2.png) [@song](https://discourse.julialang.org/u/song)
#### Post date: [November 30, 2023, 10:44pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/10 "2023-11-30T22:44:27Z")

</div>

I’m also new to Julia, but here is what I do and I think they’re working well (I’m using MacOS):

Download and installing two versions of Julia, let’s say 1.6.7 and 1.9.3. Then add Julia to PATH by running:

```bash
sudo mkdir -p /usr/local/bin
sudo rm -f /usr/local/bin/julia1.6
sudo ln -s /Applications/Julia-1.6.app/Contents/Resources/julia/bin/julia /usr/local/bin/julia1.6
sudo rm -f /usr/local/bin/julia1.9
sudo ln -s /Applications/Julia-1.9.app/Contents/Resources/julia/bin/julia /usr/local/bin/julia1.9

```

And then I can launch different Julia by running `julia1.6` or `julia1.9` from terminal.

I think things will be similar in Windows or Linux. Hope it helps.

---

<div class="post-metadata">

### Author: ![Syx\_Pek](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/syx_pek/32/6364_2.png) [@Syx\_Pek](https://discourse.julialang.org/u/Syx_Pek)
#### Post date: [December 1, 2023, 3:41am UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/11 "2023-12-01T03:41:18Z")

</div>

I would say this is not the preferred solution. Having `juliaup` installed makes managing versions very easy.

Add new channels (Julia versions) with `juliaup add 1.6.3` say and run with `julia +1.6.3`.  
(The 1.6.3 is just an example, you can do it with `lts`, `release`, `beta` or specific julia versions)

You can then alias in your command line for the specific versions.

---

<div class="post-metadata">

### Author: ![song](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/song/32/204932_2.png) [@song](https://discourse.julialang.org/u/song)
#### Post date: [December 1, 2023, 8:46am UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/12 "2023-12-01T08:46:02Z")

</div>

Thanks, I will have a try!

---

<div class="post-metadata">

### Author: ![mcmuffin6o](https://avatars.discourse-cdn.com/v4/letter/m/9f8e36/32.png) [@mcmuffin6o](https://discourse.julialang.org/u/mcmuffin6o)
#### Post date: [January 13, 2024, 6:00pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/13 "2024-01-13T18:00:21Z")

</div>

Would you mind pointing me to the documentation for the `+<version>` option? I couldn’t find it on the [CLI page](https://docs.julialang.org/en/v1/manual/command-line-interface/#command-line-interface).

---

<div class="post-metadata">

### Author: ![ffevotte](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ffevotte/32/6587_2.png) [@ffevotte](https://discourse.julialang.org/u/ffevotte)
#### Post date: [January 13, 2024, 6:11pm UTC](https://discourse.julialang.org/t/having-installed-several-versions-of-julia-on-machine-how-to-open-a-specific-version-of-julia-from-powershell/78134/14 "2024-01-13T18:11:46Z")

</div>

This option is specific to Juliaup

> **[GitHub - JuliaLang/juliaup: Julia installer and version multiplexer](https://github.com/JuliaLang/juliaup)**
>
> Julia installer and version multiplexer. Contribute to JuliaLang/juliaup development by creating an account on GitHub.
