Sida software-ka oo dhan, Windows Subsystem (WSL2) sidoo kale wuxuu leeyahay saamigiisa arrimaha cadaaladda ah. Tilmaan-bixiyahan, waxaanu ku xalin doonaa nidaamka-hoosaadka Windows-ka ee^{(Windows Subsystem for Linux)} fariimaha iyo koodhadhka khaladaadka Linux.

Hagaaji nidaamka-hoosaadka Windows^{(Fix Windows Subsystem)} ee Khaladaadka Linux^{(Linux Errors)} , Dhibaatooyinka^(Problems) & Arrimaha^(Issues)

Kuwani waa fariimo aan u doonayno in aan cilad- saarno Windows Subsystem^{(Windows Subsystem)} for Linux Error Messages and Codes .

1. Ha arkin xulashooyinka WSL 2
2. Khaladka: 0x1bc
3. Cilad: 0x80040306 Rakibaadda
4. Lagama heli karo faylasha WSL ee Windows
5. Ma bilaabi karo qaybinta WSL 2 oo kaliya arag ' WSL 2 ' ee soosaarka
6. Taliska lama helin
7. Cilad: 0x80370102 Mashiinka farsamada lama bilaabi karo sababtoo ah sifada loo baahan yahay lama rakibin
8. Cilad: 0x80040154 kadib cusboonaysiinta Windows
9. WSL^{(WSL Stops)} waxay joojisaa ku shaqaynta  cilad 0x80070003^{(Error 0x80070003)}
10. Ku muuji isbeddelka luqadda WSL
11. ^{(Installation)}Arrimaha rakibidda ka dib soo celinta nidaamka Windows
12. Ma jiro wax internet ah oo laga galo WSL
13. Oggolaanshaha waa la diiday marka la isticmaalayo Ping
14. Aan awoodin in la bootiyo ka dib marka la rakibo WSL 2
15. Aan awoodin inuu ku socodsiiyo amarrada Windows^{(Windows Commands)} gudaha qaybiyaha
16. ICS waa naafo
17. Bash waa la sudhay
18. FurSSH-Server arrimaha ku xiran
19. Golaha la tixraacay waa la heli waayay
20. ^(Correct)Qaladaadka oggolaanshaha saxda ah ( SSH ee la xidhiidha)^(SSH)

Aynu si faahfaahsan uga hadalno iyaga.

1] Ha arkin xulashooyinka WSL 2

Isticmaalayaal badan oo Windows ah ayaa ka cawday in kastoo ay ku jiraan la dhisay 1903, ma awoodaan inay arkaan fursadaha WSL 2 . Tani waxay dhacdaa marka mashiinka kombuyuutarku aanu weli qaadin dhabarka dambe ee WSL 2 .

Si aad tan u xalliso, kaliya waxaad u baahan tahay inaad hubiso wixii ku soo cusboonaado^{( check for updates)} , oo waxaad fiicnaan doontaa inaad tagto.

2] Khalad: 0x1bc

Waxaa laga yaabaa inaad aragto cilada soo socota marka "Luqadda Muujinta" ^{(“Display Language” )} ama  "System Locale"  aan loo dejin  Ingiriisi.^(English.)

wsl --set-default-version 2

Error: 0x1bc

For information on key differences with WSL 2 please visit https://aka.ms/wsl2

Si loo saxo qaladka, waxaad u baahan tahay inaad hubiso in Kernel -ku ku rakiban yahay kombuyutarkaaga. Si taas loo sameeyo, adeegso amarkan soo socda.

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

Haddii aadan haysan Kernel , ka soo deji aka.ms^(aka.ms) . Hubi inaad u soo dejiso maamule ahaan oo ku rakib Kernel mashiinkaaga si aad u xalliso qaladka.

3] Cilad: 0x80040306 Rakibaadda

Haddii aad aragto qalad: 0x80040306 Rakibaadda. Si taas loo hagaajiyo waxaad u baahan tahay inaad damiso  Console Legacy. ^{(Legacy Console. )}Si taas loo sameeyo, raac tillaabooyinka la bixiyay.

1. Fur  Command Prompt  maamule ahaan ka  bilow Menu.^{(Start Menu.)}
2. Midig ku dhufo^{(Right-click)} summada cmd oo dooro Properties.
3. Hadda, ka saar " Isticmaal Console dhaxalka ah" ^{(Use legacy console” )} oo dhagsii OK.

