F5F Stay Refreshed Hardware Desktop Virtualization enabled during BIOS setup – turned off in Task Manager

Virtualization enabled during BIOS setup – turned off in Task Manager

Virtualization enabled during BIOS setup – turned off in Task Manager

M
MistaOmega
Member
65
02-28-2016, 09:03 PM
#1
Hey there, friends. I'm trying to run my Android games on PC using Bluestacks, which needs virtualization. I've enabled it in BIOS, but when I look at the CPU tab in Task Manager, it says Virtualization is off. Since I'm using Windows 10 Home, Hyper-V isn't available, which seems odd because it should help with this issue. It's strange that it doesn't appear as turned on even though I changed the boot order to confirm it's being saved. Someone suggested it might be due to a dead CMOS battery. I managed to save BIOS settings by adjusting the boot sequence, but I'm going to try a few more things to rule out other causes. Any suggestions on what else could be blocking virtualization? Thanks!
M
MistaOmega
02-28-2016, 09:03 PM #1

Hey there, friends. I'm trying to run my Android games on PC using Bluestacks, which needs virtualization. I've enabled it in BIOS, but when I look at the CPU tab in Task Manager, it says Virtualization is off. Since I'm using Windows 10 Home, Hyper-V isn't available, which seems odd because it should help with this issue. It's strange that it doesn't appear as turned on even though I changed the boot order to confirm it's being saved. Someone suggested it might be due to a dead CMOS battery. I managed to save BIOS settings by adjusting the boot sequence, but I'm going to try a few more things to rule out other causes. Any suggestions on what else could be blocking virtualization? Thanks!

K
KingKuewyn
Member
157
03-04-2016, 05:59 AM
#2
Windows okay! Download the app from the link provided. It’s a basic tool that verifies virtualization support. Look for checks on CPU architecture and OS architecture. If they match, use the command in an elevated prompt to disable the hypervisor launch type. After rebooting, you should be all set.
K
KingKuewyn
03-04-2016, 05:59 AM #2

Windows okay! Download the app from the link provided. It’s a basic tool that verifies virtualization support. Look for checks on CPU architecture and OS architecture. If they match, use the command in an elevated prompt to disable the hypervisor launch type. After rebooting, you should be all set.

W
Waffley_1254
Member
227
03-09-2016, 07:31 AM
#3
I truly believed this would work, but it didn’t. X was present, executed an admin CMD command, and restarted the system. Nothing changed; it remains active in the BIOS.
W
Waffley_1254
03-09-2016, 07:31 AM #3

I truly believed this would work, but it didn’t. X was present, executed an admin CMD command, and restarted the system. Nothing changed; it remains active in the BIOS.

C
C00lb0y
Member
218
03-09-2016, 03:01 PM
#4
CPU virtualisation can be quite challenging. Which CPU model are you working with? If it's an AMD system, you'll likely need to turn on specific options—like AMD-V or IOMMU—to enable virtualisation. Remember, Windows 10 Home (regardless of language version) doesn't support this feature.
C
C00lb0y
03-09-2016, 03:01 PM #4

CPU virtualisation can be quite challenging. Which CPU model are you working with? If it's an AMD system, you'll likely need to turn on specific options—like AMD-V or IOMMU—to enable virtualisation. Remember, Windows 10 Home (regardless of language version) doesn't support this feature.

E
Envil_
Member
126
03-11-2016, 08:18 AM
#5
I verified that my friend is also using Windows 10 Home and is utilizing virtualization. Windows 10 Home doesn't support Hyper-V. I'm using Intel, which appears to be activated with a simple toggle.
E
Envil_
03-11-2016, 08:18 AM #5

I verified that my friend is also using Windows 10 Home and is utilizing virtualization. Windows 10 Home doesn't support Hyper-V. I'm using Intel, which appears to be activated with a simple toggle.

L
Lexi_Mexi
Junior Member
21
03-11-2016, 03:20 PM
#6
What processor are you running? The model isn’t clear. It seems like Windows isn’t interpreting the BIOS settings for virtualization properly. A BIOS update could help. Otherwise, it’s hard to pinpoint the exact problem.
L
Lexi_Mexi
03-11-2016, 03:20 PM #6

What processor are you running? The model isn’t clear. It seems like Windows isn’t interpreting the BIOS settings for virtualization properly. A BIOS update could help. Otherwise, it’s hard to pinpoint the exact problem.

G
Gekke_Meloen
Junior Member
44
03-11-2016, 08:40 PM
#7
i7-3770
G
Gekke_Meloen
03-11-2016, 08:40 PM #7

i7-3770

L
lars0100
Member
70
03-11-2016, 08:51 PM
#8
Fixed. It's really frustrating. I just turned it off, came back on, restarted, and it worked. What a waste of time. Did you try turning it off and back on again? It's annoying. Thanks for the help!
L
lars0100
03-11-2016, 08:51 PM #8

Fixed. It's really frustrating. I just turned it off, came back on, restarted, and it worked. What a waste of time. Did you try turning it off and back on again? It's annoying. Thanks for the help!