New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't install the windows feature #931

Open
Simbaclaws opened this Issue Aug 18, 2016 · 71 comments

Comments

Projects
None yet
@Simbaclaws

Simbaclaws commented Aug 18, 2016

Whenever I install the windows feature: Windows Subsystem for Linux (Beta). I am prompted to restart. Whenever I restart my computer it hangs for about a second on 56% installing the update and then restarts again. It then tells me that the windows update could not be installed and that it's reverting back changes made.
I've tried installing the windows feature from within both the command prompt and powershell.

I've ran the following commands on the command prompt:
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock" /t REG_DWORD /f /v "AllowDevelopmentWithoutDevLicense" /d "1" DISM /Online /Add-Capability /CapabilityName:Tools.DeveloperMode.Core~~~~0.0.1.0 DISM /Online /Enable-Feature /FeatureName:Microsoft-Windows-Subsystem-Linux/

And the following commands on the powershell:
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock" -Name "AllowDevelopmentWithoutDevLicense" -Value 1 Add-WindowsCapability –Online -Name Tools.DeveloperMode.Core~~~~0.0.1.0 Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

Both which ended in the same result as when trying to do it from within the windows feature menu in windows 10.

I've checked my event log and couldn't find anything related to the update. Neither in my update history. So I used the following command to gather a log file of my windows updates:
Get-WindowsUpdateLog

I will attach the log file to this post.

I expected the installation to go through smoothly so I would be able to start installing bash and start using it.

Instead, windows update tells me that it fails updating.

My windows OS build number is: 14393.51

I hope you guys can help me out, I was thinking: perhaps my anniversary update is corrupt somehow? Causing it to install corrupted files? Or does it install from an external source?

WindowsUpdate.txt

Anyways, I hope you can help me out. I would love to try this feature.

@Simbaclaws

This comment has been minimized.

Show comment
Hide comment
@Simbaclaws

Simbaclaws Aug 18, 2016

I've tried using the fix-it for windows update and it actually fixed a few things but it didn't help for installing this windows feature.

Simbaclaws commented Aug 18, 2016

I've tried using the fix-it for windows update and it actually fixed a few things but it didn't help for installing this windows feature.

@iamrockhopper

This comment has been minimized.

Show comment
Hide comment
@iamrockhopper

iamrockhopper Aug 19, 2016

Exactly same symptoms here. Followed same procedure. No luck.

Windows 10 Enterprise, OS build number 14393.51

Windows Logs under Setup kicks out Event ID 11 - can't install package lxss.

iamrockhopper commented Aug 19, 2016

Exactly same symptoms here. Followed same procedure. No luck.

Windows 10 Enterprise, OS build number 14393.51

Windows Logs under Setup kicks out Event ID 11 - can't install package lxss.

@iamrockhopper

This comment has been minimized.

Show comment
Hide comment
@iamrockhopper

iamrockhopper Aug 21, 2016

The eventlog as follows:

System

  • Provider
    [ Name] Microsoft-Windows-Servicing
    [ Guid] {BD12F3B8-FC40-4A61-A307-B7A013A069C1}
    EventID 11
    Version 0
    Level 0
    Task 1
    Opcode 0
    Keywords 0x8000000000000000
    • TimeCreated
      [ SystemTime] 2016-08-21T20:21:16.572444300Z
      EventRecordID 57
      Correlation
    • Execution
      [ ProcessID] 1896
      [ ThreadID] 1948
      Channel Setup
      Computer IT074269.massey.ac.nz
    • Security
      [ UserID] S-1-5-18
    • UserData
  • CbsUpdateChangeState
    UpdateName Microsoft-Windows-Subsystem-Linux
    PackageIdentifier Microsoft-Windows-Lxss-Optional-Package
    ErrorCode 0x800f0922
    Client Windows Optional Component Manager

iamrockhopper commented Aug 21, 2016

The eventlog as follows:

System

  • Provider
    [ Name] Microsoft-Windows-Servicing
    [ Guid] {BD12F3B8-FC40-4A61-A307-B7A013A069C1}
    EventID 11
    Version 0
    Level 0
    Task 1
    Opcode 0
    Keywords 0x8000000000000000
    • TimeCreated
      [ SystemTime] 2016-08-21T20:21:16.572444300Z
      EventRecordID 57
      Correlation
    • Execution
      [ ProcessID] 1896
      [ ThreadID] 1948
      Channel Setup
      Computer IT074269.massey.ac.nz
    • Security
      [ UserID] S-1-5-18
    • UserData
  • CbsUpdateChangeState
    UpdateName Microsoft-Windows-Subsystem-Linux
    PackageIdentifier Microsoft-Windows-Lxss-Optional-Package
    ErrorCode 0x800f0922
    Client Windows Optional Component Manager
@dkager

This comment has been minimized.

Show comment
Hide comment
@dkager

dkager Aug 31, 2016

I triggered this by:

  • Installing the subsystem, which was successful.
  • Starting Bash, creating a user and updating packages with apt.
  • Using System Restore to go back to an earlier point (for unrelated reasons).
  • Reinstalling the subsystem, since System Restore reverted the installation. Now it fails to install.

dkager commented Aug 31, 2016

I triggered this by:

  • Installing the subsystem, which was successful.
  • Starting Bash, creating a user and updating packages with apt.
  • Using System Restore to go back to an earlier point (for unrelated reasons).
  • Reinstalling the subsystem, since System Restore reverted the installation. Now it fails to install.
@Lutten

This comment has been minimized.

Show comment
Hide comment
@Lutten

Lutten Sep 10, 2016

