Close
Skip to content

15 Comments

  1. Erwin
    May 8, 2022 @ 9:09 pm

    Thank you very much.
    This article helped me a lot.
    The trick with bcedit finally solved my issue.

    Reply

  2. Peter
    February 24, 2022 @ 7:19 pm

    Works great! I went through hyperV on, reboot, hyperV off, reboot, command, reboot. Fixed half my machines. Then did it all again and the others worked. Windows sometimes just doesn't listen the first time.

    Reply

  3. CrewKk
    December 3, 2021 @ 12:54 pm

    I Can't Believe it for what I saw, every step that u told was really fix my freaking bugs of error, I saw earlier some community step and try to did it but didn't work unfortunately : (

    but after I saw this and try it, it SAFE brother and u know what…. IT WORK AND FIX MY PROBLEM. I am very proud to find people who are honest in educating people who are having problems to learn to fix their problems independently : )

    also I was to test it out with LeoMoon CPU-V and some emulator's (in case i use LDPlayer 64 Bit version and it can opened, but it still had some notification to turn off Hyper-V and other else, at least it work but i didn't the performance when gaming on there) it works

    Comment at Friday, 3 December 2021

    Reply

  4. shaan
    December 2, 2021 @ 7:47 am

    thanks so much! the bcedit command worked like magic!

    Reply

  5. _hello_world
    July 11, 2021 @ 6:00 pm

    Thank you sir! That bcdedit command fixed my problem too!

    Reply

  6. Jose
    February 6, 2021 @ 12:02 am

    I was missing that step, thanks for the help…

    Reply

  7. Omicron Norton
    January 30, 2021 @ 4:38 pm

    The bcdedit command fixed my problem as well. Thank you so, so much. I was going crazy!

    Reply

  8. Fabrice
    December 27, 2020 @ 7:51 pm

    You're my hero !!! It fixed my problem trying to launch a GNS3 VM. VMware kept telling me "intel vt-x is not supported on this platform".

    Reply

  9. Canine
    November 9, 2020 @ 11:19 pm

    Thanks it worked.

    Any thoughts on why hypervisorlaunchtype would be set to on?

    Any chance it's the Windows 10 Sandbox feature?

    Reply

  10. Nanda
    October 27, 2020 @ 11:08 am

    Fantastic! Fixed the issue

    Reply

  11. Calvin Lam
    October 2, 2020 @ 4:15 am

    Finally!!!!, this command is the solution

    Reply

  12. Alessandro Rota
    September 12, 2020 @ 1:36 pm

    It works!!! Finally I got it!
    The command line solved this damn problem.
    Thank you!

    Reply

  13. Dr. Sauce Boss
    July 29, 2020 @ 3:03 am

    Hey I know I'm a year late on this post, but I just wanted to thank you for finally finding the fix to this problem! I'm sure tons of people on Windows 10 have been running into this error message when trying to use virtualbox and I had just about admitted defeat after troubleshooting for a whole day. The command line fix at the end was the magic bullet and this post is the only place online that suggested that solution! Saved this page because I know a ton of my labmates will be running into the same issue soon enough. You're a hero! Will make sure to donate to the website as a thank you.

    Reply

  14. Matej
    July 21, 2020 @ 1:54 pm

    Same here. Disabling the Hyper-V and everything else (also to be found in other web pages) did not help – the command line finally did it. Great, thanks!

    Reply

  15. John Philippou
    November 14, 2019 @ 2:08 am

    If I could leave a thumbs up, I would! You fixed my Hyper-V problem.

    Reply

Leave a Reply

Your email address will not be published.

css.php