Looks like no one’s replied in a while. To start the conversation again, simply ask a new 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

305 replies

Oct 25, 2019 7:15 AM in response to xAndrewH1993x

Hiya

I've successfully done this mod to get audio on my mid 2011 iMac. I would be interested in a automated process script or a video if one is available though. Didnt mind going through the process to do the mod, but i've created a backup of my windows installation so I don't have to in future. But would still be handy to have a script for all or part of the process. Many thanks.

Oct 25, 2019 9:21 AM in response to Markgreatrex

Hey Markgreatrex,

The best news at the moment is that script is almost done! The script is geared to to early 2011 MacBook Pros, I have no way of testing the script without being other models. Currently I'm stuck to where I can't get past two command lines to fully finish the project. Bcdedit /set testsigning on and asl.exe /loadtable dsdt.aml will not run correctly in .cmds or .bats, without opening cmd as admin and put it these commands to work.

Oct 26, 2019 5:59 AM in response to xAndrewH1993x

So far so good, now I'm trying to get past being stuck only on the asl.exe /loadtable DSDT.aml - The command works manually but trying to automate this has been a challenge. I'm trying to make a .bat file or .cmd file to run this correctly but no luck. I'm literally 99.9% percent done. Once I can get past this, this will be uploaded on github, alternative.to, howeitworks.com, and google drive. I'll post all links once done. ANY HELP IS APPRECIATED!

Oct 27, 2019 4:23 AM in response to xAndrewH1993x

I wish I could help out, but it's beyond my skillset. If there's anything else I might be able to help with it even to give a second opinion, my emai is markheiron@yahoo.co.uk. I'm currently trying to write up the documentation for setting up my mac, there were a few things I had to fix at installation and it's hard to remember it all. I'm just really glad to have got the sound working on my mac without having to run through bootcamp. Wish I had done it years ago. I will keep an eye out for the links though. Thanks again for your work!

Oct 27, 2019 7:46 AM in response to Markgreatrex

Its all good, I figured it out, I'm going to be in testing stage tonight, Trying different version of Windows, different usernames to make sure Valor (The Script's Name) holds up. I've added BSOD fix, free cloud anti-virus that doesn't run in the background, other IT tools to keep track of the Mac's health. I've added some personal touches to express why this project is made and I've merged the old drivers and the new drivers together to make the bootcamp software work. This is going to be live hopefully in the next day or two.

Nov 28, 2019 7:33 PM in response to TGIK

We all should be saying thank you to you! You are awesome and without your methods there would be no patch! There would be no script and most of all there would be no community to aid your cause. So THANK YOU sincerely for your efforts and sticking with this before any of us came along. I had given up back in 2017 on the UEFI audio issues until I accidentally stumbled across your forum. Happy thanksgiving or happy holiday to you my friend, please let me know if there is anything else I can do to help. You have my email hmu anytime.

TGIK Author

Level 1

23 points

Dec 3, 2019 2:07 PM in response to AMcomputers

I think Andrew will be able to help you -- he is making the process a lot easier - though the steps outlined throughout this forum post are not that difficult -- it really is just cutting/copying and pasting....I also put my email on here in case people wanted me to edit their DSDT for them (though I am literally just copying and pasting 1 section) --

