WSL not updated to 1.1.0

[thucke]

Version

Microsoft Windows 10 [Version 21H2 Build 19044.2251]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.10.16

Distro Version

SUSE Tumbleweed

Other Software

No response

Repro Steps

• Without access to Microsoft Store MSI-Package has been downloaded from Github.
• Install in Powershell Admin-Box: Add-AppPackage -Path ".\Microsoft.WSL_1.1.0.0_x64_ARM64.msixbundle"

Expected Behavior

• wsl --version shows detailed version info
• Kernel is updated to version v5.15.83
• systemd is operating after is has been activated in wsl.conf

Actual Behavior

• wsl --version shows help page
• wsl --status still shows "Kernel-Version: 5.10.16"
• systemd in distro still doesn't work (wsl.conf has been already updated)

Diagnostic Logs

No response

[olivierchatry]

You are using a arm64 packages. Is your computer ARM ? or is it x64 ?

[sbradnick]

You are using a arm64 packages. Is your computer ARM ? or is it x64 ?

That's a .msixbundle, so it contains both and will install the appropriate one.

In my experience, if you currently have one version installed and try to install an update - it fails until you remove the old version ~ are you sure that's not happening here?

There are also pre-requisites for it to work in Win10, not sure if you've met them.

[elsaco]

The command is Add-AppxPackage not Add-AppPackage

[sbradnick]

If I don't remove v1.0.3, I can't install v1.1.0

Also, wsl --status & wsl --version should return results vs. a dump of wsl --help if things are updated correctly.

Latest Win10 updates (continue, as v1.0.3 did) to work for me w/ v1.1.0.

[thucke]

The command is Add-AppxPackage not Add-AppPackage
Sorry - it was a typo - I useed the correct statement.

[thucke]

If I don't remove v1.0.3, I can't install v1.1.0

Also, wsl --status & wsl --version should return results vs. a dump of wsl --help if things are updated correctly.

Latest Win10 updates (continue, as v1.0.3 did) to work for me w/ v1.1.0.

I experienced exacly that behaviour.
That's why I also deinstalled v1.0.3 incl. reboot before I installed v1.1.0.

I am experiencing the same behaviour on two machines I own (Notebook and Workstation).

Possibly important sidenote:
Both systems are managed by a foreign vendor of my company who disallowed direct access to MS Store.
That's why I need to install the appx-package.
Maybe there are addidinal GPO set which could influence the behaviour of the WSL installation?

[olivierchatry]

Maybe by forcing the upgrade / downgrade :

 Add-AppxPackage -Path .\Microsoft.WSL_1.1.0.0_x64_ARM64.msixbundle -ForceUpdateFromAnyVersion  -ForceApplicationShutdown

Between, be careful with 1.1.0, there is a nasty issue with localhost networking. ( so might be better to wait for a new version ).

[thucke]

Maybe by forcing the upgrade / downgrade :

 Add-AppxPackage -Path .\Microsoft.WSL_1.1.0.0_x64_ARM64.msixbundle -ForceUpdateFromAnyVersion  -ForceApplicationShutdown

Between, be careful with 1.1.0, there is a nasty issue with localhost networking. ( so might be better to wait for a new version ).
Thank you Olivier Chatry (@olivierchatry) ,
I meant that I've already tried both Force-Options but I tried it again.
Unfortunately also without any change even after reboot.

[sbradnick]

Can you provide screenshots of these commands being run and their output? If they're installing successfully there really shouldn't be any issue.

• Can you update Win10 to 22H2?
• What's the output of wsl --status / wsl --version (esp. if v1.0.3 || v1.1.0 install successfully)?
• I'm not sure how you listed 5.10.16[.3] kernel in use for WSL, is that a typo? It's not that that kernel wasn't ever in use, but I'm not sure it's tied to any modern-ish WSL release.

[thucke]

Thank you Scott Bradnick (@sbradnick) ,
first - here are screenshots of the commands you asked for:

The windows version I've got provided by our vendor:

Unfortunately it is not possible to update to 22H2 on my own.

It seems that the package has been installed correctly:

but it seems also that the installed files were not set active - I see only onld version of the exe in system path:

and the new W10 version is not compatible yet:

[thucke]

Update:
After going deeping into analyzing prerequisites I've installed kb5020030 following removment and reinstallation now of WSL 1.0.3.
Unfortunately without any change in behaviour.

Calling WSL.EXE as admin results in an error;

Calling it as a regular user output is as usual.
Especially wsl --version still shown the help page.

[sbradnick]

It really seems like you have some remnant of a previous install hanging around (I'm also curious what you have for "Windows Features"). Additionally, if you're "stuck" on a Win10 release < 22H2, these new releases apparently aren't going to work at all. I've progressively updated mine as they came out, being sure I was on the latest Windows release before installing them; I know that's not a possibility for everyone all the time.

I'd suggest REMOVING anything installed already (and doing what you can to verify it's gone), then going to https://github.com/microsoft/wsl/releases and grabbing ones that are <= v1.0.0 and see if any of them behave, > 1.0.0 doesn't seem like a possibility for Win10 21H2. I'm wondering if that (seemingly) old kernel version comes from some 21H2-esque WSL release and you've been attempting installs from github that just aren't compatible w/ Win10 21H2.

But in reality, the biggest roadblock for you seems to be a lack of 22H2 - since I have no issues w/ wsl --status or wsl --version or TW in general w/ systemd enabled on an up-to-date Win10 install. And I wouldn't run any WSL commands myself as Admin, shouldn't be necessary or a good compare point.

[thucke]

Hi Scott Bradnick (@sbradnick),
interesting output trying to install an older version after cleaning up:

It seems that we have to figure out what which KB-Patches have to be installed to get at least W10 version 10.0.22000.0

[thucke]

I had success installing version 0.70.0.0 and 0.70.8.0 but still without a change of kernel version and wsl.exe options.
Both installations wre launched using "-ForceUpdateFromAnyVersion -ForceApplicationShutdown".
I'm running out of ideas.

I cannot find information to the error referenced windows version. According to https://support.microsoft.com/en-us/topic/january-19-2023-kb5019275-os-builds-19042-2546-19044-2546-and-19045-2546-preview-8ae1b678-d38c-4249-848d-06b722e7c0ad the latest 22H2 build is 19044.2546. Numbers starting with 22xxxx seem do identify windows 11 builds.