WSL: launching newly installed WSL fails - multiple computers - ( same corporation) - Faulting module name: ucrtbase.dll
Version
Microsoft Windows [Version 10.0.19044.1586]
WSL Version
- WSL 2
- WSL 1
Kernel Version
n/a - cannot get that far
Distro Version
n/a - cannot get that far
Other Software
No response
Repro Steps
Two individuals at the same corporation observe the same issue. We use two different methods of installation:
Method 1:
- dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
- dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
- reboot
- WSL /install
Method 2:
- Docker for Windows
- WSL /install
- reboot
- dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
- dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
- reboot
- disable the features
- reboot
- dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
- dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
- then enable HypervisorPlatform, Microsoft-Hyper-V-All, Microsoft-Hyper-V, Microsoft-Hyper-V-Tools-All Microsoft-Hyper-V-Management-PowerShell, Microsoft-Hyper-V-Hypervisor, Microsoft-Hyper-V-Services, Microsoft-Hyper-V-Management-Clients
Expected Behavior
I expected a linux prompt or to be able to get information about wsl by typing wsl.exe --status
Actual Behavior
Windows command prompt
C:\Users\sgutkin>wsl
C:\Users\sgutkin>
Windows Application Log
Faulting application name: wsl.exe, version: 10.0.19041.1566, time stamp: 0x3c6b46b2
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x4a4
Faulting application start time: 0x01d84b72e4bffa34
Faulting application path: C:\WINDOWS\system32\wsl.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 2273027f-8a51-4253-adb0-0c1a018274cf
Faulting package full name:
Faulting package-relative application ID:
Diagnostic Logs
_No response wsl.etl.log _
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15
Thanks for reporting this @sgutkinMadrid.
Based on the logs, it looks like the WSL service is failing to start.
Can you share a screenshot of what ‘optionalfeatures.exe’ shows ? I’m wondering if some features failed to install