Hi .
I have win10 64bit, 1607, i7.
I don't remember when , but existed host of 64 bit stopped to run (VT-x is not available (VERR_VMX_NO_VMX).
When I try to create a new host I see only 32 bit.
1. The Intel i7 has VT-x support.
2. Virtualization and VT-d are enabled in BIOS
3. Hyper-v is disabled.
Antivirus McAfee.
How can I fix the problem ?
No 64 bit hosts and existed stopped to work
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: No 64 bit hosts and existed stopped to work
Something is using your VT-x. Most probable McAfee if it uses hardware acceleration. Please go thoroughly through the FAQ: I have a 64bit host, but can't install 64bit guests. Those are guidelines, you have to use your judgement...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: No 64 bit hosts and existed stopped to work
How can I check the option 3 from the FAQ ?
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: No 64 bit hosts and existed stopped to work
Windows Task Manager will show you what processes are running and you can see if there is anything in there that looks like an anti-virus product or the others described in the FAQ.
You hopefully also know what is installed on your computer that could fall into the offending categories but it isn't always easy to tell.
-Andy.
You hopefully also know what is installed on your computer that could fall into the offending categories but it isn't always easy to tell.
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Re: No 64 bit hosts and existed stopped to work
I am already about 3 months looking for what blocking the virtualization.
It seems hopeless...
It seems hopeless...
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: No 64 bit hosts and existed stopped to work
It shouldn't be hard to find. It's either Hyper-v or your AV. The first must be disabled, and the 3rd party AV is superfluous on Win10.
-
- Volunteer
- Posts: 362
- Joined: 18. Aug 2014, 21:53
- Primary OS: Debian Sid
- VBox Version: PUEL
- Guest OSses: Android, Linux
Re: No 64 bit hosts and existed stopped to work
And there is DeviceGuard too, which is blocking vt-x.
Re: No 64 bit hosts and existed stopped to work
Hyper-v is disabled.
Device Guard -> Turn On Virtualization Based Security -> Disabled.
AV installed by IT (work computer). I can't to delete it , but maybe can change something.
These installed on my PC :
McAfee Management of Native Encryption 4.1.1.4
McAfee VirusScan Enterprise
McAfee DLP Endpoint
McAfee Agent
Device Guard -> Turn On Virtualization Based Security -> Disabled.
AV installed by IT (work computer). I can't to delete it , but maybe can change something.
These installed on my PC :
McAfee Management of Native Encryption 4.1.1.4
McAfee VirusScan Enterprise
McAfee DLP Endpoint
McAfee Agent
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: No 64 bit hosts and existed stopped to work
Get your IT people to uninstall McAfee, and make sure its gone. Test if VirtualBox works. Choose a course of action once the facts are known.