I think the build process for WSL is out of date, as devkitPro/Pacman has been updated.

[nojonsko]

i looked on the releases page of devkitPro/Pacman, scrolled down to v1.0.2, to see if i could get the "devkitpro-pacman.amd64.deb" file manually. it does not exist, and therefore causes the build to fail.
i'm inexperienced with WSL and Linux in general. i tried sudo su - to gain root access, then tried "apt-get install -y pacman", and it successfully installed, but i don't think this has placed the files in the correct locations.
not sure where to go from here.

[lividhen]

Using pacman on a Debian based distro (such as Ubuntu, wsl's default image) is not generally something you want to do as it is prone to breaking things. You will want to look at the Debian section here to install dkp-pacman which is set up to not cause a ton of dependency issues on your normal system haha. You can also use 'sudo' in front of any command to run it with root privlidged. It tends to be safer than switching user to root (sudo su -) and running all your commands as root, in case you mistype
https://devkitpro.org/wiki/devkitPro_pacman

You can also follow the instructions for msys32 if you can't get wsl to work. If you would like to use wsl to learn, which I think is a lot of fun, that is how I got comfortable with bash and I now daily drive a linux desktop.
You are not stuck with Ubuntu on wsl. You can install almost any 'distro', including arch which has pacman by default so you just need to follow the instructions on the wiki for adding the devkitpro repo to your pacman.conf file.