Enable Hyper-V on MacBook Pro Late 2016 makes bootcamp unusable

Do we know if the issue is just isolated to Touch Bar 2016 MBPs, or is the function key model also affected? I assume both are affected given the details everyone has posted above, but I did wonder if anyone has confirmed on a function key model?

I recommend using Visual Studio for Mac and focus on cross platform .NET Core development that way. .NEt Core is still not fully fleshed out but at least you can still run emulators etc. in macOS. Plus you get the added benefit that the iOS emulator is native.

"So far, the only way we can even get into Safe mode with the TouchBar is a perfectly timed (with loads of trial and error) Command-R a split second after selecting Windows from the boot option, and we only get that to work 1 out of 50 tries."

You may already know this solution by now, however, when the Windows logo comes up press and hold the power button until the MacBook Pro turns off. Repeat this step 3 times and the Automatic Repair/Recovery Mode will start (at which point you can select Safe Boot Mode under Advanced Options. (Note - occasionally we had to repeat the power off cycle 5-6 times in order for this mode to start.)

Hi everyone.

I've got Hyper-V working reliably under Windows 10 installed via Bootcamp on a 2016 MBP without TouchBar. The steps are relatively advanced, but were easy to follow and most people on this thread should be comfortable. You install and EFI boot manager called rEFInd (it's the "modern" successor to a tool I used to use on my old MacBook Air called rEFIt). By tinkering with rEFInd's configuration you can get it to EFI-boot Windows with the hypervisor enabled.

Follow the instructions here, CAREFULLY: http://nuts4.net/post/hack-force-vt-x-to-be-always-on-when-booting-to-windows-on -your-macbook

I also followed the steps in this article about enabling "legacy safe mode" for Windows 10 (allowing me to press the F8 key during boot if anything goes wrong): https://medium.com/@naokisatoname/newer-mac-windows-10-on-boot-camp-hyper-v-enab led-infinite-spinning-circle-5631b36f6d1…

The net result is a clean install of W10 via Bootcamp, with working Hyper-V. I need to use rEFInd as my boot manager to EFI-boot Windows, but that's totally fine in my book.

I hope this helps people. I intend to cross post this solution on the other linked threads to get the word out there.

Regards,

Mark

Just sharing what I have been doing the last year.

I have a Macbook Pro, probably 2015 (I don't know exactly, because I don't use Mac Osx for a while..), without touch bar.

Everytime that I need to run an emulator, or VM I usually:

1. Turn of the computer.

2. Turn on while pressing COMMAND + OPTION + P + R (reset nvram)

3. You will hear the first chime, keep PRESSING.

4. You will hear the second chime, after that just keep pressing OPTION.

5. Select windows to boot, and thats it.

Windows will boot on EFI or whatever.. but my virtual machine works! 😉

Your 2016 Mac does not support Hyper-V.

Your Mac does not support CSM-BIOS. All Macs after Late 2013 are UEFI Macs. On Macs, CSM-BIOS is required for Hyper-V.

GBMini wrote:

That's a really unhelpful answer. Where is that documented?

Unhelpful, or one that you did not want. 😉.

Have you seen any documentation on a Mac where it is officially supported? Please also see Re: INACCESSIBLE_BOOT_DEVICE after enabling Hyper-V in Windows 10 on Late-2015 27" 5k iMac .

GBMini wrote:

Btw.. According to the MS "systeminfo" command it should work, all the required things at the processor level are enabled:

Here is a dump from the relevant section :

Hyper-V Requirements:	VM Monitor Mode Extensions: Yes
	Virtualization Enabled In Firmware: Yes
	Second Level Address Translation: Yes
	Data Execution Prevention Available: Yes

So assuming is something crappy in the new Macbook Pro firmware causing this.

Your own testing is telling you that it does not work, correct?

These are registry settings from a 2012 MBP. Notice the installation mode, and Hyper-V does work on my 2012 MBP.

Are you running a Hyper-V VM or a VM using Parallels, VMware or VirtualBox on the early 2015 MBP?

From OS X Terminal on the early 2015 MBP, please post the output of

sysctl -a | grep machdep.cpu.features

I'm having exactly the same issue. Searching through the forum seems to indicate Apple deprecated essential BIOS feature that is necessary to support Hyper-V on all latest Mac models. This is most disappointing. I purchased the new MBP for Visual Studio development, specifically for cross platform app using Xamarin. Missing Hyper-V support essentially means I cannot run emulators within Visual Studio, which is more than little inconvenience.

Have you considered Fusion, Parallels or VirtualBox? Please also see https://msdn.microsoft.com/en-us/library/windows/apps/jj945424.aspx .

I'm using Parallels now, with Netsted Virtulization enabled. It works but not perfect. Running a VM within a VM is not the ideal way, for obvious reasons (performance, resources, etc)