4 Comments

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

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

    Reply

  2. 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

  3. 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

  4. 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. Required fields are marked *

css.php
Shares