Skip to content

Saitin WSL ​

Kafin amfani da WSL Dashboard, dole ne tsarin Windows ɗin ku ya kunna kuma ya saita WSL 2 daidai. Wannan takaddar ta ƙunshi manyan sassa uku:

  1. Kunna da saitawa WSL: Kammala shigarwa da saitawa na asali na WSL 2.
  2. Nassi na umarni ba ya nufin nasarar shigarwa: Yana bayyana cewa aiwatar da umarnin wsl ba ya nufin za a iya shigar da Linux cikin nasara.
  3. Binciken gazawar shigarwa: Hanyoyin bincike da gyara idan shigarwa ta ci tura bayan kammala saitawa.

1. Kunna da saitawa WSL ​

Wannan sashe zai jagorance ku don kammala muhimman saitunan asali. Bayan kammala wannan sashe, karanta sashi na 2 don fahimtar bambanci tsakanin samun umarni da nasarar shigarwa; idan har yanzu akwai matsala wajen shigarwa, duba sashi na 3.

1.1 Duba buƙatun tsari ​

WSL 2 yana da mafi ƙarancin buƙatu kan sigar Windows. Latsa Win + R, shigar da winver don duba sigar ku:

  • Windows 10: Siga 1903 ko daga baya, kuma Build ya kamata ya kasance 18362 ko sama da haka.
  • Windows 11: Ana tallafawa duk sigogi.

IMPORTANT

Idan sigar ku ta yi ƙanƙanta, da farko sabunta tsarin ku ta hanyar "Windows Update".

1.2 Kunna ƙirƙirar kayan aiki na hardware ​

WSL 2 yana aiki bisa fasahar ƙirƙirar kayan aiki (virtualization), don haka dole ne a kunna Ƙirƙirar Kayan Aiki (Virtualization Technology) a cikin BIOS/UEFI na motherboard.

  • Hanyar dubawa: Buɗe "Task Manager" → shafin "Performance" → "CPU".
  • Duba matsayi: Tabbatar cewa matsayin "Virtualization" a kusurwar dama ƙasa ya nuna "An kunna".
  • Hanyar kunnawa: Idan ba a kunna ba, sake kunna kwamfutar ku don shiga saitunan BIOS/UEFI, nemo zaɓi mai kama da Intel VT-x ko AMD-V kuma saita shi zuwa Enabled.

1.3 Kunna fasalolin Windows ​

Kuna buƙatar kunna fasalolin "Windows Subsystem for Linux" da "Virtual Machine Platform" na Windows.

Hanyar A: Ta hanyar GUI (ana ba da shawarar) ​

  1. Latsa Win + S, bincika kuma buɗe "Turn Windows features on or off".
  2. Yi alama a kan waɗannan abubuwa biyu:
    • Windows Subsystem for Linux
    • Virtual Machine Platform
  3. Danna "OK", kuma sake kunna kwamfuta idan an sa ku.

Hanyar B: Ta hanyar layin umarni (gudanarwa) ​

Gudanar da PowerShell a matsayin gudanarwa (Administrator) kuma aiwatar da waɗannan umarnin:

powershell
# Enable WSL
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

# Enable Virtual Machine Platform
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Bayan kammalawa, da hannu sake kunna kwamfutar ku.

1.4 Shigarwa / sabunta kernel na WSL ​

Sifofin Windows na zamani na iya samun sabuntawar WSL ta hanyar Microsoft Store.

1.5 Saita WSL 2 azaman sigar tsoho ​

Don tabbatar da cewa sabbin rarrabawa (distributions) da aka shigar suna amfani da WSL 2 azaman tsoho, aiwatar da wannan a cikin terminal ɗin ku:

powershell
wsl --set-default-version 2

1.6 Tambayoyi da yawa ​

  • Kuskure 0x80370102: Yawanci saboda ba a kunna ƙirƙirar kayan aiki a BIOS ba, ko kuma akwai rikici da Hyper-V.
  • Canjawa tsakanin WSL 1 da WSL 2: Kuna iya amfani da wsl --set-version <sunan-rarrabawa> 2 don ɗaukaka WSL 1 ɗin ku zuwa WSL 2.

2. Nassi na umarni ba ya nufin nasarar shigarwa ​

Umurnin kamar wsl --version, wsl -l -v na iya aiwatarwa da kyau, amma bai nufi cewa an riga an sami yanayin shigar da Linux ba. Su biyun suna cikin matakai daban-daban, ba za a iya daidaita su ba.

