Markaad rakibayso WSL , haddii aad hesho khalad adoo leh - WslRegisterDistribution waxay ku fashilantay qalad: 0x80370102^{(WslRegisterDistribution failed with error: 0x80370102)} - ka dibna boostada ayaa kaa caawin doonta inaad xalliso. Khaladku wuxuu u^(Error) dhacaa dhowr sababood. Virtualization Nsted , xadka CPUID , taageerada Virtualization , iyo in ka badan.

WslRegisterDistribution failed with error: 0x80370102.
Error: 0x80370102 The Virtual machine could not be started because a required feature is not installed

WslRegisterDistribution waxay^{(WslRegisterDistribution)} ku fashilantay qalad: 0x80370102

Raac talooyinkan si aad u xalliso dhibaatada.

• Daar ka-qaadista Virtualization-ka
• Ka yeel taageerada Hyper-V heerka BIOS^{(BIOS Level)}
• Dami xaddidaadda CPUID

Waxaad u baahan doontaa ogolaanshaha maamulka iyo fahamka BIOS si loo hirgeliyo.

Daar ka-qaadista Virtualization-ka

Haddii aad ku rakibtay Windows VM ka dibna isku day inaad ku rakibto WSL , waxaad u baahan tahay inaad karti u yeelatid qaab-dhismeedka. Ku billow PowerShell^{(Launch PowerShell)} adigoo haysta ogolaanshaha maamulka, oo fuli amarka sida hoos ku xusan.

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

Haddii tani shaqayn waydo, waxaad u baahan tahay inaad karti u geliso hab-dhaqanka heerka qalabka. Tani waxay ku xirnaan doontaa BIOS ama UEFI . Wax badan oo arrintan ku saabsan Dukumentiyada Microsoft ee rasmiga ah^{(official Microsoft Documents)} .

Ka yeel taageerada Hyper-V heerka BIOS^{(BIOS Level)}

Fur BIOS/UEFI oo hubi goobaha loo yaqaan VT-x, AMD-V, SVM, Vanderpool, Intel VT-d, ama AMD IOMMU. ^{(VT-x, AMD-V, SVM, Vanderpool, Intel VT-d, or AMD IOMMU. )}Haddii ay tahay AMD , waxaad u baahan tahay inaad hubiso AMD-V , SVM , iyo wixii la mid ah. Intel , inta badan waa VT-x .

Raac boostada ku xidhan si aad u ogaato habaynta ku salaysan kombayutarkaga. Liiska waxaa ku jira dejinta Dell , Asus , Acer , iyo wixii la mid ah.

Dami xaddidaadda CPUID

Marka aad shido kumbuyuutarka, OS-gu wuxuu fulinayaa tilmaamaha CPUID si loo ogaado processor-ka iyo awoodiisa. CPUID waxay isticmaashaa marka aad isticmaalayso processor cusub oo wata OS duug ah. Daaqadaha^(Windows) waxaa laga yaabaa inay dhibaato ka haysato maaraynta macluumaadka CPUID , markaa waxaad u baahan tahay inaad joojiso.

Meesha ay ku taal Limit CPUID Maxway kala duwanaan doontaa BIOS/UEFI kasta . Markaa iska hubi inaad hareeraha eegtid si aad u heshid meesha uu ku yaal kombayutarkaga.

Waxaan rajeynayaa in boostadu ay waxtar lahayd si loo xalliyo WslRegisterDistribution 0x80370102 , kaas oo soo baxa marka la rakibayo WSL .

La mid ah WslRegisterDistribution waxay ku fashilantay khaladaad^{(Similar WslRegisterDistribution failed with errors)} :  0xc03a001a | 0x80041002 | 0x800700b7 ama 0x80080005^{(0x800700b7 or 0x80080005)} | 0x80070422 | 0x80370114 | 0x80070003 |  0x80070032 | 0x8007023e | 0x800701bc | 0x8007019e iyo 0x8000000d^{(0x8007019e and 0x8000000d)} .

la xidhiidha: ^{(Related: )}Cilad-baadhitaan nidaam-hoosaadyada Windows-ka ee farriimaha khaladaadka Linux iyo Koodhadhka.^{(Troubleshoot Windows Subsystem for Linux Error Messages and Codes.)}

WslRegisterDistribution failed with error: 0x80370102

When installing WSL, if you receive an error saying—WslRegisterDistribution failed with error: 0x80370102—then this post will help you resolve it. The Error occurs for a couple of reasons. Nested Virtualization, a limit on the CPUID, Virtualization support, and more.

WslRegisterDistribution failed with error: 0x80370102.
Error: 0x80370102 The Virtual machine could not be started because a required feature is not installed

WslRegisterDistribution failed with error: 0x80370102

Follow these suggestions to fix the problem.

• Enable Nested Virtualization
• Enable Hyper-V support at BIOS Level
• Disable limitation on CPUID

You will need admin permission and an understanding of BIOS to implement them.

Enable Nested Virtualization

If you have installed Windows in a VM and then try to install WSL, you need to enable nested virtualization. Launch PowerShell with admin permission, and execute the command as mentioned below.

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

If this doesn’t work, you need to enable virtualization at the hardware level. This will depend on the BIOS or UEFI. More on this on the official Microsoft Documents.

Enable Hyper-V support at BIOS Level

Open the BIOS/UEFI and check for settings that may be called VT-x, AMD-V, SVM, Vanderpool, Intel VT-d, or AMD IOMMU. If it’s AMD, you need to check for AMD-V, SVM, and so on. For Intel, it is usually VT-x.

Follow the linked post to find out settings according to your computer. The list includes settings for Dell, Asus, Acer, and so on.

Disable limitation on CPUID

When you turn on your computer, the OS executes CPUID instruction to determine the processor and its capabilities. CPUID uses when you are using a new processor with an old OS. Windows may have issues handling the CPUID information, and hence you need to disable it.

The location of Limit CPUID Max will vary for each BIOS/UEFI. So make sure to look around to find where it has on your computer.

I hope the post was helpful to resolve the WslRegisterDistribution 0x80370102, which appears when installing WSL.

Similar WslRegisterDistribution failed with errors: 0xc03a001a | 0x80041002 | 0x800700b7 or 0x80080005 | 0x80070422 | 0x80370114 | 0x80070003 |  0x80070032 | 0x8007023e | 0x800701bc | 0x8007019e and 0x8000000d.

Related: Troubleshoot Windows Subsystem for Linux Error Messages and Codes.

Related posts

• WslRegisterDistribution waxay ku fashilantay qalad: 0x80370114

• WslRegisterDistribution waxay ku fashilantay cilad 0x8007023e

• WslRegisterDistribution waxay ku fashilantay qalad 0x8007019e ama 0x8000000d

• WslRegisterDistribution waxay ku fashilantay qalad: 0x800701bc

• WslRegisterDistribution waxay ku fashilantay qalad: 0x80070422

• Hagaaji WslRegisterDistribution waxay ku fashilantay cilad 0x80070032

• Sida loo socodsiiyo faylka .sh ama Shell Script gudaha Windows 11/10

• WslRegisterDistribution waxay ku fashilantay cilad 0x800700b7 ama 0x80080005

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

• Hagaaji nidaamka-hoosaadka Windows-ka ee khaladaadka Linux, dhibaatooyinka iyo arrimaha

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

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

• WslRegisterDistribution waxay ku fashilantay cilad 0xc03a001a

• WslRegisterDistribution waxay ku fashilantay qalad: 0x80041002

• WSL waxay joojisay ku shaqaynta Khaladka 0x80070003

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