Ugu dambeyntii, hubi haddii ay hagaajinayso arrinta.

4] Ma geli karo faylasha WSL ee Windows

Haddii aadan awoodin inaad gasho Windows Subsystem for Linux by \\wsl$ on Windows , tani waxay la macno noqon kartaa in server-ka 9P borotokoolka uu ku guuldareysto inuu bilaabo.

Sida ugu fudud ayaa ah in la cusboonaysiiyo kombayutarka oo aad awood u siiso “cusboonaysiinta alaabta Microsoft ee Cusboonaysiinta Windows”. ^{(“updates for Microsoft products on Windows Update”. )}Si taas loo sameeyo, waxaad raaci kartaa tallaabooyinka la siiyey.

1. Ku bilow  Settings  by  Win + I.
2. Guji  Update & Security > Advanced options.
3. Isticmaal toggle si aad u damiso " Hesho cusboonaysiinta alaabta kale ee Microsoft marka aad cusboonaysiiso Windows^{(Receive updates for other Microsoft products when you update Windows)} ".

Tani waxay kuu hagaajin doontaa arrinta.

5] Ma bilaabi karo qaybinta WSL 2 oo kaliya arag ' WSL 2 ' ee soosaarka

Ciladani waa lama huraan haddii luqadaada bandhiga aan loo dhigin Ingiriis. Waxaad arki doontaa wax soo saarka soo socda markaad isku dayeyso inaad bilowdo WSL 2 .

C:\Users\me>wsl

WSL 2

Si loo saxo qaladka, waxaad u baahan tahay inaad soo dejiso oo aad gacanta ku rakibto Kernel -ka . Waxaad ka soo dejisan kartaa faylka aka.ms/wsl2kernel . Ku rakib Kernel -ka si aad si sahal ah u saxdo khaladka.

6] Amar lama helin

Tani waa mid ka mid ah khaladaadka caadiga ah ee la arko marka ay wadaan faylka .exe ee Windows gudaha Linux . Waxa laga yaabaa inaad aragto khaladka soo socda markaad isku dayayso inaad sidaas oo kale samayso.

$ notepad.exe

-bash: notepad.exe: command not found

Tani waxay dhacdaa marka  $PATH ay ku guuldareysato inay hesho faylka .exe . Xalka ugu fiican ee khaladkan waa in lagu socodsiiyo amarka soo socda ee Terminalka^(Terminal) .

export PATH=$PATH:/usr/sbin

Tan samee oo hubi haddii ay hagaajinayso qaladka.

7] Cilad: 0x80370102 Mashiinka farsamada lama bilaabi karo sababtoo ah sifada loo baahan yahay lama rakibin

Qaar badan ayaa la kulmay khaladkan markii ay isku dayeen inay rakibaan qaybiyaha Linux . Si ka duwan khaladaadkii hore, qaladkan waxa uu leeyahay in ka badan hal xal. Haddaba, xir oo akhri dhammaan xalalka.

Kuwani waa waxyaabaha aad samayn karto si aad u hagaajiso Khaladka: 0x80370102, Mashiinka farsamada lama bilaabi karo sababtoo ah sifada loo baahan yahay lama rakibin .

1. Daar Hyper-V
2. Daar ka-qaadista ka-hortagga Qalabka
3. Daar ka-qaadista Virtual Nsted

Aynu si faahfaahsan uga hadalno iyaga.

Daar Hyper-V

Hyper-V la'aanteed ma awoodid inaad abuurto deegaan Virtual^{(Environment)} . Markaa, awood u yeelo adigoo kaashanaya tillaabooyinka soo socda.

1. Ka fur  Control Panel  ee ka  bilow Menu.^{(Start Menu.)}
2. Guji  Programs and Features > Turn Windows features on or off
3. Hoos^(Scroll) u deg si aad u heshid Hyper-V , hubi, oo guji OK.

Kadib markaad awood u siiso Hyper-V^(Hyper-V) hubi haddii arintu go'an tahay.

Daar ka-qaadista ka-hortagga Qalabka

