virtualbox.org

So hello everyone I’m new on here and of course, like most I’m looking for help obviously

Recently I just reinstalled VirtualBox on Windows 10 (upgrade like most) and I want to use VB to run Windows 7, pretty straight forward on this. However, I keep coming a crossed a problem that I’m completely stumped on and hopefully I’ll find better answers on here since this is the right place to go! So anyways, I go about and create a new VM on VB, get it all set up and really to rock & roll (not my first time doing this). As I start it up for the first time I get the following message: AMD-V is not available Result Code:E_FAIL (0x80004005) Componet: Console Interface:IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}. This is point I’m lost and not sure what to do; so time to head off to Google and see what I can look up. . . .

Of what I’ve found on this matter is that Visualization on my system needs to be on in order to run VM (basically needed to access Acceleration and made sure it's active), the problem however isn't that Visualization isn't off but it's on for sure in my BIOS. I have AMD FX-8350 Black Edition Vishera 8-Core 4.0GHz (4.2GHz Turbo) Socket AM3+ running on ASUS M5A97 with AMD 970/SB950 ATX Motherboard - Socket AM3+. I've checked and made sure everything is compliant and checks out, BUT here's the thing that I’m confused about. I used Speccy to see everything and "with SVM on" it says it's Not Supported? (See pic). So I got back into my BIOS and of course it's on, I know I can see it, so I try to disable it and see what happens! I head back to Speccy after system reboots and check "with SVM off" and get the Supported, Enabled (see other pic). At this point I figured I’m in the clear and good to go (even though disabling SVM doesn't make sense to me) I try VB once again and start up VM. Now it tells me that AMD-V is disabled in the BIOS Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} so this is where I’m stuck at nor have any clue what to do at all since I’ve ran into a wall on this. So, any suggestions on what to do or where to go from here?

Hardware supported virtualization is not always necessary - it depends on the VM. It's a good idea to at least have it available however. AMD-v not available means that either it is locked in the BIOS, or something else is using it. For example, Hyper-v.

Btw, I would prefer to see logs from VirtualBox rather than some unknown dialog. That way we know what VirtualBox sees, which is all we care about.

So after you responding back to my original post and saying that something else might be running in the background, I had an idea and possibly thought maybe: hey what if it is Hyper-V that's running in the background since I was using that originally? So this morning I went about got on the computer, when is double checked everything made sure that HVM is on, and disabled Hyper-V, did a reboot and lone behold the whole thing now works lol.

I appreciate you at least saying something on that because it would have bother me the entire time unless you wouldn't have said something like that but it didn't even dawn to me! Thank you!!