WSL install fails with errors on Windows 10 guest VM

[sirredbeard]

***** Your Windows build number:** 10.0.16299.15**

*** What you're doing and what's happening:**

I installed Ubuntu from the Windows Store.

When I click Launch, I get this. It's 0x8007007e. I tried searching that error code, nothing very helpful.

I tried enabling WSL in Windows Features:

Which appears to work and then request restart:

But when I restart, it's disabled again:

Attempting to enable the feature via PowerShell gives me this error message:

I am running Windows 10 Educational edition in VMware Fusion 10.1.1 (7520154) on macOS 10.13.2 (17C205) on a MacBook Pro 2015.

The VMware image is configured to support hypervisors in the Guest.

*** What's wrong / what should be happening instead:**

Users cannot install WSL on VMware Fusion guests.

[sirredbeard]

Attempted Troubleshooting

• Uninstalling and reinstalling Ubuntu app
• Reinstalling WSL from Windows Features
• Restarting
• Ensuring virtualization enabled in VMware Fusion
• Enabling Developer Mode
• Installing OpenSUSE Leap 42
  
  
• Running bash and lxrun in cmd in Admin Mode
  

[sirredbeard]

Here is the VMware hardware information.

msinfo.nfo.txt

I would also add that I installed Windows 10 using the Easy Install option in VMware Fusion, if that makes a difference.

[bitcrazed]

Thanks for the great repro capture & sorry you're seeing this.

If LxRun.exe is not available, it looks like WSL itself isn't getting enabled on your machine! We'll get back to you soon.

Note: WSL doesn't use Hyper-V nor any hypervisor infrastructure so this shouldn't be anything to do with nested VM's etc.

[therealkenc]

Ref #2832 #2851 #2818 et al, albeit with slightly different modes of failure. It isn't going to be a "Guest VM" thing (that's my setup here; it works fine). We're flying multiple layers above with this fail. As a quick data point, is the Windows OS in your VM activated? slmgr /xpr or:

PS> Get-CimInstance -ClassName SoftwareLicensingProduct | where PartialProductKey | select Name, ApplicationId, LicenseStatus

Not saying that's the problem; just eliminating a variable. For some reason it is raining "one or more parent features are disabled so parent feature can not be enabled", whereas we weren't seeing them in volume previously.

[sirredbeard]

@therealkenc

Windows is fully activated with a license tied to my Microsoft account.

It sounds most similar to reports in #2832, in particular this one.

I am not getting the same error as in #2851, I get:

'bash' is not recognized as an internal or external command, operable program or batch file.

and #2818 involves upgrading from legacy WSL to the store, I am trying to install WSL on a fresh Windows 10 install.

[bitcrazed]

@sirredbeard - could you please email me: richturn at you know where dot com?

[sirredbeard]

I performed a clean install of Windows 10, enabled WSL from Windows Features before installing Ubuntu from the Store, and have been unable to duplicate the problem.

If the issue occurs again, I will file requested logs.

[bitcrazed]

@sirredbeard - Thanks for letting us know. Glad you're unblocked.

If you or anyone else can repro this issue, please capture the logs below and reach out to taraj at you know where dot com to arrange receipt of said logs so that we can diagnose.

TIA.

[sirredbeard]

@bitcrazed

Unfortunately I had wiped the old image before I got your request for logs. I need a bigger hard drive.

[bitcrazed]

LOL. No problem. Thanks for reporting anyhow.

We do have an internally tracked issue that may describe the root cause of the issue. When fixed, this should resolve at least one possible cause ;)

[ideal2545]

I'm also having this issue, any luck with a fix? I just can't launch bash.exe it just sits at a black screen, and then eventually I get an error. I look and I can't seem to get the service to run.

[Biswa96]

Which virtualization program do you use? I can install WSL in VirutalBox VM (haven't tried Store Apps).

[bitcrazed]

@ideal2545 -

1. Do you have WSL enabled & have you rebooted since enabling? Run the following from an elevated Cmd/PowerShell prompt to double-check you've got WSL enabled:

Get-WindowsOptionalFeature -FeatureName microsoft-windows-subsystem-linux -online

2. Do you have 3rd party Anti Virus installed?
3. What do you see when you run wslconfig /l from Cmd/PowerShell?

[ideal2545]

@Biswa96 I am using VMware fusion pro (8.5 and 10)

@bitcrazed

1. WSL is enabled based on that.
2. No Anti Virus
3. wslconfig /l - results in error: 0x800880005

P.S. I have been able to reproduce this on two machines now - both from clean/scratch without too much configuration.

[papersaltserver]

I have had the same problem on a physical machine having Insider Build 10.0.18356.1
All the symptoms were equal: feature enabled, lxrun not found, wslconfig /l shows no distros. https://aka.ms/wslstore link not working.
To fix this, I've found Ubuntu in Windows Store and installed it. Right after installation, nothing worked as well. Then I've opened Windows Store once again and pressed Launch for Ubuntu there. It has done some initialization and "bash" command started to work after that, however "lxrun" still shows "not found"