Virtualization Hardware^{(Hardware Virtualization)} waa lama huraan marka la isku deyayo in uu socodsiiyo Mishiinka Virtual^{(Virtual Machine)} . Markaa, haddii aad la kulanto Cilad: 0x80370102, isku day inaad karti u siiso Virtualization Hardware^{(enable Hardware Virtualization)} BIOS si loo xalliyo arrinta.

Daar ka-qaadista Virtual Nsted

Nested Virtualization waxay kuu oggolaanaysaa inaad ku socodsiiso Hypervisor gudaha VM. Marka, haddii aad wali wajaheyso cilada, isku day in aad karti u yeelatid Nsted Virtualization . Si taas loo sameeyo, waxaad u baahan tahay inaad ku socodsiiso PowerShell  maamule ahaan oo aad socodsiiso amarkan soo socda.

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

Amarkan ha shaqeeyo oo hubi haddii uu xalinayo arrinta.

8] Cilad: 0x80040154 kadib cusboonaysiinta Windows

Waxaa laga yaabaa inaad aragto ciladan haddii Windows Subsystem for Linux uu naafo yahay sababtoo ah Cusbooneysiinta Windows^{(Windows Update)} . Marka, si loo xalliyo arrinta, waxaan u baahanahay inaan awoodno doorashadan. Si taas loo sameeyo, raac tillaabooyinka la bixiyay.

1. Ka bilow  Xakamaynta ^(Control ) ka  bilow Menu.^{(Start Menu.)}
2. Guji  Programs and Features > Turn Windows features on or off
3. Hoos u dhaadhac si aad u hesho nidaamka-hoosaadka Windows ee Linux^{(Windows Subsystem for Linux)} , hubi, oo guji OK.

Ugu dambeyntii, dib u bilow kombayutarka oo hubi haddii arrintu sii socoto.

9] WSL Joojinta^{(WSL Stops)} ku shaqaynta  Cillad 0x80070003^{(Error 0x80070003)}

Haddii WSL ay ku joogsato summadan qaladka ah 0x80070003^{(error code 0x80070003)} , ku xalliso hagahan.

10] Muuji^(Display) luqadda beddeleysa gudaha WSL

WSL waxay si toos ah u beddeshaa deegaanka Ubuntu , si ay ugu habboonaato luqadda kumbuyuutarkaaga Windows . Haddi aanad taageere u ahayn guuritaankan, adeegso amarka soo socda si aad luuqadda bandhiga ugu dejiso hadba baahidaada.

Xusuusin: Amarka soo socda ayaa luqadda u beddeli doona en-US.

sudo update-locale LANG=en_US.UTF8

Tan samee oo hubi haddii ay hagaajinayso arrinta.

11] Arrimaha rakibaadda^{(Installation)} ka dib soo celinta nidaamka Windows

Haddii aad la kulanto arrimaha Rakibaadda ka dib soo celinta nidaamka ^{(Installation)}Windows , isku day inaad tirtirto galka Windows-ka ee Linux^{(Windows Subsystem for Linux )} . Sidan soo socotana waa jidkeedii.

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

Kumbuyuutarkaaga dib u bilow, dib u rakib Bash^(Bash) oo hubi haddii ay xalliso arrinta.

12] Ma jiro wax gal internet ah gudaha WSL

Isticmaalayaal badan ayaa sheegay in aysan awoodin in ay galaan internetka ^(Internet)WSL . Si kastaba ha ahaatee, xalku wuu ka fududaan karaa sidaad u malaynayso. Tani waxay u dhacdaa sababtoo ah anti-virus-ka koox saddexaad oo laga yaabo inaad haysato. Sida darbigu u xannibo internetka^(Internet) . Markaa, si aad tan u xalliso, ka saar anti-virus-ka oo waad fiicnaan doontaa inaad tagto.

13] Ogolaansho^(Permission) waa la diiday marka la isticmaalayo Ping

Haddii aadan awoodin in aad Ping ku gasho WSL markaa tani waxay la macno tahay inaadan haysan mudnaan maamul. Markaa, waxaad u baahan tahay inaad ku socodsiiso Ubuntu iyo Linux oo leh mudnaan maamul ama Bash.exe turjumaanka khadka taliska oo leh mudnaanta maamul.

Waxaan rajeyneynaa, tani waxay si fudud u xallin doontaa arrinta.

14] Aan awoodin in la bootiyo ka dib marka la rakibo WSL 2

