WSL: /init seems to crash when resume from S3 sleep.

Windows Version

Microsoft Windows [Version 10.0.26100.1150]

WSL Version

2.3.11.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

6.6.36.3-1

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

Windows into S3 sleep. resume Windows.

Expected Behavior

return to previous state before sleep.

Actual Behavior

the WSL Distro crashes. but, kernel is running.

[   30.465930] WSL (1) ERROR: ValidateMessageHeader:329: Protocol error: Received message size:
[   30.465945] 28, type: 7, sequence: 0. Expected type: 0, expected sequence: 2, channel: init
[   30.465972] WSL (2) ERROR: ValidateMessageHeader:329: Protocol error: Received message size:
[   30.476375] hv_utils: TimeSync IC version 4.0
[   30.485262] libc++abi:
[   30.485271] terminating due to uncaught exception of type wil::ResultException: Invalid argument @C:/__w/1/s/src/shared/inc\SocketChannel.h:331 (ValidateMessageHeader)

Diagnostic Logs

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 5
  • Comments: 18 (2 by maintainers)

Most upvoted comments

We have a fix for this we will be rolling out soon.

Updated to 2.3.12 via wsl --update --pre-release and I did not see the WSL2 guest OS crash (in my case Fedora) following a resume from S3. Thank you for the quick fix on this one 👍

i have confirmed that this has been fixed in 2.3.12.

thanks so much WSL team.

i see same behavior after upgrading from 2.2.4 to 2.3.11; besides sleep (not surprisingly) also with hibernate: distros die (both wsl and wsl --system) but kernel (as of wsl --debug-shell) survives. reverting back to 2.2.4 (and hence older kernel) makes it work again … PS: this was on ubuntu 24.04 distro with wslg, systemd and gradual memory reclaim enabled, all running on win11 10.0.22631 BTW: issue also mentioned in 2.3.11 release discussion (https://github.com/microsoft/WSL/discussions/11789#discussioncomment-10090176)