Forum Discussion
Trying to install to Windows Server + WSL error
I am trying to deploy to a Windows Server running WSL. I built a new Server 2025 VM and then enabled nested virtualization and installed WSL.
I ran the provisioning script and am getting an error message.
Successfully imported MCC Ubuntu Image into WSL
Validating imported MCC Ubuntu Image : Ubuntu-22.04-Mcc-Base is running as expected in WSL...
Failure: WSL MCC install failed with exception during installation, Return Code: 13631495
System.Management.Automation.RuntimeException: ScriptHalted
[2024-12-10] [11:53:55 AM]
WSL MCC install failed (ReturnCode: )
[2024-12-10] [11:53:55 AM]
Setting InvocationEndTime
Setting InvocationState
Installer return code 0
Any hints on what is going wrong?
1. Verify WSL Configuration
- Ensure that WSL is installed and configured properly:
- Run wsl --list --verbose to check the list of installed distributions and their states.
- Confirm that the imported distribution (Ubuntu-22.04-Mcc-Base) is listed and running.
- Try starting the imported distribution manually:
wsl -d Ubuntu-22.04-Mcc-Base. - If there’s an issue starting the distribution, check the error message for details.
2. Check Nested Virtualization
- Verify that nested virtualization is correctly enabled on the VM:
- On the host machine, run:
Get-VMProcessor -VMName <YourVMName> | Select-Object NestedVirtualizationEnabled. - Ensure it returns True.
- On the host machine, run:
- Confirm that the VM is running Windows Server 2025 and supports WSL.
3. Look Into the Provisioning Script
- Examine the script for potential issues, particularly around:
- Syntax errors.
- External dependencies (e.g., missing packages, network calls, or commands that fail silently).
- If the script is not confidential, share the relevant sections for analysis.
4. Check Return Code 13631495
- This appears to be a non-standard or application-specific error code. Check:
- Documentation or logs for MCC.
- Context within the script to identify which command failed.
- Ensure that WSL is installed and configured properly:
4 Replies
- Andy_Rivas
Microsoft
Can you take a look at the WSL_Mcc_Install_FromRegisteredTask_Status_*.txt file? More details on this error will be there.
1. Verify WSL Configuration
- Ensure that WSL is installed and configured properly:
- Run wsl --list --verbose to check the list of installed distributions and their states.
- Confirm that the imported distribution (Ubuntu-22.04-Mcc-Base) is listed and running.
- Try starting the imported distribution manually:
wsl -d Ubuntu-22.04-Mcc-Base. - If there’s an issue starting the distribution, check the error message for details.
2. Check Nested Virtualization
- Verify that nested virtualization is correctly enabled on the VM:
- On the host machine, run:
Get-VMProcessor -VMName <YourVMName> | Select-Object NestedVirtualizationEnabled. - Ensure it returns True.
- On the host machine, run:
- Confirm that the VM is running Windows Server 2025 and supports WSL.
3. Look Into the Provisioning Script
- Examine the script for potential issues, particularly around:
- Syntax errors.
- External dependencies (e.g., missing packages, network calls, or commands that fail silently).
- If the script is not confidential, share the relevant sections for analysis.
4. Check Return Code 13631495
- This appears to be a non-standard or application-specific error code. Check:
- Documentation or logs for MCC.
- Context within the script to identify which command failed.
For me it appears that the issue was nested virtualization. Looking online this seems to be a common cause of the 13631495 return code. Maybe the script could be updated to add some guidance on resolution of the error?
- Andy_Rivas
Yes, we're working on improving errors for install issues in the GA version.
- Ensure that WSL is installed and configured properly:
