Installation Failed with Error 0x8007019e

[0NG]

• Your Windows build number:
  Microsoft Windows [版本 10.0.17107.1000]

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

D:\>ubuntu
Installing, this may take a few minutes...
Installation Failed!
Error: 0x8007019e
Press any key to continue...

• What's wrong / what should be happening instead:
  Cannot run ubuntu and opensuse

I have tried Repair, Reset and reinstall these two apps, but the problem is still there. Is there anything I can do to check the detail of the problem?

[benhillis]

Could you please collect traces while trying to install?

https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs

[0NG]

I have collected some yesterday (if no mistake). However, ubuntu works again today. Sorry for I cannot reproduce it now.
detail.zip

[ItaiSent]

@0NG Make sure Windows Subsystem for Linux is checked.

[0NG]

Yes, it was checked at first, since I have used WSL for a long time. When the problem occured but I couldn't find any solution, I tried to uncheck it, test if ubuntu work, and then checked it again, but the problem was still there. I think it may not because of this Windows feature unchecked.

[benhillis]

Yep somehow the WSL feature was disabled, that's what error 0x8007019e means.

[0NG]

Thanks!

[krysjez]

In case it helps someone, I had the same error despite having WSL checked.
Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

[0NG]

@krysjez Aha! Yes, it also worked for me! Just two weeks ago, the error came up again, and I solved it by the same steps.

[NoahNye]

@ItaiSent
thanks ,it's working

[michellaevens]

Same issue here. The Windows Susbsystem for Linux feature was turned off. I guess that happened during a Windows update. However, I had another error : 0x800700b7. I could fix it by reinstalling the Ubuntu app from the store.

[janbernloehr]

I am not so happy with this having been closed without any changes. Can't we add a more descriptive error message which points the user into the right direction?

[psychohamster]

I have a similar scenario to @michellaevens except instead of a second error code, I get a GSOD - depending on the exact invocation means, it's either a SYSTEM_SERVICE_EXCEPTION in hbflt.sys or a SYSTEM_THREAD_EXCPEPTION_NOT_HANDLED in fltmgr.sys
This has been happening for the last several slow ring builds, plus the official release on Monday.
Anyone else seeing the same thing?

[Brian-Perkins]

