# Vscode is not following the executable path
**URL:** https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825
**Category:** VS Code
**Tags:** path
**Created:** [October 27, 2024, 2:39pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825 "2024-10-27T14:39:49Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@martin\_sanchez](https://discourse.julialang.org/u/martin_sanchez)
#### Post date: [October 27, 2024, 2:39pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825/1 "2024-10-27T14:39:49Z")
I am having some trouble with Julia and VScode, so I decided to use (with juliaup) the lts version. I updated the path in VScode as I show in the image:
But even though, when I run a file or a line in VScode, it is still running version 1.11:
(Don’t know if it’s relevant, but I am using wsl)
What am I missing?
---
### Author:  [@ufechner7](https://discourse.julialang.org/u/ufechner7)
#### Post date: [October 27, 2024, 2:42pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825/2 "2024-10-27T14:42:38Z")
Did you execute `juliaup default 1.10`?
---
### Author:  [@martin\_sanchez](https://discourse.julialang.org/u/martin_sanchez)
#### Post date: [October 27, 2024, 2:43pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825/3 "2024-10-27T14:43:24Z")
Thank you for your response. Yes, if I run julia in the terminal it runs the lts version.
---
### Author:  [@ufechner7](https://discourse.julialang.org/u/ufechner7)
#### Post date: [October 27, 2024, 2:44pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825/4 "2024-10-27T14:44:46Z")
Perhaps you should set this executable path: `/home/msanchezr/.juliaup/bin/julia ` ?
---
### Author:  [@martin\_sanchez](https://discourse.julialang.org/u/martin_sanchez)
#### Post date: [October 27, 2024, 2:47pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825/5 "2024-10-27T14:47:36Z")
I am going to try it. I was using the path I got from Sys.BINDIR, but that is a great point.
---
### Author:  [@BioTurboNick](https://discourse.julialang.org/u/BioTurboNick)
#### Post date: [October 27, 2024, 2:49pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825/6 "2024-10-27T14:49:42Z")
FWIW, VSCode caches the first path it has when loaded and keeps using that one. So if you were to update with Juliaup or change default channels while it is running, it won’t adjust. Restarting VSCode will allow it to find the new path. I believe I filed an issue for that.
---
### Author:  [@rocco\_sprmnt21](https://discourse.julialang.org/u/rocco_sprmnt21)
#### Post date: [October 27, 2024, 3:04pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825/7 "2024-10-27T15:04:25Z")
I just updated Julia from version 1.9 to 1.10.5.
I changed the exec path parameter just by changing the version number and that seems to be enough.
Now, since the executable is in a seemingly different place, I wonder how vscode can find it.
```julia
julia> Sys.BINDIR
"C:\\Users\\sprmn\\.julia\\juliaup\\julia-1.10.5+0.x64.w64.mingw32\\bin"
```
Now I tried to point vscode to the new 😁 release of julia, but REPL (CTRL J+CTRL o) insists on using the old version
---
### Author:  [@martin\_sanchez](https://discourse.julialang.org/u/martin_sanchez)
#### Post date: [October 27, 2024, 6:59pm UTC](https://discourse.julialang.org/t/vscode-is-not-following-the-executable-path/121825/10 "2024-10-27T18:59:25Z")
Okay, solved. I was editing on the user settings, but I needed to modify it in Remote (the wsl configuration)