Sababta sababta aadan u awoodin inaad kabaha u dhejiso ka dib markaad rakibto WSL 2   ayaa weli ah mid aan qarsoodi ahayn laakiin Microsoft waxay isku dayeysaa inay ka shaqeyso cusbooneysiinta si ay si buuxda u ogaato arrinta. Si kastaba ha ahaatee, waxaa jira laba shay oo aad samayn karto oo aad aragto haddii ay hagaajinayso arrinta.

• Isticmaal barta soo celinta nidaamka si aad u saxdo qaladka.
• Cusbooneysii Darawalka Sawirkaaga^{(Update your Graphics Driver)} oo arag haddii ay xalliso arrinta.

15] Aan awoodin inuu ku socodsiiyo amarrada Windows^{(Windows Commands)} gudaha qaybiyaha

Waxaa jira qaybiyayaal yar oo ku jira Bakhaarka Daaqadaha^{(Windows Store)} kuwaas oo aan si buuxda loo hagaajin si ay u socodsiiyaan dhammaan amarrada Windows^{(Windows Commands)} . Waxaa laga yaabaa inaad hesho mid ka mid ah khaladaadka soo socda.

-bash: powershell.exe: command not found

powershell.exe /c start

Si loo saxo qaladkan, socodsii amarka soo socda.

echo $PATH

Hadda, hubi haddii wax soo saarka ay ku jiraan " “/mnt/c/Windows/system32”

Hadda, hubi dejimaha boggaga by

cat /etc/profile

Hadda, hubi haddii hawsha Jidku^(Path) ay ka bilaabato “#” , haddii ay dhacdo, faallo ka bixi blockka. Sidoo kale, hubi haddii wsl.conf uu joogo oo hubso inaanu lahayn appendWindowsPath=false. Haddii ay dhacdo, faallo ka bixi.

Markaad tan sameyso, waxaad u baahan tahay inaad dib u bilowdo qaybinta. Waxaad isticmaali kartaa amarka soo socda si aad taas u sameyso.

wsl -t <name of the distributor>

ama

wsl --shutdown

Waxaan rajeyneynaa, in arrinta la xalin doono.

16] ICS waa naafo

WSL ma shaqayn karo la'aanteed ICS ama Wadaagga Xidhiidhka Internetka^{(ICS or Internet Connection Sharing)} . Adeegga Shabakadda  Martigelinta (HNS) ^{(Host Network Service (HNS) )} waxay isticmaashaa ICS si ay u dhisto shabakad toosan oo aasaasi ah WSL 2 si ay u abuurto NAT , DNS , DHCP , iyo wadaagista xidhiidhka martigeliyaha.

Si loo saxo qaladka, waxaan u baahanahay inaan awoodno ICS . Markaa, raac tillaabooyinka la bixiyay si aad awood ugu yeelato ICS .

1. Ka billow  adeegyada ^(Services ) ka  bilow Menu.^{(Start Menu.)}
2. Laba-guji Wadaaga Xidhiidhka Internetka (ICS), ^{(Internet Connection Sharing (ICS), )} oo guji  Start  haddi la joojiyo.
3. Ugu dambeyntii, dhagsii  Apply > Ok.

Waa inaad sidoo kale wax ka beddeshaa siyaasadaha qaarkood. Markaa, billow  Tifaftiraha Siyaasadda Kooxda ^{(Group Policy Editor )} oo u gudub meesha soo socota.

Computer Configuration > Administrative Templates > Network > Network Connections

Oo jooji siyaasadaha soo socda.

• Mamnuuc^(Prohibit) ku rakibida iyo habaynta Network Bridge ee shabakada boggaga DNS^(DNS)
• Mamnuuc isticmaalka Internet Firewall^{(Internet Connection Firewall)} ee ku xidhan shabakadaada DNS
• Mamnuuc isticmaalka Wadaagga Xidhiidhka Internetka^{(Internet Connection)} ee shabakada boggaga DNS^(DNS)
• Loo baahan^(Require) yahay isticmaalayaasha bogga in ay sare u qaadaan marka ay dejinayaan goobta shabakadda

17] Bash waa la laadlaadiyay

