Add release notes for 20226 (#939)

* command not found

* Update WSL/troubleshooting.md

* Update WSL/troubleshooting.md

* Apply suggestions from code review

* Update troubleshooting.md

* Add release notes for 20226

* On branch edburns-msft-diskpart-expand-improvement Fixes #951 resize improvement (#952)

modified:   WSL/compare-versions.md

* Update virtualization not enabled error section (#949)

Updating section describing what to do when virtualization not enabled to include error message and error code.

* Fix typo (whats → what's) (#947)

* Updated troubleshooting.md (#958)

* Remove admin recommendation where unnecessary (#966)

* Capitalize “Linux” in doc title (#962)

* Replace kernel link (#967)

* Adding more emphasis one when to Restart through the process (#961)

* Update install-win10.md (#942)

Co-authored-by: Canhua Li <[email protected]>
Co-authored-by: Craig Loewen <[email protected]>
Co-authored-by: Matt Wojciakowski <[email protected]>
Co-authored-by: Ben Hillis <[email protected]>
Co-authored-by: Ed Burns <[email protected]>
Co-authored-by: Ben Randall <[email protected]>
Co-authored-by: Andrea Spadaccini <[email protected]>
Co-authored-by: Adolfo Jayme-Barrientos <[email protected]>
Co-authored-by: Pablo Espinosa <[email protected]>
Co-authored-by: Miklos Cari <[email protected]>

Author: 11 people

WSL/compare-versions.md

@@ -1,7 +1,7 @@
 ---
 title: Comparing WSL 2 and WSL 1
-description: Compare version 1 and version 2 of the Windows Subsystem for Linux. Learn whats new in WSL 2 - actual Linux kernel, faster speed, full system call compatibility. WSL 1 works better if your storing files across operating file systems. You can expand the size of your WSL 2 Virtual Hardware Disk (VHD).
-keywords: BashOnWindows, bash, wsl, windows, windowssubsystem, gnu, linux, ubuntu, debian, suse, windows 10, UX changes, WSL 2, linux kernel, network applications, localhost, IPv6, Virtual Hardware Disk, VHD, VHD limitations, VHD error
+description: Compare version 1 and version 2 of the Windows Subsystem for Linux. Learn whats new in WSL 2 - actual Linux kernel, faster speed, full system call compatibility. WSL 1 works better if your storing files across operating file systems. You can expand the size of your WSL 2 Virtual Hard Disk (VHD).
+keywords: BashOnWindows, bash, wsl, windows, windowssubsystem, gnu, linux, ubuntu, debian, suse, windows 10, UX changes, WSL 2, linux kernel, network applications, localhost, IPv6, Virtual Hard Disk, VHD, VHD limitations, VHD error
 ms.date: 09/15/2020
 ms.topic: conceptual
 ms.localizationpriority: high
@@ -51,7 +51,7 @@ WSL 2 is only available in Windows 10, Version 1903, Build 18362 or higher. Chec
 > [!NOTE]
 > WSL 2 will work with [VMware 15.5.5+](https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html) and [VirtualBox 6+](https://www.virtualbox.org/wiki/Changelog-6.0). Learn more in our [WSL 2 FAQs.](./wsl2-faq.md#will-i-be-able-to-run-wsl-2-and-other-3rd-party-virtualization-tools-such-as-vmware-or-virtualbox)
 
-## Whats new in WSL 2
+## What's new in WSL 2
 
 WSL 2 is a major overhaul of the underlying architecture and uses virtualization technology and a Linux kernel to enable new features. The primary goals of this update are to increase file system performance and add full system call compatibility.
 
@@ -155,11 +155,11 @@ netsh interface portproxy add v4tov4 listenport=4000 listenaddress=0.0.0.0 conne
 
 WSL 2 distributions currently cannot reach IPv6-only addresses. We are working on adding this feature.
 
-## Expanding the size of your WSL 2 Virtual Hardware Disk
+## Expanding the size of your WSL 2 Virtual Hard Disk
 
-WSL 2 uses a Virtual Hardware Disk (VHD) to store your Linux files. If you reach its max size you may need to expand it.
+WSL 2 uses a Virtual Hard Disk (VHD) to store your Linux files. In WSL 2, a VHD is represented on your Windows hard drive as a *.vhdx* file.
 
-The WSL 2 VHD uses the ext4 file system. This VHD automatically resizes to meet your storage needs and has an initial maximum size of 256GB. If your distribution grows in size to be greater than 256GB, you will see errors stating that you've run out of disk space. You can fix this error by expanding the VHD size.
+The WSL 2 VHD uses the ext4 file system. This VHD automatically resizes to meet your storage needs and has an initial maximum size of 256GB. If the storage space required by your Linux files exceeds this size you may need to expand it. If your distribution grows in size to be greater than 256GB, you will see errors stating that you've run out of disk space. You can fix this error by expanding the VHD size.
 
 To expand your maximum VHD size beyond 256GB:
 
@@ -174,18 +174,54 @@ To expand your maximum VHD size beyond 256GB:
 
 4. Resize your WSL 2 VHD by completing the following commands:
    - Open Windows Command Prompt with admin privileges and enter:
-      - `diskpart`
-      - `Select vdisk file="<pathToVHD>"`
-      - `expand vdisk maximum="<sizeInMegaBytes>"`
+
+      ```powershell
+      diskpart
+      DISKPART> Select vdisk file="<pathToVHD>"
+      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**:
+
+      ```powershell
+      DISKPART> expand vdisk maximum=<sizeInMegaBytes>
+      ```
+
+   - Exit **diskpart**
+
+      ```powershell
+      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:
-    - `sudo mount -t devtmpfs none /dev`
-    - `mount | grep ext4`
-    - Copy the name of this entry, which will look like: `/dev/sdXX` (with the X representing any other character)
-    - `sudo resize2fs /dev/sdXX`
-    - Use the value you copied earlier. You may also need to install resize2fs: `apt install resize2fs`
+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.
+
+   ```powershell
+      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**:
+
+   ```powershell
+      sudo resize2fs /dev/sdb <sizeInMegabytes>M
+   ```
+
+   > [!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)
+      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]
 > In general 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.

WSL/install-win10.md

@@ -23,7 +23,7 @@ Open PowerShell as Administrator and run:
 dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
 ```
 
-We recommend now moving on to step #2, updating to WSL 2, but if you wish to only install WSL 1, you can now restart your machine and move on to [Step 6 - Install your Linux distribution of choice](./install-win10.md#step-6---install-your-linux-distribution-of-choice). To update to WSL 2, wait to restart your machine and move on to the next step.
+We recommend now moving on to step #2, updating to WSL 2, but if you wish to only install WSL 1, you can now **restart** your machine and move on to [Step 6 - Install your Linux distribution of choice](./install-win10.md#step-6---install-your-linux-distribution-of-choice). To update to WSL 2, **wait to restart** your machine and move on to the next step.
 
 ## Step 2 - Update to WSL 2
 
@@ -69,7 +69,7 @@ Once the installation is complete, move on to the next step - setting WSL 2 as y
 
 ## Step 5 - Set WSL 2 as your default version
 
-Open PowerShell as Administrator and run this command to set WSL 2 as the default version when installing a new Linux distribution:
+Open PowerShell and run this command to set WSL 2 as the default version when installing a new Linux distribution:
 
 ```powershell
 wsl --set-default-version 2
@@ -155,7 +155,7 @@ Below are related errors and suggested fixes. Refer to the [WSL troubleshooting
 
 - **Installation failed with error 0x80070003**
   - The Windows Subsystem for Linux only runs on your system drive (usually this is your `C:` drive). Make sure that distributions are stored on your system drive:  
-  - Open **Settings** -> **Storage** -> **More Storage Settings: Change where new content is saved**
+  - Open **Settings** -> **System --> **Storage** -> **More Storage Settings: Change where new content is saved**
     ![Picture of system settings to install apps on C: drive](media/AppStorage.png)
 
 - **WslRegisterDistribution failed with error 0x8007019e**
@@ -193,4 +193,4 @@ Below are related errors and suggested fixes. Refer to the [WSL troubleshooting
   3. After you enabled WSL, a reboot is required for it to take effect, reboot your machine and try again.
 
 - **Error: WSL 2 requires an update to its kernel component. For information please visit https://aka.ms/wsl2kernel .**
-  - If the Linux kernel package is missing in the %SystemRoot%\system32\lxss\tools folder, you will encounter this error. Resolve it by installing the Linux kernel update MSI package in step #4 of these installation instructions. You may need to uninstall the MSI from ['Add or Remove Programs'](ms-settings:appsfeatures-app), and install it again.
+  - If the Linux kernel package is missing in the %SystemRoot%\system32\lxss\tools folder, you will encounter this error. Resolve it by installing the Linux kernel update MSI package in step #4 of these installation instructions. You may need to uninstall the MSI from ['Add or Remove Programs'](ms-settings:appsfeatures-app), and install it again.

WSL/release-notes.md

@@ -10,6 +10,11 @@ ms.localizationpriority: high
 
 # Release Notes for Windows Subsystem for Linux
 
+## Build 20226
+For general Windows information on build 20226 visit the [Windows blog](https://blogs.windows.com/windows-insider/2020/09/10/announcing-windows-10-insider-preview-build-20226/).
+
+* Fix crash in LxssManager service. [GH 5902]
+
 ## Build 20211
 For general Windows information on build 20211 visit the [Windows blog](https://blogs.windows.com/windows-insider/2020/09/10/announcing-windows-10-insider-preview-build-20211/).
 

WSL/troubleshooting.md

@@ -9,22 +9,21 @@ ms.localizationpriority: high
 
 # Troubleshooting Windows Subsystem for Linux
 
-For support with issues related to WSL, please see our GitHub repo: https://github.com/Microsoft/wsl/issues
+For support with issues related to WSL, please see our [WSL product repo on GitHub](https://github.com/Microsoft/wsl/issues).
 
 ## Search for any existing issues related to your problem
 
-For technical issues, use the product repo: https://github.com/Microsoft/wsl/issues
+For technical issues, use the [product repo](https://github.com/Microsoft/wsl/issues).
 
-For issues related to the contents of this documentation, use the docs repo: https://github.com/MicrosoftDocs/wsl/issues
+For issues related to the contents of this documentation, use the [docs repo](https://github.com/MicrosoftDocs/wsl/issues).
 
 ## Submit a bug report
 
 For bugs related to WSL functions or features, file an issue in the product repo: https://github.com/Microsoft/wsl/issues
 
 ## Submit a feature request
 
-To request a new feature related to WSL functionality or compatibility, file an issue in the product repo:
-	https://github.com/Microsoft/wsl/issues
+To request a new feature related to WSL functionality or compatibility, [file an issue in the product repo](https://github.com/Microsoft/wsl/issues).
 
 ## Contribute to the docs
 
@@ -36,42 +35,46 @@ Lastly, if your issue is related to the Windows Terminal, Windows Console, or th
 
 ## Common issues
 
-### I'm on Windows 10 version 1903 and I still do not see options for WSL 2. 
+### I'm on Windows 10 version 1903 and I still do not see options for WSL 2
 
-This is likely because your machine has not yet taken the backport for WSL 2. The simplest way to resolve this is by going to Windows Settings and clicking 'Check for Updates' to install the latest updates on your system. You can view the full instructions on taking the backport [here](https://devblogs.microsoft.com/commandline/wsl-2-support-is-coming-to-windows-10-versions-1903-and-1909/#how-do-i-get-it). 
+This is likely because your machine has not yet taken the backport for WSL 2. The simplest way to resolve this is by going to Windows Settings and clicking 'Check for Updates' to install the latest updates on your system. See [the full instructions on taking the backport](https://devblogs.microsoft.com/commandline/wsl-2-support-is-coming-to-windows-10-versions-1903-and-1909/#how-do-i-get-it).
 
-If you hit 'Check for Updates' and still do not receive the update you can install KB KB4566116 manually by [following this link](https://www.catalog.update.microsoft.com/Search.aspx?q=KB4566116).  
+If you hit 'Check for Updates' and still do not receive the update you can [install KB KB4566116 manually](https://www.catalog.update.microsoft.com/Search.aspx?q=KB4566116).  
 
 ### Error: 0x1bc when `wsl --set-default-version 2`
+
 This may happen when 'Display Language' or 'System Locale' setting is not English.
-```
+
+```powershell
 wsl --set-default-version 2
 Error: 0x1bc
 For information on key differences with WSL 2 please visit https://aka.ms/wsl2
 ```
 
 THe actual error for `0x1bc` is:
-```
+
+```powershell
 WSL 2 requires an update to its kernel component. For information please visit https://aka.ms/wsl2kernel
 ```
 
 For more information, please refer to issue [5749](https://github.com/microsoft/WSL/issues/5749)
 
-
 ### Cannot access WSL files from Windows
+
 A 9p protocol file server provides the service on the Linux side to allow Windows to access the Linux file system. If you cannot access WSL using `\\wsl$` on Windows, it could be because 9P did not start correctly.
 
-To check this, you can check the start up logs using: `dmesg |grep 9p`, and this will show you any errors. A successfull output looks like the following: 
+To check this, you can check the start up logs using: `dmesg |grep 9p`, and this will show you any errors. A successfull output looks like the following:
 
-```
+```bash
 [    0.363323] 9p: Installing v9fs 9p2000 file system support
 [    0.363336] FS-Cache: Netfs '9p' registered for caching
 [    0.398989] 9pnet: Installing 9P2000 support
 ```
 
 Please see [this Github thread](https://github.com/microsoft/wsl/issues/5307) for further discussion on this issue.
 
-### Can't start WSL 2 distro and only see 'WSL 2' in output
+### Can't start WSL 2 distribution and only see 'WSL 2' in output
+
 If your display language is not English, then it is possible you are seeing a truncated version of an error text.
 
 ```powershell
@@ -81,17 +84,49 @@ WSL 2
 
 To resolve this issue, please visit `https://aka.ms/wsl2kernel` and install the kernel manually by following the directions on that doc page. 
 
-### Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
+### `command not found` when executing windows .exe in linux
 
-1. Check the [Hyper-V system requirements](/windows-server/virtualization/hyper-v/system-requirements-for-hyper-v-on-windows#:~:text=on%20Windows%20Server.-,General%20requirements,the%20processor%20must%20have%20SLAT.)
-2. If your machine is a VM, please enable [nested virtualization](./wsl2-faq.md#can-i-run-wsl-2-in-a-virtual-machine) manually. Launch powershell with admin, and run: 
+Users can run Windows executables like notepad.exe directly from Linux. Sometimes, you may hit "command not found" like below: 
 
-```powershell
-Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
+```Bash
+$ notepad.exe
+-bash: notepad.exe: command not found
 ```
 
-3. Please follow guidelines from your PC's manufacturer on how to enable virtualization. In general, this can involve using the system BIOS to ensure that these features are enabled on your CPU. 
-4. Restart your machine after enabling the `Virtual Machine Platform` optional component. 
+If there are no win32 paths in your $PATH, interop isn't going to find the .exe.
+You can verify it by running `echo $PATH` in Linux. It's expected that you will see a win32 path (for example, /mnt/c/Windows) in the output.
+If you can't see any Windows paths then most likely your PATH is being overwritten by your Linux shell. 
+
+Here is a an example that /etc/profile on Debian contributed to the problem:
+
+```Bash
+if [ "`id -u`" -eq 0 ]; then
+  PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+else
+  PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
+fi
+```
+
+The correct way on Debian is to remove above lines.
+You may also append $PATH during the assignment like below, but this lead to some [other problems](https://salsa.debian.org/debian/WSL/-/commit/7611edba482fd0b3f67143aa0fc1e2cc1d4100a6) with WSL and VSCode..
+
+For more information, see issue [5296](https://github.com/microsoft/WSL/issues/5296) and issue [5779](https://github.com/microsoft/WSL/issues/5779).
+
+### Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS
+
+Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
+
+1. Check the [Hyper-V system requirements](/windows-server/virtualization/hyper-v/system-requirements-for-hyper-v-on-windows#:~:text=on%20Windows%20Server.-,General%20requirements,the%20processor%20must%20have%20SLAT.)
+
+2. If your machine is a VM, please enable [nested virtualization](./wsl2-faq.md#can-i-run-wsl-2-in-a-virtual-machine) manually. Launch powershell with admin, and run:
+
+    ```powershell
+    Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
+    ```
+
+3. Please follow guidelines from your PC's manufacturer on how to enable virtualization. In general, this can involve using the system BIOS to ensure that these features are enabled on your CPU. Instructions for this process can vary from machine to machine, please see [this article](https://www.bleepingcomputer.com/tutorials/how-to-enable-cpu-virtualization-in-your-computer-bios/) from Bleeping Computer for an example.
+
+4. Restart your machine after enabling the `Virtual Machine Platform` optional component.
 
 ### Bash loses network connectivity once connected to a VPN
 
@@ -309,7 +344,7 @@ This error is related to being in a bad install state. Please complete the follo
 
 If you're seeing this error:
 
-```
+```bash
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 @         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ -318,10 +353,10 @@ Permissions 0777 for '/home/artur/.ssh/private-key.pem' are too open.
 
 To fix this, append the following to the the ```/etc/wsl.conf``` file:
 
-```
+```bash
 [automount]
 enabled = true
 options = metadata,uid=1000,gid=1000,umask=0022
 ```
 
-Please note that adding this command will include metadata and modify the file permissions on the Windows files seen from WSL. Please see the [File System Permissions](./file-permissions.md) for more information.
+Please note that adding this command will include metadata and modify the file permissions on the Windows files seen from WSL. Please see the [File System Permissions](./file-permissions.md) for more information.