"Installation package is not supported by this processor type" error when running wsl --update

pdrgnclvs commented 2 years ago

Version

Microsoft Windows [Version 10.0.19044.1620]

WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version

5.10.60.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

Simply check for updates
Windows Update reports an update for Windows Subsystem for Linux (kernel 5.10.93.2)

Expected Behavior

The installation should go smoothly (I don't think it would pose a problem)

Actual Behavior

The installation halts with error 0x80070661, and doing wsl --update through Command Line as a workaround yields the "Installation package is not supported by this processor type" message

Diagnostic Logs

No response

yu-shiba commented 2 years ago

I am facing the same problem. My environment is Intel but it seems to be trying to apply the arm64 update.

huohaodong commented 2 years ago

I have encountered the same problem when am tring to update WSL on my ryzen laptop. (AMD 5800H cpu).

danny-burrows commented 2 years ago

I also have the same issue attemping the update on an intel processor running Windows 11

ravik694 commented 2 years ago

Seeing the same issue on my own system running Windows 11 Pro.

Version

cmd.exe /c ver
Microsoft Windows [Version 10.0.22000.556]

WSL Version

wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Stopped         2

Kernel Version

wsl.exe --status
Default Distribution: Ubuntu
Default Version: 2

Windows Subsystem for Linux was last updated on 2022-03-11
WSL automatic updates are on.

Kernel version: 5.10.60.1

Repro Steps

Run wsl --update as admin in Windows Terminal.

Expected Behavior

WSL is upgraded to the newest version. Currently this is 5.10.93.2 according to Windows Update.

Actual Behavior

 wsl --update
Checking for updates...
Downloading updates...
Installing updates...
This installation package is not supported by this processor type. Contact your product vendor.

Diagnostic Logs

Generated via steps at https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md

<feedback-hub:?contextid=677&feedbackid=6ab58987-e18e-4812-84c0-ccc6eb8a8cc3&form=1&src=1>

wmic cpu get name
Name
12th Gen Intel(R) Core(TM) i7-12800H

systeminfo

Host Name:                <redacted>
OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22000 N/A Build 22000
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          <redacted>
Registered Organization:   Razer
Product ID:                00330-80000-00000-AA292
Original Install Date:     2022-03-09, 21:20:09
System Boot Time:          2022-03-24, 18:13:06
System Manufacturer:       Razer
System Model:              Blade 15 (2022) - RZ09-0421
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 154 Stepping 3 GenuineIntel ~2400 Mhz
BIOS Version:              Razer 1.08, 2022-02-16
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume2
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 <redacted>
Total Physical Memory:     16,067 MB
Available Physical Memory: 9,574 MB
Virtual Memory: Max Size:  21,187 MB
Virtual Memory: Available: 12,012 MB
Virtual Memory: In Use:    9,175 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    WORKGROUP
Logon Server:             <redacted>
Hotfix(s):                 4 Hotfix(s) Installed.
                           [01]: KB5010474
                           [02]: KB5010690
                           [03]: KB5011493
                           [04]: KB5009641
Network Card(s):           2 NIC(s) Installed.
                           [01]: Intel(R) I210 Gigabit Network Connection
                                 Connection Name: Ethernet
                                 Status:          Hardware not present
                           [02]: Bluetooth Device (Personal Area Network)
                                 Connection Name: Bluetooth Network Connection
                                 Status:          Media disconnected
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

NoahELE commented 2 years ago

got the same problem with my intel processor laptop with Windows 11

Garphy commented 2 years ago

same err this morning... windows update fail 0x80070661

elsaco commented 2 years ago

Here's a quick workaround:

download latest WSL2 release from https://github.com/microsoft/WSL/releases/download/0.56.2/Microsoft.WSL_0.56.2.0_x64_ARM64.msixbundle
rename file to Microsoft.WSL_0.56.2.0_x64_ARM64.zip
run Expand-Archive Microsoft.WSL_0.56.2.0_x64_ARM64.zip
change into Microsoft.WSL_0.56.2.0_x64_ARM64 folder
run Add-AppPackage Microsoft.WSL_0.56.2.0_x64.msix - thanks @joeloguete
run wsl --status to check the upgrade

It should show WSL version: 0.56.2.0 This workaround ...worked on my Win11 notebook!

When running wsl --update it should output The most recent version of Windows Subsystem for Linux is already installed

kahennig commented 2 years ago

Same here... wsl is working fine but the update package fails to install. It fails both trying to update via Windows Update as well as with: wsl --update this is what it looks like:

❯ wsl --update Checking for updates... Downloading updates... Installing updates... This installation package is not supported by this processor type. Contact your product vendor.

and on windows update:

Screenshot 2022-03-24 224605

4x0v7 commented 2 years ago

Also experiencing this: Win 10 19044.1586 Intel Core i7 1165G7

joeloguete commented 2 years ago

run Add-AppPackage Microsoft.WSL_0.56.2.0_x64.misx should be run Add-AppPackage Microsoft.WSL_0.56.2.0_x64.msix

jackgallivan commented 2 years ago

I had the same issue. After I updated Windows to release 22581.1 (Beta Insider channel), the WSL kernel update disappeared from windows update, but "wsl --update" worked again and updated WSL from 5.10.60.1 to 5.10.102.1.

pcbeard commented 2 years ago

I installed the workaround, and wsl --update does tell me that I have the latest. However, Windows update is still showing the error Install error - 0x80070661. I'm hoping this will get fixed on the Microsoft side.

shubhamsethi97 commented 2 years ago

Facing the same issue with my Intel processor laptop with Windows 10.

yongzhang commented 2 years ago

same issue happens today

PS C:\Windows\system32> wsl --update
Checking for updates...
Downloading updates...
Installing updates...
This installation package is not supported by this processor type. Contact your product vendor.

$ uname -r
5.10.16.3-microsoft-standard-WSL2

Processor   Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz   2.60 GHz
Installed RAM   16.0 GB (15.9 GB usable)
System type 64-bit operating system, x64-based processor

Edition Windows 10 Pro
Version 21H2
Installed on    ‎11/‎12/‎2020
OS build    19044.1620
Experience  Windows Feature Experience Pack 120.2212.4170.0

erbanku commented 2 years ago

Same here... wsl is working fine but the update package fails to install. It fails both trying to update via Windows Update as well as with: wsl --update this is what it looks like:

❯ wsl --update Checking for updates... Downloading updates... Installing updates... This installation package is not supported by this processor type. Contact your product vendor.

and on windows update:

Same here.

markstachowski commented 2 years ago

I see the same errors and waiting for a fix.

d2kx commented 2 years ago

Same here. Windows Update error, Windows 11 Stable, Surface Laptop Studio.

aguther commented 2 years ago

Same for me, Windows 11 Stable:

favefan commented 2 years ago

Same issue on Windows 10 Pro (19044.1586) with AMD R7 5800H processor.

pcaversaccio commented 2 years ago

same on Windows 11

Alexey71 commented 2 years ago

Download latest Windows Subsystem for Linux Update - 5.10.93.2 https://www.catalog.update.microsoft.com/Search.aspx?q=wsl
Unpuck xxxxxxxx.cab file
Install wsl_update_x64.msi

marcorotondi commented 2 years ago

Download latest Windows Subsystem for Linux Update - 5.10.93.2 https://www.catalog.update.microsoft.com/Search.aspx?q=wsl

Unpuck xxxxxxxx.cab file

Install wsl_update_x64.msi

Confirm that workaround is a valid solution!

pdrgnclvs commented 2 years ago

As @marcorotondi already confirmed, the workaround provided by @Alexey71 works wonders 🙏

Based on this, we can assume that Windows Update is incorrectly trying to install the ARM64 binary on the X64 platform; that's kind of weird since there should be some sort of check in place to make sure that Windows Update only installs updates for that specific Windows architecture 🤔

Anyway, thanks to @Alexey71 and everyone else who gave a workaround 👏

I could close the issue, but I'm going to wait for someone high above us to give some sort of an explanation to what happened 🤨

markstachowski commented 2 years ago

@pdrgnclvs who can we git blame 😆 - but in all seriousness thank you guys for finding a quick workaround. Happy Friday!

cr08 commented 2 years ago

Also seeing this on a Ryzen 7 5800X running Windows 11. Error code 0x80070661 in Windows Update.

wsl --update
Checking for updates...
Downloading updates...
Installing updates...
This installation package is not supported by this processor type. Contact your product vendor.

Can confirm the workaround above took care of it though. Cheers!

arencambre commented 2 years ago

@elsaco's instructions at https://github.com/microsoft/WSL/issues/8184#issuecomment-1078570745 ran successfully but some caveats:

Skip the rename step. It's unnecessary. Just run Expand-Archive .\Microsoft.WSL_0.56.2.0_x64_ARM64.msixbundle
It will upgrade your kernel to 5.10.102.1. That is a higher release than the version of the package recommended by Windows Update: 5.10.93.2. That said, I am not sure if the update package's version is the same as the kernel version.
Does not resolve the Windows Update issue. After following his steps, the same install error still appears, still unsuccessfully trying to shove a 5.10.93.2 update package at me. I am concerned that once Microsoft fixes this, I could be downgraded to a prior kernel. Rebooting does not cause this update or its error to go away.

pdrgnclvs commented 2 years ago

That's a good point @arencambre 🤔

It looks to me that running the workaround @elsaco provided, you'll be updating all WSL components on Windows 11 since that's the package that was recently published to the Microsoft Store and you'll also get the latest kernel version which is pretty nice 👍

Meanwhile the workaround provided by @Alexey71 allows you to update just the kernel which was causing the error in Windows Update in the first place - this way the error went away and now Windows Update doesn't complain anymore 👌

Maybe @elsaco's workaround applies to Windows 11 only since you can only install WSL from the Store in Windows 11, while @Alexey71's could apply to both Windows 10 and 11 since it simply updates the kernel? 🤨

This article could also provide some insight: https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/

What a mess 😅

EDIT: Maybe having WSL installed from the Store and in-box at the same time causes Windows Update to keep trying to shove an outdated kernel version since they don't know about or conflict with each other? 🤔

elsaco commented 2 years ago

The wsl_update_x64.msi from https://www.catalog.update.microsoft.com/Search.aspx?q=wsl has two files inside, the license and a Linux kernel:

PS C:\Catalog\wsl_update_x64> ls

    Directory: C:\Catalog\wsl_update_x64

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         1/31/2022   8:33 PM          19292 FID_LICENSE
-a----         1/31/2022   8:34 PM       43301584 FID_LXSS_KERNEL

The kernel is version 5.10.93.2-microsoft-standard-WSL2 #1 SMP Wed Jan 26 22:38:54 UTC 2022 It boots fine, but it's an older kernel.

pdrgnclvs commented 2 years ago

And now it's doing the same thing with version 5.10.102.1, the most recent, meaning that a new version of the kernel is available but still being incorrectly applied architecture-wise 🤔

WSL_FAIL

Thankfully, repeating @Alexey71's workaround, it gets fixed once again 🙏

CodesauceOverflow commented 2 years ago

Download latest Windows Subsystem for Linux Update - 5.10.93.2 https://www.catalog.update.microsoft.com/Search.aspx?q=wsl

Unpuck xxxxxxxx.cab file

Install wsl_update_x64.msi

How do you upack? I try at command line Expand-Archive ("Operation stopped"), and when going inside the .cab file i see the msi file but only get option to "Extract" when right-clicking on the msi file but then destination file does not show anything or just don't know where to extract it to (file- not folder) and I don't get any option to simply extract the contents of the .cab file through the windows Explorer..

Alexey71 commented 2 years ago

How do you upack? I try at command line Expand-Archive ("Operation stopped"), and when going inside the .cab file i see the msi file but only get option to "Extract" when right-clicking on the msi file but then destination file does not show anything or just don't know where to extract it to (file- not folder) and I don't get any option to simply extract the contents of the .cab file through the windows Explorer..

Winrar or 7z no problem. U can rename .cab to .zip and open

arencambre commented 2 years ago

The update just now worked, and it didn't downgrade my kernel. Still at 5.10.102.1 per what I did at https://github.com/microsoft/WSL/issues/8184#issuecomment-1079104958.

d2kx commented 2 years ago

And now it's doing the same thing with version 5.10.102.1, the most recent, meaning that a new version of the kernel is available but still being incorrectly applied architecture-wise 🤔

Can't confirm. The new 5.10.102.1 has updated successfully for me through Windows Update on both of my systems.

However it said "5.10.102.2" when it came through Windows Update, even though the actual kernel is .1 not .2. Maybe try updating again.

pdrgnclvs commented 2 years ago

And now it's doing the same thing with version 5.10.102.1, the most recent, meaning that a new version of the kernel is available but still being incorrectly applied architecture-wise 🤔

Can't confirm. The new 5.10.102.1 has updated successfully for me through Windows Update on both of my systems.

Because since my last message and now maybe someone at Microsoft fixed the problem on their side 😉

CodesauceOverflow commented 2 years ago

Thank you. I had tried all the renaming and unpacking options on that .cab file and none worked, and tried changing it to .exe file and windows couldn’t run it. When attempting to unpack, it seemed to show a windowsbase file or something. Lost the screen. I’m running Acer Nitro5 with intel cpu, 32gb ram (crucial), windows 11 pro, 1TB +265 gb ssd storage. BUT!!

Regular windows update just went through and updated it.

Thank you all for your replies.. people are quick on this stuff lol. Love it.

Alexey71 commented 2 years ago

I uninstall Windows Subsystem for Linux Update And try wsl --update. No error, MS fixed poblem

Hananel-Hazan commented 2 years ago

It seems the bug in the WSL update as been corrected. I just refreshed windows update and the update been downloaded and installed without a problem. I had the same issue couple of hours ago, I didn't apply the workaround, waited for Microsoft official fix, so it arrived it seems.

(win 10 10.0.19044.1620)

pdrgnclvs commented 2 years ago

It seems the bug in the WSL update as been corrected. I just refreshed windows update and the update been downloaded and installed without a problem. I had the same issue couple of hours ago, I didn't apply the workaround, waited for Microsoft official fix, so it arrived it seems.

(win 10 10.0.19044.1620)

Yes, it's been fixed since around 5PM-6PM (GMT) so it shouldn't pose a problem again 😉

benhillis commented 2 years ago

/dupe

microsoft / WSL