-
VersionMicrosoft Windows 10 [Version 21H2 Build 19044.2251] WSL Version
Kernel Version5.10.16 Distro VersionSUSE Tumbleweed Other SoftwareNo response Repro Steps
Expected Behavior
Actual Behavior
Diagnostic LogsNo response |
Beta Was this translation helpful? Give feedback.
Replies: 15 comments 1 reply
-
You are using a arm64 packages. Is your computer ARM ? or is it x64 ? |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
The command is |
Beta Was this translation helpful? Give feedback.
-
If I don't remove v1.0.3, I can't install v1.1.0 Also, Latest Win10 updates (continue, as v1.0.3 did) to work for me w/ v1.1.0. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I experienced exacly that behaviour. I am experiencing the same behaviour on two machines I own (Notebook and Workstation). Possibly important sidenote: |
Beta Was this translation helpful? Give feedback.
-
Maybe by forcing the upgrade / downgrade :
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 ). |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Can you provide screenshots of these commands being run and their output? If they're installing successfully there really shouldn't be any issue.
|
Beta Was this translation helpful? Give feedback.
-
Thank you @sbradnick , The windows version I've got provided by our vendor: 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: |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
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/ |
Beta Was this translation helpful? Give feedback.
-
Hi @sbradnick, 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 |
Beta Was this translation helpful? Give feedback.
-
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. 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. |
Beta Was this translation helpful? Give feedback.
-
If there is no version info with |
Beta Was this translation helpful? Give feedback.
If there is no version info with
wsl --version
after WSL package install,I recommend to install latest Cumulative update such as KB5030211 from Windows Update Catalog.
(*be careful to Windows version and machine type)
Also, you can search wsl.exe executable file in your system.
In my case, wsl package 1.2.5 version is installed in
C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wsl.exe
, but wsl.exe under System32 was not replaced.After updating KB5030211, it is replaced properly and show
wsl --version
.