Lompat ke konten Lompat ke sidebar Lompat ke footer
Beranda / Fix Windows Subsystem for Linux Errors, Problems and Issues

Fix Windows Subsystem for Linux Errors, Problems and Issues

Posting Komentar

Like all software, the Windows Subsystem (WSL2) too has its in-bounds shares of issues. In this guide, we are going to troubleshoot Windows Subsystem for Linux Error Messages and Codes.

Determine Windows Subsystem for Linux Errors, Problems & Issues

These are messages for which we are loss to troubleshoot Windows Subsystem for Linux Error Messages and Codes.

  1. Do not see options for WSL 2
  2. Error: 0x1bc
  3. Error: 0x80040306 on Installation
  4. Cannot access WSL files from Windows
  5. Can't start WSL 2 distribution and lonesome see 'WSL 2' in turnout
  6. Command Not Found
  7. Error: 0x80370102 The virtual machine could non comprise started because a required feature is non installed
  8. Mistake: 0x80040154 after Windows update
  9. WSL Chicago impermanent with Error 0x80070003
  10. Exhibit language changing in WSL
  11. Installation issues after Windows system restore
  12. Atomic number 102 internet access in WSL
  13. Permission Denied when using Ping
  14. Unable to boot after instalmen WSL 2
  15. Not able to move Windows Commands inside a electrical distributor
  16. ICS is handicapped
  17. Bash is decorated
  18. OpenSSH-Server connection issues
  19. The documented assembly could non be found
  20. Correct (SSH related) license errors

Let us talk about them in detail.

1] Do non see options for WSL 2

Many Windows users take complained that even up though they are at built no 1903, they are unable to see options for WSL 2. This happens when your computing machine machine has not yet taken the backport for WSL 2.

To hole this, you just postulate to learn for updates, and you will exist good to go.

2] Error: 0x1bc

You may see the following error when the "Display Language"or"System Locale"is non set toEnglish. 

wsl --set-nonpayment-version 2  Error: 0x1bc  For information on key differences with WSL 2 please visit https://aka.ms/wsl2

To fix the error, you motive to confirmation if the Kernel is installed on your reckoner. To do that, use the following overtop.

dir %SystemRoot%\system32\lxss\tools\kernel

If you don't have Kernel, download it from aka.ms. Reach reliable to download it as an administrator and install the Gist on your machine to fix the error.

3] Error: 0x80040306 connected Installation

Fix Windows Subsystem for Linux Errors, Problems & Issues

If you are seeing Error: 0x80040306 on Installation. To fix this you need to disableLegacy Comfort.To do that, keep abreast the given steps.

  1. WideCommand Promptas an executive from theStart Menu.
  2. Conservative-come home on the cmd logotype and choice Properties.
  3. Now, uncheck " Use legacy console"and click Ok.

Finally, check if it fixes the issue.

4] Cannot access WSL files from Windows

If you are unable to entree Windows Subsystem for Linux by \\wsl$ on Windows, this could be mean that the 9P protocol file server fails to start.

The easiest fix is to update your computer and enable "updates for Microsoft products on Windows Update".To set that, you can follow the given steps.

  1. Set upSettingsasideWin + I.
  2. ClickUpdate & Security > Precocious options.
  3. Use the toggle to disable "Take in updates for other Microsoft products when you update Windows".

This will pay back the issue for you.

5] Can't start WSL 2 statistical distribution and solely see 'WSL 2' in turnout

This error is inevitable if your reveal oral communicatio is not set to English people. You volition see the following output when trying to start WSL 2.

C:\Users\Maine>wsl  WSL 2

To pay off the error, you need to download and install the Marrow manually. You can download the lodge from aka.ms/wsl2kernel. Install the Kernel to fix the computer error easily.

6] Instruction Not Found

This is one of the common errors united sees when they run a .exe file of Windows in Linux. You Crataegus laevigata see the following error when trying to Doctor of Osteopathy the same.

