MBP UEFI WINDOWS SOUND FIXED!!!!

Question

Level 1

23 points

MBP UEFI WINDOWS SOUND FIXED!!!!

If anyone is still interested I have found the solution for audio on MBP 2011 Windows 10 UEFI installs - it has taken me 4 years to figure out. I was given the answer from a tutorial only adjacently related -here:

https://egpu.io/forums/pc-setup/fix-dsdt-override-to-correct-error-12/

essentially what we knew was that windows didn't 'see' the correct audio devices when booted in pure efi-

The part that was frustrating to me was that many users like myself have lots of UEFI installs on their 2011 MBP and those OS's have no problem 'seeing' the HD audio controller -

So what was windows doing different?

I had messed around with mm commands in a UEFI shell (The shell provided in the rEFIt package) to no avail*

I had tried to pass SETPCI commands from grub into Windows 10- no luck*

A quote from the link above got my brain spinning

"A Windows system's DSDT table root bridge definition (ACPI PNP0A08 or PNP0A03) is usually confined to a reserved 32-bit space (under 4GB) budgeted to be large enough to host the notebook's PCIe devices. A watermark TOLUD value is then set and locked in the system firmware. Windows OS honors the root bridge definition and will allocate PCIe devices within it. macOS ignores the root bridge constraints as too does Linux when booted with the 'pci=noCRS' parameter. Neither of those OS require a DSDT override and can allocate freely in the huge 64-bit PCIe address space"

So Windows 'honors' the root bridge and OSX and linux disregard it --hmmm interesting.

As someone who also deals in hackintoshes I am very aware of DSDT's and how editing them can help get OSX running on home brew PC hardware- I had played around with installing Clover (the UEFI bootloader almost synonymous with Hackintoshes) on USB thumb drives and putting the DSDT from my MBP 2011 in the /Clover/ACPI/Windows folder - still nothing-- I thought that pointing windows to a DSDT would be enough.......

A side note is that there are people who have 'bricked' their real Macs when using clover, I have never had that issue personally (a sub-link in the link above describes such a situation)*

If you follow the guide and make a modified DSDT (one that add 'qwords' to the dwords section) you can test it in two ways-

I used Maciasl to extract and edit my DSDT to add a 'Qword' section - I placed the DSDT in two locations /EFI/Clover/ACPI/Patched [not sure if that one matters] & /EFI/Clover/ACPI/Windows

holding ALT/option during bootup I selected "EFI Boot" from the USB clover and booted into Clover

for the exact Clover configuration send me a message

After booting into windows the sound card was immediately working (this was because I had installed the cirrus logic drivers from bootcamp 4) - the display audio driver in device manager had an exclamation point but I was able to install the display audio driver from intel's driver support for the i7 2470m CPU in this machine-

I also looked at device manager via 'by resources' and saw that a new entry 'Large memory with an address range appeared

And low and behold the address range for the 'large memory section' contained the range for the hd audio controller

I then wanted to see if the method described in the initial link posted above where you force that memory map into the registry and turn on 'test signing' worked --

it did, which allowed me to boot directly into windows without the help of clover --

*NOTE: when I tested the registry method I skipped the first few steps since I already had a modified DSDT- I did need to create the 'C:\dsdt folder and extract the windows binaries to that folder - but I did not use their acpi dump nor compiler (I check for errors and compiled my dsdt in Maciasl in OSX)

I would gladly go more in depth but I doubt there are many more who need this information- just glad to have figured it out without the BIOS emulation of bootcamp- going to test this method on other 'pre 2013' Macs with non complient UEFI bios'

MacBook Pro

Posted on Feb 3, 2019 11:57 AM

Reply

Answer 1

Top-ranking reply

xAndrewH1993x

Level 1

4 points

Sep 8, 2020 1:54 PM in response to TGIK

UPLOADED OF VALOR AND VALOR LITE WILL BE DONE BY 9/8/2020 8:00 PM EST OR SOONER

MAJOR UPDATE FOR VALOR (Valor AIO) & VALOR LITE

HAPPY LABOR DAY OR "HAPPY HOLIDAY"

