Skip to content

[Windows] Fix misleading WSLv1 entry in Arm64 software reports - #14444

Open
v-davit-ioramashvili wants to merge 1 commit into
actions:mainfrom
v-davit-ioramashvili:fix/14076-wsl-arm64-readme
Open

[Windows] Fix misleading WSLv1 entry in Arm64 software reports#14444
v-davit-ioramashvili wants to merge 1 commit into
actions:mainfrom
v-davit-ioramashvili:fix/14076-wsl-arm64-readme

Conversation

@v-davit-ioramashvili

Copy link
Copy Markdown
Contributor

Description

Bug fixing.

The Arm64 Windows software reports advertise Windows Subsystem for Linux (WSLv1): Enabled, but WSL is not functional on windows-11-arm: WSL2 requires nested virtualization (unavailable on Azure Arm64 VM sizes) and WSL1 is a legacy component that does not work on Arm64. This is misleading to customers.

This guards the WSLv1 line in Generate-SoftwareReport.ps1 so it is not emitted on Arm64. The generated Arm64 readmes will drop the line automatically on the next image build / readme update.

Related issue:

#14076

Check list

  • Related issue / work item is attached
  • Tests are written (if applicable)
  • Documentation is updated (if applicable)
  • Changes are tested and related VM images are successfully generated

WSL is not functional on windows-11-arm: WSL2 requires nested
virtualization (unavailable on Azure Arm64 sizes) and WSL1 is a legacy
component that does not work on Arm64. Guard the WSLv1 software-report
line on Arm64 so it is no longer advertised in the generated readmes.

Fixes actions#14076
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants