WSL 2 broken on Windows Server Preview (since change to fe_release branch)

[aPinat]

Environment

WSL 2 on Windows Server Preview Build 20262 (Windows Server 2019 Datacenter)
but is applicable to all (server?) preview builds ever since flighting changed to the "fe_release[_server]" branch, so 20246+

Steps to reproduce

Run any WSL 2 related command like for example wsl --set-default-version 2 or wsl --set-version Ubuntu 2 or try to run Docker Desktop with the WSL 2 backend.

Expected behavior

Command executes successfully.

Actual behavior

Commands just result in the same output as wsl --help shows.
Noting that it does NOT output Invalid command line option: <options> in first line, but in fact only the usage info as in wsl --help.
Docker Desktop with WSL 2 backend startup also fails showing the same output (wsl --help) as error.

Additional links

Related discussion: https://techcommunity.microsoft.com/t5/windows-server-insiders/wsl-2-not-working-after-installing-20262/m-p/1928823

[dennisameling]

Can confirm the --set-default-version 2 and --set-version Ubuntu 2 commands aren't working in Windows Server 2022 (build 20298.fe_release.210220-1636)

[buvinghausen]

@aPinat it appears the last WSL2 compatible build of Server was 20241 and that time bombed out on 1/31 so you can no longer start WSL without setting your clock back but then TLS and everything else goes up in smoke.

I have confirmed that the recently released build 20313 still has the same behavior you listed above. It would be nice if Microsoft would at least broach the subject....

[buvinghausen]

@benhillis @bpulliam & @craigloewen-msft is there an update? I just tried again with build 20317 and it's the same behavior as listed in here. It's been broken for over 4 months now can Microsoft at least acknowledge the problem so it can be remedied in the future?

[LubomirH]