TESTED AND CREATED FOR WINDOWS 10 BUILD 2004 (MAY 27TH 2020 UPDATE)

UPDATES:

7-ZIP FILES ARE NO LONGER AVAILABLE – MOUNT ISOs OR MAKE USB

BIN FILES ARE NO LONGER AVAILABLE – MOUNT ISOs OR MAKE USB

NEW DRIVERS UPDATE – FIXES DPC WATCHDOG BSOD & INCREASES PERFORMANCE

UPDATED GOOGLE DRIVE LINKS AND YOUTUBE LINKS

UPDATED STANDALONE MODDED BOOTCAMP DRIVERS

-FIXES DPC WATCHDOG BSOD & INCREASES PERFORMANCE

ADDED WPD TO HAVE MORE SECURITY OVER PRIVACY SETTINGS OF WINDOWS 10

ADDED ISOTOUSB TO ISO

ADDED SNAPPY DRIVERS FOR EMERGENCY (MACBOOK PRO 8,1 ONLY) UNDER ROOTFOLDER >RESOURCES>INSTALLERS>NOT PART OF SCRIPT>MACBOOKPRO 8,1

FIXED BUGS

______________________________________________________________________________

SAME FROM PREVIOUS UPDATE:

ISO IMAGES AVAILABLE

ISO-TO-USB AVAILABLE

NEW TUTORIAL

ORGANIZED GOOGLE DRIVE

NEW DRIVERS UPDATED

SHORTCUTS FIXED

FIXED BUGS

VALOR LITE - PEOPLE WHO ONLY WANT DRIVERS, SCRIPT (SMALLER DOWNLOAD FOR PEOPLE ON METERED CONNECTIONS)

Valor Script: A Frankin-Mac Project ( http://www.howeitworks.com/valor )

DSDT Patch to Enable Audio Drivers in EFI Installed Version of Windows 10, Blue Screen Of Death Fix, and more.

This is meant to work with only MacBook Pro Early 2011 13inch or MacBookPro8,1 Please keep in mind if you use this script on a different model terms below applies!

ALL THANKS GOES TO TGIK AND itayemi's METHODS! TGIK IS DA MAN! TGIK APPLE FOURM: https://discussions.apple.com/thread/250137979 AND itayemi's Windows Method (This without the script or drivers) (How to do this manually):http://www.itayemi.com/blog/2019/09/12/dual-booting-mac-osx-and-windows-on-macbookpro/ -THANKS AGAIN itayemi!

TGIK provided the full Mac/Clover bootloader version of creating and executing the DSDT patch, while itayemi provided a Windows alternative of creating and executing the DSDT patch. I'm the guy who took the two and made a script for Windows and added other needed and useful tools that is needed to make Windows 10 ver 1903 and higher to be compatible.

I'M NOT RESPONSIBLE FOR ANY DAMAGES CAUSED TO YOUR MAC OR PC (NOT MEAN'T FOR PC USERS). IT IS THE USERS RESPONSIBILITY TO MAINTAIN PC AND REFORMAT WINDOWS IF DONE INCORRECTLY. SO IF YOU DON'T UNDERSTAND THESE TERMS, EXIT IMMEDIATELY!

Welcome to Valor!

Thanks for being here and giving this a spin!

Download Free & Enjoy! No Advertisements or Surveys Required.

Tutorial links:

Valor & Valor Lite USB Setup & ISO Mounting Tutorial (PART 1): https://youtu.be/rb-B9M7ro5A -UPDATED LINK

Valor Deployment Tutorial (PART 2): https://youtu.be/c72B5Zajo2g -UPDATED LINK

Please do not mirror link:

Valor (DSDT Patch Script & Modified Apple Drivers Package/Script for MacbookPro8,1) Download Link:

https://drive.google.com/drive/folders/1mhAXrunkKsOlIi4Hs-g9hgcXbRtTlBVs?usp=sharing

https://www.paypal.com/paypalme2/howeitworks - Donation Link (Fully Optional Not Enforced)

Do Not Forget to show appreciation to TGIK and itayemi!

1.) This is a script that will install a DSDT file to make your audio drivers work for your MacBook Pro Early 2011 in EFI mode. This is means if you want to install multiple Windows Partitions you can in EFI and you are no longer dependent on the DVD Rom.

2.) BootCamp drivers downloaded and changed as of 10/23/2019. The modifications are MacHaldriver.sys has been completely removed and through this script installs a MacHaldriver.inf instead to avoid Blue Screen Of Death with Windows 10 ver. 1903 or higher because of incompatibility. Untested on Mid 2011 and Late 2011 Macbooks, please provide feedback if there are any issues. This will be automatically executed when using the script.

3.) Legacy Windows essentials programs will be installed to ease user experience transitioning for Windows 7. Ninite will be executed to insure all users are setup with modern day browsers and including the must have tools to maintain this machine. Anti-Virus will be provided and other useful Microsoft programs including Windows Media Center-Port Over from Windows 7.

Please look into the Script Directory and Resources\Installers Directory to look over what will be installed or offered to be installed as you go through the script! Thanks again I hope you enjoy!

Please checkout my website for more information ( http://www.howeitworks.com/valor )

EXTRAS

Standalone Modded BootCamp Drivers for Windows 10 ver. 1903 or higher (Blue Screen Of Death Fix):

https://drive.google.com/drive/folders/1IPcJvIdnBMhpTUm0bnsdXdIh-I_NH-Mz?usp=sharing

(THIS IS BUILT INTO VALOR SCRIPT) (ONLY FOR USERS WHO NEEDS IT FOR LEGACY WINDOWS INSTALL)

Reply

Answer 2

Dec 28, 2020 4:23 PM in response to TGIK

Thanks for this, managed to get sound working on my 2012 13'' MBP.

I did the Clover method.

Quick note, when you download the W10 ISO on a Mac from the Microsoft website, its almost 6GB in size, whereas the one from the ISO creation tool is 2GB smaller, not sure why this is.

Regardless, I noticed because of this, when bootcamp created the USB, it formatted as exFAT, and the MBP came up with 2 partitions to boot from, Windows or EFI Boot.

I could only get EFI boot to work, however no matter what I tried, I could not get Clover to boot, for some reason, the MBP was booting \EFI\Microsoft\Boot\bootmgfw.efi completely ignoring \EFI\Boot\BOOTX64.efi (Clover)

In order to fix this, I downloaded an ISO directly from the ISO Creation Tool, created a UEFI FAT32 USB with Rufus, and copied over BootCamp drivers etc to install later.

This time, the MBP boot selector showed 1 USB device, EFI Boot.

I then reinstalled Windows (For what appeared to be the 100th time that weekend troubleshooting this) with the non-bootcamped W10 install.

And Voila - Copied over Clover EFI with patched DSDT and I now have working sound.

I'm not sure why my BootCamp W10 install was skipping the BOOTX64.efi, I have a feeling the Bootcamp install is some legacy/UEFI combo thats messing things up

Reply

Answer 3

Feb 4, 2020 5:11 PM in response to xAndrewH1993x

-Removed Comment-

Reply

Answer 4

TGIK Author

Level 1

23 points

Jun 23, 2019 11:10 AM in response to eraldm349

https://sourceforge.net/projects/maciasl/

in OSX dump your dsdt file and add the 'qwords' as described

in this link https://egpu.io/forums/pc-setup/fix-dsdt-override-to-correct-error-12/ compile your dsdt and save it as 'dsdt-modified.aml' (put it on a shared drive or a thumb drive to be able to copy it into Windows

'i. Download and install required tools:

Windows Binary Tools (WBT - Dec 2016) extracted to c:\dsdt directory. [ newer WBT has parsing errors]
Windows Driver Kit (WDK), which contains the Windows ASL Compiler (asl.exe)
Notepad++ text editor with Search->Goto (line) menu for fast line editting if asl or iasl compilation fails below

mkdir c:\dsdt
c: & cd \dsdt
set 64bit_OS_asl="C:\Program Files (x86)\Windows Kits\10\Tools\x64\ACPIVerify\asl.exe"
set 32bit_OS_asl="C:\Program Files (x86)\Windows Kits\10\Tools\x86\ACPIVerify\asl.exe"
copy /y %32bit_OS_asl% c:\dsdt > nul & copy /y %64bit_OS_asl% c:\dsdt > nul
if not exist c:\dsdt\asl.exe echo ERROR: Failed to copy asl.exe to c:\dsdt

copy your dsdt-modified.aml to C:\dsdt

Step 2. Load your dsdt-modified.aml as a registry override or in-memory substitution

OPTION 1: Load your dsdt-modified.aml as a registry override with Windows test signing mode enabled

Here we load your dsdt-modified.aml as Windows registry DSDT override. Do note that an invalid dsdt-modified.aml loaded in this way can cause a BSOD on bootup. Furthermore, Windows test signing mode can be problematic for app compatibility. Both these issues can be avoided by using OPTION 2: Avoid test signing mode - load your dsdt-modified.aml as an in memory DSDT substitution.

i. At Command Prompt (admin) type the following. WDK containing asl.exe must be installed per Step 1 (i) and (ii) for this to work.

c: & cd \dsdt
asl /loadtable dsdt-modified.aml

ii. Enable TESTSIGNING mode for the registry override to apply. At the Command Prompt (admin) type:

bcdedit -set TESTSIGNING ON

If get an error like below when do this, then disable SECURE BOOT in your BIOS.

An error has occurred setting the element data

The value is protected by Secure Boot policy and cannot be modified or deleted

iii. Reboot your system and check for 'large memory' in step 3.

Reply

Answer 5

Oct 28, 2019 1:02 PM in response to TGIK

Get Ready Set and Go! Tonight at 10:00pm EST, Valor (Script) goes live! https://www.youtube.com/watch?v=gLiz8Soxiig&feature=youtu.be @ http://howeitworks.com/valor

Valor: A Frankin-Mac Project

DSDT Patch to Enable Audio Drivers in EFI Installed Version of Windows 10, Blue Screen Of Death Fix, and more.

ALL THANKS GOES TO TGIK AND itayemi's METHODS! TGIK IS DA MAN! TGIK APPLE FOURM: https://discussions.apple.com/thread/250137979 AND itayemi's Windows Method (This without the script or drivers) (How to do this manually):http://www.itayemi.com/blog/2019/09/12/dual-booting-mac-osx-and-windows-on-macbookpro/ -THANKS AGAIN itayemi!

TGIK provided the full Mac/Clover bootloader version of creating a executing the DSDT patch, and gave a solution to the issue, itayemi provided a Windows alternative of creating and executing the DSDT patch. I'm the guy who took the two and made a script for Windows and added other needed and useful tools that is needed to make Windows 10 ver 1903 and higher to be compatible. This is the safest way without mistakenly bricking your Macbook and ruining your firmware. This is only targeted to MacBook Pro Early 2011 "13" inch models aka MacBookPro8,1.

Welcome to Valor!

Thanks for being here and giving this a spin!

1.) This is a script that will install a DSDT file to make your audio drivers work for your MacBook Pro Early 2011 in EFI mode. This is means if you want to install multiple Windows Partitions you can in EFI and you are no longer dependent on the DVD Rom.

