Update vhd file size instructions based on #533

Author: mattwojo

WSL/compare-versions.md

@@ -169,65 +169,78 @@ To expand your maximum VHD size beyond 256GB:
 
 1. Terminate all WSL instances using the command: `wsl --shutdown`
 
-2. Find your distribution installation package name ('PackageFamilyName')
+2. To find your distribution installation package name ('PackageFamilyName'):
     - Using PowerShell (where 'distro' is your distribution name) enter the command:
     - `Get-AppxPackage -Name "*<distro>*" | Select PackageFamilyName`
+    - For example: `Get-AppxPackage -Name "*Ubuntu*" | Select PackageFamilyName`
 
-3. Locate the VHD file `fullpath` used by your WSL 2 installation, this will be your `pathToVHD`:
-     - `%LOCALAPPDATA%\Packages\<PackageFamilyName>\LocalState\<disk>.vhdx`
-     - As an example, to find the path for Ubuntu, you would enter: `Get-AppxPackage -Name "*Ubuntu*" | Select PackageFamilyName`
-     ![Get-AppxPackage command line screenshot](/media/get-AppxPackage.png)
+    ![Get-AppxPackage command line screenshot](./media/get-appxpackage.png)
+
+3. Use the resulting `PackageFamilyName` to locate the VHD file `fullpath` used by your WSL 2 installation, this will be your `pathToVHD`. To find the full path:
+   - In your Start menu, enter: "%LOCALAPPDATA%" and select to open the %LOCALAPPDATA% file folder.
+   - Next, open the "Packages" folder and search for the `PackageFamilyName` of your distribution. Open that folder (ie. CanonicalGroupLimited.Ubuntu20.04onWindows_79xxxxx).
+   - Inside the `PackageFamilyName` folder, open the "LocalState" folder and find the `<disk>.vhdx` file.
+   - Copy the path to that file, it should look something like:
+     `%LOCALAPPDATA%\Packages\<PackageFamilyName>\LocalState\<disk>.vhdx`
+   - For example, the `<pathToVHD>` for Ubuntu 20.04 should look something like: `%LOCALAPPDATA%\Packages\CanonicalGroupLimited.Ubuntu20.04onWindows_79xxxx\LocalState\ext4.vhdx`.
 
 4. Resize your WSL 2 VHD by completing the following commands:
    - Open Windows Command Prompt with admin privileges and enter:
 
-      ```powershell
+      ```cmd
       diskpart
+      ```
+
+      ```cmd
       DISKPART> Select vdisk file="<pathToVHD>"
+      ```
+
+      ```cmd
       DISKPART> detail vdisk
       ```
 
-   - Examine the output of the **detail** command.  The output will include a value for **Virtual size**.  This is the current maximum.  Convert this value to megabytes.  The new value after resizing must be greater than this value.  For example, if the **detail** output shows **Virtual size: 256 GB**, then you must specify a value greater than **256000**.  Once you have your new size in megabytes, enter the following command in **diskpart**:
+   - Examine the output of the **detail** command.  The output will include a value for **Virtual size**. This is the current maximum. Convert this value to megabytes. For example, if the **detail** output shows **Virtual size: 256 GB**, convert this to **256000**.
+   - The new value you enter must be greater than this original value. As an example, to double the virtual size listed above, you could enter the value: **512000**. Once you have determined the number you would like to set for your new size (in megabytes), enter the following command in your Windows Command Prompt **diskpart** prompt:
 
-      ```powershell
+      ```cmd
       DISKPART> expand vdisk maximum=<sizeInMegaBytes>
       ```
 
    - Exit **diskpart**
 
-      ```powershell
+      ```cmd
       DISKPART> exit
       ```
 
 5. Launch your WSL distribution (Ubuntu, for example).
 
-6. Make WSL aware that it can expand its file system's size by running these commands from your Linux distribution command line.
-
-   > [!NOTE]
-   > You may see this message in response to the first **mount** command: **/dev: none already mounted on /dev**.  This message can safely be ignored.
+6. Make WSL aware that it can expand its file system's size by running these commands from your WSL distribution command line.
 
-   ```powershell
+   ```bash
       sudo mount -t devtmpfs none /dev
       mount | grep ext4
    ```
 
-   Copy the name of this entry, which will look like: `/dev/sdX` (with the X representing any other character).  In the following example the value of **X** is **b**:
+   - You may see this message in response to the first **mount** command: "/dev: none already mounted on /dev." This message can safely be ignored.
+   - Copy the name of this entry, which will look like: `/dev/sdX` (with the X representing any other character).  In the following example the value of **X** is **b**:
 
-   ```powershell
+   ```bash
       sudo resize2fs /dev/sdb <sizeInMegabytes>M
    ```
 
+   - Using the example from above, we changed the vhd size to **512000**, so the command would be: `sudo resize2fs /dev/sbd 512000M`.
+
    > [!NOTE]
    > You may need to install **resize2fs**.  If so, you can use this command to install it:  `sudo apt install resize2fs`.
 
    The output will look similar to the following:
 
    ```bash
-      resize2fs 1.44.1 (24-Mar-2018)
+      resize2fs 1.44.1 (24-Mar-2021)
       Filesystem at /dev/sdb is mounted on /; on-line resizing required
       old_desc_blocks = 32, new_desc_blocks = 38
       The filesystem on /dev/sdb is now 78643200 (4k) blocks long.
       ```
 
-> [!NOTE]
-> We recommend that you do not modify, move, or access the WSL related files located inside of your AppData folder using Windows tools or editors. Doing so could cause your Linux distribution to become corrupted. If you would like to access your Linux files from Windows that is possible via the path `\\wsl$\<distroName>\`. To learn more, see the blog post: [Accessing Linux files from Windows](https://devblogs.microsoft.com/commandline/whats-new-for-wsl-in-windows-10-version-1903/#accessing-linux-files-from-windows).
+> [!IMPORTANT]
+> We recommend that you do not modify, move, or access the WSL related files located inside of your AppData folder using Windows tools or editors. Doing so could cause your Linux distribution to become corrupted. If you would like to access your Linux files from Windows, that is possible via the path `\\wsl$\<distroName>\`. Open your WSL distribution and enter `explorer.exe .` to view that folder. To learn more, see the blog post: [Accessing Linux files from Windows](https://devblogs.microsoft.com/commandline/whats-new-for-wsl-in-windows-10-version-1903/#accessing-linux-files-from-windows).