Marka Bash uu soo laadlaadsado ama xidho oo uu joojiyo ka jawaabista gelintaada waxaad dib u bilaabi kartaa mishiinkaga maadaama ay taasi hagaajin doonto khaladka ama soo sheegi doonta kaydka xusuusta. Tan dambe waxay u horseedi kartaa shil nidaam, markaa, badbaadi shaqadaada ka hor intaanad warbixinta soo sheegin.

18] Arrimaha xidhiidhka ee SSH-Server-ka

Haddii aad aragto arin isku xidhka OpenSSF-Server, waxa ugu horeeya ee aad u baahan tahay inaad samayso waa inaad hubiso in OpenSSH-server uu shaqaynayo. Waxaad isticmaali kartaa amarka soo socda si aad taas u sameyso.

sudo service ssh status

Haddii aysan socon, adeegso amarka soo socda si aad u bilowdo adeegga.

sudo service ssh start

Haddii ay socoto, waa inaad dib ugu bilowdaa adeegga amarkan soo socda oo aad hubiso inay hagaajinayso arrinta.

sudo service ssh restart

Haddi ay awoodi waydo in ay xaliso arinta, isku day in aad ku bilawdo SSHD qaabka debug. Intaa ka hor, isticmaal amarka soo socda si aad u joojiso adeegga SSH .

sudo service ssh stop

Hadda, adeegso amarkan soo socda si aad u bilowdo SSDHD^(SSHD) qaabka debug.

sudo /usr/sbin/sshd -d

Waxaan rajeyneynaa, tani waxay hagaajineysaa qaladka.

19] Golaha la tixraacay lama helin

Isticmaalayaal badan ayaa la kulmaya "Shirka la tixraacay lama helin"^{(“The referenced assembly could not be found”)} markay isku dayaan inay awood u yeeshaan sifada dheeraadka ah ee WSL . Haddii aad ka mid tahay iyaga, isku day inaad awood u siiso Windows Subsystem for Linux ^{(Windows Subsystem for Linux )} from Control Panel oo aad cusboonaysiiso kombayutarkaga. Waxaan rajeyneynaa^(Hopefully) , taasi waxay hagaajin doontaa qaladka.

20] Qaladaadka oggolaanshaha saxda^(Correct) ah ( SSH ee la xidhiidha).^(SSH)

Haddii aad aragto qaladka soo socda, ku dheji qaybtan xalka.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0777 for '/home/artur/.ssh/private-key.pem' are too open.

Si arrintan loo xalliyo, Microsoft waxay kuu soo jeedinaysaa inaad tagto faylka /etc/wsl.conf  oo aad ku dhejiso kuwan soo socda:

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

Tani waxay hagaajin doontaa qaladka. Kahor, inaad tan sameyso, hubi inaad haysato ogolaansho kugu filan.

Kuwani waxay ahaayeen qaar ka mid ah nidaamka- hoosaadka Windows^{(Windows Subsystem)} -ka ee Farriimaha Khaladaadka Linux^{(Linux Error Messages)} iyo Koodhadhka^(Codes) iyo talooyinkooda cilad-raadinta. Waxaan rajeyneynaa inay kaa caawiyaan hagaajinta Khaladaadka WSL, Dhibaatooyinka^(Problems) , iyo Arrimaha^(Issues) .

Fix Windows Subsystem for Linux Errors, Problems and Issues

Like all ѕoftware, the Windows Subsystem (WSL2) too has its fаir shares of issues. In this guide, we are going to troubleshoot Windows Subsystem for Linux Error Messages and Codes.

Fix Windows Subsystem for Linux Errors, Problems & Issues

These are messages for which we are going 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 only see ‘WSL 2’ in output
6. Command Not Found
7. Error: 0x80370102 The virtual machine could not be started because a required feature is not installed
8. Error: 0x80040154 after Windows update
9. WSL Stops working with Error 0x80070003
10. Display language changing in WSL
11. Installation issues after Windows system restore
12. No internet access in WSL
13. Permission Denied when using Ping
14. Unable to boot after installing WSL 2
15. Not able to run Windows Commands inside a distributor
16. ICS is disabled
17. Bash is hung
18. OpenSSH-Server connection issues
19. The referenced assembly could not be found
20. Correct (SSH related) permission errors

Let us talk about them in detail.

1] Do not see options for WSL 2

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

To fix this, you just need to check for updates, and you will be good to go.

