 So recently I had a viewer ask, how do you get a bash shell on a Windows machine? And I wanted to do a video response, but I don't have any Windows machines and setting up Windows in a virtual machine is just a pain in the butt. But I did get access to a Windows machine and I had an opportunity to record a couple of videos on this topic. Unfortunately, I installed OBS to record the video and I record both videos. There was no microphone, so I had to use my phone to record the audio and OBS to record the video. Assuming the OBS, I didn't I didn't change any of the settings. I just want the default settings assuming it would save to an MKV or an MP4 or even an OG file. But no, it's saved as a flash video file, FLV file, and which I don't know why. And so I finished recording these videos and I went to look at them. And of course, Windows out of the box can't play those files, that Windows Media Player just doesn't support that codec. So I couldn't even check the videos after recording them. And I finally got them back to my Linux machine, popped them on and it seems like they got like one frame every five seconds of recording. So I apologize. This is the best I could do in the situation that I had. But here is a video installing, actually, busybox on a Windows machine to get a Unix type shell. This particular compilation of busybox has something that's called Bash. Although, as I mentioned in the video, I don't think it truly is Bash. I would highly doubt it. And I did double check that Linux installs of busybox do not have a Bash shell. It's just the Ash shell, ASH, which I'm assuming is probably what this is linking to. And just calling it Bash, just as a pointer, a shortcut or a hyperlink or not hyperlink, but just a symbolic link to the Ash shell. Anyway, here's that video. Sorry about the quality. Hopefully you can follow along. Okay, I'm recording the audio and video separately because I don't have a microphone on this machine. So hopefully things will be somewhat in sync. Okay, so we're going to be looking at installing Bash kind of sort on Windows. And there's a few different ways to do this and I'll go over a few different ways over a couple of videos. But right now we're just going to be looking at I like to try to find single individual binary files. And I have found binaries of Bash in the past. But I haven't been unable to find that particular binary file. But most of the time when I'm on a Windows machine and I need a decent shell, I usually look to busybox because it also has a lot of those core tools built into it. And although it may not actually truly be Bash, but let's let's quickly get that. Just Google this box for Windows. And one of the first ones that will come up will be this box dash W32 flippery.org. And we're going to scroll down here to where there's a link to the executable somewhere, somewhere, somewhere, right here. We'll download that. And then I'm going to open up CMD, navigate to my downloads directory. And if we look at what's in here, you can see that busybox 64 is in there. And if we run busybox 64, 64 bit, go ahead, answer. And we'll give us a list of commands. You notice that it has a lot of those tools that you'll expect to find with busybox. But certain things are missing. You don't have basically the server type stuff. You don't have your HTTP demon, your web server, FTP server or Telnet server. You have the clients for those sort of things, such as W get. But you have a lot of your core tools here. You have DD, you have DF, you have echo, you have grep, ock, and netcat, or NC, MV to move, PWD, who is all this sort of stuff. Some of these are slimmed down. They aren't the full versions of the program, just like busybox on Linux. Like, for example, like W get or the NC program may not be fully featured, but a lot of those core features are there. And the way you could use a lot of these is you type busybox in the command you want, such as W get. I didn't give it a URL, so it's just giving me the help output for that. We don't want to have to type busybox and then the command every single time. Well, if you, again, run busybox, excuse me, you'll see list of commands and you'll notice that it has here, it has bash listed as a command. Well, I'm not really sure if this is truly bash. I've never noticed that it actually said bash before. I've always noticed that it's the ash shell or A-S-H shell. And I'm assuming, and I could be wrong, someone can correct me here, that bash in this is actually probably linking to the ash shell and it's just putting that in there so that scripts will look towards that because they're probably mostly compatible, but they may not be fully compatible. So if I wanted to, I could type in our executable here and then type in bash and it actually gives me a bash shell. And now all those commands, it works like a shell just on your Linux or Unix-like machine. And I can start running these commands. I can type W get and W gets there. I can type in Vi. It actually has Vi in there and I can type hello world. I can quit that. If I type help at any point, it will give me a list of those commands, netcat, crap, awk. And again, these might be slimmed down versions of programs, but those core tools are there where if you had just a bash binary, a lot of these core tools, you'll be able to do pure bash stuff, but a lot of these core tools that are not part of bash would be in there. And the nice thing about this binary file here of busybox, I list this out, you'll see it's about half a megabyte. So it's relatively small and it has a majority of those tools you're going to use. Now, if you want to be able to access this from anywhere on your system, you can copy it to one of your path directories. I usually will copy it to your Windows system 32 folder. Of course, you'll need admin rights to do that. So we'll go ahead and do CMD and then you can right click and say run as administrator or oops, what I normally do is just hit the control shift and enter and let's click yes to get past this user access controller, whatever it's called. And now I can copy from my users, middle X 1000 downloads, busybox and said busybox 64, I'll just call it busybox.exe. And now I should be able to call busybox from anywhere on my system. So even though I'm not in the directory of busybox, I should be able to run busybox here and I could just type anywhere busy. Busybox SH or bash or ash, I'm pretty sure they all link into the same thing. And now I have my shell anywhere I want. And actually a lot of these core tools, there is a way to link them to be just like you would on a Linux system to where I could use W get or end cat or sleep or sort or all these commands in like just regular what you call it batch file and actually call them from the windows shell rather than actually logging to the shell here. But usually this is why I do and when I'm in a pinch and I'm stuck at a windows machine and I need a decent shell, that is what I use. Next time we'll look at another option that might. Be useful for you. So that's it. Thank you for watching. If you have questions, let me know in the comments below. Have a great day.