I've wanted to install docker on my windows. I'm getting an error. Hardware assisted virtualization and data execution protection must be enabled in the BIOS. See . I can't go to my bios, after pressing f2 i have just a black screen, i tried to restart my computer manually and from windows in advanced settings from tutorials. In task manager my virtualization is off, I checked my Cpu supports virtualization on Intel Processor Identification Utility and it is. My Cpu is i7 4770k 3,5Ghz. I downloaded bios update for my motherboard but I know, I have to put it on my Pendrive and open it from my bios, couldn't install it straight from my pc with .CAP extension. My motherboard is Asus Z97M-PLUS. I tried to set my virtualization without bios with tutorials, PowerShell commands, changing settings, avast, hyperV. Can't describe exactly what I was doing and which commands I was putting in because I tried everything I found.
It is difficult to help you in this case as this is a very case-specific problem, especially hardware specific. The fact that you can't enter your bios will make enabling virtualization very difficult, as this switch must be switched there, and only there. I suppose you could try resetting your BIOS by shorting two pins / pressing a button on your motherboard, to see if that makes it want to open again.
Try this motherboard manual document at section 1.2.6 and 1.2.7 depending on your use case.
Furthermore, this website probably is not the best place to ask these sort of questions, and tech forums would probably be better able to help you further.
I set up a virtual machine (Linux - Ubuntu) on "Oracle VM VirtualBox Manager" (Application). I can't start it because:
"AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED)" (Error Msg upon attempt to start)
My desktop use Windows 10 and has Virtualization option supported and enabled, I also disabled Hyper-V as instructed here:
"How to disable Hyper-V in command line?" (link), and closed my desktop after applying the change.
I still have "Oracle_VM_VirtualBox_Manager/Settings/System/Acceleration" (path to option box) grayed out, which stop me from enabling AMD-V.
I'm clearly missing something to access this option and yet I have visualization enabled and Hyper-V disabled. Any leads would be appreciated.
Fixed it, having virtualization enabled and hyper-V disabled isn't enough apparently.
Asus BIOS wasn't something I'm used to, but if you go in the BIOS:
advance setting/CPU
and you enable svm Mode, you should get access to a 64-bytes version of your virtual machine in the settings of the application you are using. From there, my virtual machine managed to start up without issues.
hope this help anyone...
Your Virtualization is disabled so you need to enable it
**go to BIOS**
->Restart your system and click Fn+f2
next
**go to configuration**
click SVM and enable it (if you have AMD processor)
or
Click intel virtual Technology and enable it (if you have intel processor)
I've installed Docker and I'm getting this error when I run the GUI:
Hardware assisted virtualization and data execution protection must
be enabled in the BIOS
Seems like a bug since Docker works like a charm from the command line, but I'm wondering if anyone has a clue about why this is happening?
Before you ask, yes, I've enabled virtualization in the BIOS and the Intel Processor Identification Utility confirms that it's activated. Docker, docker-machine and docker-compose all work from the command line, Virtualbox works, running Docker from a Debian or Ubuntu VM works.
There's just this weird issue about the GUI.
My specs:
Windows 10 Pro x64 Anniversary Edition
Intel core i5-6300HQ # 2.30GHz
If the features described are enabled, the problem is with Hyper-V that is disabled or Hypervisor agent not running.
SOLUTION A (If Hyper-V is totally disabled or not installed)
Open PowerShell as administrator and
Enable Hyper-V with
dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
SOLUTION B (If Hyper-V feature is already enabled but doesn't work)
Enable Hypervisor with
bcdedit /set hypervisorlaunchtype auto
Now restart the system and try again.
SOLUTION C
If the problem persists, probably Hyper-V on your system is corrupted, so
Go in Control Panel -> [Programs] -> [Windows Features] and completely uncheck all Hyper-V related components. Restart the system.
Enable Hyper-V again. Restart.
NOTE 1:
Hyper-V needs hardware virtualization as prerequisite. Make sure your PC supports it, if yes and still won't work, there is the possibility your BIOS is not configured correctly and this feature is disabled. In this case, check, enable it and try again. The virtualization features could be reported under different names according the platform used (e.g if you don't see any option that uses virtualization label explicitly, on AMD you have to check SVM feature state, on Intel the VT-x feature state).
NOTE 2:
Hyper-V can be installed only with some version e.g.:
Windows 10 Enterprise; Windows 10 Professional; Windows 10 Education.
Hyper-V cannot be installed on cheaper or mobile Windows versions e.g.:
Windows 10 Home; Windows 10 Mobile; Windows 10 Mobile Enterprise.
Below is working solution for me, please follow these steps
Open PowerShell as administrator or CMD prompt as administrator
Run this command in PowerShell-> bcdedit /set hypervisorlaunchtype auto
Now restart the system and try again.
cheers.
In my case I had to enable virtualization in the BIOS setting.
Restart PC
While you are on the 'restart' screen press any of these keys and you enter the bios settings in windows: esc, f1, f2, f3, f4, f8 or delete
For intel based systems:
press f7 (advanced mode)
go to advanced
cpa configuration
enable virtualization
And after all above steps, it finally works :-)
Note: If your version of Windows supports Hyper-V, you can install docker directly by selecting Use Hyper-V during installation.
However, if your Windows does not have this support, follow the solution below.
I had a similar problem.
I have enabled Intel Virtual Technology in the bios settings.
Then I updated the Linux kernel from here.
and it worked
My specs:
Microsoft Windows 10 Home x64 Single Language
Intel(R) Core(TM) i5-7300 # 2.50GHz
I uninstalled Intel HAXM and VirtualBox, Docker now runs
For me, all I had to do it uninstalling VMware.
Docker now is running
Open the task manager and click on the performance tab. If virtualization is disabled, you need to follow the instructions here to enable it: https://blogs.technet.microsoft.com/canitpro/2015/09/08/step-by-step-enabling-hyper-v-for-use-on-windows-10/
If solution above does not work, then
Go to command prompt and type systeminfo. check Hyper-V Requirements section.
If all listed Hyper-V requirements have a value of Yes, your system can run the Hyper-V role.
In my case virtualization enable in Firmware was NO.
So, I did enabled in system bios by making Virtualization Technology enabled in my HP laptop.
Please visit this link to enable it:
https://2nwiki.2n.cz/pages/viewpage.action?pageId=75202968
Try these steps
Run this command in powershell
bcdedit /set hypervisorlaunchtype
auto
Restart your PC
Now try docker --version in cmd line
Can you try enabling Hyper-V manually, and potentially creating and running a Hyper-V VM manually? Details:
https://docs.docker.com/docker-for-windows/#/what-to-know-before-you-install
https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install
Enable the Hyper-V role through Settings
Right click on the Windows button/Icon and select ‘Apps and Features’.
1- Select Programs and Features on the right under related settings.
2- Select Turn Windows Features on or off.
2- Select Hyper-V and click OK.
follow the steps bellow:
go to: windows setting => Update & Security => Recovery => Advanced Startup and click on : Restart Now.
Troubleshoot => Advanced Option => UEFI Firmware => Restart.
go to Bios => configuration => Virtualization technology => enable it.
save change and it will works.
It helped me:
Disable components Virtual Machine Platform and Windows Subsystem for Linux
Restart
Enable components
Restart
I think my problem was related to beta version of WSL2.
I tried to install android subsystem. But I have deleted it some time ago. So, there was only beta WSL2 left
In my case I had to uninstall hyper-v, restart pc, and run docker again.
Try this in PowerShell(admin enabled):
Enable-WindowsOptionalFeature –Online -FeatureName Microsoft-Hyper-V –All -NoRestart
This will install HyperVisor without management tools, and then you can run Docker after this.
I also use vagrant. It appears I can only use 1 thing at a time. Uninstalling vagrant/virtualBox allowed me to run docker and vise versa
I have tried many suggestions above but docker keeps complaining about hardware assisted virtualization error. Virtualization is enabled in BIOS, and also Hyper-V is installed and enabled. After a few try and errors, I eventually downloaded coreinfo tool and found out that Hypervisor was not actually enabled. Using ISE (64 bit) as admin and run command from above Solution B and that enables Hypervisor successfully (checked via coreinfo -v again). After restart, docker is now running successfully.
If everything is fine with BIOS option I just forced disabling and enabling all HyperV features and this solved my issue
--cmd
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
--restart
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V –All
In my case even though I used all the solutions mentioned above but nothing worked for me. So I decided to uninstall docker and install it again.
Now in the process, I have noticed that I did not check Use Windows containers instead of Linux containers (this can be changed after installation) in my previous installation, and that is why I got the problem above and the solutions still did not fix it. So ensure to check it before you run desktop docker or uninstall it and install it again by checking this option.
I had the same issue after installing VMWare, I uninstalled it but this didn't fix the issue.
Solution for me: in "Turn windows features on or off" I turned off:
hyper-v
containers
windows subsystem for linux
then restart
After the restart I got this message from docker:
I ran the ran the command as said in the message
Enable-WindowsOptionalFeature -Online -FeatureName $("VirtualMachinePlatform", "Microsoft-Windows-Subsystem-Linux")
Then restart and voilà, Docker was back with WSL2
For me, disabling and then enabling Virtualisation in BIOS helped, strangely.
Issue for me was solved when I uninstalled Cygwin.
I tried many of the suggestions here, but did not manage to get it running. What worked for me in the end was to go straight in to the BIOS to activate it. The following article was of great help:
https://www.nextofwindows.com/how-to-enable-configure-and-use-hyper-v-on-windows-10
#Silverstorm
I had Hyperv installed and virtualization enabled in my BIOS.
But SOLUTION A didn't work for me.
However, SOLUTION B worked like a charm.
SOLUTION B (If Hyper-V feature is already enabled but doesn't work)
Enable Hypervisor with
bcdedit /set hypervisorlaunchtype auto
Now restart the system and try again.
Besides the original answer, I have done the following:
Disable Hyper-V in Windows Features
Turning virtualization off and on in BIOS
Log back in windows, enabled Hyper-V. I was prompted there are updates for Hyper-V and I did the update. Restart when prompted.
It worked!
If the problem persists probably Hyper-V on your system is corrupted, so
Go in Control Panel -> [Programs] -> [Windows Features] and completely uncheck all Hyper-V related components. Restart the system.
Enable Hyper-V again. Restart.
In my case virtualization is disabled so I need to do some configuration in my bios,
Please check following link I think it will help you to make bios setup
https://support.bluestacks.com/hc/en-us/articles/4409279876621-How-to-enable-Virtualization-VT-on-Windows-11-for-BlueStacks-5
In bios the setting are dependent on your system manufacture so please find setting accordingly.
Hope it will help you and save your time.
Thanks :)
On AMD machines the BIOS setting you have to change might be called SVM Mode. That was the case for my Gigabyte X570 board.
Setting is found in BIOS at: Advanced mode -> Tweaker -> Advanced CPU Settings -> SVM mode (set to enabled)
AMD-V is the renamed trademark for Secure Virtual Machine Mode (SVM).
I don't know how this works, and I don't even know what these commands do, I don't know what is hypervisor or what it does that it interferes with Docker, and I don't know what the nx means in the second command which it is apparently turning it off. I had these commands saved on my computer as "Turn VT-x off" (yet another thing that I don't know what it is, I think it's related to Virtualization Technology which I don't know what that does/is either). But nothing else worked for me (including the accepted answer (which I tested all of it's solutions) and other upvoted answers, although I didn't read all of them), except running both of these. It is completely up to you to test these, I do not guarantee any fixes to you, but it worked for me, I put it in here because I thought it might be helpful for someone else like me who also didn't find other answers to be that helpful:
bcdedit /set hypervisorlaunchtype auto
bcdedit /set nx AlwaysOff
shutdown /s
On 10th Jan'2023, I faced the same issue. After that, I untick windows subsystem for Linux and Hyper-v and restart my pc. Then I open the docker desktop and when it notify me to turn on Hyper-v then I did that and after that, it was working well.
I was so happy today that I have been finally able to install Windows Phone 8 SDK and try it a bit. I installed fresh new installation of Windows 8 Pro into my virtual machine (I am running if from Parallels) and then installed Windows Phone 8 SDK.
Everything went smooth, Visual Studio Express is installed and running, but when I created new project and tried to deploy it, VS fails with really weird message.
First of all, message box informing that "The Windows Phone Emulator wasn't able to create the virtual machine: Generic failure" appears. Really informing, really professional - generic error, that's really good. Then the information that deployment failed appears (thanks a lot for keeping me informed about that, I didn't noticed that it crashed completely). And then in the Error List, there is an information about "Invalid pointer" - even better. No clue at all about what failed or what's wrong.
Can anybody help me with that? There is nothing on the internet about this topic so far and I don't know where the problem is. I scanned the Windows events and logs, but there is nothing (probably I haven't been searching properly, so please guide me through that if you can).
Anybody can help?
The Windows Phone 8 emulator requires hardware Hyper-V support. In particular, it requires second-level address translation, hardware assisted virtualization, and hardware DEP support enabled and to not be ran in a hypervisor(no nesting). If you bought your machine within the past 4 years you should have no problem with these requirements. You can check out this article to see more information about that and how to find if your PC supports it.
Because of these hardware requirements, this means you can't run the phone emulator inside of most virtualization technologies... With one exception: I've been using VMWare 9 which appears to include an "unsupported" feature to allow Hyper-V to work though.. So your only choice for running the phone emulator is to either buy VMWare 9 (or 8 with more configuration) or upgrade a physical machine to Windows 8
The unsupported way VMWare allows you to run Hyper-V inside of a VM is that there is a manual option (hypervisor.cpuid.v0 = “FALSE”) which basically tells VMWare not to report to the virtual machine that it's running in a VM. Hyper-V checks if it's running in a VM and won't work if it is, so this gets Hyper-V to work past that check. I personally have tested this whole nested-VM thing with the Phone emulator(including before public release), and other than being quite slow, it does work pretty well with no immediate crashes or anything.
There is a workaround for VMWare Workstation 8 as well in an answer below. However, 9 is much easier to configure, so if you have it use this method.
I ran into the same issue and I fixed it by enabling Hypervisor applications in this virtual machine and adding the following line to the .vmx file:
hypervisor.cpuid.v0 = "FALSE"
This got the emulator working just fine. I found this answer here.
Hope this helps.
Actually, it works quite nicely with VMware Fusion 5.0.1
All I had to do is to add to the .vmx file of the virtual machine the following lines:
hypervisor.cpuid.v0 = “FALSE”
vhv.enable = "true"
Save and restart VMWARE (obviously the VM must be stopped before the changes are made)
I'm right now debugging a test app from VS2012 using the emaulator inside a VM in my Macbook
I'm a happy camper
:-)
I posted the same question on Parallels forum.
Reply:
The emulator is actually a virtual machine, so we are talking about a vm inside a vm, this requires support for nested Hyper-V, which afaik is planned but not implemented yet, also VMWare Fusion already supports this, if you are so desperate.
————-
See Parallels forum post: http://forum.parallels.com/showthread.php?p=646448#post646448
This works for me
Set RAM to 4g
Set at least 2 cores
add to vmx file.
vhv.enable = "TRUE"
hypervisor.cpuid.v0="FALSE"
Goot article
http://social.msdn.microsoft.com/Forums/en-US/wptools/thread/ed72010c-321c-4667-97b2-3ff1540e7f87/
You need SLAT compatible hardware to run Hyper-V, which is a requirement for using the emulator.
Can you clarify what kind of hardware you're attempting to run this on, and if you have enabled Virtualization in your BIOS settings?
The "Invalid pointer" error just means it cannot connect to the emulator (and/or device).
Just as an addition to https://stackoverflow.com/a/13163762/1964969 (top answer at the moment):
manually appending "hypervisor.cpuid.v0" key works for VmWare Player 5 as well (the main reason - this software is free for non-commercial use so it's perfect product if you test the waters, just download from VmWare website and install, it's fully-functional).
Slightly unexpected, any of the following amends solve the problem with WP8 emulator:
hypervisor.cpuid.v0="FALSE"
hypervisor.cpuid.v0="TRUE"
hypervisor.cpuid.v0=""
Yeah, you can apply empty value for that key - but why? Have no idea but it works. I did some notes in my blog as well:
http://windowsasusual.blogspot.ru/2013/01/how-to-launch-windows-phone-8-emulator.html
Under Parallels Desktop 8 follow this guide: http://kb.parallels.com/en/115211
Edit:
Oh, I didn't noticed that you are trying to run emulator on VM. My answer is for non-VM environment.
First of all, you need to check hardware requirement at here
Be careful, successful installation of SDK does not guarantee "your hardware is compatible"
If your hardware is compatible and Hyper-V is running(described in the link above), please check your BIOS and be sure to enable hardware virtualization in CPU Configuration
(for me, I could find it at Booting > BIOS > Advanced > Advanced > CPU Configuration)
Brief summary:
64bit CPU and OS
4GB RAM
Hardware-assisted virtualization supported CPU
Second Level Address Translation (SLAT) supported hardware
Hardware-based Data Execution Prevention (DEP) supported hardware
Proper BIOS settings
For me the solution adding line:
hypervisor.cpuid.v0 = "FALSE"
I use VMware Player and added the line (hypervisor.cpuid.v0 = "FALSE")in the .vmx file.
My virtual machine with Windows 8 Pro runs the emulator for Windows Phone 8 perfectly.
Solved the problem by uninstalling an older VPN client from the machine. It turns out some VPN clients might have compatibility issues with Windows 8. After uninstalling VPN client I was able to run the emulator without issues (of course after making sure Hyper-V was installed and enabled on the machine)
Not enough rep. to comment on the accepted answer, but Microsoft provide instructions specifically for Fusion here. It worked for me, after a couple of reboots of both Mac and VM. I installed W8.1 without Hyper-V support initially and had to install it after the fact ("Turn Windows Features On or Off" in Control Panel), but apart from that no problems. Quite speedy on a 16Gb 2013 MBP.