Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install fails with 0x800f080c and I can't enable requried Windows features. #12516

Open
2 tasks
DomatesGames opened this issue Jan 29, 2025 · 10 comments
Open
2 tasks

Comments

@DomatesGames
Copy link

DomatesGames commented Jan 29, 2025

Windows Version

10.0.19045.5371

WSL Version

wsl.exe --version doesn't work. CMD says me "Usage: wsl.exe [Argument]..."

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

Ubuntu 24.01.1 (please look at Step 6, Repro Steps)

Other Software

No response

Repro Steps

Developer options is enable. I ran Powershell as an Administrator. I ran CMD as an Administrator. I am using Windows Home Single Language. I tried dism /online /cleanup-image /restorehealth and sfc /scannow. They don't work and I tried chkdsk c: /f then they worked.

1. Install WSL via PowerShell: wsl --install
2. Enabling WSL feature via GUI.
3. Enabling WSL feature via Command Prompt: dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
4. Enabling Virtual Machine Platform feature via GUI.
5. Enabling Virtual Machine Platform feature via Command Prompt: dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
6. I installed Ubuntu 24.04.1 with Microsoft Store but I can't run it.

Expected Behavior

1. I would wait for the WSL to be installed.
2. Selecting Windows Subsystem for Linux in Windows features settings and enable it.
3. (This is not mine PS I found it from Internet.)
Image
4. Selecting Virtual Machine Platform in Windows features settings and enable it.
5. (This is not mine PS I found it from Internet.)
Image
6. I expected to run it.

Actual Behavior

1.

PS C:\Windows\system32> wsl --install
Error: 0x800f080c

2.
WSL doesn't appear on "Turn Windows Features on or off" setting.
Image

3.

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

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.5371

Error: 0x800f080c

Feature name Microsoft-Windows-Subsystem-Linux is unknown.
A Windows feature name was not recognized.
Use the /Get-Features option to find the name of the feature in the image and try the command again.

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

4. Setting doesn't appear.
Image

5.

Image

6.

Image
"Linux için Windows Alt Sistemi etkinleştirilmedi." means "The Windows Subsystem for Linux has not been enabled. "

Diagnostic Logs

For ease of review, I deleted the old log and tried the steps again. These are new logs:

dism.log after run Step 3:
dism.log

dism.log after run Step 5:
dism.log

Old log:
dism1.log

Powershell error about WSL logs:
PS C:\Windows\system32> Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
PS C:\Windows\system32> Set-ExecutionPolicy Bypass -Scope Process -Force
PS C:\Windows\system32> .\collect-wsl-logs.ps1
Get-WindowsOptionalFeature : Get-WindowsOptionalFeature failed. Error code = 0x800f0819
At C:\Windows\system32\collect-wsl-logs.ps1:57 char:1

  • Get-WindowsOptionalFeature -Online > $folder/optional-components.txt
  •   + CategoryInfo          : NotSpecified: (:) [Get-WindowsOptionalFeature], COMException
      + FullyQualifiedErrorId : Microsoft.Dism.Commands.GetWindowsOptionalFeatureCommand
    
    

Log collection is running. Please reproduce the problem and once done press any key to save the logs.
Saving logs...
Logs saved in: C:\Windows\system32\WslLogs-2025-01-29_13-16-03.zip. Please attach that file to the GitHub issue.

WSL logs:
WslLogs-2025-01-29_13-16-03.zip
Bot says this log is wrong. I tried it again and PS created a new file:
collect-wsl-logs.zip

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
Issue was edited and new log file was found: https://github.com/user-attachments/files/18585965/WslLogs-2025-01-29_13-16-03.zip
Appx package is not installed
Found no WSL traces in the logs

Copy link

Failed to parse logs. Unexpected file: collect-wsl-logs.ps1
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
Issue was edited and new log file was found: https://github.com/user-attachments/files/18586056/collect-wsl-logs.zip
Found no WSL traces in the logs

@DomatesGames
Copy link
Author

Failed to parse logs. Unexpected file: collect-wsl-logs.ps1 The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

I ran the command PS said nothing?
Image

Only file I found is this.

@DomatesGames
Copy link
Author

I closed it by mistake.

@OneBlue
Copy link
Collaborator

OneBlue commented Jan 29, 2025

Thank you for reporting this @DomatesGames. I don't see anything in the logs, could you run the log collection while you get the wsl --install error ?

@DomatesGames
Copy link
Author

Powershell does not respond to the command. collect-wsl-logs.ps1 file is created in System32.
collect-wsl-logs.zip
Am I doing it right?

Copy link

Failed to parse logs. Unexpected file: collect-wsl-logs.ps1
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
Found no WSL traces in the logs

@OneBlue
Copy link
Collaborator

OneBlue commented Jan 30, 2025

Unfortunately not. Do these instructions work /logs ?

Copy link
Contributor

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants