Skip to content

Can't upgrade kali-linux to wsl2 #6875

New issue
New issue
Closed
Closed
Can't upgrade kali-linux to wsl2#6875

Description

@sagniksen31
Sagnik Sen (sagniksen31)
opened on Apr 27, 2021

Hello,
I am Having a issue that I can't Upgrade my kali linux to wsl2
Here is the output when i try to upgrade it
PS C:\Windows\system32> wsl --set-default-version 2 For information on key differences with WSL 2 please visit https://aka.ms/wsl2 PS C:\Windows\system32> wsl --set-version kali-linux 2 Conversion in progress, this may take a few minutes... For information on key differences with WSL 2 please visit https://aka.ms/wsl2 The operation could not be started because a required feature is not installed. PS C:\Windows\system32>

Can Anyone explain what am I doing Wrong
As I have enabled virtualisation in BIOS and enadbled WSL and Virtual Machine platform.
Please help I am stuck on it for days.

PC Specs-
GPU-Nvidia GT610 2GB
CPU - Intel i3 3220
Ram-4GB

Virtualization is also enabled.

Activity

  1. sagniksen31 commented on Apr 27, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 27, 2021
    Author

    I am on windows 10 pro And the OS build is latest

  2. benhillis commented on Apr 27, 2021

    @benhillis
    Ben Hillis (benhillis)
    on Apr 27, 2021
    Member

    Sagnik Sen (@sagniksen31) - I suspect virtualization is not enabled in your BIOS.

  3. sagniksen31 commented on Apr 27, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 27, 2021
    Author

    Sagnik Sen (@sagniksen31) - I suspect virtualization is not enabled in your BIOS.

    No, It is enabled.I have checked it 3 times.

  4. benhillis commented on Apr 27, 2021

    @benhillis
    Ben Hillis (benhillis)
    on Apr 27, 2021
    Member

    Sagnik Sen (@sagniksen31) - could you share the output of msinfo32.exe?

  5. sagniksen31 commented on Apr 27, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 27, 2021
    Author

    Sagnik Sen (@sagniksen31) - could you share the output of msinfo32.exe?

    Screenshot (152)

  6. sagniksen31 commented on Apr 28, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 28, 2021
    Author

    This is my msinfo32 ss

  7. sagniksen31 commented on Apr 28, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 28, 2021
    Author

    Please help I am stuck in it for days

  8. onomatopellan commented on Apr 29, 2021

    @onomatopellan
    Jonathan (onomatopellan)
    on Apr 29, 2021

    Are you using any other virtualization solution like VirtualBox or VMware? It seems the hypervisor has been disabled even if you have virtualization enabled in the BIOS.

    Try opening an elevated cmd and run bcdedit /set hypervisorlaunchtype auto. After reboot msinfo32 should show "Hypervisor has been detected" and WSL2 should work.

  9. sagniksen31 commented on Apr 29, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 29, 2021
    Author

    Are you using any other virtualization solution like VirtualBox or VMware? It seems the hypervisor has been disabled even if you have virtualization enabled in the BIOS.

    Try opening an elevated cmd and run bcdedit /set hypervisorlaunchtype auto. After reboot msinfo32 should show "Hypervisor has been detected" and WSL2 should work.

    Yes, I use bluestacks beta 5, and VMware, So if I enable Hypervisor I won't be able to use bluestacks beta 5 .So is it only the solution?

  10. sagniksen31 commented on Apr 29, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 29, 2021
    Author

    Are you using any other virtualization solution like VirtualBox or VMware? It seems the hypervisor has been disabled even if you have virtualization enabled in the BIOS.

    Try opening an elevated cmd and run bcdedit /set hypervisorlaunchtype auto. After reboot msinfo32 should show "Hypervisor has been detected" and WSL2 should work.

    Did as you told so, still no change

  11. onomatopellan commented on Apr 30, 2021

    @onomatopellan
    Jonathan (onomatopellan)
    on Apr 30, 2021

    Yes, I use bluestacks beta 5, and VMware, So if I enable Hypervisor I won't be able to use bluestacks beta 5 .So is it only the solution?

    Correct. You need the hypervisor running if you want to use WSL2. Read this for a working BlueStacks under hyper-v. Latest version of VMware >15.5 already works under hyper-v.

    Did as you told so, still no change

    Can you post the output of running bcdedit?

  12. sagniksen31 commented on Apr 30, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 30, 2021
    Author

    Yes, I use bluestacks beta 5, and VMware, So if I enable Hypervisor I won't be able to use bluestacks beta 5 .So is it only the solution?

    Correct. You need the hypervisor running if you want to use WSL2. Read this for a working BlueStacks under hyper-v. Latest version of VMware >15.5 already works under hyper-v.

    Did as you told so, still no change

    Can you post the output of running bcdedit?

    So, after enabling the hypervisor, I found that it shows "a hypervisor is detected " in msinfo32 and then I tried to upgrade kali Linux to wsl2, but still got the same error

  13. onomatopellan commented on Apr 30, 2021

    @onomatopellan
    Jonathan (onomatopellan)
    on Apr 30, 2021

    Now that you are under the hypervisor you can follow the steps for installing WSL2

  14. sagniksen31 commented on Apr 30, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 30, 2021
    Author

    Now that you are under the hypervisor you can follow the steps for installing WSL2

    So this should do the work?

  15. onomatopellan commented on Apr 30, 2021

    @onomatopellan
    Jonathan (onomatopellan)
    on Apr 30, 2021

    Yes, pay special attention to step 3 and 4.

  16. sagniksen31 commented on Apr 30, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 30, 2021
    Author

    Thanks, If I have any issues I will leave a comment here

  17. sagniksen31 commented on Apr 30, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 30, 2021
    Author

    Yes, pay special attention to step 3 and 4.

    `Installing, this may take a few minutes...
    WslRegisterDistribution failed with error: 0x80370114
    Error: 0x80370114 The operation could not be started because a required feature is not installed.

    Press any key to continue...`

    Still This Error :(

    The Machine is Talking about which feature?

  18. onomatopellan commented on Apr 30, 2021

    @onomatopellan
    Jonathan (onomatopellan)
    on Apr 30, 2021

    Sagnik Sen (@sagniksen31) You are now at this point #4626. Try gajama solution as it helped lots of people.

  19. sagniksen31 commented on Apr 30, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on Apr 30, 2021
    Author

    Sagnik Sen (@sagniksen31) You are now at this point #4626. Try gajama solution as it helped lots of people.

    I also tried it, It didn't work.

  20. onomatopellan commented on Apr 30, 2021

    @onomatopellan
    Jonathan (onomatopellan)
    on Apr 30, 2021

    Then I don't know what's happening. What I'd try is disabling WSL2 and enabling it again.

    • Open Windows features

    GitHub Logo

    • uncheck Windows Subsystem for Linux and Virtual Machine Platform
    • reboot
    • Open Windows features again
    • check Windows Subsystem for Linux and Virtual Machine Platform
    • reboot
    • try running WSL2 again

  21. sagniksen31 commented on May 1, 2021

    @sagniksen31
    Sagnik Sen (sagniksen31)
    on May 1, 2021
    Author

    I tried this, But I will try it once more
    Edit - Jonathan (@onomatopellan) answer worked, and don't forget to turn On hypervisor using bcdedit /set hypervisorlaunchtype auto and then follow Jonathan (@onomatopellan) 's step. If any problem Occurs refer to #4626, and then follow Jonathan (@onomatopellan) 's step.
    Thank You Jonathan (@onomatopellan).

  22. Sagnik Sen (sagniksen31)
    closed this as completedon May 1, 2021

  23. ojeh-a commented on Apr 19, 2024

    @ojeh-a
    Ojeh Agbaje (ojeh-a)
    on Apr 19, 2024

    IMG_20240419_063932_917.jpg
    I got stuck while upgrading at 5% for 10 hours, then I restarted the system and tried again, I've been stuck here since. What do I do?

  24. alphaxlegion commented on May 18, 2024

    @alphaxlegion
    alphaxlegion
    on May 18, 2024

    try this command it fixed my issue in kali linux wsl

    Steps

    1. Open Powershell as administration
    2. Run this command wsl --unresgister
    3. Uninstall Linux WSL from Windows
    4. Again download from Microsoft store
    5. Then run your Linux WSL after installation
    6. Don't run any upgrade just run sudo apt-get update
    7. After that run these two command in Linux WSL
    8. "sudo mv /usr/sbin/telinit /usr/sbin/telinit.bak "
    9. "sudo ln -s /usr/bin/true /usr/sbin/telinit"
    10. After this then run sudo apt-get update && sudo apt-get upgrade
    11. Boom Problem fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions