Post command line installation ASCII in cmd atop PowerShell 7.5.0 via Windows Terminal

[MikeFarrington]

This is probably just a minor visual glitch with post-installationt status information, but I figured I'd pass it along anyway.

I just performed a wsl --install' in a Windows Terminal that had been launched as PowerShell 7.5.0, but had launched cmdwithin it before doing thewsl --install`. For an extra variable, this is also on Windows on ARM (24H2) in VM on Apple silicon.

I'm guessing the installation incorrectly assumed it was running under PowerShell when it was actually running within a cmd prompt within PowerShell, and thus it tried displaying visually interesting information that cmd couldn't handle.

A whole lot of appears to me to be ASCII terminal codes got spit out at the end of the installation.

[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://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 [email protected] 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'.

[MikeFarrington]

I was unaware that nested virtualization isn't currently supported on Windows on ARM, so this was a fruitless exercise on my part. Oh well. It seems like the WSL installer should have mentioned something about that (perhaps that was the ASCII I couldn't read).

[zcobol]

@MikeFarrington indeed nested virtualization is not supported on (some) ARM processors. I'm using a DevKit 2023.

However, the WSL team could add a warning message to WSL Settings app:

The warning show only when launching a WSL instance:

wsl: Nested virtualization is not supported on this machine.