Samun umarni yana nufin kawai:

  • ✅ An riga an kunna/an shigar da ɓangarorin WSL a Windows
  • ✅ Kayan aikin layin umarni wsl.exe yana samuwa
  • ✅ Tsarin na iya gane umarnin da suka shafi WSL

Amma don shigar da rarrabawar Linux cikin nasara, akwai ƙarin sharuɗɗa. Matsalolin da suka fi yawan kamawa sune:

  1. Ƙirƙirar kayan aiki an rufe ta: Ba a kunna VT-x / AMD-V a BIOS/UEFI ba, WSL 2 ba zai iya farawa ba, ko kuma ya ba da rahoton kuskuren ƙirƙirar kayan aiki yayin shigar da rarrabawa (duba 1.2 Kunna ƙirƙirar kayan aiki na hardware).
  2. Sigar Windows / Build ɗin ta yi ƙanƙanta: WSL 2 yana da buƙatu kan kernel da sigar; sigar gida (Home), hotunan kamfani (enterprise images) da suka tsufa suna iya rasa wasu fasaloli (duba 1.1 Duba buƙatun tsari).
  3. Ba a riga an shigar da rarrabawar Linux ba: wsl -l -v yana lissafa rarrabawar da aka shigar kawai; idan ba a shigar da komai ba, jerin zai kasance fanko, wanda baya nufin za ku iya gudanar da Ubuntu kai tsaye ba.
  4. Matsalar hanyar sadarwa / Microsoft Store: wsl --install -d <rarrabawa> yana buƙatar saukar hoto daga shagon ko hanyar sadarwa; hanyar sadarwar kamfani, proxy, ko firewall na iya toshe shi.
  5. Rashin izini: Shigar da rarrabawa ko gyara saitunan WSL yana buƙatar izinin gudanarwa (Administrator).

TIP

A taƙaice: iyan amfani da umarnin WSL baya nufin Linux a shirye, kuna da "tikiti na shiga" kawai, ba a shigar da tsarin da gaske ba.

3. Binciken gazawar shigarwa ​

Bayan kammala saitawa bisa sashi na 1 (ko kuna ganin kun kammala), idan aiwatar da wsl --install har yanzu ya ci tura, duba kamar haka a jere.

3.1 Gwajin danni ɗaya ​

Gudanar da PowerShell a matsayin gudanarwa (Administrator), aiwatar da:

powershell
wsl --install --no-distribution
wsl --set-default-version 2
  • ✅ Idan duka waɗannan umarnin biyu suka aiwata cikin nasara, yana nufin an kunna zaɓaɓɓun ɓangarorin WSL, kuma yanayin ƙirƙirar kayan aiki ya cika.
  • ❌ Idan ya ci tura, zai nuna abin da ya ɓace kai tsaye (kamar Virtual Machine Platform, Hyper-V, ƙirƙirar kayan aiki a BIOS, da sauransu).

Sa'an nan aiwatar da systeminfo, tabbatar da cewa a cikin fitarwa akwai Virtualization Enabled In Firmware: Yes. Idan babu wani kuskure a sama, za ku iya aminci aiwatar da wsl --install don shigar da rarrabawa.

NOTE

Babu wani umarni da zai iya ba da tabbacin 100% cewa wsl --install zai yi nasara, amma gwaje-gwajen da ke sama na iya tabbatar da ko sharuɗɗan shigarwa sun cika.

3.2 Jerin dubawa na hannu ​

Idan "gwajin danni ɗaya" har yanzu bai gano matsalar ba, duba kowane abu:

  1. Duba ko an kunna ƙirƙirar kayan aiki a BIOS/firmware: A cikin PowerShell na gudanarwa aiwatar da systeminfo, a cikin fitarwa dole ne a ga Virtualization Enabled In Firmware: Yes.
  2. Duba ko an kunna fasalolin Windows:
    powershell
    Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
    Get-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform
    Matsayin duka umarnin biyu ya kamata ya kasance Enabled.
  3. Duba ko WSL yana samuwa: Aiwatar da wsl --version ya kamata ya ba da fitarwa mai kyau; idan ya ce umarnin ba ya nan, yana nufin ba a shigar da ɓangarorin WSL ba, koma zuwa sashi na 1.
  4. Duba ko za a iya amfani da WSL 2 (kernel & Virtual Machine Platform): Aiwatar da wsl --set-default-version 2 ya kamata ya dawo cikin nasara. Abubuwan da suka fi yawan haifar da gazawa: ba a kunna Virtual Machine Platform ba, ko ba a kunna VT-x / AMD-V a BIOS ba.

3.3 Dalilan gazawar gama gari ​

YanayiBayaniHanyar magance
Ba a kunna ƙirƙirar kayan aiki a BIOS baTabbas zai ci turaSake kunna shiga BIOS don kunna VT-x / AMD-V (duba 1.2)
Windows 10 ƙasa da 19041Ba ya goyan bayan wsl --installSabunta tsarin (duba 1.1)
An hana Hyper-V / ƙirƙirar kayan aiki a muhallin kamfaniYana iya ci turaTuntuɓi mai gudanar da tsarin
Tsohuwar sigar gidaAna buƙatar shigarwa da hannuShigar da kernel na WSL da hannu bisa 1.4

3.4 Kuskure 0xc03a0014: Ba a sami mai tallafin faifan virtual ba ​

Saƙon kuskure: Cannot find a virtual disk support provider for the specified file. Wannan ba matsalar rarrabawar Linux ɗin kanta ba, amma tsarin faifan VHD/VHDX na Windows baya aiki da kyau, WSL 2 ya kasa yin rijistar rarrabawa, ƙirƙirar/ɗora ext4.vhdx.

Da farko yi ƙaramin gwaji: Gudanar da PowerShell a matsayin gudanarwa, aiwatar da gwajin New-VHD (misali New-VHD -Path C:\test.vhdx -SizeBytes 1GB). Idan wannan umurnin ma ya ba da rahoton wannan kuskuren, matsalar 100% tana gefen Windows, ba ta da alaƙa da rarrabawar.

Duba da gyara a jere:

  1. Sabis na Virtual Disk bai gudana ba: Buɗe services.msc, nemo sabis na Virtual Disk, saita nau'in farawa zuwa "Automatic" kuma fara shi.

  2. Fasalolin WSL / Virtual Machine Platform ba a kunna su ba (ko ba su yi tasiri ba): Sake aiwatar da umarnin a cikin 1.3 Kunna fasalolin Windows, sa'an nan dole ne ku sake kunna kwamfuta. Windows Home ba shi da cikakken Hyper-V, amma WSL 2 yana buƙatar Virtual Machine Platform kawai, ba wajen gudanarwar Hyper-V ba.

  3. Rashin direban/na'urar faifan virtual: Buɗe Device Manager, duba ko akwai a cikin "System devices / Storage controllers":

    • Microsoft Virtual Disk Provider
    • Microsoft Virtual Drive Enumerator
    • Microsoft VHD Loopback Controller

    Idan sun ɓace, za ku iya ƙara su da hannu ta hanyar hdwwiz.exe (Storage controllers → Microsoft → Microsoft VHD Loopback Controller), kuma tabbatar ba a kashe sabis na FsDepends ba.

  4. Hoton da aka shigo da shi bai dace da buƙatun WSL ba: Lokacin amfani da wsl --import --vhd, VHDX dole ne ya kasance tsarin fayil na ext4, ba faifan LUKS da aka ɓoye ba, ba raw.img na yau da kullun ba, ba Live ISO ko faifan fanko da aka tsara da NTFS/FAT ba. .img / .qcow2 / .iso ba za a iya shigo da su kai tsaye ta wsl --import --vhd ba.

  5. Matsalar hanya/izini/tsarin fayil: Dole ne kundayen da aka zaɓa ya kasance akan faifan NTFS (FAT32/exFAT ba su yi ba); guje wa harshen Sinanci, sarari da alamomi na musamman a cikin hanya; kar a shigo da su daga faifan cibiyar sadarwa, OneDrive, ko kundayen da aka matse; tabbatar da amfani da PowerShell na gudanarwa na gaskiya (ba wani tasha na yau da kullun ba).

  6. Lalacewar ɓangarorin tsarin: Gudanar da DISM da SFC a jere don gyara ɓangarorin tsarin, sa'an nan sake gwadawa:

    powershell
    DISM.exe /Online /Cleanup-Image /RestoreHealth
    sfc /scannow

TIP

Ƙwayoyin kwamfuta na ɓangare na uku (VirtualBox, VMware) ko ayyukan sandbox/karɓar kariya na software na tsaro (kamar 360, Huorong) na iya tsoma baki a aikin faifan virtual, ana iya kashe su na ɗan lokaci yayin bincike.