2] Error: 0x1bc

You may see the following error when the “Display Language” or “System Locale” is not set to English.

wsl --set-default-version 2

Error: 0x1bc

For information on key differences with WSL 2 please visit https://aka.ms/wsl2

To fix the error, you need to check if the Kernel is installed on your computer. To do that, use the following command.

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

If you don’t have Kernel, download it from aka.ms. Make sure to download it as an administrator and install the Kernel on your machine to fix the error.

3] Error: 0x80040306 on Installation

If you are seeing Error: 0x80040306 on Installation. To fix this you need to disable Legacy Console. To do that, follow the given steps.

1. Open Command Prompt as an administrator from the Start Menu.
2. Right-click on the cmd logo and select 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 access 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 do that, you can follow the given steps.

1. Launch Settings by Win + I.
2. Click Update & Security > Advanced options.
3. Use the toggle to disable “Receive updates for other Microsoft products when you update Windows“.

This will fix the issue for you.

5] Can’t start WSL 2 distribution and only see ‘WSL 2’ in output

This error is inevitable if your display language is not set to English. You will see the following output when trying to start WSL 2.

C:\Users\me>wsl

WSL 2

To fix the error, you need to download and install the Kernel manually. You can download the file from aka.ms/wsl2kernel. Install the Kernel to fix the error easily.

6] Command Not Found

This is one of the common errors one sees when they run a .exe file of Windows in Linux. You may see the following error when trying to do the same.

$ notepad.exe

-bash: notepad.exe: command not found

This happens when the $PATH fails to find the .exe file. The best solution for this error is to run the following command in the Terminal.

export PATH=$PATH:/usr/sbin

Do this and check if it fixes the error.

7] Error: 0x80370102 The virtual machine could not be started because a required feature is not installed

Many have experienced this error when trying to install a Linux distributor. Unlike previous errors, this error has more than one solution. So, buckle up and read all the solutions.

These are the things you can do to fix Error: 0x80370102, The virtual machine could not be started because a required feature is not installed.

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

Let us talk about them in detail.

Enable Hyper-V

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

1. Open Control Panel from the Start Menu.
2. Click Programs and Features > Turn Windows features on or off
3. Scroll down to find Hyper-V, check it, and click Ok.

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 facing the Error: 0x80370102, try to enable Hardware Virtualization from the BIOS to fix the issue.

Enable Nested Virtualization

Nested Virtualization allows you to run Hypervisor inside a VM. So, if you are still facing the error, try enabling Nested Virtualization. To do that, you need to run PowerShell as an administrator and run the following command.

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

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

8] Error: 0x80040154 after Windows update

You may see 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 do that, follow the given steps.

1. Launch Control from the Start Menu.
2. Click Programs and Features > Turn Windows features on or off
3. Scroll down to find Windows Subsystem for Linux, check it, and click Ok.

Finally, restart your computer and check if the issue persists.

9] WSL Stops working with Error 0x80070003

If WSL stops with this error code 0x80070003, solve 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 following command to set the display language according to your needs.

Note: The following command will change the language to en-US.

sudo update-locale LANG=en_US.UTF8

Do this and check if it fixes the issue.

11] Installation issues after Windows system restore

If you are facing Installation issues after Windows system restore, 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 check if it fixes the issue.

12] No internet access in WSL

Many users have reported 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 third-party antivirus that you may have. As the firewall blocks the Internet. So, to fix this, remove the anti-virus and you will be good to go.

13] Permission Denied when using Ping

If you are not able to Ping in WSL then this means that you don’t have administrative privilege. So, you need to run Ubuntu and Linux with administrative privilege or Bash.exe on your command line interpreter with administrative privilege.

Hopefully, this will fix the issue easily.

14] Unable to boot after installing WSL 2

The reason why you are unable to boot after installing WSL 2  is still uncanny but Microsoft is trying to work on an update to fully diagnose the issue. However, there are two things that you can do and see if it fixes the issue.

• Use System Restore 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 few distributors in Windows Store that are not completely optimized to run all Windows Commands. You may get any of the following errors.

-bash: powershell.exe: command not found

powershell.exe /c start

To fix this error, run the following command.

echo $PATH

Now, check if the output includes “/mnt/c/Windows/system32”, if you are facing the error, then most probably the path won’t be there.

