WSL: Cannot install WSL from PowerShell

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.

If you have a feature request, please post to the UserVoice.

If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.

Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".

Please fill out the below information:

  • Your Windows build number: (Type ver at a Windows Command Prompt) Microsoft Windows [Version 10.0.17134.523]
  • What you’re doing and what’s happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.) Running as administrator

PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux Enable-WindowsOptionalFeature : The referenced assembly could not be found. At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- …
  •   + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
      + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand
    
    
    
  • What’s wrong / what should be happening instead:

I’m not able to install WSL as per instructions

  • Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).

  • For WSL launch issues, please collect detailed logs.

log creation also failing:

PS C:\WINDOWS\system32> logman.exe create trace lxcore_kernel -p {0CD1C309-0878-4515-83DB-749843B3F5C9} -mode 0x00000008 -ft 10:00 -o .\lxcore_kernel.etl -ets

logman.exe : A value that is not valid (.\lxcore_kernel.etl) was specified for the outputFormat parameter. Valid values are Text and Xml. At line:1 char:1

  • logman.exe create trace lxcore_kernel -p {0CD1C309-0878-4515-83DB-749 …
  •   + CategoryInfo          : InvalidArgument: (:) [], ParameterBindingException
      + FullyQualifiedErrorId : IncorrectValueForFormatParameter
    
    

PS C:\WINDOWS\system32> logman.exe create trace lxcore_user -p {D90B9468-67F0-5B3B-42CC-82AC81FFD960} -ft 1:00 -rt -o .
lxcore_user.etl -ets logman.exe : A value that is not valid (.\lxcore_user.etl) was specified for the outputFormat parameter. Valid values are Text and Xml. At line:1 char:1

  • logman.exe create trace lxcore_user -p {D90B9468-67F0-5B3B-42CC-82AC8 …
  •   + CategoryInfo          : InvalidArgument: (:) [], ParameterBindingException
      + FullyQualifiedErrorId : IncorrectValueForFormatParameter
    
    

PS C:\WINDOWS\system32> logman.exe create trace lxcore_service -p {B99CDB5A-039C-5046-E672-1A0DE0A40211} -ft 1:00 -rt -o .\lxcore_service.etl -ets logman.exe : A value that is not valid (.\lxcore_service.etl) was specified for the outputFormat parameter. Valid values are Text and Xml. At line:1 char:1

  • logman.exe create trace lxcore_service -p {B99CDB5A-039C-5046-E672-1A …
  •   + CategoryInfo          : InvalidArgument: (:) [], ParameterBindingException
      + FullyQualifiedErrorId : IncorrectValueForFormatParameter
    
    

See our contributing instructions for assistance.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 16 (4 by maintainers)

Most upvoted comments

Same issue, above suggestions didn’t help. powershell I’m also on Windows 10 LTSC, so the “turn windows features on or off” option won’t work for me.