WSL2: every process launch fails with Wsl/Service/RPC_S_SYSTEM_HANDLE_TYPE_MISMATCH (0x8007072c) on 26300.9711/.9818, AMD; WSL1 works
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 22/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp, linux
- Domain
- operating-systems
Research direction
Start with the WSL service events and collect-wsl-logs.ps1 trace attached to the report, then follow the WSL2 CreateLxProcess result unmarshalling for the five sh_socket handles. Compare that path with WSL1’s sh_file handles and the related report in #42077. The failure is reproduced by importing the Alpine 3.24 minirootfs and running wsl -d wsltest -- echo hi; done means WSL2 prints hi successfully.
Written by the indexing model from the issue text.
Description
Windows Version
Microsoft Windows [Version 10.0.26300.9818] (Windows 11 Enterprise 26H2, after KB5127936). Also reproduced on 10.0.26300.9711 (KB5127648).
WSL Version
3.0.5.0 (kernel 6.18.58.1-1). Also reproduced on 3.0.3.0 (kernel 6.18.54.1-1).
Are you using WSL 1, WSL 2, or WSLC?
- WSL 2
- WSL 1
- WSLC
Kernel Version
6.18.58.1-microsoft-standard-WSL2
Distro Version
Any: Ubuntu 22.04, Ubuntu 24.04, Ubuntu 26.04, and a plain Alpine 3.24 minirootfs imported with wsl --import. wsl --system fails the same way.
Other Software
AMD Ryzen 7 7800X3D, NVIDIA RTX 4080 SUPER (driver 621.01). VirtualMachinePlatform + Microsoft-Windows-Subsystem-Linux enabled; full Hyper-V not installed. VBS running with Credential Guard only (HVCI off).
Third-party software has been ruled out: the error persists after uninstalling Huorong, VMware Workstation and AlibabaProtect, and also in a clean boot with all 37 non-Microsoft services, 8 non-hardware third-party kernel drivers (NetFilter SDK xfilter, Xunlei XLWFP, etc.) and all startup apps disabled. The 64-bit Winsock catalog contains only Microsoft providers (no LSP). sfc /scannow and DISM /RestoreHealth report no problems.
Repro Steps
wsl --import wsltest C:\wsltest alpine-minirootfs-3.24.4-x86_64.tar.gz --version 2wsl -d wsltest -- echo hi
Expected Behavior
hi is printed.
Actual Behavior
The RPC call contains a handle that differs from the declared handle type.
Error code: Wsl/Service/RPC_S_SYSTEM_HANDLE_TYPE_MISMATCH
wsl.exe exits with -1. Every command that starts a Linux process fails this way: default shell, wsl -u root, first-run OOBE (which then reports "failed to read passwd database"), wsl --system and wsl --debug-shell. It makes no difference whether wsl.exe runs in Windows Terminal, conhost, with pipes or file redirection, with a clean environment, or elevated.
Things that still work: wsl --status, wsl -l -v, wsl --version, wsl --shutdown, wsl --import, wsl --unregister and wsl --manage ... --set-sparse.
The same distro works under WSL1. After wsl --set-version wsltest 1, wsl -d wsltest -- sh -c 'echo hi; uname -r' prints hi and 4.4.0-26100-Microsoft. Converting it back to WSL2 brings the error back.
Turning off optional features in .wslconfig changes nothing. I tried guiApplications=false, networkingMode=none, dnsTunneling=false, autoProxy=false, firewall=false, nestedVirtualization=false and safeMode=true.
What the trace shows (from collect-wsl-logs.ps1, Microsoft.Windows.Lxss.Manager events):
- The utility VM boots and mini_init runs.
LxMiniInitMessageCreateInstanceResultreturnsResult = 0.LxInitMessageInitializeResponsereports the distro (alpine 3.24.4).LxInitMessageCreateSessionand thenLxInitMessageCreateProcessUtilityVmboth succeed (the latter returns a port).- wslservice logs no error after that. wsl.exe then fails with 0x8007072c.
So the guest side and wslservice both appear to succeed. The failure seems to happen when the result of ILxssUserSession::CreateLxProcess is unmarshalled back into wsl.exe. On the WSL2 path that result carries five [out, system_handle(sh_socket)] hvsocket handles: StandardIn, StandardOut, StandardErr, CommunicationChannel and InteropSocket. On WSL1 the out handles are sh_file instead, which would explain why WSL1 works. Downgrading WSL won't help, because every 2.5.8+ / 2.6 / 2.7 / 3.0 release uses the same sh_socket marshalling.
An AF_HYPERV socket created in a normal user process on this machine looks correct: File object on \Device\Afd, XP1_IFS_HANDLES set, SIO_BASE_HANDLE returns the same handle, and the provider is the Microsoft "Hyper-V RAW" entry.
Possibly related: this machine was also affected by the AMD HcsGetServiceProperties("ProcessorCapabilities") -> ERROR_INVALID_DATA regression (#41917). That warning is gone after KB5127936 (26300.9818), but the RPC_S_SYSTEM_HANDLE_TYPE_MISMATCH error is not. The only other report of this error I could find is #42077, which was closed without logs.
Diagnostic Logs
Logs collected with collect-wsl-logs.ps1 while reproducing wsl -d wsltest -- echo hi. I will email them to [email protected] with this issue number in the subject.
- Dominant language
- C++
- Stars
- 34.4k
- Forks
- 1.9k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 166
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/WSL
-
feature wsl2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
microsoft/WSL#42306 · 3 comments ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/WSL#42114 · 3 comments ·
Maintainers usually reply within 1 day
-
feature kernel wsl2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/WSL#41107 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
feature kernel
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/WSL#41054 · 9 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
feature GPU
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
microsoft/WSL#13592 · 4 comments ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
nextcloud/passman-android#214 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
2026.11.0 fails to install on Intel macOS: requirements.txt pins cryptography==50.0.2 for Darwin x86_64May be free again A pull request for this issue was closed without being merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 87/100
esphome/esphome#22892 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
arch-based hyprland
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
noctalia-dev/noctalia#5423 ·
Maintainers usually reply within 1 day