Bootcamp + windows 10 + hyper-v enabled

Question

Bootcamp + windows 10 + hyper-v enabled

Hi,

Just got new MacBook pro 2016 with touch panel

Installed windows 10, works perfect fine until I enable Hyper-v feature.

Once I enables hyper-v in windows 10, the windows screen start up screen shows for more than 30 minutes,

After waiting for 30 minutes, login screen comes up, but MacBook keyboard does not work, Wi-Fi does not work.

so cannt login to windows without keyboard.

Looks like windows OS installed but no bootcamp drivers to support apple's hardware.

Visited to apple stored and explained this issue. They said this is the first time reported this type of issue.

May be bootcamp is not well tested in this new version of MacBook pro 2016.

FYI

1. I followed lot of different suggestion, like goto mac os then start bootcamp first and then goto windows 10.

2. If I attached USB keyboard and USB mouse, then at least I can enter credential to login to windows.

Thank,

Dhirendra

MacBook Pro (15-inch, Late 2016), Windows 10

Posted on Dec 18, 2016 10:31 AM

Reply

Answer 1

Niherlas

Level 1

42 points

Mar 27, 2017 6:09 PM in response to dhirendrapatil

Late 2016 MacBook Pro 13" w/ Touch Bar here.

Just installed the macOS 10.12.4 update, and noticed something interesting in the Security Contents at https://support.apple.com/en-us/HT207615

EFI

Available for: macOS Sierra 10.12.3

Impact: A malicious Thunderbolt adapter may be able to recover the FileVault 2 encryption password

Description: An issue existed in the handling of DMA. This issue was addressed by enabling VT-d in EFI.

CVE-2016-7585: Ulf Frisk (@UlfFrisk)

And it's the disabling of VT extensions in Mac EFI that's been causing Hyper-V installations to fail, according to most reports. I did a clean Boot Camp install (fresh partition) of Windows 10 Pro using a recent ISO downloaded from Microsoft. Once the Apple Boot Camp driver installation completed in Windows, but before joining a WiFi network or installing any MS Updates, I went to "Turn Windows features on or off", enabled Hyper-V, and allowed it to reboot.

Reboot was successful. Hyper-V is installed and enabled. I'll be installing MS updates and doing further tests...

Reply

Answer 2

Loner T

Level 9

59,536 points

Dec 18, 2016 6:37 PM in response to dhirendrapatil

From my perspective, since three other virtualization products, viz., Parallels, VMWare Fusion and VirtualBox, all work without any issues, the issue is Hyper-V. This should be a Microsoft issue. If they need engineering help, they can ask Apple, but Apple cannot address any Windows Support issues.

Also, I posted a link - looking-at-the-hyper-v-event-log - in the other discussion. You can try and debug it further and ask Microsoft to look at the events.

Reply

Answer 3

Apr 30, 2017 5:29 AM in response to Niherlas

How are things working out for you? Still no issues?

I just ran into this problem myself after installing Docker in Windows 10. If hyper-v can be enabled without further problems the way you describe it’s worth re-installing everything from scratch, even though I’ve spent the last couple of days setting up my Bash on Windows environment.

Reply

Answer 4

Loner T

Level 9

59,536 points

Dec 18, 2016 2:01 PM in response to dhirendrapatil

Please see Enable Hyper-V on MacBook Pro Late 2016 makes bootcamp unusable . Hyper-V is not supported on 2016 Macs. Try nested virtualization via VMware Fusion, Parallels or VirtualBox.

Reply

Answer 5

Dec 18, 2016 6:21 PM in response to Loner T

Hi Loner,

Thanks for the suggestion.

Hyper-v does not work in virtual box or parallel if the host OS does not have hyper-v enabled. also as per msdn, to enable Hyper-v on windows, hardware should be compatible. The old MacBook Pro works perfectly fine with windows 10 and hyper-v.

Its very weird that no one accepting that its issue with their product ( apple or microsoft). I called Microsoft, they says if keyboard is not working, then not windows 10 issue. Apple support team says its windows 10 issue and we have limited support with bootcamp.

so you think I should not hope to get hyper-v working on macbook proc.

thanks,

Dhirendra

Reply