2.) BootCamp drivers downloaded and changed as of 10/23/2019. The modifications are MacHaldriver.sys has been completely removed and through this script installs a MacHaldriver.inf instead to avoid Blue Screen Of Death with Windows 10 ver. 1903 or higher because of incompatibility. Untested on Mid 2011 and Late 2011 Macbooks, please provide feedback if there are any issues. This will be automatically executed when using the script.

3.) Legacy Windows essentials programs will be installed to ease user experience transitioning for Windows 7. Ninite will be executed to insure all users are setup with modern day browsers and including the must have tools to maintain this machine. Anti-Virus will be provided and other useful Microsoft programs including Windows Media Center-Port Over from Windows 7.

Please look into the Script Directory and Resources\Installers Directory to look over what will be installed or offered to be installed as you go through the script! Thanks again I hope you enjoy!

Reply

Answer 6

KUTOTULe

Level 1

8 points

Sep 8, 2019 3:19 PM in response to TGIK

Hi TGIK,

I’m one of those “unlucky” people that purchased an old 2011 MBP and wanted to bootcamp Windows 10 on it, and I went through the USB EFI boot installation after turning MBR to GPT and you all know what I’m talking about more than how I do, and I got the same issue as anyone else with that method, which is having no audio coming out of the machine.

I found your method of fixing this mess really mind blowing and I tried to figure out how to do that by myself too, but I’m not so competent and most of the time I wouldn’t have known what I was doing so I decided to do something different.