It appears hbflt.sys is a BitDefender file-system filter, and there have been a couple of other reports (#1750, #2323) involving BitDefender. Those were usability issues instead of crashes, but possibly all related.

[psychohamster]

@Brian-Perkins - Aha - You are correct! Uninstalling BitDefender allowed WSL to run. I'll work on seeing if there is an updated version of it available to get pushed out to our dev machines. Had been working until roughly mid-march builds, if I recall correctly.

[AGiantSquid]

In case this helps anyone else, I had this problem show up today after using WSL for months with no problems. I recently changed my startup to automatically open ConEmu on system boot. All I did to rectify this was to close all open terminals. I reopened ConEmu and now it seems to be working fine. Perhaps trying to open WSL too early in the boot process can cause this error.

[AnthonySteele]

The happened to me today. I have been using WSL daily, suddenly it does not work. The Windows feature is checked.

to: fix: uncheck the feature, reboot, check the feature, reboot.

[JuKu]

I get the same error, but my linux subsystem is already installed and enabled.

[AnthonySteele]

This comes and goes on mine.

[ghost]

I get a same error in Win 10 1803. I am sad...

[JuKu]

@benhillis Maybe this issue should be reopened?

[ghost]

I don't know... I will be wait for bugfix... ⁣Отправлено с помощью BlueMail ​ На 3 июля 2018 г., 22:46, в 22:46, JuKu <[email protected]> написал:п>@benhillis Maybe this issue should be reopened?

…

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #2982 (comment)

[molnare]

@AnthonySteele this reminds me of The IT Crowd: "Have you tried turning it off and on again?"
But I must say... It worked! 👍

[AnthonySteele]

I have seen a similar error a few more times, usually right after the machine was started up.
In those cases, I tried again 5 minutes later and it worked then. Without a re-install.

[jlng23]

#2576
[solved]

[ghost]

你需要在"开启/关闭Windows功能"处启用WSL。

[checor]

I think this should to the common troubleshooting on: https://docs.microsoft.com/en-us/windows/wsl/install-win10

[stsands]

@krysjez, thank you!

[SalamiArmy]

I think I'm the first person in this thread for whom unchecking and re-checking didn't work. I've tried Ubuntu 18, OpenSuse and Debian

[JuKu]

@SalamiArmy This didn't work for me, too.
But after a while (and many windows updates) it works now without doing anything.

[CarlosOrtiz4200]

@0NG Make sure Windows Subsystem for Linux is checked.

i love you bro

[nuno-andre]

Rebooting only after enabling worked for me:

1. Run as administrator:

   disable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online -norestart
   enable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online 
   

2. Reboot.

Or as a script:

#requires -runasadministrator
disable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online -norestart
enable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online -norestart
restart-computer -force

[dksadiq]

Rebooting only after enabling worked for me:

1. Run as administrator:

   disable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online -norestart
   enable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online 
   

2. Reboot.

Running the second line of this as Admin on PowerShell and then rebooting right afterwards also worked for me.

[lawrencekiba]

@0NG Make sure Windows Subsystem for Linux is checked.

This worked like a charm for me for now.

[niusealeo]

@JuKu Did you discover what the problem was?
I currently have the same issue

[pra17dod]

@0NG Make sure Windows Subsystem for Linux is checked.

Thanks man!! It worked

[KasperKivimaeki]

I had this error after WSL had crashed/frozen.

My wsl crashed after I had opened two Ubuntu wsl terminals and moved some files to its filesystem with file explorer. Afterwards I got this error everytime I opened WSL. I had used Ubuntu WSL previously for years. I hope to find out how to properly reproduce this.

I solved this problem by disabling and enabling the feature and then rebooting.

[anony436]

In case it helps someone, I had the same error despite having WSL checked.
Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

I have an issue of automatically unchecking wsl after restart. Error when restart: we couldn't complete the features undoing changes..

[anony436]

In case it helps someone, I had the same error despite having WSL checked.
Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

I have an issue of automatically unchecking wsl after restart. Error when restart: we couldn't complete the features undoing changes..

[anony436]

I think I'm the first person in this thread for whom unchecking and re-checking didn't work. I've tried Ubuntu 18, OpenSuse and Debian

I have an issue of automatically unchecking wsl after restart. Error when restart: we couldn't complete the features undoing changes..

[deathblade287]

In case it helps someone, I had the same error despite having WSL checked.
Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

Thank You So Much... This fixed my error

[yaoayh]

It's helped for Me also, just checked it and restart pc.
I used UbuntuLTD20.4
Thx

[catafest]

Windows Subsystem for Linux is checked if is , uncheck and check again ... then need to be restart in order to have LxssManager on Services.msc, then install Ubuntu app from ms store ...

[measproem]

@0NG Make sure Windows Subsystem for Linux is checked.

It works for me thank

[tuanluu-agilityio]

In case it helps someone, I had the same error despite having WSL checked. Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

Work like a charm!

[Newtoxton]

Rebooting only after enabling worked for me:

1. Run as administrator:

   disable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online -norestart
   enable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online 
   

2. Reboot.

Or as a script:

#requires -runasadministrator
disable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online -norestart
enable-windowsoptionalfeature -featurename 'microsoft-windows-subsystem-linux' -online -norestart
restart-computer -force

This worked for me

[Vasavi00]

Have the virtual machine checked... This helped

[adibenc]

thank you @ItaiSent

[firefighter-19]

Windows 11. All of the suggestions above didn't help -_- still error.

[starktonys]

1.win+x，choose Windows PowerShell（admin）
2. input that Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
3. choose Y wait reboot

[slyfox1186]

I have tried everything suggested here and nothing works. I reset my PC due to terrible performance and webpages not loading anymore and now I can no longer use WSL.

This really can not be closed until this is fixed as this is a level I would call OS BREAKING.

However, I found one solution.

Download the latest RELEASE version of WSL from GitHub github.com/microsoft/WSL/releases/tag/2.2.4

I used the MSI installer x64. And lo and behold it immediately started working without restarting the PC.

[lukethomas1]

Tried unchecking, rebooting, re-checking, didn't work.

Tried @Newtoxton 's method, didn't work.

Finally, tried @slyfox1186 's method, and it immediately started working, no reboot needed.

[Strafe153]

@slyfox1186 I've been trying to fix the issue after the complete PC reset for about an hour and nothing had helped, until I found your solution and it worked. Liked the comment, lifesaver