No Audio/Sound and integrated Intel HD 4000 graphics working in Windows 10 Bootcamp in UEFI mode

Zythyr wrote:

How do you know that the mid 2012 model is a preUEFI model? I want to do EFI install so I can have more than 4 partitions on my hard drive, and I hear the boot time is much faster.

When I look at Bootcamp's info.plist, my model (MacbookPro9,1) is not listed under the "preUEFI" as show below:

<key>PreUEFIModels</key>

<array>

<string>MacBook7</string>

<string>MacBookAir5</string>

<string>MacBookPro10</string>

<string>MacPro5</string>

<string>Macmini6</string>

<string>iMac13</string>

</array>

You are misinterpreting the array. If you notice, there is not MBP8,x, MBP7,x,... . The array indicates the models or prior models as preUEFI. Any MBP10,x or older is a preUEFI model.

Please also see How to identify MacBook Pro models - Apple Support, which indicates that any MBP model, prior to Late 2013 is preUEFI.

Could it be that Bootcamp v6 is not downloading the proper drivers for the EFI install in order for the sound to work? In macOS Sierra, is there any modifications I need to do to Bootcamp's info.plist so that it will download the proper drivers that will enable the audio in EFI version of Windows 10 for my MacbookPro9,1 model?

BC6 is downloading appropriate drivers. It does not download any EFI firmware to update a Mac. Do not modify the Info.plist.

This is W10 on a 13-in MBP 2012 in legacy BIOS. Notice that Cirrus Audio drivers are installed.

On 2012 Models, which are preUEFI Macs, EFI Boot does not work. Audio will not work on 2012 Macs using EFI Boot.

What is the specific reason to try EFI on 2012 models? I have EFI Boot on a late 2013 model 13/15 Macs.

Zythyr wrote:

1) I am still trying to understand what exactly is causing Intel HD 4000 drivers from being installed in the EFI mode? It seems to detect that there is integrated graphics device and its missing the drivers, but upon installing the drivers, the system crashes... Is there no possible way with software modification, driver hacking, or EFI modification to get graphics/audio to work in EFI install of Windows 10 on a PreUEFI model? Is this a hardware issue or there is still hope for a software fix?

The Audio devices are exposed by the CSM-BIOS layer which is supported on EFI systems. If EFI is used, the BIOS layer is never invoked, hence the missing devices. Instead of hacking/modifications, why not use the available method. This is not a hardware issue. This is by design. I have investigated the possibility of making the pre-2012 models as EFI compliant, but there is no interest.

2) Referring to question 1, is there a EFI firmware modification that can be done? What if I install a firmware for a Macbook Pro 2014 or 2015 on my 2012 model? Would it be even possible?

You will cause more problems than solve them. Apple will not allow cross-model firmware installation. Most likely you will have to take the Mac back to Apple Genii to put back the supported FW. I strongly recommend against such experiments, unless it is an experiment.

3) One reason I was trying to do EFI install was so I can have more than 4 partitions on HDD/SSD on my Macbook Pro mid 2012. I want to triple boot macOS, Ubuntu, and Windows 10. In addition, EFI install provides faster boot-up times. Is there any other alternative you can suggest since I can't do EFI install of Windows?

Get a Late 2013 or a later model, and use EFI/GPT. EFI is 'faster' but for a consumer, a few seconds of boot time is not tragic. If you buy a later model, W7 is supported on 2013-2014 models only.

4) I did a MBR/BIOS legacy install of Windows 10. Everything including audio works. There is only one issue; I am unable to get integrated Intel HD 4000 graphics to work. In the Device Manager, Intel HD 4000 display drivers are not visible. Only the dedicated GeForce GT 650M drivers are visible. I manually tried to install the Intel HD 4000 drivers, but I am getting an error. Here are more details on the issue: https://apple.stackexchange.com/questions/260668/intel-hd-4000-graphics-device-d rivers-missing-in-windows-10-bootcamp-on-macbook

This is by design. Use a Linux variant and test. The W10 device driver update methodology is quite abysmal and the forced updates are far worse.

If you are primarily a Windows user, I suggest buying a PC, instead of such contortions to make a product do something outside it's designed tolerances. I personally have stayed away from W10 to avoid these issues (except to experiment). W7 is far more stable.

Zythyr wrote:

Would rEFInd be a possible solution? www.rodsbooks.com/refind/

rEFInd is a boot manager, not a boot loader. It allows you to see available OSes, not how they boot. For example, it cannot modify PCI registers for hardware to function in a certain mode.