If you already have Windows installed in UEFI mode you a literally seven minutes from getting it to work with sound -- (though don't count on thunderbolt functionality as of right now)

let us know how to help

Dec 5, 2019 5:48 AM in response to AMcomputers

Hello AMcomputers I see that you are having an issue, good news I have a script called Valor that can automatically patch your audio issues and get your drivers working. Please check out http://www.howeitworks.com/valor and its tutorial videos to learn how to install and deploy the script. If you get stuck please let me know, I just released an update on Thanksgiving. Remember Valor Lite is pretty much the script so use this if you want just the patch, if you want more exclusive content use Valor AIO. I apologize for the late response I've been sick as a dog, I'll get back to you as soon as I can, I start back to work tomorrow working 11 hour shifts until this coming Monday.

Dec 10, 2019 1:43 PM in response to KyuR_pt

Hello KyuR_pt, please look at www.howeitworks.com/valor to see methods and videos both from TGIK and itayemi. Download Valor Lite to access content if not Valor AIO use zip or iso downloads. Tutorial videos, written text files for breakdown is in archives of Valor. Tutorial videos for Valor are on my website.

Dec 11, 2019 12:52 PM in response to KyuR_pt

Yes actually use the .iso instead so that windows will mount it and then click on Valor_Lite_Start and it will copy over the directories exactly the way it needs to be. If the folder and sub folders are not setup right the script won't work. So use the iso file and double click to mount it and then you will see it under "This PC" until ejected or when you reboot your computer.

Dec 23, 2019 5:28 PM in response to TGIK

I'm on a 2012 MBP and already have an external drive UEFI Windows 10 boot largely working, except for built in sound over headphones and speakers. (External sound over HDMI works great with the NVIDIA drivers.) I'm not sure how I originally set this up (it's been a while) but I'm pretty sure I didn't use Clover. I've got a partition with an EFI folder on it, and I'll try the registry mod method, but it sounds like there are potential performance issues. In reading through the linked guides, I've come across the automate-eGPU EFI method, but can't find a standalone installer whose version matches that in the article. The old one (1.0.4) fails on install asking me to upgrade to High Sierra...but I'm on Mojave. The terminal string provided in the 1.0.5 instructions doesn't work. I tried manually copying the EFI folder onto my EFI volume and I get to a bootloader, but it doesn't seem to actually work to boot Windows. Any guidance you can provide is greatly appreciated (and not in the slightest bit time critical, this is a hobby machine.)

Dec 27, 2019 5:06 PM in response to Misha Syeed

This is what I use, it works for Windows EFI and Windows Legacy.... Hopefully this works for ya. I want to do a stand alone video but I need hardware to pull it off and I just don't have the resources to do so.... I'm sorry for the late response, I work for Amazon currently and OMG 10-12 hour shifts with Mandatory Over Time has been kicking my rear end. https://www.rodsbooks.com/refind/installing.html if need more info let me know I'll try to get back to you as soon as I can!

Dec 31, 2019 5:56 AM in response to Misha Syeed

Hey my pleasure I'm glad it worked out! The big thanks goes to TGIK and itayemi because the project would have never happened if they never came out with there methods, all I did was script it together and did some mods. I appreciate it though! Happy New Years!

Jan 26, 2020 8:33 AM in response to TGIK

We're now in 2020 and I still need help with this. (~_*). Happy New Year guys.

I would have downloaded xAndrewH1993x's patch, but he constantly reminds us that his patch is for MBP 2011 and I fear "bricking" my machine.

My machine is a Mid 2012 MBP. I have installed EFI windows and I have been without sound. I was reading till the end of the thread to see if TGIK's video was linked somewhere. Seems he dumped it eventually once xAndrewH1993x finalized his process. I also tried itayemi's link but the link is now broken.

I'll appreciate any help I can get. I'm a noob at this but surely love to experiment. I'm open to a zoom walkthrough or to an upgrade in xAndrewH1993x's patch that will accommodate Mid 2012 MBP, or to a step by step from any of your geniuses in the house.

Thanks in advance.

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

Hey Spirit hope you're doing well so I just so happened to see your post in my email and I'm going to clear some things up. See everything is in Valor so itayemi methods is literally copied and pasted into a text file that is located within the patch so you just have to look for it in the file once you download Valor. Next thing I want to make it clear to everyone that there is no way to possiblely brick your MacBook using Valor. The only way you're going to break/brick your MacBook is if you're installing and manipulating the bootloader itself and even then that's pretty much like heavy stuff. All you need to do is just run Valor and if it doesn't work then reinstall Windows. This is supporting the latest Windows 10 ISO release from Microsoft. Please if you have any other questions fill free to reach out to me directly if you have questions about valor's compatibility. I have made it clear that if somebody is using Valor on Windows that is not meant for the 2011 MacBook pro they can risk breaking Windows itself causing you to have a blue screen so make sure you do a system restore point and try it and if it fails... restore from the last system restore point through windows recovery and if that doesn't reinstall Windows 10. Restore point help link: https://www.windowscentral.com/how-use-system-restore-windows-10 I put a disclaimer on my website and on forums to protect myself. However after multi users testing I've seen compatibility on 2012s.

MBP UEFI WINDOWS SOUND FIXED!!!!