Windows 10: Unable to enable WSL

Hi,


I'm trying to enable WSL on my Laptop using following documentation:

https://docs.microsoft.com/en-us/windows/wsl/install-win10


when I enter the command cmd admin mode:


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



Deployment Image Servicing and Management tool

Version: 10.0.17763.771



Image Version: 10.0.17763.1158



Enabling features

[==========================100.0%==========================]



Error: 14081



The referenced assembly could not be found.



The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log



When I try to enable the feature trough the GUI I get the same error message.


In tthe logs I can see following errors:



2020-05-30 21:03:58, Info DISM DISM Package Manager: PID=3028 TID=5568 Initiating Changes on Package with values: 5, 7 - CDISMPackage::Internal_ChangePackageState
2020-05-30 21:03:58, Info DISM DISM Package Manager: PID=3028 TID=5568 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2020-05-30 21:03:59, Info DISM DISM Package Manager: PID=3028 TID=6260 Error in operation: null CBS HRESULT=0x80073701 - CCbsConUIHandler::Error
2020-05-30 21:03:59, Error DISM DISM Package Manager: PID=3028 TID=5568 Failed finalizing changes. - CDISMPackageManager::Internal_Finalizehr:0x80073701
2020-05-30 21:03:59, Error DISM DISM Package Manager: PID=3028 TID=5568 Failed processing package changes with session options - CDISMPackageManager:rocessChangesWithOptionshr:0x80073701
2020-05-30 21:03:59, Error DISM DISM Package Manager: PID=3028 TID=5568 Failed ProcessChanges. - CPackageManagerCLIHandler:rivate_ProcessFeatureChangehr:0x80073701
2020-05-30 21:03:59, Error DISM DISM Package Manager: PID=3028 TID=5568 Failed while processing command enable-feature. - CPackageManagerCLIHandler::ExecuteCmdLinehr:0x80073701
2020-05-30 21:03:59, Info DISM DISM Package Manager: PID=3028 TID=5568 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2020-05-30 21:03:59, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80073701
2020-05-30 21:03:59, Info DISM DISM Provider Store: PID=3028 TID=6260 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-30 21:03:59, Info DISM DISM Provider Store: PID=3028 TID=6260 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-30 21:03:59, Info DISM DISM Provider Store: PID=3028 TID=6260 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2020-05-30 21:03:59, Info DISM DISM Provider Store: PID=3028 TID=6260 Finalizing the servicing providerDISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider


WIN 10, version 1809 OS Build 1763.1158


I tried to run: DISM.exe /Online /Cleanup-image /Restorehealth But the issue remained.


Did anybody experience this problem or know how to fix this?


Thanks

:)

 

0x8000000d Ubuntu installation fails with error 0x8000000d installed using the Microsoft Store application with WSL enabled

Although WSL was already enabled and I had rebooted, I also received this error when trying to run Ubuntu for the first time. I resolved it by running the enable step again. Open PowerShell as Administrator, and run:

 

WSL unable to perform DNS lookup

Hi my name is Ross, I'm an independent advisor. I'd be happy to help with your issue.

Try following the steps in this article (Section - Bash loses network connectivity once connected to a VPN) to modify your resolv.conf file and manually add your correct DNS settings.

If you don't know the correct settings then you can just use 1.1.1.1 or 8.8.8.8

https://docs.microsoft.com/en-us/windows/wsl/tr...

Regards,

Ross

 

WSL in windows Store

Actually, this is a consumer-oriented forum for general Windows 10 questions.

As WSL concerns mostly developers and Enterprise, I suggest asking there.