Actually, as I understood, the problem between MBP hardware and windows 10 was in EFI boot mode, and I focused on that, more precisely looking for some way to “switch” the bootcamp partition booting mode from EFI to legacy / BIOS, and I found a really handy software called Winclone that has a specific tool for that.

After turning the Windows 10 bootcamp partition into Legacy, when I first tried booting it up it crashed, as I was expecting, but I didn’t give up, and still without knowing exactly what I was doing I pressed F2 on startup, just before the windows logo appeared, and it brought me to the Windows Boot Manager. Once there, I could run Windows in Safe Mode so that I could install Cirrus driver etc., and I don’t really know how but when I rebooted it without safe mode it worked perfectly in BIOS mode, and just then I could listen audio from the Apple machine with Windows 10 running.

I don’t know if I’ve been clear enough because, seriously, I’m not experienced in this kind of things, but I think that if I managed to fix it in another way despite of your, this was the best place where to share my story.

And forgive me for my bad English, eventually: I’m Italian, so I’m not even supposed to be in this discussion, but, as I said, I made it, and I made it much easier than what you and a lot of other people in the world did or tried to.

Anyway, I thank you a lot for the help and the inspiration, and if you want you can explain me what I did exactly to make my MBP work from what I told you about my way.

Riccardo

Reply

Answer 7

Mar 12, 2020 4:25 AM in response to TGIK

I did take a look in all this stuff but honestly my mind is trowing division by zero errors all the time. Probably because I don't know exactly how boot works in macOS or Windows beyond the very basics (where is io.sys, config.sys, autoexec.bat, etc), but also because you are telling in short words four years of hard working.

Regular users will need step by step instructions.

As long I had a bad experience with BIOS Windows installation with no sound either and other issues, I will try again, maybe will work this time, who knows? I have a EFI install working good since I don't install bootcamp that results in blue screen all the time, this stuff is quite mysterious...

Reply

Answer 8

TGIK Author

Level 1

23 points

Mar 21, 2019 11:00 AM in response to sdgros01

You need to use a DSDT for your exact computer

use this software to dump your DSDT in OSX : https://sourceforge.net/projects/maciasl/

Then, following the link I posted you have to modify a section in that DSDT--

If you are not going to use clover (which I would advise against unless you are very familiar with how it works) you have to follow the guide to force windows to use that DSDT with a registry edit -

I could walk you through how to get and modify your DSDT --- if you happen to be the southern California area I could work with you in person -

If you are going to use rEFInd you have to use the registry edit method as rEFInd does not have the capability that Clover has to force a DSDT into memory every boot -

reach out to me and I will help you as much as I can

-Cheers

Reply

Answer 9

Apr 15, 2020 8:14 AM in response to TGIK

I followed itayemi's steps and the audio issue is finally fixed on my mbp mid-2012 13 inch!

Thanks for all of your contributions for this to work! xAndrewH1993x itayemi and of course TGIK! I have to give credit to T Loner too though he's not that popular in this thread. It's him who posted around saying that the audio issue is due to the uefi and old macs, that's why I changed my keyword search strategy to find this thread.

I'm so lucky, I didn'thave to wait 4 years to install a windows on my mac, I started trying only a few days ago. Believe me, I'm a noob, all i want is to play AOE on steam. I almost dunno how to use the command, let alone all those in depth code editing.