$ notepad.exe  -bash: notepad.exe: command not found

This happens when the$PATH fails to get hold the .exe filing cabinet. The unexceeded solution for this error is to run the favourable command in the Terminal.

export PATH=$Way:/usr/sbin

Make out this and check if it fixes the error.

7] Error: 0x80370102 The practical motorcar could non be started because a required sport is not installed

Many hold experienced this error when nerve-racking to install a Linux distributor. Dissimilar previous errors, this error has more than one solution. So, buckle up and read all the solutions.

These are the things you nates cause to localization Fault: 0x80370102, The essential machine could not beryllium started because a required feature article is not installed.

  1. Enable Hyper-V
  2. Enable Hardware Virtualization
  3. Enable Nested Virtualization

Have U.S.A talk about them in item.

Enable Hyper-V

Without Hyper-V, you won't be able to create a Virtual Environment. So, enable it with the help of the pursual steps.

  1. OpenControl Panelfrom theStart Bill of fare.
  2. ClickPrograms and Features > Call on Windows features on or off
  3. Scroll down to find Hyper-V, tick it, and click Satisfactory.

After enabling Hyper-V check if the issue is fixed.

Enable Hardware Virtualization

Hardware Virtualization is a must when trying to run Virtual Machine. So, if you veneer the Computer error: 0x80370102, try to enable Hardware Virtualization from the BIOS to fix the issue.

Enable Nested Virtualization

Nested Virtualization allows you to ravel Hypervisor inside a VM. And so, if you are standing cladding the wrongdoing, try enabling Nested Virtualization. To do that, you need to run PowerShellEastern Samoa an administrator and run the pursual statement.

Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true

Let this command run and check if it fixes the issue.

8] Erroneous belief: 0x80040154 after Windows update

troubleshoot Windows Subsystem for Linux Error Messages and Codes

You may realise this error if Windows Subsystem for Linux is disabled because of a Windows Update. So, to fix the issue, we need to enable this option. To doh that, watch the given steps.

  1. Set upControlfrom thePop Menu.
  2. ClickPrograms and Features > Turn Windows features on or cancelled
  3. Scroll down to find Windows Subsystem for Linux, check IT, and click Ok.

Finally, re-start your computer and check if the issue persists.

9] WSL Stops working with Error 0x80070003

If WSL stops with this error inscribe 0x80070003, resolve it with this guide.

10] Display language changing in WSL

WSL automatically changes the Ubuntu locale, for it to match the language of your Windows computer. If you are not a fan of this move, use the succeeding command to set the exhibit nomenclature according to your needs.

Note: The following mastery will change the language to nut-US.

sudo update-locus LANG=en_US.UTF8

Do this and chip if it fixes the issue.

11] Installation issues after Windows system reinstate

If you are facing Installation issues afterward Windows system fix, try deleting the Windows Subsystem for Linux folder. The following is its path.

%windir%\System32\Tasks\Microsoft\Windows\Windows Subsystem for Linux

Restart your computer, reinstall Bash and chink if it fixes the issue.

12] No internet access in WSL

Many users have according that they are not able to access the Internet in WSL. However, the solution might be easier than you think. This happens because of any tertiary-party antivirus that you may deliver. As the firewall blocks the Internet. Soh, to fix this, dispatch the anti-computer virus and you will be good to give way.

13] Permission Denied when using Knock

If you are not competent to Ping in WSL past this means that you don't have body privilege. So, you need to run Ubuntu and Linux with administrative privilege or Bash.exe on your command line spokesperson with administrative privilege.

Hopefully, this testament fix the issue easily.

14] Incapable to kicking after installing WSL 2

The reason why you are unable in addition after installing WSL 2  is still extraordinary but Microsoft is disagreeable to workplace on an update to fully diagnose the issue. However, there are two things that you tin do and come across if it fixes the issue.

  • Use System Reconstruct Distributor point to fix the error.
  • Update your Graphics Driver and see if it fixes the issue.

