WSL Service Crashes During VM Creation on Windows 11 25H2 (Build 26200.7171)

Nobody has claimed this yet.

### Windows Version

Microsoft Windows [Version 10.0.26200.7171]

### WSL Version

2.6.1.0

### Are you using WSL 1 or WSL 2?

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

_No response_

### Distro Version

_No response_

### Other Software

OS: Windows 11 Home (Official Stable Release)
Version: 25H2
Build: 26200.7171
WSL Version: 2.6.1.0
System: MSI MS-7E06, Intel Core (Model 183), 64GB RAM
Previously Installed Virtualization Software: VirtualBox and VMware (completely uninstalled)

### Repro Steps

## Repro Steps

1. Open PowerShell as Administrator
2. Run `wsl --install -d Ubuntu-24.04` (or any other distribution)
3. Wait for download to complete
4. Observe installation attempt

**Alternative methods attempted (all fail identically):**
- `wsl --install` (default Ubuntu)
- `wsl --install -d Ubuntu-22.04`
- `wsl --install -d Debian`
- Installing from Microsoft Store (Ubuntu 24.04, 22.04, 20.04, Debian)
- Manual download and AppX installation

**Reproducibility:** 100% - Fails every single time across all distributions and installation methods

### Expected Behavior

## Expected Behavior

Based on official documentation (https://learn.microsoft.com/en-us/windows/wsl/install):

1. WSL should download the selected Linux distribution
2. WSL should register the distribution
3. WSL should create a Hyper-V VM for the distribution
4. The distribution should launch and prompt for user setup
5. Command should complete successfully with the distribution installed and ready to use

Example of expected successful output:
```
Downloading: Ubuntu 24.04 LTS
Installing: Ubuntu 24.04 LTS
Ubuntu 24.04 LTS has been installed.
Launching Ubuntu 24.04 LTS...
```

### Actual Behavior

## Actual Behavior

The installation process fails during VM creation with the following error:

```
Downloading: Ubuntu 24.04 LTS
Installing: Ubuntu 24.04 LTS
An address incompatible with the requested protocol was used.
Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/0x8007273f
```

**What happens behind the scenes:**
- Download completes successfully
- Initial registration begins
- **WSL Service (`wslservice.exe`) crashes during CreateVm operation**
- Installation rolls back
- No distribution is installed

**Event Log Evidence:**
```
Event ID: 7034
Source: Service Control Manager
Level: Error
Message: The WSL Service service terminated unexpectedly.

Event ID: 1000
Source: Application Error
Level: Error
Message: Faulting application name: wslservice.exe, version: 2.6.1.0
```

### Diagnostic Logs

## Error Details

### Error Message
```
An address incompatible with the requested protocol was used.
Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/0x8007273f
```

### Event Log Evidence
```
ProviderName: Service Control Manager
TimeCreated: 11/12/2025 10:39:02 PM
Id: 7034
Level: Error
Message: The WSL Service service terminated unexpectedly.
```

```
ProviderName: Application Error
Id: 1000
Level: Error
Message: Faulting application name: wslservice.exe, version: 2.6.1.0
```

## System Verification - All Tests Pass

### Virtualization Status
```powershell
# All services running correctly
Get-Service vmcompute # Status: Running
Get-Service HvHost # Status: Running
Get-Service LxssManager # Status: Running

# All required features enabled
Get-WindowsOptionalFeature -Online
VirtualMachinePlatform # State: Enabled
HypervisorPlatform # State: Enabled

# Hypervisor configured correctly
bcdedit /enum | findstr hypervisorlaunchtype
# Output: hypervisorlaunchtype Auto

# Virtualization-based Security active
systeminfo | findstr /C:"Hyper-V"
# Output: A hypervisor has been detected. Features required for Hyper-V will not be displayed.

# VBS running correctly
Get-CimInstance -ClassName Win32_DeviceGuard
VirtualizationBasedSecurityStatus: 2 (Running)
```

### System Integrity - No Corruption Found
```powershell
# Windows image health check
Dism /Online /Cleanup-Image /CheckHealth
# Result: The component store is repairable.

Dism /Online /Cleanup-Image /ScanHealth
# Result: No component store corruption detected.

Dism /Online /Cleanup-Image /RestoreHealth
# Result: The restore operation completed successfully.

# System file verification
sfc /scannow
# Result: Windows Resource Protection did not find any integrity violations.
```

## Extensive Troubleshooting Attempted

### Network Stack Resets
```powershell
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
# Restarted after each - No effect
```

### WSL Reinstallation Attempts
```powershell
# Tried default installation
wsl --install

# Tried specific distributions
wsl --install -d Ubuntu-24.04
wsl --install -d Ubuntu-22.04
wsl --install -d Debian

# Attempted WSL updates
wsl --update
wsl --update --web-download
wsl --update --pre-release

# Attempted version switching
wsl --set-default-version 2
wsl --set-default-version 1 # Failed: WSL_E_WSL1_NOT_SUPPORTED
```

### Windows Feature Management
```powershell
# Disabled and re-enabled all WSL/Hyper-V features
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
Disable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
# Restarted

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
# Restarted

# Also tried via DISM
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
dism.exe /online /enable-feature /featurename:HypervisorPlatform /all /norestart
# Restarted
```

### Attempted Installations from Multiple Sources
- Command line (`wsl --install`)
- Microsoft Store (Ubuntu 24.04, 22.04, 20.04, Debian)
- All methods result in identical crash

### Configuration Adjustments
- Removed experimental `.wslconfig` settings (mirrored networking)
- Disabled Norton VPN and network adapter
- Verified no conflicting virtualization software remains

### Registry Verification
```powershell
Get-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Lxss"
# NatIpAddress: 172.25.19.120
# DefaultVersion: 2
# No abnormalities detected
```

## What Does NOT Work
❌ Any `wsl --install` command (all distributions)
❌ Microsoft Store installations
❌ Network stack resets
❌ Feature disable/enable cycles
❌ WSL service restarts
❌ System integrity repairs (DISM/SFC)
❌ Removing `.wslconfig` configuration
❌ WSL updates

## Observations
1. **WSL Service crashes specifically during CreateVm operation** - All pre-VM steps succeed (download, initial registration)
2. **Hyper-V infrastructure is fully functional** - vmcompute and HvHost services run normally
3. **System passes all integrity checks** - No corruption detected by Microsoft's own tools
4. **Error is reproducible 100% of the time** across all distributions and installation methods
5. **Issue appears specific to Windows 11 25H2 (Build 26200.7171)** - This is the official stable release from November 11, 2025

## Similar Reports
Other users have reported similar issues that only resolved after clean Windows reinstallation, suggesting a system-level bug in Windows 11 25H2 that integrity tools cannot detect or repair.

## Request
This appears to be a genuine bug in Windows 11 25H2 build 26200.7171 affecting WSL VM creation despite perfect system configuration. The WSL service crash during CreateVm suggests an issue with the Hyper-V integration layer specific to this build.

**Please do not suggest:**
- Network resets (already attempted)
- Feature reinstallation (already attempted multiple times)
- DISM/SFC repairs (completed with no issues found)
- Virtualization software conflicts (all removed)
- Basic troubleshooting steps (exhaustively tested)

**Requested:**
- Acknowledgment of this as a known issue in build 26200.7171
- Timeline for potential fix or workaround
- Any advanced diagnostic steps specific to WSL service crashes during VM creation
- Alternative solutions that don't require Windows reinstallation

## Additional Information Available
- Full event logs from WSL service crashes
- Detailed vmcompute service logs
- Complete system configuration details
- Registry dumps of WSL-related keys

Thank you for your attention to this issue.

Reproduce the failure with wsl --install -d Ubuntu-24.04 on Windows 11 25H2 build 26200.7171 and focus on the CreateVm stage. Start with the WSL service and vmcompute logs, alongside the Event IDs 7034 and 1000 cited in the report. Done means identifying a confirmed cause and a validated fix or workaround for the service crash.

Written by the indexing model from the issue text.