diff --git a/foundations/installations/installation_guides/linux/virtual_machine.md b/foundations/installations/installation_guides/linux/virtual_machine.md
index 5ff08dedab0..a1ff4a7972d 100644
--- a/foundations/installations/installation_guides/linux/virtual_machine.md
+++ b/foundations/installations/installation_guides/linux/virtual_machine.md
@@ -10,7 +10,7 @@ Installing a VM is a straightforward process. This guide uses Oracle's VirtualBo
#### Use only your VM for The Odin Project
-Once you have completed these instructions, **you are expected to work entirely in the VM.** Maximize the window, add more virtual monitors if you have them, fire up the Internet Browser in the **Whisker Menu**  on the top left of the desktop. You should not be using anything outside of the VM while working on The Odin Project. If you feel like you have a good understanding after using the VM for a while, and or want to improve your experience, we recommend dual-booting Ubuntu, which there are instructions for below.
+Once you have completed these instructions, **you are expected to work entirely in the VM.** Maximize the window, add more virtual monitors if you have them, fire up the Internet Browser in the **Whisker Menu**  on the top left of the desktop. Any task you are working on for The Odin Project should take place within your VM. If you feel like you have a good understanding after using the VM for a while, and or want to improve your experience, we recommend dual-booting Ubuntu, which there are instructions for below.
@@ -20,15 +20,23 @@ Once you have completed these instructions, **you are expected to work entirely
#### Step 1.2: Download Xubuntu
-There are thousands of distributions of Linux out there, but Xubuntu is undoubtedly one of the most popular and user friendly. When installing Linux on a VM, we recommend downloading [Xubuntu](https://mirror.us.leaseweb.net/ubuntu-cdimage/xubuntu/releases/22.04/release/). There are a few files listed here, download the one ending in `.iso`. Xubuntu uses the same base software as Ubuntu but has a desktop environment that requires fewer computer resources and is therefore ideal for virtual machines. If you find the download speed slow, you can download the [Xubuntu `.iso` directly from the official Ubuntu image server](https://cdimage.ubuntu.com/xubuntu/releases/jammy/release/), as the previous link points to a US-based server.
+There are thousands of distributions of Linux out there, but Ubuntu is undoubtedly one of the most popular and user friendly. When installing Linux on a VM, we recommend downloading Xubuntu, which is a lightweight flavor of Ubuntu. Xubuntu uses the same base software as Ubuntu but has a desktop environment that requires fewer computer resources and is therefore ideal for virtual machines. Click on the `Direct Downloads` button on the [24.04 release page for Xubuntu](https://xubuntu.org/release/24.04/), find your nearest server location and click on it. There are a few files listed here, download the one ending in `.iso`, which will also be the largest one (around 4 gigabytes). If you find the download speed slow, you can download the [Xubuntu `.iso` directly from the official Ubuntu image server](https://cdimage.ubuntu.com/xubuntu/releases/noble/release/), as the previous link points to a US-based server.
-If you reach the download page and are unsure about what version to choose, it is recommended that you pick the Long-Term Support (LTS) version 22.04 (Jammy Jellyfish). You may be tempted to choose a more recent release, but this version is tried and tested by the Odin Project community and therefore the most reliable option for the purposes of this curriculum.
+If you reach the download page and are unsure about what version to choose, it is recommended that you pick the Long-Term Support (LTS) version 24.04 (Noble Numbat). You may be tempted to choose a more recent release, but this version is tried and tested by the Odin Project community and therefore the most reliable option for the purposes of this curriculum.
### Step 2: Install VirtualBox and set up Xubuntu
#### Step 2.1: Install VirtualBox
-Installing VirtualBox is very straightforward. It doesn't require much technical knowledge and is the same process as installing any other program on your Windows computer. Double clicking the downloaded VirtualBox file will start the installation process. If you receive an error about needing Microsoft Visual C++ 2019 Redistributable Package, you can find it on the [official Microsoft Learn page](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022). You most likely want the version with `X64` Architecture (that means 64-bit) - download and install it then try installing VirtualBox again.
+Installing VirtualBox is very straightforward. It doesn't require much technical knowledge and is the same process as installing any other program on your Windows computer. Double clicking the downloaded VirtualBox file will start the installation process.
+
+
+
+#### Microsoft Visual C++ 2019
+
+If you receive an error about needing Microsoft Visual C++ 2019 Redistributable Package, you can find it on the [official Microsoft Learn page](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022). You most likely want the version with `X64` Architecture (that means 64-bit) - download and install it then try installing VirtualBox again.
+
+
During the installation, you'll be presented with various options. We suggest dropping the Python Support as you don't need it by clicking on the drive icon with an arrow and choosing **Entire feature will be unavailable**:
@@ -38,32 +46,32 @@ This is how your installation window should look like after turning it off:
+You do not have to exclude Python Support. It is an optional package to allow for automation Virtual Machines with VirtualBox, which is out of scope for this curriculum, and we simply do not want you to install more than what you have to.
+
Make sure you install the application on `C:` drive, as it has tendency to error out otherwise. The virtual machine itself can be installed anywhere but we'll get to that soon.
As the software installs, the progress bar might appear to be stuck; just wait for it to finish.
-#### Step 2.2: Prepare VirtualBox for Xubuntu
+#### Step 2.2: New Virtual Machine
-Now that you have VirtualBox installed, launch the program. Once open, you should see the start screen.
+Now that you have VirtualBox installed, launch the program. Once open, you should see the start screen. Click on the **New** button to create a virtual operating system.
-
+
-Click on the **New** button to create a virtual operating system. Give it a name of **Xubuntu**, if you want the VM installed somewhere else than default `C:` location, change that accordingly in the **Folder** option. This is the place where your virtual disk will reside, so make sure that you've got at least 30GB for that. In **ISO Image** choose **Other** - you'll see a window open for you to find the `.iso` file on your PC. It most likely is in the `Downloads` folder. Leave **Skip Unattended Installation** as it is.
+Give it a name of **Xubuntu-TOP**. If you want the VM installed somewhere else than default `C:` location, change that accordingly in the **Folder** option. This is the place where your virtual disk will reside, so make sure that you've got at least 30GB for that. In **ISO Image** choose **Other** - you'll see a window open for you to find the `.iso` file on your PC. It most likely is in the `Downloads` folder.
-
+**Uncheck "Proceed with Unattended Installation".** This feature does not work and you will not be able to control your installation. If you do enable it accidentally before installing just delete your VM and try again.
-Continue by pressing **Next** and follow the next steps:
+The fields should auto populate once you enter the VM Name.
-#### Step 2.2.1: Unattended guest OS install setup
-
-You should see a window like this one now:
+
-
+Do **not** click Finish yet! We're not done. Continue the setup process by pressing the **Specify virtual hardware** accordion and follow the next steps.
-You want to tick the **Guest Additions** and **Install in Background** options and also change your **Username** and **Password** fields to your liking. Note that your username must be all lower-case and no more than 32 characters. If you forget to change the default password, it will be `changeme`. Leave the **Guest Additions ISO**, **Hostname** and **Domain Name** as they are. Continue by pressing **Next**.
+#### Step 2.3: Specify Virtual Hardware
-#### Step 2.2.2: Hardware
+You should see a window like this one now:
-
+
In the **Hardware** section of the installation you want to set your **Base Memory** to at least 2048 MB or more if possible - the upper limit is half of your total RAM but 4096 MB with the settings we recommend should give you a smooth experience.
@@ -77,86 +85,189 @@ Difficulty converting your Gigabytes (GB) into Megabytes (MB)? 1 GB of RAM is eq
-As for **Processors** you want this to be at 2 and no more. Leave **Enable EFI (special OSes only)** as it is - that is **unchecked** - and click **Next** to continue.
+As for **Processors** you want this to be at 2 and no more. Leave **Use EFI** unchecked.
-#### Step 2.2.3: Virtual hard disk
+We're still not ready for the Finish button yet. Click the **Specify virtual hard disk accordion** to continue.
-
+#### Step 2.4: Specify Virtual Hard Disk
-Now, you want to leave all the settings as they are besides the **Disk Size**, we recommend giving the VM **at least 30GB** of space. Reminder that this disk will be created in the folder that you've specified on the very first step of the VM creation process but nonetheless, the disk can be moved and resized in the future if needed.
+Now, you want to leave all the settings as they are besides the **Disk Size**, we recommend giving the VM **at least 30GB** of space. Reminder that this disk will be created in the folder that you've specified on the very first step of the VM creation process but nonetheless, the disk can be moved and increased in the future if needed.
-#### Step 2.2.4: Begin the unattended installation
+
-Click **Next** to be taken to a **Summary** page, on which you can click **Finish** to begin the process of unattended installation. The neat thing about it? It installs the OS and GuestAdditions on its own, without your input! Just let it do its own thing, you will know it is finished when you will see a login screen like this one in the **Preview** section:
+We are now ready to hit **Finish**. Please do so.
-
+#### Step 2.5: Virtual Video RAM
-Just click the green arrow called **Show** and you'll be presented with a VM window and the login screen. Log in with the password you've set up during the installation process and we'll have one bit of configuration left to do.
+One last step is required before we start up the Virtual Machine and start the installation process. Please click on the **Settings** button.
-It is possible that you'll receive an error like this one after clicking **Finish**:
+
-
+The Settings page for your Virtual Machine will open and look like the image below.
-It means you have to [enable virtualization in your computer's BIOS/UEFI settings](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-troubleshooting-enabling_intel_vt_x_and_amd_v_virtualization_hardware_extensions_in_bios). [Alternative instructions for enabling virtualization in BIOS/UEFI settings](https://wiki.2n.com/faqac/en/virtualizace-vt-x-amd-v-povoleni-virtualizace-na-vasem-pocitaci-pro-spusteni-2n-access-commander-100572533.html). If you have an AMD CPU, you're probably looking for something called `SVM` to enable, for Intel CPUs, `Intel Virtualization Technology`. The error should tell you what it is looking for. After you deal with it, just **Start** the machine and let things happen, you'll know that the process has finished when you see a login screen:
+
-
+Please click on the **Display** button. You will then be on the Display settings screen. What you must do here is increase the **Video Memory** to maximum. You can also increase the number of Virtual Monitors if you have multiple physical monitors. We recommend to do this later once you are comfortable in your VM.
-### Step 3: Setting correct sudo permissions
+
-Due to how the unattended installation is configured by VirtualBox, your account doesn't have proper `sudo` permissions. Think of them as the equivalent to `Run as administrator` on your Windows machine - you can imagine why it would be important to have them in order.
+Click **OK**. Now we're ready to begin the installation.
-#### Step 3.1: Navigate to users and group
+### Step 3: Begin Xubuntu installation
-First, if you haven't already, login with the username and password created earlier, then click on the  in top left of your window, afterwards type in `Users` and you should see `Users and Groups` show up. Click on it.
+You should find yourself back on the start screen. Click the **Start** button with your VM selected. If you accidentally open the dropdown for the Start button you can click **Start with GUI**, or click the Start button again. Another way to start your VM is by double-clicking the VM itself!
-
+
-#### Step 3.2: Manage groups
+A new window should appear that shows some images to indicate that you are loading an Oracle Virtual Machine. It will then transition to a start screen for Xubuntu called the GRUB Boot Menu. By default you have 30 seconds to choose an option by using the arrow keys and selecting via Enter. Typically the default option selected is the one you want, and in this case it's **Try or Install Xubuntu**. If you choose the wrong option just end the VM by clicking File and Close, or hitting the X button, and choosing **Power off the machine**.
-In the window that just came up you want to click on **Manage Groups**, click somewhere on the list and type `sudo` on your keyboard. That should bring you to the `sudo` entry like in the picture:
+And yes, the screen will be small at this point. We will fix that later.
-
+
-#### Step 3.3: Add yourself to sudo
+You should then see some console text show on the screen show up and disappear, and eventually make it to the Xubuntu desktop screen.
-With `sudo` selected, click **Properties** and in the window that shows up tick your user's name like this:
+This is a temporary environment called a Live Desktop. Any changes you make here (besides installing the operating system on the VM) are not permanent.
-
+To continue double click on the **Install Xubuntu** desktop icon.
-And then click **OK**. You will be greeted with a password prompt - it's the same one you logged in with.
+
-#### Step 3.4: Reboot your VM
+Another window should open titled *Welcome to Xubuntu*. Select your language and click **Next**.
-Now that this is all done, you can close those windows and reboot your VM. You can open a `Terminal` window by doing Ctrl + Alt + T and type in `reboot` and then press Enter to execute the command. Alternatively, you can click on the , then click on the power icon in bottom right and pick **Restart**.
+
-
+The next screen will ask you to *Select your keyboard layout*. You can optionally type in the input field to test and make sure your selection is correct. Do so and click **Next**.
-
+
-#### Step 3.5: Test your newly gained sudo privileges
+The next screen will ask you to configure your settings so you can *Connect to the internet*. If it is not selected you should choose **Use wired connection**. VirtualBox is configured to use your host machines network device, so whether the VM knows you're wired or wireless it **does not matter**, to it you are essentially hard wired to the internet.
-Now that you have access to `sudo`, we can use this to update our Xubuntu through the `Terminal`. Open the `Terminal` and use these commands, one after another:
+If you cannot select **Use wired connection** then you should run the VirtualBox installer again and select **repair**.
-
+> **Note for VPN Users**: If you are unable to continue with the installation or run updates because your VM seemingly cannot connect to the internet **and** you're using a VPN, consider whitelisting your VM, use a reverse split tunnel, or temporarily disable it all together. If split tunnel does not work try setting the VM Network Adapter to *Bridged Adapter* and try again.
-#### A note on typing passwords in the terminal
+
-When using a command in the terminal that requires you to enter your password for authentication (such as `sudo`), you will notice that the characters aren't visible as you type them. While it might seem like the terminal isn't responding, don't worry!
+The next screen will ask you *How would you like to install Xubuntu?* Once again we leave the default setting of **Interactive installation** because we do not have a configuration file prepared, nor do we want one in this case. This is more for IT professionals who are setting up workspaces for employees, or if you want to set up a homelab and have a solid OS installation template. This feature is out of scope for this curriculum, so let's click **Next** and move on.
-This is a security feature to protect confidential information, like how password fields on websites use asterisks or dots. By not displaying the characters you write, the terminal keeps your password secure.
+
-You can still enter your password as normal and press Enter to submit it.
+The next screen will ask you *What apps would you like to install to start with?*, of which once again we want the default option of all of them. If you're going to be using this VM as your studying tool then it should be fully featured. Click **Next** and move on.
-
+
+
+The next screen will ask you if you want to *Install recommended proprietary software?*, to which we answer: yes. Click both checkboxes and **Next** to move on.
+
+
+
+The next screen will ask you *How do you want to install Xubuntu?* In this case, we will once again select the default option to **Erase disk and install Xubuntu**. This action is safe and does not touch your host hard drive/disk because it is virtualized. As for Manual installation this is out of scope for the curriculum but if you'd like to dive deeper in the future it is recommended. Click **Next** when you're ready to move on.
+
+
+
+The next screen will have you *Create your account* by entering your name and a password. The computer name and username are auto generated by the name input, but you can customize these to your hearts content with valid characters. You should absolutely set a password, make it something you will be able to remember, one that you will be using often, and then please click **Next**.
+
+
+
+The next screen will ask you to *Select your timezone*. Insert either your location or timezone in the provided input boxes and click **Next**.
+
+
+
+The next screen will ask you to *Review your choices* and finalize the installation. The information shown in the window, while a bit confusing to understand right now, should reflect the decisions we have made along the way during this process. Once you're ready to wait for a while click the **Install** button and go grab some more coffee.
+
+
+
+The next few screens will go by automatically during the installation process. There is not much you can do but wait.
+
+
+
+Once you have reached this screen that signals the installation has been successfully completed. You are now being prompted to exit your live desktop environment so you can boot your newly installed Xubuntu OS on your VM. Click **Restart now** to continue the process. If you end up clicking Continue testing and wish to continue, just click the , click Log Out, and then click Restart. After restarting and you end up sitting on a black screen for a long time please have some patience. If it goes longer than 10 minutes then please close the VM and start again manually.
+
+
+
+When your VM restarts you should end up on this screen here that is presenting you with a login screen. Enter your password and click **Log in**.
+
+
+
+### Step 4: Updates and Guest Additions
+
+Before you can start using your Virtual Machine you might have noticed that it is a little choppy, a little laggy, and maybe even a little small. The reason being is that we have not installed all of the necessary drivers for Xubuntu to take advantage of the VM's "hardware". This is what the **Guest Additions** accomplishes. VirtualBox provides an image for Guest Additions, so we will use it. But even before we do that, we should run updates.
+
+We're going to learn a neat shortcut right now to open one of the most helpful tools available to you in a Linux based OS: The Virtual Terminal, or Terminal for short. The Terminal is actually virtual whether you're running in a VM or not, but that is out of scope for the curriculum. If you'd like to learn more about Linux in general check out the free book [The Linux Command Line](https://linuxcommand.org/tlcl.php).
+
+When you press win + T a new window should open up that provides you with some information and prompts you for input. This is your terminal. You can have many terminals open at a time, but for now stick to one.
+
+
+
+Now that we have the terminal open we can start running updates the *cool* way. There is a graphical user interface (GUI) process for running updates, but it looks really impressive when you run some commands in a command line interface (CLI) and a bunch of text runs across your screen with a progress bar and everything.
+
+You're going to enter these commands exactly and hit enter after each new line. You cannot copy and paste yet.
```bash
sudo apt update
+```
+
+When you entered that first command you were prompted for your password. When you try to enter it there will be no feedback from the terminal, as if you are not writing anything at all. This is not a bug; It's a feature. A security feature. A lot of applications will represent your password as a number of dots. Linux goes the next step and does not give onlookers the opportunity to count dots on a screen.
+
+Enter your password and hit enter, and you'll pull down the latest available updates.
+
+
+
+You will know when the process is done because the terminal will be available to take your input again. You'll get a print-out of how many packages can be upgraded.
+
+Now that we have ran the update command, we still need to run the command to *upgrade* our packages. With Ubuntu flavored operating systems the process is two steps. Your mileage may vary in other systems.
+
+The next command is this, type it in and hit enter:
+
+```bash
sudo apt upgrade
```
-You will be asked for your password after using the first one - type it in and use Enter to provide your terminal with the password. There is no visual feedback about what you're typing in but you are indeed doing so.
+That will show a whole lot more text and then ask you if you want to continue by typing either `Y` for Yes and `n` for No. Type `Y` and hit enter.
+
+Also notice that if you did these two commands in sequence you were not prompted for your password again. There is a timer that starts when you run a `sudo` command successfully in that it will only wait for that timer to conclude before asking you again. More security features!
+
+This may take a while.
+
+
+
+Once the upgrade has been completed let us install some helpful packages that will ensure our success with installing Guest Additions.
+
+```bash
+sudo apt install build-essential dkms
+```
-After `sudo apt upgrade` runs for a while you will be asked whether you want to install things - do so to update your machine. If you have any issues, do not hesitate to come over to our [Discord server](https://discord.gg/V75WSQG) and ask for help in the `#virtualbox-help` channel.
+Be sure to enter `Y` to allow these packages to install. These are two separate packages being installed. Explaining them is out of scope but feel free to look them up on your own time.
+
+
+
+This next step is something that is difficult to take a screenshot of, so the highlight here will be the menu that you must click on to find it. On the top VM toolbar click **Devices** and navigate to the bottom of the dropdown where you see **Insert Guest Additions CD image...** and click on that. It might take a few seconds but a notification will appear that the CD has been mounted and a file explorer will open showing you the contents of the image.
+
+
+
+The easiest way to install the Guest Additions from the contents of the image is to drag and drop the icon into the terminal. You are looking specifically for `VBoxLinuxAdditions.run`, and you want to click and hold and drag the icon onto your open terminal.
+
+First let us clear our terminal output to make it cleaner by typing `clear` and pressing enter. Once it has been cleared type `sudo` with a space after it because we need it for administrative privileges. Do *not* hit enter yet. Then drag and drop the icon into the terminal. Once your terminal has the path to the file, click back to your terminal, away from the file explorer.
+
+Behold the mystical three-part instructional images.
+
+Press enter on your terminal and type your password if it is required to continue.
+
+
+
+
+
+
+
+Your window may change size during this process. To complete the installation of the Guest Additions you need to reboot your VM. New shortcut unlocked: `sudo reboot`
+
+Upon logging in you may not notice anything different, but try to maximize your VM now. Look at all of this room for activities!
+
+
+
+You should also have less performance issues overall and should now be ready to move on with the curriculum. Don't forget to eject the Guest Additions image by clicking this button here. It doesn't hurt to leave mounted but it's far more tidy to remove it as we do not need it anymore.
+
+
### Step 4: Understand your new VM
@@ -168,9 +279,10 @@ From now on, stick with The Odin Project (TOP) website within your VM and follow
Here are some tips to help you get started in a virtual environment:
-- Enable the toolbar in your VM settings - there are useful options there that you might want to play around with, especially the ones concerning full screen or multiple displays. To do so, click on **Settings** and then navigate to **User Interface** and finally tick **Show at Top of Screen**.
+- If the toolbar is not showing for you: Enable the toolbar in your VM settings - there are useful options there that you might want to play around with, especially the ones concerning full screen or multiple displays. To do so, click on **Settings** and then navigate to **User Interface** and finally tick **Show at Top of Screen**.
- All your work should happen in the VM. You will install everything you need for coding, including your text editor, language environments and various tools inside the VM. The Xubuntu installation inside of your VM also comes with a web browser pre-installed but we'll be installing Chrome shortly.
+- Enable Shared Clipboard - On the aforementioned toolbar, under devices, you can enable Bidirectional under **Shared Clipboard**. Now you can copy and paste if you need to from your Host to Guest and Guest to Host. Please do remember you should be working fully within your VM if you can help it. Extra tip: `ctrl+shift+v` to paste in your terminal.
- To install software on your VM, you will follow the Linux (Ubuntu) installation instructions from inside the Xubuntu VM.
- You might need to take screenshots when asking for help on our Discord, here's how depending on where you use it:
- **Inside the VM:** you can use Shift + PrtSrc to take screenshots of portion of your screen. Alternatively, you can click the **Whisker Menu** and type in **Screenshot**, in which you can choose to take a screenshot of your entire screen, the current window you are on or to select a certain area to capture.
@@ -189,30 +301,29 @@ Here are some tips to help you get started in a virtual environment:
- When running the VM, minimize your Windows activity. You probably want to be plugged into power as well if you're using a laptop.
- Make sure your processors are set to only 2 and the Memory you've given your VM is at most half of your total RAM but at least 2GB. If you can't spare the 2GB, dual boot.
- If videos lag in the VM, make sure to max out Video Memory to whatever you can or alternatively play them on your Windows if your machine can handle it. Disable 3D Acceleration if you have it enabled.
- - Do look out for the  icon in the bottom right of your VM window. This signifies that something called Hyper-V is turned on. A thread on the VirtualBox forums describes [how to turn off Hyper-V completely](https://forums.virtualbox.org/viewtopic.php?f=25&t=99390). You want to have the icon of a chip with a V  icon instead. If you don't see either of these icons in the bottom right, you have to exit full screen mode to see them.
+ - Do look out for the  icon in the bottom right of your VM window. This signifies that something called Hyper-V is turned on. A thread on the VirtualBox forums describes [how to turn off Hyper-V completely](https://forums.virtualbox.org/viewtopic.php?f=25&t=99390). You want to have the icon of a chip with a V  icon instead. If you don't see either of these icons in the bottom right, you have to exit full screen mode to see them. *Yes, the turtle is present in all of the helpful screenshots above.*
- If your performance is still lacking, go for a dual boot as this will make sure you're using all of your specs for one OS only, thus improving your experience significantly.
- If your scroll wheel behaves oddly in Google Chrome and/or in other applications and you have gone through VM performance tips to make sure your VM is working as intended, look into [whether your version of Guest Additions is correct](https://discord.com/channels/505093832157691914/690588860085960734/1195697147123867668).
-### Step 5: Safely shutting down your VM
-
-You don't pull the plug on your everyday use computer, right? Why would you do the same to your virtual computer? When you click the X button and just close out your VM, you might as well say goodbye to your files. In this section, you'll understand three ways you can shut off your VM.
+- **Safely shutting down your VM**
-#### Option 1 - Shutting down from inside the VM with UI
+ - You don't pull the plug on your everyday use computer, right? Why would you do the same to your virtual computer? When you click the X button and just close out your VM, you might as well say goodbye to your files. In this section, you'll understand three ways you can shut off your VM.
+ - Option 1 - Shutting down from inside the VM with UI
-Clicking on the **Whisker Menu**  and clicking the power icon will give you several options on how to modify your session, including **Shutting Down**. Yep, that's the same place you might've used to **Restart** before!
+ Clicking on the **Whisker Menu**  and clicking the power icon will give you several options on how to modify your session, including **Shutting Down**. Yep, that's the same place you might've used to **Restart** before!
-#### Option 2 - Shutting down from inside the VM with the terminal
+ - Option 2 - Shutting down from inside the VM with the terminal
-Typing `poweroff` inside the terminal will do in this case. Your system will immediately shutdown.
+ Typing `poweroff` inside the terminal will do in this case. Your system will immediately shutdown.
-#### Option 3 - Shutting down from outside the VM
+ - Option 3 - Shutting down from outside the VM
-The last way to accomplish this goal of safely shutting down is by using the VM interface. Clicking on the File tab and hitting the close button (which also has a Power Icon) will bring up a popup titled **Close Virtual Machine**. This popup asks if you want to **Save the machine state**, **Send the shutdown signal**, or **Power off the machine**.
+ The last way to accomplish this goal of safely shutting down is by using the VM interface. Clicking on the File tab and hitting the close button (which also has a Power Icon) will bring up a popup titled **Close Virtual Machine**. This popup asks if you want to **Save the machine state**, **Send the shutdown signal**, or **Power off the machine**.
-
+ 
-
+ 
-To be safe, click the **Send the shutdown signal** radio and hit OK. This will safely power down your VM and your files will not get corrupted.
+ To be safe, click the **Send the shutdown signal** radio and hit OK. This will safely power down your VM and your files will not get corrupted.
[Return to Installations lesson](https://www.theodinproject.com/lessons/foundations-installations#os-installation)
diff --git a/foundations/installations/installations/imgs/03_start_screen.png b/foundations/installations/installations/imgs/03_start_screen.png
index 84ed973696e..40cf4fca743 100644
Binary files a/foundations/installations/installations/imgs/03_start_screen.png and b/foundations/installations/installations/imgs/03_start_screen.png differ
diff --git a/foundations/installations/installations/imgs/04_install_start.png b/foundations/installations/installations/imgs/04_install_start.png
index 4cdf00aeb22..d4e7ffe466e 100644
Binary files a/foundations/installations/installations/imgs/04_install_start.png and b/foundations/installations/installations/imgs/04_install_start.png differ
diff --git a/foundations/installations/installations/imgs/05_specify_virtual_hardware.png b/foundations/installations/installations/imgs/05_specify_virtual_hardware.png
new file mode 100644
index 00000000000..78990c48017
Binary files /dev/null and b/foundations/installations/installations/imgs/05_specify_virtual_hardware.png differ
diff --git a/foundations/installations/installations/imgs/05_unattended_install.png b/foundations/installations/installations/imgs/05_unattended_install.png
deleted file mode 100644
index eb8bafa2d24..00000000000
Binary files a/foundations/installations/installations/imgs/05_unattended_install.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/06_hardware.png b/foundations/installations/installations/imgs/06_hardware.png
deleted file mode 100644
index 1f92adbe020..00000000000
Binary files a/foundations/installations/installations/imgs/06_hardware.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/06_specify_virtual_hard_disk.png b/foundations/installations/installations/imgs/06_specify_virtual_hard_disk.png
new file mode 100644
index 00000000000..fd4b5462880
Binary files /dev/null and b/foundations/installations/installations/imgs/06_specify_virtual_hard_disk.png differ
diff --git a/foundations/installations/installations/imgs/07_start_screen_settings.png b/foundations/installations/installations/imgs/07_start_screen_settings.png
new file mode 100644
index 00000000000..e13add13ff4
Binary files /dev/null and b/foundations/installations/installations/imgs/07_start_screen_settings.png differ
diff --git a/foundations/installations/installations/imgs/07_virtual_hard_disk.png b/foundations/installations/installations/imgs/07_virtual_hard_disk.png
deleted file mode 100644
index 1ce8425eaf1..00000000000
Binary files a/foundations/installations/installations/imgs/07_virtual_hard_disk.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/08_preview_login.png b/foundations/installations/installations/imgs/08_preview_login.png
deleted file mode 100644
index fe94fccf89f..00000000000
Binary files a/foundations/installations/installations/imgs/08_preview_login.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/08_settings_screen.png b/foundations/installations/installations/imgs/08_settings_screen.png
new file mode 100644
index 00000000000..31ada74fe10
Binary files /dev/null and b/foundations/installations/installations/imgs/08_settings_screen.png differ
diff --git a/foundations/installations/installations/imgs/09_display_settings_screen.png b/foundations/installations/installations/imgs/09_display_settings_screen.png
new file mode 100644
index 00000000000..21ae3b4d250
Binary files /dev/null and b/foundations/installations/installations/imgs/09_display_settings_screen.png differ
diff --git a/foundations/installations/installations/imgs/09_virtualization_error.png b/foundations/installations/installations/imgs/09_virtualization_error.png
deleted file mode 100644
index c183646d5c6..00000000000
Binary files a/foundations/installations/installations/imgs/09_virtualization_error.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/10_login_screen.png b/foundations/installations/installations/imgs/10_login_screen.png
deleted file mode 100644
index b226a95c122..00000000000
Binary files a/foundations/installations/installations/imgs/10_login_screen.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/10_start_screen_start_button.png b/foundations/installations/installations/imgs/10_start_screen_start_button.png
new file mode 100644
index 00000000000..108d8655a27
Binary files /dev/null and b/foundations/installations/installations/imgs/10_start_screen_start_button.png differ
diff --git a/foundations/installations/installations/imgs/11_grub.png b/foundations/installations/installations/imgs/11_grub.png
new file mode 100644
index 00000000000..fd0bd9b3a1c
Binary files /dev/null and b/foundations/installations/installations/imgs/11_grub.png differ
diff --git a/foundations/installations/installations/imgs/11_users_and_groups.png b/foundations/installations/installations/imgs/11_users_and_groups.png
deleted file mode 100644
index 6397f96888f..00000000000
Binary files a/foundations/installations/installations/imgs/11_users_and_groups.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/12_sudo_group.png b/foundations/installations/installations/imgs/12_sudo_group.png
deleted file mode 100644
index 98bb18596f1..00000000000
Binary files a/foundations/installations/installations/imgs/12_sudo_group.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/12_xubuntu_live_desktop.png b/foundations/installations/installations/imgs/12_xubuntu_live_desktop.png
new file mode 100644
index 00000000000..b9d8d3b6ace
Binary files /dev/null and b/foundations/installations/installations/imgs/12_xubuntu_live_desktop.png differ
diff --git a/foundations/installations/installations/imgs/13_choose_your_language.png b/foundations/installations/installations/imgs/13_choose_your_language.png
new file mode 100644
index 00000000000..9c07cc7cb4d
Binary files /dev/null and b/foundations/installations/installations/imgs/13_choose_your_language.png differ
diff --git a/foundations/installations/installations/imgs/13_sudo_properties.png b/foundations/installations/installations/imgs/13_sudo_properties.png
deleted file mode 100644
index 556e26d4aa0..00000000000
Binary files a/foundations/installations/installations/imgs/13_sudo_properties.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/14_logout.png b/foundations/installations/installations/imgs/14_logout.png
deleted file mode 100644
index d3c432871da..00000000000
Binary files a/foundations/installations/installations/imgs/14_logout.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/14_select_keyboard_layout.png b/foundations/installations/installations/imgs/14_select_keyboard_layout.png
new file mode 100644
index 00000000000..2c976f9f68b
Binary files /dev/null and b/foundations/installations/installations/imgs/14_select_keyboard_layout.png differ
diff --git a/foundations/installations/installations/imgs/15_connect_to_the_internet.png b/foundations/installations/installations/imgs/15_connect_to_the_internet.png
new file mode 100644
index 00000000000..fdac0345d37
Binary files /dev/null and b/foundations/installations/installations/imgs/15_connect_to_the_internet.png differ
diff --git a/foundations/installations/installations/imgs/15_restart.png b/foundations/installations/installations/imgs/15_restart.png
deleted file mode 100644
index b75d739854e..00000000000
Binary files a/foundations/installations/installations/imgs/15_restart.png and /dev/null differ
diff --git a/foundations/installations/installations/imgs/16_type_of_installation.png b/foundations/installations/installations/imgs/16_type_of_installation.png
new file mode 100644
index 00000000000..6b82dd10bfa
Binary files /dev/null and b/foundations/installations/installations/imgs/16_type_of_installation.png differ
diff --git a/foundations/installations/installations/imgs/17_applications.png b/foundations/installations/installations/imgs/17_applications.png
new file mode 100644
index 00000000000..7a67e3561db
Binary files /dev/null and b/foundations/installations/installations/imgs/17_applications.png differ
diff --git a/foundations/installations/installations/imgs/18_optimize_your_computer.png b/foundations/installations/installations/imgs/18_optimize_your_computer.png
new file mode 100644
index 00000000000..35b2d1fdc4d
Binary files /dev/null and b/foundations/installations/installations/imgs/18_optimize_your_computer.png differ
diff --git a/foundations/installations/installations/imgs/19_disk_setup.png b/foundations/installations/installations/imgs/19_disk_setup.png
new file mode 100644
index 00000000000..2145b3c9826
Binary files /dev/null and b/foundations/installations/installations/imgs/19_disk_setup.png differ
diff --git a/foundations/installations/installations/imgs/20_create_your_account.png b/foundations/installations/installations/imgs/20_create_your_account.png
new file mode 100644
index 00000000000..13153831b28
Binary files /dev/null and b/foundations/installations/installations/imgs/20_create_your_account.png differ
diff --git a/foundations/installations/installations/imgs/21_select_your_timezone.png b/foundations/installations/installations/imgs/21_select_your_timezone.png
new file mode 100644
index 00000000000..b4104d9ef04
Binary files /dev/null and b/foundations/installations/installations/imgs/21_select_your_timezone.png differ
diff --git a/foundations/installations/installations/imgs/22_ready_to_install.png b/foundations/installations/installations/imgs/22_ready_to_install.png
new file mode 100644
index 00000000000..e08f3f78ff2
Binary files /dev/null and b/foundations/installations/installations/imgs/22_ready_to_install.png differ
diff --git a/foundations/installations/installations/imgs/23_installation_in_progress.png b/foundations/installations/installations/imgs/23_installation_in_progress.png
new file mode 100644
index 00000000000..011a0018859
Binary files /dev/null and b/foundations/installations/installations/imgs/23_installation_in_progress.png differ
diff --git a/foundations/installations/installations/imgs/24_installation_complete.png b/foundations/installations/installations/imgs/24_installation_complete.png
new file mode 100644
index 00000000000..1036420b309
Binary files /dev/null and b/foundations/installations/installations/imgs/24_installation_complete.png differ
diff --git a/foundations/installations/installations/imgs/25_login_screen.png b/foundations/installations/installations/imgs/25_login_screen.png
new file mode 100644
index 00000000000..205cf3ffdb9
Binary files /dev/null and b/foundations/installations/installations/imgs/25_login_screen.png differ
diff --git a/foundations/installations/installations/imgs/26_new_terminal.png b/foundations/installations/installations/imgs/26_new_terminal.png
new file mode 100644
index 00000000000..7945fd92ac1
Binary files /dev/null and b/foundations/installations/installations/imgs/26_new_terminal.png differ
diff --git a/foundations/installations/installations/imgs/27_sudo_apt_update.png b/foundations/installations/installations/imgs/27_sudo_apt_update.png
new file mode 100644
index 00000000000..039128b7235
Binary files /dev/null and b/foundations/installations/installations/imgs/27_sudo_apt_update.png differ
diff --git a/foundations/installations/installations/imgs/28_sudo_apt_upgrade.png b/foundations/installations/installations/imgs/28_sudo_apt_upgrade.png
new file mode 100644
index 00000000000..0b8aab29afd
Binary files /dev/null and b/foundations/installations/installations/imgs/28_sudo_apt_upgrade.png differ
diff --git a/foundations/installations/installations/imgs/29_sudo_apt_install_helper_packages.png b/foundations/installations/installations/imgs/29_sudo_apt_install_helper_packages.png
new file mode 100644
index 00000000000..68716b14bb8
Binary files /dev/null and b/foundations/installations/installations/imgs/29_sudo_apt_install_helper_packages.png differ
diff --git a/foundations/installations/installations/imgs/30_devices.png b/foundations/installations/installations/imgs/30_devices.png
new file mode 100644
index 00000000000..5191e67e6c0
Binary files /dev/null and b/foundations/installations/installations/imgs/30_devices.png differ
diff --git a/foundations/installations/installations/imgs/31_drag_and_drop_part_1.png b/foundations/installations/installations/imgs/31_drag_and_drop_part_1.png
new file mode 100644
index 00000000000..c6ec3f0a04e
Binary files /dev/null and b/foundations/installations/installations/imgs/31_drag_and_drop_part_1.png differ
diff --git a/foundations/installations/installations/imgs/32_drag_and_drop_part_2.png b/foundations/installations/installations/imgs/32_drag_and_drop_part_2.png
new file mode 100644
index 00000000000..1218ad38ef3
Binary files /dev/null and b/foundations/installations/installations/imgs/32_drag_and_drop_part_2.png differ
diff --git a/foundations/installations/installations/imgs/33_drag_and_drop_part_3.png b/foundations/installations/installations/imgs/33_drag_and_drop_part_3.png
new file mode 100644
index 00000000000..b8ce6312e36
Binary files /dev/null and b/foundations/installations/installations/imgs/33_drag_and_drop_part_3.png differ
diff --git a/foundations/installations/installations/imgs/34_room_for_activities.png b/foundations/installations/installations/imgs/34_room_for_activities.png
new file mode 100644
index 00000000000..af12c7ebb24
Binary files /dev/null and b/foundations/installations/installations/imgs/34_room_for_activities.png differ
diff --git a/foundations/installations/installations/imgs/35_iso_eject_button.png b/foundations/installations/installations/imgs/35_iso_eject_button.png
new file mode 100644
index 00000000000..5a7d49ae2dd
Binary files /dev/null and b/foundations/installations/installations/imgs/35_iso_eject_button.png differ