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

Installation of 2.1.0 does not remove all older installed wsl packages #11049

Closed
1 of 2 tasks
janderssonse opened this issue Jan 19, 2024 · 3 comments
Closed
1 of 2 tasks
Labels

Comments

@janderssonse
Copy link

janderssonse commented Jan 19, 2024

Windows Version

Microsoft Windows [Version 10.0.19045.3930]

WSL Version

2.1.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

Ubuntu 22.04.03

Other Software

No response

Repro Steps

Having an older version of WSL installed, namely 5.10.16, https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=3a0c55a7-52db-4f8f-91bc-52683cf327cc. Install 2.1.0 with installer package or intune. Notice that 5.10.16 is still left dangling even though 2.1.0 succeded.

Expected Behavior

When installing 2.1.0 older wsl packages are removed, like in my case https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=3a0c55a7-52db-4f8f-91bc-52683cf327cc 5.10.16 update should not be left dangling.

Actual Behavior

When installing 2.1.0 older wsl packages like 5.10.16 is left dangling, which leaves an old wsl.exe under System32. This might lead to starting up ancient wsl-versions, depending on PATH-order etc. In my case wsl 2.1.0 is installed under Program Files/WSL/ which is not first in my PATH, so you can guess what happens (and with no admin rights, there is no possibilty to change PATH order either).

Diagnostic Logs

No response

Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Closed similar issues:

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

@janderssonse
Copy link
Author

janderssonse commented Jan 22, 2024

bild

The dangling old component in red. This should not be left after installation of 2.1.0 or at least be at the same updated .version . calls to wsl.exe will use this as anything "Program Files/WSL" due to being in "System32/wsl", i. e earlier in the default env PATHS. in windows.

@benhillis
Copy link
Member

The component you have circled above is the kernel for the inbox version of WSL. This will be getting removed in the future once the lifted version of WSL is available everywhere.

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

No branches or pull requests

2 participants