Updated troubleshooting to resolve merge conflicts

craigloewen-msft · craigloewen-msft · commit 59c945c27baf · 2020-10-22T13:13:44.000-07:00
diff --git a/WSL/install-win10.md b/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.
diff --git a/WSL/troubleshooting.md b/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,19 +84,51 @@ 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
+
+Users can run Windows executables like notepad.exe directly from Linux. Sometimes, you may hit "command not found" like below: 
+
+```Bash
+$ notepad.exe
+-bash: notepad.exe: command not found
+```
+
+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).
+
 ### "Error: 0x80370102 The virtual machine could not be started because a required feature is not installed."
 
 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
-```
+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.
 
-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. 
+4. Restart your machine after enabling the `Virtual Machine Platform` optional component.
 
 ### Bash loses network connectivity once connected to a VPN
 
@@ -311,7 +346,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!          @
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ -320,7 +355,7 @@ 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
diff --git a/WSL/tutorials/wsl-containers.md b/WSL/tutorials/wsl-containers.md
@@ -27,7 +27,7 @@ To learn more, checkout the [Introduction to Docker containers](/learn/modules/i
 
 - Ensure your machine is running Windows 10, [updated to version 2004](ms-settings:windowsupdate), **Build 18362** or higher.
 - [Enable WSL, install a Linux distribution, and update to WSL 2](../install-win10.md).
-- [Download and install the Linux kernel update package](/windows/wsl/wsl2-kernel).
+- [Download and install the Linux kernel update package](../install-win10.md#step-4---download-the-linux-kernel-update-package).
 - [Install Visual Studio Code](https://code.visualstudio.com/download) *(optional)*. This will provide the best experience, including the ability to code and debug inside a remote Docker container and connected to your Linux distribution.
 - [Install Windows Terminal](/windows/terminal/get-started) *(optional)*. This will provide the best experience, including the ability to customize and open multiple terminals in the same interface (including Ubuntu, Debian, PowerShell, Azure CLI, or whatever you prefer to use).
 - [Sign up for a Docker ID at Docker Hub](https://hub.docker.com/signup) *(optional)*.
@@ -157,4 +157,4 @@ For more help with general troubleshooting issues in WSL, see the [Troubleshooti
 - [VS Code Blog: Guidelines for choosing a development environment](https://code.visualstudio.com/docs/containers/choosing-dev-environment#_guidelines-for-choosing-a-development-environment)
 - [VS Code Blog: Using Docker in WSL 2](https://code.visualstudio.com/blogs/2020/03/02/docker-in-wsl2)
 - [VS Code Blog: Using Remote Containers in WSL 2](https://code.visualstudio.com/blogs/2020/07/01/containers-wsl)
-- [Hanselminutes Podcast: Making Docker lovely for Developers with Simon Ferquel](https://hanselminutes.com/736/making-docker-lovely-for-developers-with-simon-ferquel)
+- [Hanselminutes Podcast: Making Docker lovely for Developers with Simon Ferquel](https://hanselminutes.com/736/making-docker-lovely-for-developers-with-simon-ferquel)
diff --git a/WSL/wsl2-mount-disk.md b/WSL/wsl2-mount-disk.md
@@ -1,13 +1,13 @@
 ---
-title: Get started mounting a linux disk in WSL 2 (preview)
+title: Get started mounting a Linux disk in WSL 2 (preview)
 description: Learn how to set up a disk mount in WSL 2 and how to access it.
 keywords: wsl, windows, windowssubsystem, gnu, linux, bash, disk, ext4, filesystem, mount
 ms.date: 06/08/2020
 ms.topic: article
 ms.localizationpriority: medium
 ---
 
-# Get started mounting a linux disk in WSL 2 (preview)
+# Get started mounting a Linux disk in WSL 2 (preview)
 
 If you want to access a Linux disk format that isn't supported by Windows, you can use WSL 2 to mount your disk and access its content.
 
@@ -170,4 +170,4 @@ If `Diskpath` is omitted, all attached disks are unmounted and detached.
 
 - USB flash drives are not supported at this time and will fail to attach to WSL 2. USB disks are supported though.
 
-- Only filesystems that are natively supported in the kernel can be mounted by `wsl --mount`. This means that it's not possible to use installed filesystem drivers (such as ntfs-3g for example) by calling `wsl --mount`.
+- Only filesystems that are natively supported in the kernel can be mounted by `wsl --mount`. This means that it's not possible to use installed filesystem drivers (such as ntfs-3g for example) by calling `wsl --mount`.
