Lỗi this host supports amd-v but amd-v is disabled năm 2024

two days ago one of my virtualization software (QEMU) stopped working because of missing Virtualization support. I reinstalled the software, but it didn't changes anything, also VMWare Player and VMBox show the same error.

I did a BIOS Update and configuration reset, enabled virtualization support again, but it still doesn't work. What could be the problem?

My Hardware:

CPU: AMD Ryzen 7 2700X

Mainboard: MSI Gaming Plus (MS-7B79)

Chipset: X470

CPUBIOS VersionSVM

1 Solution

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Print
• Report Inappropriate Content

I got the root cause! Just in case someone faces the same issue and will find this thread - here the solution:

You have to disable "core isolation" in device security settings

For allready created VMBox VMs the "Nested VT-x/AMD-V" checkbox remains grayed out (like in my screenshots in previous post), so you have to execute this command with VBoxManage program

VBoxManage modifyvm "Virtual Machine Name" --nested-hw-virt on

Now I remember, there was a popup from windows, that device safety isn't optimal, and I should enable core protection...I just did it, it took few seconds and I forgot about it, and now it took me 2 days and a lot of pain, to figure it out.

Thanks to everyone, who tried to help me and good luck with this solution for seekers

• All forum topics
• Previous Topic
• Next Topic

10 Replies

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Print
• Report Inappropriate Content

Hello, I collected some interesting information, and got an workaround, but I still interested in solution; please advice me where can I find logs for VM Player (prefered solution) or what kind of logs can help?

With VMWare Player, I can select AMD-V support, but while VM setup i'm getting error "Virtualized AMD-V/RVI is not supported on this platform" (2 days ago it was supported)

On Oracle VM Box I can't even select AMD-V usage

I didn't used Hyper-V before, but I activated it, like you proposed and it works with nested virtualization support

unfortunatelly for my application hyper-v is the least prefered option and I have to figure out, what happened two days ago with VM-Box and VMWare

What should I check next?

p.s. I think this command for hyper-v does the difference, so probably there was some driver update or something like that and there is some global system wide switch to turn nested virtualization on/off

Set-VMProcessor -VMName "GNS3 VM" -ExposeVirtualizationExtensions $true

what could it be?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Print
• Report Inappropriate Content

Thanks, onkelbenz. I think I have used most of these over the years but settled on HyperV a long time ago, and now know little about the others. I am curious why HyperV does not satisfy. What version of Windows (winver command in Commend Prompt). Thanks and enjoy, John.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Print
• Report Inappropriate Content

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Print
• Report Inappropriate Content

Maybe if you post your PC information plus the versions of Windows or Linux and VMware Workstation Player plus any other programs that runs with Player.

That way someone more knowledgeable might be able to help you.

I was thinking that maybe VMware Player got updated in the last two days to a new version that isn't compatible.

But you would have noticed that immediately. So something else changed to break AMD-V.

Do you have the latest BIOS for your PC installed?

Could your Player could have gotten corrupt in the last 2 days?

What GPU are you using? The APU Integrated Graphics or a GPU card?

Are you using a Professional GPU card by any chance?

I would also check Windows OS, that is if you are not running Linux, by running the following command in a elevated Command Prompt or Powershell: SFC /scannow

Also did Windows Update, including drivers, in the last 2 days?

Trying to eliminate any changes to your OS or Driver or Adobe Program.

EDIT: If you haven't opened a thread yet a VMware Forum you should. Possibly others are having the same issue in the last couple of days.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Print
• Report Inappropriate Content

I got the root cause! Just in case someone faces the same issue and will find this thread - here the solution:

You have to disable "core isolation" in device security settings

For allready created VMBox VMs the "Nested VT-x/AMD-V" checkbox remains grayed out (like in my screenshots in previous post), so you have to execute this command with VBoxManage program

VBoxManage modifyvm "Virtual Machine Name" --nested-hw-virt on

Now I remember, there was a popup from windows, that device safety isn't optimal, and I should enable core protection...I just did it, it took few seconds and I forgot about it, and now it took me 2 days and a lot of pain, to figure it out.

Thanks to everyone, who tried to help me and good luck with this solution for seekers

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Print
• Report Inappropriate Content

Good troubleshooting.

I had a similar issue with installing a program. I also had CORE PROTECTION on which prevented it from installing.

I needed to temporarily disable Core Protection to install the program and then enable it again.

The first time I tried to enable Core Protection I was told a specific Acronis driver needed to be removed before it can be enabled. So finding out that file belong to a Acronis feature that I don't use I renamed the driver with .OLD . After that I was able to enable Core Protection.