Windows technically has the self update mechanism, but no ability to switch between the release and releasepreview channel ![]()
On Win 11 the message for juliaup update and juliaup self update both seem to be checking for new julia versions rather than one checking for a new juliaup.
And juliaup self uninstall is not available. This is juliaup version 1.20.9.
PS C:\data\st\Downloads> juliaup self
Manage this juliaup installation
Usage: juliaup.exe self <COMMAND>
Commands:
update Update the Julia versions database
uninstall Uninstall this version of juliaup from the system (UNAVAILABLE)
help Print this message or the help of the given subcommand(s)
Options:
-h, --help Print help
PS C:\data\st\Downloads> juliaup self update
Checking for new Julia versions
No updates available.
PS C:\data\st\Downloads> juliaup update
Checking for new Julia versions
Tidyup No unused Julia installations to clean up.
PS C:\data\st\Downloads>
juliaup self update always also checks for new versions on all platforms because we want to make sure you are on the latest version db before we update the binaries.
juliaup self update on Windows does check whether there is a new version available on the Windows store, and if it is will trigger an update. There just isn’t anything new available at the moment.
And yes, we should wire up the juliaup self uninstall, that is not supported right now.
All of this is true for the Windows Store installed version, the app installer is lacking the self update support, and the MSI stuff of course doesn’t support any self update at all…
You can put:
[Desktop Entry]
Version=1.0
Type=Application
Name=Juliaup GUI
Comment=Manage Julia versions and channels
Exec=juliaup gui
Icon=julia
Terminal=false
Categories=Development;Science;IDE;
in a file with your favorite editor:
$ nano ~/.local/share/applications/juliaup-gui.desktop
$ chmod +x ~/.local/share/applications/juliaup-gui.desktop
for getting “Juliaup GUI” in the startup menu (next to Visual Studio code, or type it in).
I read such is already automatic for Windows, planned for Linux (and macOS). Until then…
juliaup v1.22.7 has been released and juliaup gui should now work on all platforms.
Getting the following abnormal exit error after upgrade to 1.22.7 of juliaup.
Microsoft Windows [Version 10.0.26200.9457]
(c) Microsoft Corporation. All rights reserved.
C:\Users\Owner>juliaup --version
Juliaup 1.22.7
C:\Users\Owner>juliaup gui
Error: The GUI at ‘C:\Program Files\WindowsApps\JuliaComputingInc.Julia_1.22.7.0_x64__b0ra4bp6jsp6c\Julia\juliaupgui.exe’ exited abnormally (exit code: 0xc0000005).
Ok. Works for me on Windows 11, WSL, Linux (x64). Thanks!
Can you try to launch it via juliaupgui or just the start menu option? For me both work, but juliaup gui also works on my system…
Works for me on Windows 11 (+ already worked on MacOS 27)
It may be a permissions issue. I am an Administrator of the Windows 11 laptop. When I try to access the c:\Program Files\WindowsApps folder it denies me access. As a point of reference juliaup itself works properly.
When I launch juliaup gui from the terminal it holds the terminal but opens a separate window for the GUI, thats fine because when I launch a version specific julia from the GUI it uses that held terminal, but when I try to exit() from julia it hangs till I kill the GUI window with the kernel and then julia exits. Maybe im doing it wrong.
That is normal and how it is supposed to be, that is the security model that MSIX installed applications use. In general as a user you should not reach into that WindowsApps folder ever yourself, that is all a backend management location for the MSIX engine.
Yeah, that doesn’t seem ideal. Can you open an issue?
Thanks for opening the issue. This kind of stuff is above my pay grade.
Opening issues are simple by design, dont overthink what the maintainer needs to solve. You just describe behaviour you dont think is right and an expected behavior. Its up to the maintainer to provide the behavior. You just provide a description for most cases.
Worked for me on a MAC, but the command line version is IMHOP better.
