2.3.26

[benhillis]

• Update kernel to 5.15.167.4
  • Update to stable kernel version v5.15.167
  • Include an out-of-tree patch fixing a bug in the XSAVES subsystem.

---

This discussion was created from the release 2.3.26.

[astroboylrx]

Whenever an update is released, Windows Store terminates my WSL and updates it for me, regardless of any running processes. I'm using WSL2 for work for a long time. I don't think the update was this aggressive previously, at least before 2024.
Is there something I can do to prevent this? Thanks in advance.

Maybe it is not Windows Store who actually did the update? Maybe the Store just shows an update was done? What module performs the update?
I already turned off auto app updates in the Store settings and even enabled "Turn off Automatic Downloads and Install of updates" in the group policy.

WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4391

[JavierMP-97]

Also, same here too. When the update came, it crashed a process running on WSL and forced windows to restart without any warning :/

[spintonp4]

Same for me too.

[awtomb]

System auto-updated to 2.3.26.0, and killed by Ubuntu-system ("Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified.")

I followed the advice from various open issues (example: #11288) triggered by previous updates, and manually installed previous version (2.3.24) - which brought my system back to life.

[nowakowskir]

Same here!

Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified.
Error code: Wsl/Service/CreateInstance/CreateVm/MountVhd/HCS/ERROR_FILE_NOT_FOUND

[process exited with code 4294967295 (0xffffffff)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

Rolling back to 2.3.24 solved the issue. Thanks @awtomb

[JavierMP-97]

Same here. Auto updated without a previous warning, and then the same error. Going back to 2.3.34 also solved it.

[Scarlett-Jns]

Does this release remove nfs2? How to recover？

[elsaco]

nfs2 support is built into the kernel. If you check kernel's config there's CONFIG_NFS_V2=y