Now, check your Profile settings by

cat /etc/profile

Now, check if a Path assignment starts with “#”, if it does, comment out the block. Also, check if wsl.conf is present and make sure that it doesn’t have appendWindowsPath=false. If it does, comment it out.

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

wsl -t <name of the distributor>

or

wsl --shutdown

Hopefully, the issue will be fixed.

16] ICS is disabled

A WSL can not operate without ICS or Internet Connection Sharing. The Host Network Service (HNS) uses the ICS to build a fundamental virtual network for WSL 2 to create NAT, DNS, DHCP, and host connection sharing.

To fix the error, we need to enable ICS. So, follow the given steps to enable ICS.

1. Launch Services from the Start Menu.
2. Double-click on Internet Connection Sharing (ICS), and click Start if it’s stopped.
3. Finally, click Apply > Ok.

You should also edit some policies. So, launch Group Policy Editor and navigate to the following location.

Computer Configuration > Administrative Templates > Network > Network Connections

And disable the following policies.

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

17] Bash is hung

When Bash hangs or deadlocks and stops responding to your input you can either restart your machine as that will fix the error or report a memory dump. The latter may lead to a system crash, so, save your work prior to reporting.

18] OpenSSH-Server connection issues

If you are seeing any OpenSSF-Server connection issue, the first thing you need to do is to check if the OpenSSH-Server is running. You can use the following command to do that.

sudo service ssh status

If it’s not running, use the following command to start the service.

sudo service ssh start

If it’s running, you should restart the service with the following command 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 command to stop SSH service.

sudo service ssh stop

Now, use the following command to start SSHD in debug mode.

sudo /usr/sbin/sshd -d

Hopefully, this fixes the error.

19] The referenced assembly could not be found

Many users are encountering “The referenced assembly could not be found” when they try to enable WSL additional feature. If you are one of them, try enabling Windows Subsystem for Linux from Control Panel and updating your computer. Hopefully, that will fix the error.

20] Correct (SSH related) permission errors

If you are seeing the following error, thread this section for the solution.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0777 for '/home/artur/.ssh/private-key.pem' are too open.

To fix this issue, Microsoft suggests that you go to /etc/wsl.conf file and append the following:

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

This will fix the error. Before, doing this, make 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.

Related posts

• Ku dhis LineageOS Windows 10 adoo isticmaalaya Windows Subsystem ee Linux

• Sida loo rakibo Windows Subsystem-ka Linux ee Windows 11

• Sida loo hubiyo nidaamka-hoosaadka Windows ee nooca Linux (WSL) gudaha Windows

• Hagaaji OneNote Aan shaqayn, Furin, Dhibaatooyin, Khaladaad, Arimo

• Sida loo dejiyo nooca Linux qaybinta WSL1 ama WSL2 gudaha Windows 10

• Hagaaji League of Legends Sound arrimaha

• Sida loo Hagaajiyo Windows 10 Cabbirka Muujinta iyo Arrimaha Xallinta

• Hagaaji Dhibaatooyinka Kaydka Dukumentiga Microsoft Office oo la musuqmaasuqay

• Hagaaji mugga muraayadda maqan ka dib markii dib loo rakibo Windows 11/10

• Windows 10 Dhibaatooyinka, arrimaha xalalka iyo hagaajinta

• Hagaaji koodka khaladka kaabta ee Windows 0x8078012D, Hawlgalka kaydinta ayaa fashilmay

• Hagaaji mashaakilaadka guud ee daabacadaha gudaha Windows 10

• Hagaaji Photoshop Scratch Disks waa arrin ka buuxda Windows iyo Mac

• Hagaaji qaladka qoraalka Windows 11/10

• Fix Error 1962, Looma helin nidaamka qalliinka ee kumbuyuutarrada Windows 11/10

• Windows 10 nooca 2004 arrimaha la og yahay iyo dhibaatooyinka

• Sida loo Hagaajiyo Dhibaatooyinka Muujinta Kormeeraha Kumbuyuutarka

• Hagaaji muraayadda muraayadda Amazon Firestick Arrimaha

• Hagaaji ShellExecuteEx qalad ku fashilmay Windows 11/10

• Ku hagaaji cilada Cusboonaysiinta Windows 0x800f024b gudaha Windows 10