Same problem here. Everthing was working fine until i had to restore my windows installation to an earlier point. After this i cant reactivate it again. On the required reboot the windows update could not install it and is reverting back changes. Maybe important (or not), the systemlanguage is "german".
This is the win10 logmsg:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Servicing" Guid="{BD12F3B8-FC40-4A61-A307-B7A013A069C1}" />
    <EventID>11</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2016-09-09T21:28:23.175364900Z" />
    <EventRecordID>44</EventRecordID>
    <Correlation />
    <Execution ProcessID="1684" ThreadID="1712" />
    <Channel>Setup</Channel>
    <Computer>T460S</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <CbsUpdateChangeState xmlns="http://manifests.microsoft.com/win/2004/08/windows/setup_provider">
      <UpdateName>Microsoft-Windows-Subsystem-Linux</UpdateName>
      <PackageIdentifier>Microsoft-Windows-Lxss-Optional-Package</PackageIdentifier>
      <ErrorCode>0x800f0922</ErrorCode>
      <Client>Windows Optional Component Manager</Client>
    </CbsUpdateChangeState>
  </UserData>
</Event>"

Lutten commented Sep 10, 2016

Same problem here. Everthing was working fine until i had to restore my windows installation to an earlier point. After this i cant reactivate it again. On the required reboot the windows update could not install it and is reverting back changes. Maybe important (or not), the systemlanguage is "german".
This is the win10 logmsg:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Servicing" Guid="{BD12F3B8-FC40-4A61-A307-B7A013A069C1}" />
    <EventID>11</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2016-09-09T21:28:23.175364900Z" />
    <EventRecordID>44</EventRecordID>
    <Correlation />
    <Execution ProcessID="1684" ThreadID="1712" />
    <Channel>Setup</Channel>
    <Computer>T460S</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <CbsUpdateChangeState xmlns="http://manifests.microsoft.com/win/2004/08/windows/setup_provider">
      <UpdateName>Microsoft-Windows-Subsystem-Linux</UpdateName>
      <PackageIdentifier>Microsoft-Windows-Lxss-Optional-Package</PackageIdentifier>
      <ErrorCode>0x800f0922</ErrorCode>
      <Client>Windows Optional Component Manager</Client>
    </CbsUpdateChangeState>
  </UserData>
</Event>"

@Simbaclaws

This comment has been minimized.

Show comment
Hide comment
@Simbaclaws

Simbaclaws Sep 11, 2016