15] Not able to run Windows Commands inside a distributor

There are a couple of distributors in Windows Store that are non wholly optimized to run all Windows Commands. You may commence any of the shadowing errors.

-bash: powershell.exe: command not found
powershell.exe /c start

To fix this error, hightail it the following command.

echo $PATH

Nowadays, check if the output includes "/mnt/c/Windows/system32", if you are facing the error, then most probably the track won't be there.

Like a sho, check your Profile settings by

cat /etc/profile

Now, crack if a Itinerary assignment starts with "#", if it does, point out out the block. Also, check if wsl.conf is present and make sure that it doesn't give birth appendWindowsPath=false. If it does, comment it out.

After doing this, you indigence to restart distribution. You john use the following command to do that.

wsl -t <name of the distributor>

or

wsl --closure

Hopefully, the issue will glucinium stationary.

16] ICS is disabled

A WSL ass not go without ICS or Internet Connection Sharing. TheHost Web Service (HNS)uses the ICS to build a important virtual network for WSL 2 to create NAT, DNS, DHCP, and host connection communion.

To pay back the misplay, we demand to enable ICS. So, follow the given steps to enable ICS.

  1. LaunchServicesfrom theStart Menu.
  2. Double-click happening Internet Connection Unselfish (ICS),and tickStartif it's stopped.
  3. Finally, clickHold > Ok.

You should also edit some policies. So, launchGroup Insurance policy Editorand navigate to the following location.

Computer Configuration > Administrative Templates > Network > Network Connections

And invalid the following policies.

  • Prohibit installation and configuration of Meshing Bridge on your DNS domain network
  • Prohibit the use of Net Connection Firewall on your DNS domain network
  • Prohibit the use of Internet Joining Sharing on your DNS domain network
  • Require domain users to elevate when setting a network's location

17] Bash is adorned

When Bash hangs or deadlocks and stops responding to your input you can either restart your machine atomic number 3 that will pay off the wrongdoing or report a memory rubbish dump. The latter may lead to a scheme crash, thusly, save your work prior to reportage.

18] OpenSSH-Server connection issues

If you are seeing any OpenSSF-Waiter connection issue, the start matter you take to do is to check if the OpenSSH-Server is running. You buttocks use the following instruction to do that.

sudo service ssh status

If it's not moving, function the following command to start the service.

sudo service ssh start

If it's moving, you should restart the military service with the chase instruction and check if IT fixes the issue.

sudo service ssh restart

If it's unable to fix the issue, try to start SSHD in debug mode. Before that, use the following control to stop SSH service.

sudo service ssh stop

Now, exercise the pursual command to start SSHD in debug mode.

sudo /usr/sbin/sshd -d

Hopefully, this fixes the error.

19] The referenced assembly could non be found

Many users are encountering "The referenced assembly could not Be found" when they try to enable WSL additive have. If you are single of them, try facultative Windows Subsystem for Linuxfrom Command Panel and updating your computer. Hopefully, that will fix the error.

20] Correct (SSH related) permission errors

If you are seeing the next misplay, thread this section for the root.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: UNPROTECTED Clubby KEY Register! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Permissions 0777 for '/base/artur/.ssh/snobbish-key.pem' are too open.

To restore this issue, Microsoft suggests that you attend /etc/wsl.conffile and append the following:

[automount] enabled = true options = metadata,uid=1000,gid=1000,umask=0022

This will fix the erroneous belief. Before, doing this, get sure you have adequate permission.

These were some of the Windows Subsystem for Linux Error Messages and Codes and their troubleshooting tips. We hope that they help you fix WSL Errors, Problems, and Issues.

Fix Windows Subsystem for Linux Errors, Problems and Issues

Source: https://www.thewindowsclub.com/troubleshoot-windows-subsystem-for-linux-error-messages-and-codes

Posting Komentar untuk "Fix Windows Subsystem for Linux Errors, Problems and Issues"