I studied this post like it's my final disseartation and finally chose to follow itayemi's steps. I was tempted to use valor but since my mbp is mid-2012, it doesn't guranteed success. Here's what I did,

tried bootcamp installer, of course it's designed to fail.
did a little resaerch and made my own bootdisk, but windows didn't allow fat32/exfat as partition(a file is too big).
Then I came across a magical video, I was about to give a dislike, but then, wait a second, something new!? https://www.youtube.com/watch?v=Ez46RNTR2Ws, all it says is, to partition the windows portion into mac journaled, then delete and press next when installing windows. Worked!
Audio issues, searhc everything that would come to one's mind, and saw T Loner's comments on those posts
Came across this post and edited my dsdt(whatever that is).

Reply

Answer 10

Feb 13, 2019 8:46 PM in response to TGIK

You are my hero. I've actually done this exact DSDT mod before, but never thought about trying it to fix the sound issue on my 2011 iMac. It worked perfect.

Reply

Answer 11

Nov 11, 2019 5:41 AM in response to TGIK

I confirm this works with 2011 iMac sound issues when installing windows 10 x64 in UEFI mode. Pretty straight forward, follow the guide in the link.

Reply

Answer 12

TGIK Author

Level 1

23 points

May 11, 2019 7:41 PM in response to dw1985

I would suggest using the registry mod method -- if you have a good rEFInd setup that you spent time customizing there is little point in moving over to Clover -

To answer your questions though->

I cannot confirm that there are no issues when using Clover installed directly to an EFI partition -- I have never had issues, and the people who have claimed that Clover 'bricked' their Macs I am suspect of--- despite that, I would only endorse the Clover method if you are familiar with how it functions.

**NOTE**

You also don't have to install Clover to the EFI partition, on another 2011 MBP I have a small HFS+ partition where clover is installed where I blessed the volume to have it show up in the boot menu selector --

2) Yes, Clover can be customized to only show what drives you want visible

But again, if you have a good rEFInd setup-- use that, do the registry-mod.

****NOTE*****

I have been doing tests on whether this 'hack' disables thunderbolt --- still figuring that out -- just wanted to point out caveats

-Cheers

Reply

Answer 13

medham

Level 1

4 points

Jan 2, 2021 5:09 PM in response to pcwiztech

If you use Refind, this method worked for my MBP 2012 with refind.

https://youtu.be/LbmLVOUpVOA

Reply

Answer 14

Jan 26, 2020 11:45 AM in response to Spirit_TY

One other piece of advice do not install the drivers from the boot camp assistant tool do not download the drivers from Apple use the drivers that are inside of Valor which has been manipulated to work with the current version of Windows 10 build 1909.... The reason why I say this is because a while back whenever I was developing Valor Microsoft had release 1903 prior and I finally had updated to that build and realize that my project was broken and it was because of Apple not updating their certificates on the drivers making them compatible with Windows 10. they're only doing it for the newer edition of MacBooks that support Windows 10. See my model was only supported to Windows 7. But try it out if it doesn't work restore and then install your drivers and if you notice a blue screen then you have a driver problem.

Reply

Answer 15

Jan 30, 2020 10:27 PM in response to Spirit_TY

Hi xAndrewH1993x.

So, here's my feedback. Valor, as it is presently, does not work for my MBP Mid 2012. Here's what I tried:

I uninstalled my older version of windows, formatted the partition and installed Win 10 x64 build 1909 in EFI mode.
I did not download Bootcamp support softwares from Apple.
I mounted the Valor (or Valor lite) from the iso and ran the valor script from there (this was done 5 times).
I did not restart at any time until I ran the last tool which eventually restarted the computer.

I used both Valor and Valor lite just in case one would work for me. I also did this 5 times just to see if I missed any step at all. The 5th time was when I now created a restore point so I don't have to keep re-installing windows when next I try.

I suspect the reason might be in the DSDT file that you used in your script. The DSDT for 2011 might be different for 2012, just thinking out loud here.

Any help please. Thank you.

PS: I can afford to keep formatting the partition because it is a fairly new install so I am fine with formatting it without losing any doc.

Reply