After trying to talk to tech support from microsoft (in the hopes they might be able to solve my issue) I was redirected almost (I haven't even counted) times from tier 1 to tier 2 to tier 3 etc.... including 3 missed appointed schedules from their end and having to pay around 50 bucks to call from the netherlands to the united states, I got to the point where they wanted me to pay for a professional tech support team that would cost me 500$ to fix the issue.

In which case I decided to reinstalled my windows 10 and everything worked like expected.
I suppose my anniversary update for WSL got corrupted somehow (which I also claimed in the beginning of talking to tech support and in my first post in this page) and apparently I was right.

Great... I payed 50 bucks for nothing and avoided having to pay 500 dollars for something I could easily fix myself....

I honestly can't beleave why they wouldn't agree with me on that it could've been corrupted and suggest me to reinstall but whatever, I'm never going to contact microsoft support again. It's hell. After 8 days I kind of lost my patience....

Simbaclaws commented Sep 11, 2016

After trying to talk to tech support from microsoft (in the hopes they might be able to solve my issue) I was redirected almost (I haven't even counted) times from tier 1 to tier 2 to tier 3 etc.... including 3 missed appointed schedules from their end and having to pay around 50 bucks to call from the netherlands to the united states, I got to the point where they wanted me to pay for a professional tech support team that would cost me 500$ to fix the issue.

In which case I decided to reinstalled my windows 10 and everything worked like expected.
I suppose my anniversary update for WSL got corrupted somehow (which I also claimed in the beginning of talking to tech support and in my first post in this page) and apparently I was right.

Great... I payed 50 bucks for nothing and avoided having to pay 500 dollars for something I could easily fix myself....

I honestly can't beleave why they wouldn't agree with me on that it could've been corrupted and suggest me to reinstall but whatever, I'm never going to contact microsoft support again. It's hell. After 8 days I kind of lost my patience....

@yann-scheydeker

This comment has been minimized.

Show comment
Hide comment
@yann-scheydeker

yann-scheydeker Sep 26, 2016

Hello,

Same issue for me :

Installing the subsystem, which was successful.
Starting Bash, creating a user and updating packages with apt.
Using System Restore to go back to an earlier point (for unrelated reasons).
Reinstalling the subsystem, since System Restore reverted the installation. Now it fails to install.

yann-scheydeker commented Sep 26, 2016

Hello,

Same issue for me :

Installing the subsystem, which was successful.
Starting Bash, creating a user and updating packages with apt.
Using System Restore to go back to an earlier point (for unrelated reasons).
Reinstalling the subsystem, since System Restore reverted the installation. Now it fails to install.
@dfishman222

This comment has been minimized.

Show comment
Hide comment
@dfishman222

dfishman222 Sep 29, 2016

Agree, the folks at MSFT want me to pay for hours of support fixing, but I don't think they know how to fix.

dfishman222 commented Sep 29, 2016

Agree, the folks at MSFT want me to pay for hours of support fixing, but I don't think they know how to fix.

@olfilato

This comment has been minimized.

Show comment
Hide comment
@olfilato

olfilato Oct 30, 2016

Member

Getting the same issue on my desktop (laptop is fine though), no idea how to make it work.

Member

olfilato commented Oct 30, 2016

Getting the same issue on my desktop (laptop is fine though), no idea how to make it work.

@afarra

This comment has been minimized.

Show comment
Hide comment
@afarra

afarra Nov 1, 2016

I have the same issue as well, also caused by going to a system restore after having already installed the windows linux subsystem. I wonder if some files or registry keys need to be deleted/added manually or something. I hope the devs can provide a fix / recommendation for this. I thought I was the only one, but seems it's a common problem for anyone who's done a system restore after installing it.

afarra commented Nov 1, 2016

I have the same issue as well, also caused by going to a system restore after having already installed the windows linux subsystem. I wonder if some files or registry keys need to be deleted/added manually or something. I hope the devs can provide a fix / recommendation for this. I thought I was the only one, but seems it's a common problem for anyone who's done a system restore after installing it.

@imWillX

This comment has been minimized.

Show comment
Hide comment
@imWillX

imWillX Nov 30, 2016

+1

Installing the subsystem, which was successful.
Starting Bash, creating a user and updating packages with apt.
Using System Restore to go back to an earlier point (for unrelated reasons).
Reinstalling the subsystem, since System Restore reverted the installation. Now it fails to install.

imWillX commented Nov 30, 2016

+1

Installing the subsystem, which was successful.
Starting Bash, creating a user and updating packages with apt.
Using System Restore to go back to an earlier point (for unrelated reasons).
Reinstalling the subsystem, since System Restore reverted the installation. Now it fails to install.
@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Dec 1, 2016

Member

Thanks for the bug report and really apologize for the super delay in the response. @jackchammons has a repro of this (thanks, Jack) and we are looking into it. We have also opened a bug on our end to track it. And, please keep the feedback coming. We do appreciate it!

Member

sunilmut commented Dec 1, 2016

Thanks for the bug report and really apologize for the super delay in the response. @jackchammons has a repro of this (thanks, Jack) and we are looking into it. We have also opened a bug on our end to track it. And, please keep the feedback coming. We do appreciate it!

@sunilmut sunilmut added the bug label Dec 1, 2016

@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Dec 5, 2016

Member

@ALL As a workaround, after the system restore and prior to installing bash again, can you try a full uninstall of WSL by doing lxrun /uninstall /full? You will need to have the WSL enabled in the optional features prior to this step.

Member

sunilmut commented Dec 5, 2016

@ALL As a workaround, after the system restore and prior to installing bash again, can you try a full uninstall of WSL by doing lxrun /uninstall /full? You will need to have the WSL enabled in the optional features prior to this step.

@dkager

This comment has been minimized.

Show comment
Hide comment
@dkager

dkager Dec 5, 2016

I re-enabled it, but prior to reboot the lxrun command doesn't seem to be installed yet. Of course after the reboot it rolls back.

dkager commented Dec 5, 2016

I re-enabled it, but prior to reboot the lxrun command doesn't seem to be installed yet. Of course after the reboot it rolls back.

@olfilato

This comment has been minimized.

Show comment
Hide comment
@olfilato

olfilato Dec 5, 2016

Member

Experiencing exact same issue as @dkager , I enable it in the optional features, but it doesn't install properly on reboot.

Member

olfilato commented Dec 5, 2016

Experiencing exact same issue as @dkager , I enable it in the optional features, but it doesn't install properly on reboot.

@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Dec 5, 2016

Member

@dkager - lxrun is part of the optional feature and will only show up after the reboot. Just to be clear, is that not the case for you?

@filoleg - Can you please clarify what you mean by 'doesn't install properly? Is lxrun` not showing up for your after reboot?

Member

sunilmut commented Dec 5, 2016

@dkager - lxrun is part of the optional feature and will only show up after the reboot. Just to be clear, is that not the case for you?

@filoleg - Can you please clarify what you mean by 'doesn't install properly? Is lxrun` not showing up for your after reboot?

@dkager

This comment has been minimized.

Show comment
Hide comment
@dkager

dkager Dec 5, 2016

@sunilmut Upon reboot the installation progress is briefly shown, then it starts to roll back/revert and reboot once more to undo the installation. My guess is that fully uninstalling the feature would work, but it seems like it is stuck halfway with the packages downloaded from the Store but not properly installed.

Are there any logs I can share?

dkager commented Dec 5, 2016

@sunilmut Upon reboot the installation progress is briefly shown, then it starts to roll back/revert and reboot once more to undo the installation. My guess is that fully uninstalling the feature would work, but it seems like it is stuck halfway with the packages downloaded from the Store but not properly installed.

Are there any logs I can share?

@olfilato

This comment has been minimized.

Show comment
Hide comment
@olfilato

olfilato Dec 5, 2016

Member

@sunilmut That is correct. I enable WSL in the optional features (tried through powershell as well, same outcome), it runs installer, then says "reboot to finish installing," it reboots, tries to do install, then quickly flashes "Updates failed to install", and then boots normally. After that, everything is back to square one, WSL feature is unchecked in the optional features, lxrun doesn't show up as a valid command.

Member

olfilato commented Dec 5, 2016

@sunilmut That is correct. I enable WSL in the optional features (tried through powershell as well, same outcome), it runs installer, then says "reboot to finish installing," it reboots, tries to do install, then quickly flashes "Updates failed to install", and then boots normally. After that, everything is back to square one, WSL feature is unchecked in the optional features, lxrun doesn't show up as a valid command.

@afarra

This comment has been minimized.

Show comment
Hide comment
@afarra

afarra Dec 5, 2016

@sunilmut I'm experiencing same issue as @dkager and @sunilmut. I can't uninstall the feature because after system restore, the feature doesn't even show that it is installed, and if I 'install it' so that I can uninstall it with lxrun /uninstall /full the installation doesn't complete because during reboot it says it is being rolled back (as @dkager mentioned) so after reboot it again shows that it is not installed, so can't uninstall it with lxrun

afarra commented Dec 5, 2016

@sunilmut I'm experiencing same issue as @dkager and @sunilmut. I can't uninstall the feature because after system restore, the feature doesn't even show that it is installed, and if I 'install it' so that I can uninstall it with lxrun /uninstall /full the installation doesn't complete because during reboot it says it is being rolled back (as @dkager mentioned) so after reboot it again shows that it is not installed, so can't uninstall it with lxrun

@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Dec 6, 2016

Member

@dkager, @filoleg @afarra - Sorry to hear about your experience.
Can you enable the feature by doing the below from a cmd prompt:
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux
And, after the reboot (and failed installation of the feature), share the log:
%windir%\Logs\DISM\dism.log
We might be able to get a better idea what is going on with the feature installation.

Member

sunilmut commented Dec 6, 2016

@dkager, @filoleg @afarra - Sorry to hear about your experience.
Can you enable the feature by doing the below from a cmd prompt:
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux
And, after the reboot (and failed installation of the feature), share the log:
%windir%\Logs\DISM\dism.log
We might be able to get a better idea what is going on with the feature installation.

@olfilato

This comment has been minimized.

Show comment
Hide comment
@olfilato

olfilato Dec 7, 2016

Member

@sunilmut same thing happened with cmd, archive with my dism.log is attached.
dism.zip

Member

olfilato commented Dec 7, 2016

@sunilmut same thing happened with cmd, archive with my dism.log is attached.
dism.zip

@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Dec 7, 2016

Member

Thanks @filoleg for sending the logs. Just heard from the dism team that we also need the %windir%\logs\cbs logs. Could you provide them too?

Member

sunilmut commented Dec 7, 2016

Thanks @filoleg for sending the logs. Just heard from the dism team that we also need the %windir%\logs\cbs logs. Could you provide them too?

@olfilato

This comment has been minimized.

Show comment
Hide comment
@olfilato

olfilato Dec 7, 2016

Member

@sunilmut no problem.
CBS.zip

Member

olfilato commented Dec 7, 2016

@sunilmut no problem.
CBS.zip

@afarra

This comment has been minimized.

Show comment
Hide comment
@afarra

afarra Dec 7, 2016

@sunilmut I've also ran that command and have the logs (dism.log/cbs.zip) from the failed update. Let me know how I can share them with you/WSL team (I'd rather not attach it here in case there's sensitive info in the logs)

afarra commented Dec 7, 2016

@sunilmut I've also ran that command and have the logs (dism.log/cbs.zip) from the failed update. Let me know how I can share them with you/WSL team (I'd rather not attach it here in case there's sensitive info in the logs)

@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Dec 7, 2016

Member

@filoleg Thanks much, appreciate it.

@afarra - I have shared logs from @filoleg with the DISM team and if they are not conclusive, I might ask for your logs using the Insider email address.

Just out of curiosity, after you restore the system using the system restore, is developer mode enabled at that time?

Member

sunilmut commented Dec 7, 2016

@filoleg Thanks much, appreciate it.

@afarra - I have shared logs from @filoleg with the DISM team and if they are not conclusive, I might ask for your logs using the Insider email address.

Just out of curiosity, after you restore the system using the system restore, is developer mode enabled at that time?

@afarra

This comment has been minimized.

Show comment
Hide comment
@afarra

afarra Dec 7, 2016

@sunilmut Developer mode remains on, yes. But WSL turns back off.

afarra commented Dec 7, 2016

@sunilmut Developer mode remains on, yes. But WSL turns back off.

@afarra

This comment has been minimized.

Show comment
Hide comment
@afarra

afarra Dec 7, 2016

Oh, sorry, you mentioned restore (I read restart). No, after restoring the system with System Restore both WSL and Developer mode are off, I think it was because the system restore was taken before turning on developer mode.

afarra commented Dec 7, 2016

Oh, sorry, you mentioned restore (I read restart). No, after restoring the system with System Restore both WSL and Developer mode are off, I think it was because the system restore was taken before turning on developer mode.

@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Dec 8, 2016

Member

@dkager, @filoleg @afarra and everyone else here who is stuck in the optional feature installation after a system restore, can you please try this workaround:

schtasks /query /tn "\Microsoft\Windows\Windows Subsystem for Linux\AptPackageIndexUpdate"
and share the output in GitHub

  1. schtasks /delete /tn "\Microsoft\Windows\Windows Subsystem for Linux\AptPackageIndexUpdate" /f
    N.B - Do not do this if your optional feature is fully installed and working.
  2. Enable the WSL optional feature (if not already)
  3. Reboot
  4. lxrun /uninstall /full
  5. Install bash
Member

sunilmut commented Dec 8, 2016

@dkager, @filoleg @afarra and everyone else here who is stuck in the optional feature installation after a system restore, can you please try this workaround:

schtasks /query /tn "\Microsoft\Windows\Windows Subsystem for Linux\AptPackageIndexUpdate"
and share the output in GitHub

  1. schtasks /delete /tn "\Microsoft\Windows\Windows Subsystem for Linux\AptPackageIndexUpdate" /f
    N.B - Do not do this if your optional feature is fully installed and working.
  2. Enable the WSL optional feature (if not already)
  3. Reboot
  4. lxrun /uninstall /full
  5. Install bash
@abalakersky

This comment has been minimized.

Show comment
Hide comment
@abalakersky

abalakersky Jan 16, 2018

I am in an identical situation as @pentacore above. Tried all the options and still cannot get it installed.

abalakersky commented Jan 16, 2018

I am in an identical situation as @pentacore above. Tried all the options and still cannot get it installed.

@sunilmut

This comment has been minimized.

Show comment
Hide comment
@sunilmut

sunilmut Jan 16, 2018

Member

@pentacore, @abalakersky - There are many things going on in this issue. So, I am not clear on what is exactly failing for you. Can you please post more details on exactly what is failing? And, also post the output of the command that you are trying and that is failing?

Member

sunilmut commented Jan 16, 2018

@pentacore, @abalakersky - There are many things going on in this issue. So, I am not clear on what is exactly failing for you. Can you please post more details on exactly what is failing? And, also post the output of the command that you are trying and that is failing?

@pentacore

This comment has been minimized.

Show comment
Hide comment
@pentacore

pentacore Jan 16, 2018

@sunilmut well, i try to enable WSL, restart the computer i get back in and its unticked and not installed.

No empty folder to delete in "Tasks" folder, Running the powershell command throws some error about missing or not enabled DISM features and whatnot

pentacore commented Jan 16, 2018

@sunilmut well, i try to enable WSL, restart the computer i get back in and its unticked and not installed.

No empty folder to delete in "Tasks" folder, Running the powershell command throws some error about missing or not enabled DISM features and whatnot

@abalakersky

This comment has been minimized.

Show comment
Hide comment
@abalakersky

abalakersky Jan 16, 2018

abalakersky commented Jan 16, 2018

@pentacore

This comment has been minimized.

Show comment
Hide comment
@pentacore

pentacore Jan 16, 2018

@abalakersky ill try that and report back!

EDIT
That seems to have solved my issues, thanks!

pentacore commented Jan 16, 2018

@abalakersky ill try that and report back!

EDIT
That seems to have solved my issues, thanks!

@EnzeCheng

This comment has been minimized.

Show comment
Hide comment
@EnzeCheng

EnzeCheng Jan 25, 2018

When I want to turn on WSL. Everything works fine, but after reboot update gets stuck on 32%. Then it reboots again and says update cannot complete and undo the update. I tried all method listing here, but none of them works.

EnzeCheng commented Jan 25, 2018

When I want to turn on WSL. Everything works fine, but after reboot update gets stuck on 32%. Then it reboots again and says update cannot complete and undo the update. I tried all method listing here, but none of them works.

@CCarrMcMahon

This comment has been minimized.

Show comment
Hide comment
@CCarrMcMahon

CCarrMcMahon Jan 29, 2018

I have tried everything so far and nothing works. Restarting after checking the box for the feature or using cmd results in it restarting, then restarting again right after. Once I get back on my system, the box is unchecked and I am back to square one. I had also tried a diagnostic boot while only loading the necessary drivers and programs just in case something I had installed was the culprit, it did not work. The only change I saw was a new message that said: "We couldn't complete the features, Undoing changes, Don't turn off your computer." I would like to know if anyone else is having this issue, and see if we can find a solution.

CCarrMcMahon commented Jan 29, 2018

I have tried everything so far and nothing works. Restarting after checking the box for the feature or using cmd results in it restarting, then restarting again right after. Once I get back on my system, the box is unchecked and I am back to square one. I had also tried a diagnostic boot while only loading the necessary drivers and programs just in case something I had installed was the culprit, it did not work. The only change I saw was a new message that said: "We couldn't complete the features, Undoing changes, Don't turn off your computer." I would like to know if anyone else is having this issue, and see if we can find a solution.

@olzk

This comment has been minimized.

Show comment
Hide comment
@olzk

olzk Jan 31, 2018

I have tried everything so far and nothing works. Restarting after checking the box for the feature or using cmd results in it restarting, then restarting again right after. Once I get back on my system, the box is unchecked and I am back to square one. I had also tried a diagnostic boot while only loading the necessary drivers and programs just in case something I had installed was the culprit, it did not work. The only change I saw was a new message that said: "We couldn't complete the features, Undoing changes, Don't turn off your computer." I would like to know if anyone else is having this issue, and see if we can find a solution.

Same for me. I have tried all the methods I could find but nothing helped.
Fresh install win 10 enterprise, version 1709, build 16299.125. Wsl folder doesn't exist.
What i've tried

  1. fixing windows update folders (renaming software distribution and catroot folders)
  2. @abalakersky's solution

olzk commented Jan 31, 2018

I have tried everything so far and nothing works. Restarting after checking the box for the feature or using cmd results in it restarting, then restarting again right after. Once I get back on my system, the box is unchecked and I am back to square one. I had also tried a diagnostic boot while only loading the necessary drivers and programs just in case something I had installed was the culprit, it did not work. The only change I saw was a new message that said: "We couldn't complete the features, Undoing changes, Don't turn off your computer." I would like to know if anyone else is having this issue, and see if we can find a solution.

Same for me. I have tried all the methods I could find but nothing helped.
Fresh install win 10 enterprise, version 1709, build 16299.125. Wsl folder doesn't exist.
What i've tried

  1. fixing windows update folders (renaming software distribution and catroot folders)
  2. @abalakersky's solution
@paralin

This comment has been minimized.

Show comment
Hide comment
@paralin

paralin Feb 8, 2018

I have not been able to find a solution to this problem, even with trying all of the combinations of workarounds given.

paralin commented Feb 8, 2018

I have not been able to find a solution to this problem, even with trying all of the combinations of workarounds given.

@EmhyrVarEmreis

This comment has been minimized.

Show comment
Hide comment
@EmhyrVarEmreis

EmhyrVarEmreis Feb 9, 2018

Me too. None of this workarounds worked.

EmhyrVarEmreis commented Feb 9, 2018

Me too. None of this workarounds worked.

@ynotzort

This comment has been minimized.

Show comment
Hide comment
@ynotzort

ynotzort Feb 14, 2018

Same issue here... I have Win 10 Pro Version 1709, build 16299.194

Edit: The solution from @JenusL worked for me! Just removed the Check Point VPN software and the installation of WSL succeeded.

ynotzort commented Feb 14, 2018

Same issue here... I have Win 10 Pro Version 1709, build 16299.194

Edit: The solution from @JenusL worked for me! Just removed the Check Point VPN software and the installation of WSL succeeded.

@JenusL

This comment has been minimized.

Show comment
Hide comment
@JenusL

JenusL Feb 15, 2018

Same issue here. Pretty fresh install and currently running 16299.248 and I don't think I've restored any time.
The %windir%\System32\Tasks\Microsoft\Windows\Windows Subsystem for Linux doesn't exist on my system so it has to be something else.
This has to be a new regression given the amount of comments here in the last weeks.

JenusL commented Feb 15, 2018

Same issue here. Pretty fresh install and currently running 16299.248 and I don't think I've restored any time.
The %windir%\System32\Tasks\Microsoft\Windows\Windows Subsystem for Linux doesn't exist on my system so it has to be something else.
This has to be a new regression given the amount of comments here in the last weeks.

@JenusL

This comment has been minimized.

Show comment
Hide comment
@JenusL

JenusL Feb 21, 2018

@sunilmut Got any new workaround for all of us that are unable to install the WSL feature in 2018?
I have tried everything I can think of and nothing has worked.
Just let me know if you need anything from me.

JenusL commented Feb 21, 2018

@sunilmut Got any new workaround for all of us that are unable to install the WSL feature in 2018?
I have tried everything I can think of and nothing has worked.
Just let me know if you need anything from me.

@JenusL

This comment has been minimized.

Show comment
Hide comment
@JenusL

JenusL Feb 22, 2018

Solved it!
After a lot of detective work I found this in the CBS.log...
2018-02-21 21:14:03, Error [0x01805b] CSI 0000004e (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

So I guessed it had something to do with Network Adapters. I only have one physical network card and a Checkpoint VPN adapter. My first instinct was to uninstall the VPN and then try to install WSL again but before I did that I went to the Checkpoint site to see if there was a new version out...
And BINGO! E80.80 of Checkpoint VPN had the following in the change log:
Resolved an issue when some third-party products are unable to create or delete network adapters.

So instead of removing the VPN I decided to update it to E80.80 and after that WSL installed without problems.
Hope this can help some more people as well.

JenusL commented Feb 22, 2018

Solved it!
After a lot of detective work I found this in the CBS.log...
2018-02-21 21:14:03, Error [0x01805b] CSI 0000004e (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

So I guessed it had something to do with Network Adapters. I only have one physical network card and a Checkpoint VPN adapter. My first instinct was to uninstall the VPN and then try to install WSL again but before I did that I went to the Checkpoint site to see if there was a new version out...
And BINGO! E80.80 of Checkpoint VPN had the following in the change log:
Resolved an issue when some third-party products are unable to create or delete network adapters.

So instead of removing the VPN I decided to update it to E80.80 and after that WSL installed without problems.
Hope this can help some more people as well.

@mingyuea

This comment has been minimized.

Show comment
Hide comment
@mingyuea

mingyuea Mar 6, 2018

@JenusL Hey there, so I seem to have the same problem as you did. I looked at your solution, and also viewed my CBS.log (I had no idea what that was before this), and found the same error. I don't have a Checkpoint VPN though, so I don't think that's causing the problem. I do have a Qualcomm Wireless Network Adapter. Should I try updating that?

mingyuea commented Mar 6, 2018

@JenusL Hey there, so I seem to have the same problem as you did. I looked at your solution, and also viewed my CBS.log (I had no idea what that was before this), and found the same error. I don't have a Checkpoint VPN though, so I don't think that's causing the problem. I do have a Qualcomm Wireless Network Adapter. Should I try updating that?

@JenusL

This comment has been minimized.

Show comment
Hide comment
@JenusL

JenusL Mar 6, 2018

@mingyuea That sounds strange... Can you please post your error message?

JenusL commented Mar 6, 2018

@mingyuea That sounds strange... Can you please post your error message?

@mingyuea

This comment has been minimized.

Show comment
Hide comment
@mingyuea

mingyuea Mar 6, 2018

@JenusL @sunilmut So I've been trying to install WSL after I updated my network card drivers, but I still get the error of not being able to install it, and Windows rolling back. The log from the event viewer has this at 7:45:43 AM

Update Microsoft-Windows-Subsystem-Linux of package Microsoft-Windows-Lxss-Optional-Package failed to be turned on. Status: 0x800f0922.

After checking the CBS.log for more info, I found this error at around the same time:

2018-03-06 07:45:25, Error [0x01805b] CSI 0000004d (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

Which is pretty much the same error you got. However, I don't have any VPN installed like you do, so I don't know what could be causing my error. I definitely don't have the WSL folder anywhere either.

UPDATE: I looked down further in the CBS.log, and found maybe more specifics about the error:

`2018-03-06 07:45:35, Error CSI 00000070 (F) Installer: Network Drivers Binary Name: NetSetupAI.dll ErrorCode: 80070005 Phase: 31 Mode: Delta Component: NONE[gle=0x80004005]

2018-03-06 07:45:35, Info CSI 00000071 ==Error Summary End==

2018-03-06 07:45:35, Error CBS Startup: Failed to process advanced operation queue, startupPhase: 0. A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]`

After that, the computer starts rolling back the transactions

mingyuea commented Mar 6, 2018

@JenusL @sunilmut So I've been trying to install WSL after I updated my network card drivers, but I still get the error of not being able to install it, and Windows rolling back. The log from the event viewer has this at 7:45:43 AM

Update Microsoft-Windows-Subsystem-Linux of package Microsoft-Windows-Lxss-Optional-Package failed to be turned on. Status: 0x800f0922.

After checking the CBS.log for more info, I found this error at around the same time:

2018-03-06 07:45:25, Error [0x01805b] CSI 0000004d (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

Which is pretty much the same error you got. However, I don't have any VPN installed like you do, so I don't know what could be causing my error. I definitely don't have the WSL folder anywhere either.

UPDATE: I looked down further in the CBS.log, and found maybe more specifics about the error:

`2018-03-06 07:45:35, Error CSI 00000070 (F) Installer: Network Drivers Binary Name: NetSetupAI.dll ErrorCode: 80070005 Phase: 31 Mode: Delta Component: NONE[gle=0x80004005]

2018-03-06 07:45:35, Info CSI 00000071 ==Error Summary End==

2018-03-06 07:45:35, Error CBS Startup: Failed to process advanced operation queue, startupPhase: 0. A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]`

After that, the computer starts rolling back the transactions

@JenusL

This comment has been minimized.

Show comment
Hide comment
@JenusL

JenusL Mar 6, 2018

@mingyuea I'm not sure I can help you... But just in case, could you run Get-NetAdapter in PowerShell to make sure you only have one adapter and that it's the physical one.
This issue seems to have started with Fall Creators Update. Maybe MS changed something with Network Drivers and now hardware companies need to update their drivers to be compatible again.

JenusL commented Mar 6, 2018

@mingyuea I'm not sure I can help you... But just in case, could you run Get-NetAdapter in PowerShell to make sure you only have one adapter and that it's the physical one.
This issue seems to have started with Fall Creators Update. Maybe MS changed something with Network Drivers and now hardware companies need to update their drivers to be compatible again.

@mingyuea

This comment has been minimized.

Show comment
Hide comment
@mingyuea

mingyuea Mar 7, 2018

@JenusL @sunilmut So I ran that command, and I do have two adapters, one for wi-fi and one for ethernet. I've updated both, but it still doesn't work

mingyuea commented Mar 7, 2018

@JenusL @sunilmut So I ran that command, and I do have two adapters, one for wi-fi and one for ethernet. I've updated both, but it still doesn't work

@gyroknight

This comment has been minimized.

Show comment
Hide comment
@gyroknight

gyroknight Mar 25, 2018

I'm getting the same issue as @mingyuea, but only after uninstalling WSL and trying to re-enable it again. The error is exactly the same in CBS.log with the same Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) error. There is no Windows Subsystem for Linux folder in %windir%\System32\Tasks\Microsoft\Windows and setting those services to automatic did not change anything; the services were already started.

gyroknight commented Mar 25, 2018

I'm getting the same issue as @mingyuea, but only after uninstalling WSL and trying to re-enable it again. The error is exactly the same in CBS.log with the same Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) error. There is no Windows Subsystem for Linux folder in %windir%\System32\Tasks\Microsoft\Windows and setting those services to automatic did not change anything; the services were already started.

@maxgrass

This comment has been minimized.

Show comment
Hide comment
@maxgrass

maxgrass Mar 28, 2018

2018-03-27 18:31:53, Info                  CSI    0000004c@2018/3/27:16:31:53.141 CSI Advanced installer perf trace:

CSIPERF:AIDONE;{a111f280-5923-47c0-9a68-d0bafb577901};(null);50635us
2018-03-27 18:31:53, Info                  CSI    0000004d End executing advanced installer (sequence 0)
    Completion status: HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) 

2018-03-27 18:31:53, Error      [0x01805b] CSI    0000004e (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
2018-03-27 18:31:53, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.

Removed possible candidates: Privatefirewall (Privacyware) and Shrewsoft VPN. And installation worked. Thanks for nice logging 👍
Maybe this must be added to official MS Docs/Page for installation.

maxgrass commented Mar 28, 2018

2018-03-27 18:31:53, Info                  CSI    0000004c@2018/3/27:16:31:53.141 CSI Advanced installer perf trace:

CSIPERF:AIDONE;{a111f280-5923-47c0-9a68-d0bafb577901};(null);50635us
2018-03-27 18:31:53, Info                  CSI    0000004d End executing advanced installer (sequence 0)
    Completion status: HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) 

2018-03-27 18:31:53, Error      [0x01805b] CSI    0000004e (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
2018-03-27 18:31:53, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.

Removed possible candidates: Privatefirewall (Privacyware) and Shrewsoft VPN. And installation worked. Thanks for nice logging 👍
Maybe this must be added to official MS Docs/Page for installation.

@cym104

This comment has been minimized.

Show comment
Hide comment
@cym104

cym104 Mar 29, 2018

Windows 10 ENT x64 build 17127, NICs are Killer E2400 GE & Killer Wireless 1535 WLAN.
When tring to enable WSL, the install fails after first reboot and then rolls back.

The following message is recorded in CBS.log

2018-03-22 20:54:37, Info                  CSI    00000121 Begin executing advanced installer phase 31 index 0 (sequence 0)
    Old component: [l:0]''
    New component: [l:0]''
    Install mode: delta
    Smart installer: true
    Installer ID: {a111f280-5923-47c0-9a68-d0bafb577901}
    Installer name: 'Network Drivers'
2018-03-22 20:54:37, Info                  CSI    00000122 Begin NetSetup servicing operation
2018-03-22 20:54:37, Info                  CSI    00000123 Begin loading the binding engine
2018-03-22 20:54:37, Info                  CSI    00000124 Finished loading the binding engine - elapsed time: 15ms
2018-03-22 20:54:37, Info                  CSI    00000125 Begin calculating changes
2018-03-22 20:54:37, Info                  CSI    00000126 Installing network driver ms_vfpext
2018-03-22 20:54:37, Info                  CSI    00000127 Installing network driver netAdapterDriver-{72FEF6B3-26F8-42AA-A41C-5B491CBB0914}
2018-03-22 20:54:37, Info                  CSI    00000128 Installing network driver vms_pp
2018-03-22 20:54:40, Info                  CSI    00000129 Error while printing exception records to this log file
2018-03-22 20:54:40, Info                  CSI    0000012a@2018/3/22:12:54:40.193 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{a111f280-5923-47c0-9a68-d0bafb577901};(null);2981555us
2018-03-22 20:54:40, Info                  CSI    0000012b End executing advanced installer (sequence 0)
    Completion status: HRESULT_FROM_WIN32(1726) 
2018-03-22 20:54:40, Error      [0x01805b] CSI    0000012c (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(1726).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

I'm not using 3rd party AV/firewall software(only windows defener), and there's no VPN application installed.
I tired to manually install this vms_pp driver with:
netcfg -l C:\Windows\WinSxS\amd64_dual_wvms_pp.inf_31bf3856ad364e35_10.0.17120.1_none_04bc0d690be4e471\wvms_pp.inf -c p -i vms_pp
but it simpley give me a error 0xe000022f.

I've already tried:

  • made sure VT-x and VT-d enabled in BIOS
  • remove any other virt soft (e.g. VMware workstation).
  • remove any software that might modify network stack.
  • DISM and sfc
  • update driver for all NICs.
  • rollback driver for all NICs to windows default.
  • disable all NICs in BIOS.
  • reset network from Settings app.

cym104 commented Mar 29, 2018

Windows 10 ENT x64 build 17127, NICs are Killer E2400 GE & Killer Wireless 1535 WLAN.
When tring to enable WSL, the install fails after first reboot and then rolls back.

The following message is recorded in CBS.log

2018-03-22 20:54:37, Info                  CSI    00000121 Begin executing advanced installer phase 31 index 0 (sequence 0)
    Old component: [l:0]''
    New component: [l:0]''
    Install mode: delta
    Smart installer: true
    Installer ID: {a111f280-5923-47c0-9a68-d0bafb577901}
    Installer name: 'Network Drivers'
2018-03-22 20:54:37, Info                  CSI    00000122 Begin NetSetup servicing operation
2018-03-22 20:54:37, Info                  CSI    00000123 Begin loading the binding engine
2018-03-22 20:54:37, Info                  CSI    00000124 Finished loading the binding engine - elapsed time: 15ms
2018-03-22 20:54:37, Info                  CSI    00000125 Begin calculating changes
2018-03-22 20:54:37, Info                  CSI    00000126 Installing network driver ms_vfpext
2018-03-22 20:54:37, Info                  CSI    00000127 Installing network driver netAdapterDriver-{72FEF6B3-26F8-42AA-A41C-5B491CBB0914}
2018-03-22 20:54:37, Info                  CSI    00000128 Installing network driver vms_pp
2018-03-22 20:54:40, Info                  CSI    00000129 Error while printing exception records to this log file
2018-03-22 20:54:40, Info                  CSI    0000012a@2018/3/22:12:54:40.193 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{a111f280-5923-47c0-9a68-d0bafb577901};(null);2981555us
2018-03-22 20:54:40, Info                  CSI    0000012b End executing advanced installer (sequence 0)
    Completion status: HRESULT_FROM_WIN32(1726) 
2018-03-22 20:54:40, Error      [0x01805b] CSI    0000012c (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT HRESULT_FROM_WIN32(1726).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

I'm not using 3rd party AV/firewall software(only windows defener), and there's no VPN application installed.
I tired to manually install this vms_pp driver with:
netcfg -l C:\Windows\WinSxS\amd64_dual_wvms_pp.inf_31bf3856ad364e35_10.0.17120.1_none_04bc0d690be4e471\wvms_pp.inf -c p -i vms_pp
but it simpley give me a error 0xe000022f.

I've already tried:

  • made sure VT-x and VT-d enabled in BIOS
  • remove any other virt soft (e.g. VMware workstation).
  • remove any software that might modify network stack.
  • DISM and sfc
  • update driver for all NICs.
  • rollback driver for all NICs to windows default.
  • disable all NICs in BIOS.
  • reset network from Settings app.
@chunkyen

This comment has been minimized.

Show comment
Hide comment
@chunkyen

chunkyen May 21, 2018

I have encountered the same issue with subsystem for Linux rolling back each time after reboot but none of the solution listed here worked for me.
It turns out that Checkpoint VPN is the culprit and uninstalling it works for me.
Cheers

chunkyen commented May 21, 2018

I have encountered the same issue with subsystem for Linux rolling back each time after reboot but none of the solution listed here worked for me.
It turns out that Checkpoint VPN is the culprit and uninstalling it works for me.
Cheers

@q587p

This comment has been minimized.

Show comment
Hide comment
@q587p

q587p May 27, 2018

Not running server version, but have same problem as #931 (comment)

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : Feature name Microsoft-Windows-Subsystem-Linux is unknown.
At line:1 char:1
+ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

Sysinfo:

systeminfo | Select-String "^OS Name","^OS Version"

OS Name:                   Майкрософт Windows 10 Pro
OS Version:                10.0.16299 N/A Build 16299

q587p commented May 27, 2018

Not running server version, but have same problem as #931 (comment)

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : Feature name Microsoft-Windows-Subsystem-Linux is unknown.
At line:1 char:1
+ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

Sysinfo:

systeminfo | Select-String "^OS Name","^OS Version"

OS Name:                   Майкрософт Windows 10 Pro
OS Version:                10.0.16299 N/A Build 16299
@newlukai

This comment has been minimized.

Show comment
Hide comment
@newlukai

newlukai Jun 1, 2018

Also for me it's not possible to install WSL. Each time I tried to activate it, it was rolled back during reboot. I found the following line in the CBS logs:
2018-06-01 07:04:05, Error [0x018020] CSI 00000041 (F) Failed execution of queue item Installer: Mof ({9f4ec79f-3a97-4772-b635-2899468900a2}) with HRESULT 8004402f [Error,Facility=FACILITY_ITF,Code=16431 (0x402f)]. Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

newlukai commented Jun 1, 2018

Also for me it's not possible to install WSL. Each time I tried to activate it, it was rolled back during reboot. I found the following line in the CBS logs:
2018-06-01 07:04:05, Error [0x018020] CSI 00000041 (F) Failed execution of queue item Installer: Mof ({9f4ec79f-3a97-4772-b635-2899468900a2}) with HRESULT 8004402f [Error,Facility=FACILITY_ITF,Code=16431 (0x402f)]. Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

@mberasategi

This comment has been minimized.

Show comment
Hide comment
@mberasategi

mberasategi Jun 5, 2018

Just for the record, @abalakersky's solution worked for me. Thanks!

mberasategi commented Jun 5, 2018

Just for the record, @abalakersky's solution worked for me. Thanks!

@BlackstarSolar

This comment has been minimized.

Show comment
Hide comment
@BlackstarSolar

BlackstarSolar Jun 5, 2018

I removed CheckPoint VPN and was able to install WSL successfully. Reinstalled CheckPoint VPN afterwards with no issues.

BlackstarSolar commented Jun 5, 2018

I removed CheckPoint VPN and was able to install WSL successfully. Reinstalled CheckPoint VPN afterwards with no issues.

@Fierr

This comment has been minimized.

Show comment
Hide comment
@Fierr

Fierr Aug 16, 2018

Wanted to share my experience with this error after having tried all of the above. After removing my antivirus and firewall (Zonealarm & Avast; disabling didn't help), I was successfully able to install WSL.

Fierr commented Aug 16, 2018

Wanted to share my experience with this error after having tried all of the above. After removing my antivirus and firewall (Zonealarm & Avast; disabling didn't help), I was successfully able to install WSL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment