# Managing Julia installation on Windows

**URL:** <https://discourse.julialang.org/t/managing-julia-installation-on-windows/58074>\
**Category:** General Usage\
**Created:** [March 27, 2021, 12:20pm UTC](https://discourse.julialang.org/t/managing-julia-installation-on-windows/58074 "2021-03-27T12:20:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![SL6Trip](https://avatars.discourse-cdn.com/v4/letter/s/4da419/32.png) [@SL6Trip](https://discourse.julialang.org/u/SL6Trip)\
**Post date:** [March 27, 2021, 12:20pm UTC](https://discourse.julialang.org/t/managing-julia-installation-on-windows/58074/1 "2021-03-27T12:20:39Z")

</div>

So recently I came across [jill.py](https://github.com/johnnychen94/jill.py) which seems to be using Python to help with automating the installation and/or upgrading of Julia to newer releases. I think it is a great tool especially on Linux distributions (as I tend to switch between both Ubuntu and Arch) since it will not be tied to the distribution’s package manager.

On Windows, I have always been using [scoop](https://github.com/lukesampson/scoop), a command-line installer in Powershell to handle my Julia installation. I use `scoop` to also handle quite a number of other tools that I use (eg.` ffmpeg`, `openjdk`, `r`).

Is there any reason I should let the management of the Julia installation be done using `jill.py` instead of `scoop`? I’m not sure if there is the problem that other package managers such as chocolatey providing incorrect binary dependencies as stated on the `jill.py` github page, but I believe `scoop` downloads the zip package from the Julia website.