Still the same in the build 20324 :(

[RobertSpir]

stll broken in 20344, which even removed timebomb and cannot be activated with the preview keys...

[Oosl]

same issue in widnows server 2022 20348.11

[craigloewen-msft]

Hi folks, we've added support for WSL 2 distros on Windows Server 2022! This is available right now by installing KB5014021. Currently this update is only available for seekers, and next month it will be pushed by default.

Going forwards, WSL will be supported both on Windows server and Windows desktop SKUs. Thank you all for the feedback, we appreciate your energy and passion for WSL!

I've edited this comment to give more accurate up to date information. Below you can find the original comment.

---

Hi all, thank you for your patience on this. Support for WSL 2 distros in the Windows Subsystem for Linux (WSL) is not included in Windows Server versions. WSL was created to support inner development loop scenarios. The Windows Desktop SKUs (where WSL 2 is supported) are recommended SKUs for these scenarios. For those who would like to use Linux in production scenarios in a server environment we recommend using server products such as Hyper-V VMs, and AKS on Azure Stack HCI. As always, we welcome any further Windows Server feedback through our Feedback Hub.

[RobertSpir]

In that case, update wsl.exe tool on windows server that it will not list version 2 options in help

[craigloewen-msft]

I agree, that's a great action item for us to take for future server versions. I've filed a bug for that on the team.

[buvinghausen]

@craigloewen-msft I disagree vehemently with this decision. It was working perfectly in prior releases. Telling customers that want to use WSL2 on a Server to use Desktop SKUs just strikes me as an incredibly tone deaf move by Microsoft. Why even have WSL1 on Windows Server at that point?

[Damasker]

Prob

Hi all, thank you for your patience on this. Support for WSL 2 distros in the Windows Subsystem for Linux (WSL) is not included in Windows Server versions. WSL was created to support inner development loop scenarios. The Windows Desktop SKUs (where WSL 2 is supported) are recommended SKUs for these scenarios. For those who would like to use Linux in production scenarios in a server environment we recommend using server products such as Hyper-V VMs, and AKS on Azure Stack HCI. As always, we welcome any further Windows Server feedback through our Feedback Hub.

Try to use docker desktop in production without wsl2, OSM maps for example. Is bloody hell. Docker not always start with hyper-v, and preparing custom WS builds with docker+hyper-v did not work. In W10 all work, but only 10 TCP connection. So we should give up and migrate to linux?

[TBBle]

That's correct. Per #6301 (comment), the advice for hosting Linux production workloads on Windows Server is Linux in a VM, or for containerised workloads, have Linux and Windows nodes available in a Kubernetes deployment.

[Squall124]

Hi all, thank you for your patience on this. Support for WSL 2 distros in the Windows Subsystem for Linux (WSL) is not included in Windows Server versions. WSL was created to support inner development loop scenarios. The Windows Desktop SKUs (where WSL 2 is supported) are recommended SKUs for these scenarios. For those who would like to use Linux in production scenarios in a server environment we recommend using server products such as Hyper-V VMs, and AKS on Azure Stack HCI. As always, we welcome any further Windows Server feedback through our Feedback Hub.

What's the point ?
It was working on previous builds, what's the point of removing it ?

That's a nonsense.

Completely disagree on this decision.

[cvb941]

I have been waiting years to be able to run Docker using WSL 2 on Windows Server with Desktop Experience, which suits my needs perfectly.

The decision to remove the support for WSL 2 in Windows Server 2022 is very saddening...

[catthehacker]

It's really unfortunate since I was expecting 2022 to have WSL2 so we could run tests for Docker on Windows (Linux containers). GitHub Actions and Azure DevOps Pipelines use Windows Server only so we won't be able to do anything.

[DVLP]

I was hoping that once LTSC version comes out the support for WSL2 will be restored as it was already working in older Windows Server insider builds. Unfortunately it's still broken. Anyone found a hack to i.e. replace some system files from an older build where WSL2 used to work?

[akbaryahya]

so it just works without "server" label :(

[vnkazna]

Windows Server é uma merda!

[slonopotamus]

So, do I understand correctly that WSL2 will work if I install Azure Kubernetes Service onto Windows Server Datacenter?

[TBBle]

Not as far as I understand. If you're using AKS on Azure Stack HCI or Windows Server 2019 Datacenter, then the cluster is using Linux VMs, not WSL2.

[3JoB]

And using WSL (WSL2) in Windows Server 2022 has a chance to cause a blue screen error that the kernel security check fails

[farrukhfida]

I agree, that's a great action item for us to take for future server versions. I've filed a bug for that on the team.

is it fixed in Windows server 2022 datacenter? As I have tried but WSL is not switching to wsl2 and I have to use hyper vm to use docker desktop. Any suggestion that could help to fix this issue and i can run docker desktop with WSL2 support on windows server 2022?

[TBBle]

is it fixed in Windows server 2022 datacenter?

I'm pretty sure "future server versions" here meant after Windows Server 2022, which was already "RTM" at the time of that comment.

Also, the "action item" was removing the WSL2 option from wsl.exe, not "Make WSL2" work. There remains, as far as I've seen publicly, no intention to support WSL2 (or Docker Desktop, technically) on Windows Server now or future versions.

[terrafirma2021]

20H2 EOL is in 2 days, Craig. May I ask if you have an issue with DDA and WS2?

[mihailescu2m]

looking for updates on this as well...

[iambenmitchell]

Any update? I want to run linux dockers/containers on Windows Server 2022 using WSL

[akbaryahya]

I don't think it's going to happen, the reason I want to use Windows Server is because I can completely delete the antivirus because it's useless and slow when building Java projects because the antivirus keeps scanning even when it's turned off and the filter folder.

[sudo-kraken]

It is ridiculous that you allow WSL1 but not 2 its hypocrisy, you can have it... but not with full kernel support, can you at least say why you wont allow this to be a fully functional kernel. Clearly it is what your users are wanting, when we are checking this after it being open for 6 months...

[ylluminate]

Sadly WSL2 has some serious trouble still that I think they may want to solve before moving it forward. They have a "schizophrenia" problem with networking between WSL1 vs WSL2 at the moment (check out these 591 comments for an example: #4150).

[iambenmitchell]

Well until WSL2 is supported on Windows Server, people are going to run Windows 10/11 in the data center simply because a lot of people need to run docker or other container platforms and it is inefficient to run in a VM instead.

[ylluminate]

@iambenmitchell to be honest, I'm finding that running Proxmox on Hyper-V is more sane at the moment since it gives networking stability + management of LXCs (and Docker if you configure it to do so through some additional effort). Personally I think LXC mgmt via Proxmox is a little cleaner and visible, so to speak, for various applications.

[ohault]

This issue is a real shame for Microsoft. The very unfair answer would be that Microsoft decides to only fix this on Azure HCI.

[craigloewen-msft]

Hi folks, we've added support for WSL 2 distros on Windows Server 2022! This is available right now by installing KB5014021. Currently this update is only available for seekers, and next month it will be pushed by default.

Going forwards, WSL will be supported both on Windows server and Windows desktop SKUs. Thank you all for the feedback, we appreciate your energy and passion for WSL!

[iambenmitchell]

Hi folks, we've added support for WSL 2 distros on Windows Server 2022

Amazing! Music to my ears, and I am sure a lot of other people are pleased by this thanks!

[sudo-kraken]

Hi folks, we've added support for WSL 2 distros on Windows Server 2022! This is available right now by installing KB5014021. Currently this update is only available for seekers, and next month it will be pushed by default.

Going forwards, WSL will be supported both on Windows server and Windows desktop SKUs. Thank you all for the feedback, we appreciate your energy and passion for WSL!

Amazing, thank you for listening to the community! Great work.

[buvinghausen]

Thanks @craigloewen-msft

[ssbarnea]

When is this going to be available on github action runners? (self-hosted does not count)

[buvinghausen]

When is this going to be available on github action runners?

Pretty sure you can do it with a self-hosted runner

[tristanbarcelon]

Installed KB5014021, rebooted, ran wsl --install, rebooted and let it finish wsl install after reboot. It seems that I can only access wsl2 from command prompt. Using Windows Terminal v1.13.11431 gives me this error. Has anybody reported this problem?

[TBBle]

@tristanbarcelon See #6995 and possibly microsoft/terminal#3158 (comment). AFAIK this is possibly a known issue with WSL2, and depending on the exact problem, that second link mentions a workaround and the reason.

[TBBle]

@ssbarnea At a minimum, it'll be when https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md is incremented past Build 740. It's currently Build 707 (the last regular update) and that happened within a few days of the update itself being released. So probably mid-June for that.

I hit an issue earlier this year that suggested the Virtualisation Platform (used by both WSL2 and Hyper-V container isolation) isn't enabled on the Server 2022 GitHub runners, so that may need to be enabled as well. https://github.com/marketplace/actions/setup-wsl agrees that Hyper-V is not enabled on the windows-2022 image; so it's likely that even after the WSL2-supporting version of Server 2022 is deployed, a ticket at https://github.com/actions/virtual-environments/issues/ would be needed. Existing actions/runner-images#1481 and actions/runner-images#183 contain relevant history too, and the latter suggests that something in their infrastructure prevents Hyper-V nested isolation from working, or at least it used to.

So you may find that a self-hosted runner is your only option there, sadly.

[terrafirma2021]

Thank you @craigloewen-msft

[jaredhagel]

Hi @craigloewen-msft, are there plans to backport this change to Windows Server 2019?

[tristanbarcelon]

@ssbarnea At a minimum, it'll be when https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md is incremented past Build 740. It's currently Build 707 (the last regular update) and that happened within a few days of the update itself being released. So probably mid-June for that.

I hit an issue earlier this year that suggested the Virtualisation Platform (used by both WSL2 and Hyper-V container isolation) isn't enabled on the Server 2022 GitHub runners, so that may need to be enabled as well. https://github.com/marketplace/actions/setup-wsl agrees that Hyper-V is not enabled on the windows-2022 image; so it's likely that even after the WSL2-supporting version of Server 2022 is deployed, a ticket at https://github.com/actions/virtual-environments/issues/ would be needed. Existing actions/virtual-environments#1481 and actions/virtual-environments#183 contain relevant history too, and the latter suggests that something in their infrastructure prevents Hyper-V nested isolation from working, or at least it used to.

So you may find that a self-hosted runner is your only option there, sadly.

Are the github runners hosted on AWS EC2 or Azure VMs? With our previous attempts at this with Azure, certain VM types do not have nested virtualization turned on and this prevented us from running docker. A WSL2 faq seems to confirm this.

[craigloewen-msft]

@jaredhagel no we do not plan to backport this change to Windows Server 2019.

[TBBle]

Yeah, they're Azure-hosted Standard_DS2_v2 virtual machines. The doc for DSv2-series says

Nested Virtualization: Not Supported

so yeah, I guess unless something changes (like upgrading to Standard_D2s_v3), WSL2 on GH-hosted GHA runners still won't happen even though the OS supports it.

That said, actions/runner-images#183 (comment) suggests that maybe the documentation is out-of-date, and they're running on nested-virtualisation-capable hardware after all, and it might just be a configuration change that needs to be made in https://github.com/actions/virtual-environments. The immediately-following comment clarified that this was talking about the runner-image-building hosts, not the hosts used to run the runners. (And I now remember I've been through exactly this process before.)

[heapybruh]

Can confirm that it is working as intended :)

[karstennilsen]

WSL2 crashes on my server 2022:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x800706be
Error: 0x800706be Kan RPC niet uitvoeren.

Logs:
WslLogs-2022-05-30_13-30-35.zip

Debug:

[    0.000000] Linux version 5.10.16.3-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Fri Apr 2 22:23:49 UTC 2021
[    0.000000] Command line: initrd=\initrd.img panic=-1 nr_cpus=2 swiotlb=force console=ttyS0,115200 debug pty.legacy_count=0
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
[    0.000000] x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
[    0.000000] x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
[    0.000000] x86/fpu: Enabled xstate features 0xe7, context size is 2432 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000e0fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000001fffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x0000000000200000-0x00000000f7ffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000287dfffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] Hypervisor detected: Microsoft Hyper-V
[    0.000000] Hyper-V: features 0x2e7f, privilege high: 0x3b8030, hints 0x26c2c, misc 0xe0bed7b2
[    0.000000] Hyper-V Host Build:20348-10.0-0-0.740
[    0.000000] Hyper-V: LAPIC Timer Frequency: 0x1e8480
[    0.000000] tsc: Marking TSC unstable due to running on Hyper-V
[    0.000000] Hyper-V: Using hypercall for remote TLB flush
[    0.000000] clocksource: hyperv_clocksource_tsc_page: mask: 0xffffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns: 440795202120 ns
[    0.000009] tsc: Detected 2999.973 MHz processor
[    0.000028] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000030] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000035] last_pfn = 0x287e00 max_arch_pfn = 0x400000000
[    0.000147] MTRR default type: uncachable
[    0.000148] MTRR fixed ranges enabled:
[    0.000150]   00000-3FFFF write-back
[    0.000151]   40000-7FFFF uncachable
[    0.000152]   80000-8FFFF write-back
[    0.000153]   90000-FFFFF uncachable
[    0.000153] MTRR variable ranges enabled:
[    0.000154]   0 base 00000000000 mask 7FF00000000 write-back
[    0.000155]   1 base 00100000000 mask 7F000000000 write-back
[    0.000156]   2 disabled
[    0.000157]   3 disabled
[    0.000157]   4 disabled
[    0.000158]   5 disabled
[    0.000158]   6 disabled
[    0.000159]   7 disabled
[    0.000192] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.000252] last_pfn = 0xf8000 max_arch_pfn = 0x400000000
[    0.000287] Using GB pages for direct mapping
[    0.001377] RAMDISK: [mem 0x03035000-0x03043fff]
[    0.001393] ACPI: Early table checksum verification disabled
[    0.001412] ACPI: RSDP 0x00000000000E0000 000024 (v02 VRTUAL)
[    0.001452] ACPI: XSDT 0x0000000000100000 000044 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.001463] ACPI: FACP 0x0000000000101000 000114 (v06 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.001468] ACPI: DSDT 0x00000000001011B8 01E184 (v02 MSFTVM DSDT01   00000001 MSFT 05000000)
[    0.001472] ACPI: FACS 0x0000000000101114 000040
[    0.001474] ACPI: OEM0 0x0000000000101154 000064 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.001477] ACPI: SRAT 0x000000000011F33C 0002D0 (v02 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.001480] ACPI: APIC 0x000000000011F60C 000058 (v04 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.001493] ACPI: Local APIC address 0xfee00000
[    0.002496] Zone ranges:
[    0.002498]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.002500]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.002501]   Normal   [mem 0x0000000100000000-0x0000000287dfffff]
[    0.002503]   Device   empty
[    0.002504] Movable zone start for each node
[    0.002504] Early memory node ranges
[    0.002505]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.002506]   node   0: [mem 0x0000000000200000-0x00000000f7ffffff]
[    0.002507]   node   0: [mem 0x0000000100000000-0x0000000287dfffff]
[    0.006654] Zeroed struct page in unavailable ranges: 865 pages
[    0.006663] Initmem setup node 0 [mem 0x0000000000001000-0x0000000287dfffff]
[    0.006666] On node 0 totalpages: 2620575
[    0.006667]   DMA zone: 59 pages used for memmap
[    0.006668]   DMA zone: 22 pages reserved
[    0.006670]   DMA zone: 3743 pages, LIFO batch:0
[    0.006704]   DMA32 zone: 16320 pages used for memmap
[    0.006705]   DMA32 zone: 1011712 pages, LIFO batch:63
[    0.034695]   Normal zone: 25080 pages used for memmap
[    0.034699]   Normal zone: 1605120 pages, LIFO batch:63
[    0.035934] ACPI: Local APIC address 0xfee00000
[    0.035942] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[    0.036675] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
[    0.036679] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.036682] ACPI: IRQ9 used by override.
[    0.036684] Using ACPI (MADT) for SMP configuration information
[    0.036984] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[    0.036997] [mem 0xf8000000-0xffffffff] available for PCI devices
[    0.036999] Booting paravirtualized kernel on Hyper-V
[    0.037001] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.041730] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:2 nr_node_ids:1
[    0.042870] percpu: Embedded 52 pages/cpu s173272 r8192 d31528 u1048576
[    0.042877] pcpu-alloc: s173272 r8192 d31528 u1048576 alloc=1*2097152
[    0.042879] pcpu-alloc: [0] 0 1
[    0.042894] Built 1 zonelists, mobility grouping on.  Total pages: 2579094
[    0.042896] Kernel command line: initrd=\initrd.img panic=-1 nr_cpus=2 swiotlb=force console=ttyS0,115200 debug pty.legacy_count=0
[    0.050820] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.054936] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.055709] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.106017] Memory: 4094132K/10482300K available (16403K kernel code, 2459K rwdata, 3464K rodata, 1444K init, 1164K bss, 287772K reserved, 0K cma-reserved)
[    0.106047] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.106057] ftrace: allocating 49613 entries in 194 pages
[    0.123486] ftrace: allocated 194 pages with 3 groups
[    0.125503] rcu: Hierarchical RCU implementation.
[    0.125505] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2.
[    0.125507]  Rude variant of Tasks RCU enabled.
[    0.125507]  Tracing variant of Tasks RCU enabled.
[    0.125508] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.125509] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.128571] Using NULL legacy PIC
[    0.128573] NR_IRQS: 16640, nr_irqs: 440, preallocated irqs: 0
[    0.129403] random: crng done (trusting CPU's manufacturer)
[    0.129429] Console: colour dummy device 80x25
[    7.167047] printk: console [ttyS0] enabled
[    7.204892] ACPI: Core revision 20200925
[    7.280534] Failed to register legacy timer interrupt
[    7.376006] APIC: Switch to symmetric I/O mode setup
[    7.450083] Hyper-V: Using IPI hypercalls
[    7.479584] Hyper-V: Using enlightened APIC (xapic mode)
[    7.480808] Calibrating delay loop (skipped), value calculated using timer frequency.. 5999.94 BogoMIPS (lpj=29999730)
[    7.490767] pid_max: default: 32768 minimum: 301
[    7.490767] LSM: Security Framework initializing
[    7.490767] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    7.490767] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    7.490767] Last level iTLB entries: 4KB 128, 2MB 8, 4MB 8
[    7.490767] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[    7.490767] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    7.490767] Spectre V2 : Mitigation: Enhanced IBRS
[    7.490767] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    7.490767] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    7.490767] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    7.490767] Freeing SMP alternatives memory: 52K
[    7.490767] smpboot: CPU0: Intel(R) Xeon(R) Gold 6248R CPU @ 3.00GHz (family: 0x6, model: 0x55, stepping: 0x7)
[    7.491061] Performance Events: unsupported p6 CPU model 85 no PMU driver, software events only.
[    7.500933] rcu: Hierarchical SRCU implementation.
[    7.511286] smp: Bringing up secondary CPUs ...
[    7.520994] x86: Booting SMP configuration:
[    7.530790] .... node  #0, CPUs:      #1
[    7.532427] smp: Brought up 1 node, 2 CPUs
[    7.550780] smpboot: Max logical packages: 1
[    7.560783] smpboot: Total of 2 processors activated (11999.89 BogoMIPS)
[    7.596462] node 0 deferred pages initialised in 20ms
[    7.601321] devtmpfs: initialized
[    7.610942] x86/mm: Memory block size: 128MB
[    7.621206] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    7.740792] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    7.781246] NET: Registered protocol family 16
[    7.811050] thermal_sys: Registered thermal governor 'step_wise'
[    7.811120] cpuidle: using governor menu
[    7.830868] ACPI: bus type PCI registered
[    7.840875] PCI: Fatal: No config space access function found
[    7.851869] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    7.860805] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    7.870865] raid6: skip pq benchmark and using algorithm avx512x4
[    7.880810] raid6: using avx512x2 recovery algorithm
[    7.890845] ACPI: Added _OSI(Module Device)
[    7.900783] ACPI: Added _OSI(Processor Device)
[    7.910781] ACPI: Added _OSI(3.0 _SCP Extensions)
[    7.920787] ACPI: Added _OSI(Processor Aggregator Device)
[    7.930796] ACPI: Added _OSI(Linux-Dell-Video)
[    7.940785] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    7.950787] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    7.964978] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    7.973353] ACPI: Interpreter enabled
[    7.980810] ACPI: (supports S0 S5)
[    7.990786] ACPI: Using IOAPIC for interrupt routing
[    8.000907] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    8.011154] ACPI: Enabled 1 GPEs in block 00 to 0F
[    8.022246] iommu: Default domain type: Translated
[    8.031058] SCSI subsystem initialized
[    8.040909] hv_vmbus: Vmbus version:5.2
[    8.070933] hv_vmbus: Unknown GUID: c376c1c3-d276-48d2-90a9-c04748072c60
[    8.071442] PCI: Using ACPI for IRQ routing
[    8.110791] PCI: System does not support PCI
[    8.140928] clocksource: Switched to clocksource hyperv_clocksource_tsc_page
[    8.392761] VFS: Disk quotas dquot_6.6.0
[    8.421826] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    8.470655] FS-Cache: Loaded
[    8.490740] pnp: PnP ACPI init
[    8.513413] pnp 00:00: Plug and Play ACPI device, IDs PNP0501 (active)
[    8.556904] pnp 00:01: Plug and Play ACPI device, IDs PNP0501 (active)
[    8.598970] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[    8.642496] pnp: PnP ACPI: found 3 devices
[    8.673619] NET: Registered protocol family 2
[    8.717749] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    8.782155] TCP established hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    8.844283] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    8.891891] TCP: Hash tables configured (established 131072 bind 65536)
[    8.939778] UDP hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    8.990918] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes, linear)
[    9.048644] NET: Registered protocol family 1
[    9.102008] RPC: Registered named UNIX socket transport module.
[    9.189425] RPC: Registered udp transport module.
[    9.261233] RPC: Registered tcp transport module.
[    9.306564] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    9.354672] PCI: CLS 0 bytes, default 64
[    9.386187] Trying to unpack rootfs image as initramfs...
[    9.423199] Freeing initrd memory: 60K
[    9.451531] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    9.495936] software IO TLB: mapped [mem 0x00000000f4000000-0x00000000f8000000] (64MB)
[    9.550979] KVM: vmx: using Hyper-V Enlightened VMCS
[    9.589936] kvm: already loaded the other module
[    9.626983] Initialise system trusted keyrings
[    9.660620] workingset: timestamp_bits=46 max_order=22 bucket_order=0
[    9.710178] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    9.753033] NFS: Registering the id_resolver key type
[    9.791216] Key type id_resolver registered
[    9.824599] Key type id_legacy registered
[    9.854680] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    9.900104] Key type cifs.idmap registered
[    9.933958] fuse: init (API version 7.32)
[    9.971427] SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, no debug enabled
[   10.038447] 9p: Installing v9fs 9p2000 file system support
[   10.077623] FS-Cache: Netfs '9p' registered for caching
[   10.117751] FS-Cache: Netfs 'ceph' registered for caching
[   10.163036] ceph: loaded (mds proto 32)
[   10.199635] NET: Registered protocol family 38
[   10.264692] xor: automatically using best checksumming function   avx
[   10.352159] Key type asymmetric registered
[   10.414346] Asymmetric key parser 'x509' registered
[   10.463955] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[   10.518652] hv_vmbus: registering driver hv_pci
[   10.555683] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[   10.608983] 00:00: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[   10.667414] 00:01: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[   10.722342] Non-volatile memory driver v1.3
[   10.757067] brd: module loaded
[   10.789308] loop: module loaded
[   10.834431] hv_vmbus: registering driver hv_storvsc
[   10.888393] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[   10.981471] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[   11.047639] tun: Universal TUN/TAP device driver, 1.6
[   11.080221] PPP generic driver version 2.4.2
[   11.112404] PPP BSD Compression module registered
[   11.147177] PPP Deflate Compression module registered
[   11.147268] scsi host0: storvsc_host_t
[   11.187956] PPP MPPE Compression module registered
[   11.250161] NET: Registered protocol family 24
[   11.281870] hv_vmbus: registering driver hv_netvsc
[   11.317626] VFIO - User Level meta-driver version: 0.3
[   11.359109] hv_vmbus: registering driver hyperv_keyboard
[   11.398744] rtc_cmos 00:02: RTC can wake from S4
[   11.485440] rtc_cmos 00:02: registered as rtc0
[   11.559207] rtc_cmos 00:02: setting system clock to 2022-05-30T11:40:47 UTC (1653910847)
[   11.624222] rtc_cmos 00:02: alarms up to one month, 114 bytes nvram
[   11.667796] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
[   11.731221] device-mapper: raid: Loading target version 1.15.1
[   11.780699] hv_utils: Registering HyperV Utility Driver
[   11.826181] hv_vmbus: registering driver hv_utils
[   11.863724] hv_vmbus: registering driver hv_balloon
[   11.863800] hv_utils: cannot register PTP clock: 0
[   11.932145] hv_vmbus: registering driver dxgkrnl
[   11.996991] hv_utils: TimeSync IC version 4.0
[   11.998665] hv_balloon: Using Dynamic Memory protocol version 2.0
[   12.060989] (NULL device *): dxgk: dxg_drv_init  Version: 2103
[   12.153949] Free page reporting enabled
[   12.154014] drop_monitor: Initializing network drop monitor service
[   12.215491] hv_balloon: Cold memory discard hint enabled
[   12.250486] Mirror/redirect action on
[   12.372349] IPVS: Registered protocols (TCP, UDP)
[   12.410800] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
[   12.481423] IPVS: ipvs loaded.
[   12.532593] IPVS: [rr] scheduler registered.
[   12.600530] IPVS: [wrr] scheduler registered.
[   12.638533] IPVS: [sh] scheduler registered.
[   12.676370] ipip: IPv4 and MPLS over IPv4 tunneling driver
[   12.723061] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[   12.774491] Initializing XFRM netlink socket
[   12.813467] NET: Registered protocol family 10
[   12.879505] Segment Routing with IPv6
[   12.921446] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[   13.051135] NET: Registered protocol family 17
[   13.080155] Bridge firewalling registered
[   13.106206] 8021q: 802.1Q VLAN Support v1.8
[   13.139344] sctp: Hash tables configured (bind 256/256)
[   13.220365] 9pnet: Installing 9P2000 support
[   13.298889] Key type dns_resolver registered
[   13.353175] Key type ceph registered
[   13.381971] libceph: loaded (mon/osd proto 15/24)
[   13.415681] NET: Registered protocol family 40
[   13.451951] hv_vmbus: registering driver hv_sock
[   13.509108] IPI shorthand broadcast: enabled
[   13.559664] registered taskstats version 1
[   13.617053] Loading compiled-in X.509 certificates
[   13.675075] Btrfs loaded, crc32c=crc32c-generic
[   13.710275] Unstable clock detected, switching default tracing clock to "global"
[   13.710275] If you want to keep using the local clock, then add:
[   13.710275]   "trace_clock=local"
[   13.710275] on the kernel command line
[   13.937497] Freeing unused kernel image (initmem) memory: 1444K
[   14.030909] Write protecting the kernel read-only data: 22528k
[   14.075660] Freeing unused kernel image (text/rodata gap) memory: 2028K
[   14.141378] Freeing unused kernel image (rodata/data gap) memory: 632K
[   14.220490] Run /init as init process
[   14.267552]   with arguments:
[   14.318381]     /init
[   14.334840]   with environment:
[   14.356212]     HOME=/
[   14.373585]     TERM=linux
WSL has terminated, press any key to continue...

[TBBle]

@karstennilsen Maybe worth trying some of the solutions in #5768? Otherwise, I'd suggest opening a new issue, since this issue is already quite long, has a lot of subscribers, and is Closed so may not get the attention you need.

[composite]

@karstennilsen

WSL2 crashes on my server 2022:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x800706be
Error: 0x800706be Kan RPC niet uitvoeren.

Don't run distro as Administrator or it won't worked. create a user with Administrators group and try again. It worked for me.