Updating to WSL-2 version 2.2.2 failing

[mwoodpatrick]

Windows Version

Windows version: 10.0.22635.3430

WSL Version

2.2.1.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.150.1-2

Distro Version

Debian

Other Software

No response

Repro Steps

wsl --update --pre-release

Expected Behavior

wsl would update if there is a new pre release

Actual Behavior

Checking for updates.
Updating Windows Subsystem for Linux to version: 2.2.2.
Update failed (exit code: 1618).
Log file: C:\Users\mlwp\AppData\Local\Temp\wsl-install-logs.txt
Error code: Wsl/UpdatePackage/0x80070652

Diagnostic Logs

cat C:\Users\mlwp\AppData\Local\Temp\wsl-install-logs.txt
=== Verbose logging started: 4/6/2024 8:36:18 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Program Files\WSL\wsl.exe ===
MSI (c) (E8:4C) [08:36:18:685]: Resetting cached policy values
MSI (c) (E8:4C) [08:36:18:685]: Machine policy value 'Debug' is 0
MSI (c) (E8:4C) [08:36:18:685]: ******* RunEngine:
******* Product: C:\Users\mlwp\AppData\Local\Temp\wsl.2.2.2.0.x64 (9).msi
******* Action:
******* CommandLine: **********
MSI (c) (E8:4C) [08:36:18:685]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E8:4C) [08:36:18:685]: Grabbed execution mutex.
MSI (c) (E8:4C) [08:36:18:690]: Cloaking enabled.
MSI (c) (E8:4C) [08:36:18:690]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (E8:4C) [08:36:18:694]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (E8:4C) [08:36:18:695]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (E8:4C) [08:36:18:695]: MainEngineThread is returning 1618
=== Verbose logging stopped: 4/6/2024 8:36:18 ===

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

• Can not update from 2.0.0 to 2.0.4 (#10636), similarity score: 0.75

Closed similar issues:

• Updating Windows Subsystem for Linux to version: 2.1.5 hangs (#11313), similarity score: 0.80
• wsl --update --pre-release failed (#10635), similarity score: 0.79
• 2.0.0 to 2.0.3 update failure (#10577), similarity score: 0.78
• Unable to update past ver 2.0.0.0 (#10591), similarity score: 0.77

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

[mwoodpatrick]

Running as an admin the update completed:

wsl --version
WSL version: 2.2.2.0
Kernel version: 5.15.150.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22635.3430