MBP UEFI WINDOWS SOUND FIXED!!!!

So you made a patched dsdt (or one was made for you)?

You created a c:\dsdt folder?

you downloaded

• 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)

extracted the first (WBT) to this newly created c:\dsdt folder?

ran the second installer?

ran this command

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

and this command

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

and this command

bcdedit -set TESTSIGNING ON

and it still is not booting in 'test mode' ?

-let me know

Cheers

Simple perhaps...but you are asking him to open the chassis twice, disconnect delicate flat cabling etc....it is all good brother, it was a playful tease ----- personally since I don't use thunderbolt on the windows side, have no use for a second monitor (I have plenty of desktops)-- I believe the EFI method just makes for a faster, more elegant machine-- even in shallow ways; the native GOP boot screen graphics look better then the VESA modes of BIOS emulation. Both methods have caveats — and besides my boot loader screen looks way more interesting then you ever could do with BIOS emulation where even if it is a linux disk you have the boring hard disk icon and the title of ‘WINDOWS’ 

the fruit salad loader

In response to why I would do all this work - my answer is embedded in your response -

1) Bios emulation sucks, yes you can patch the MBR to activate AHCI mode but.....that sucks --so do hybrid GPT/MBR schemes (it's a 'bad' work around)

2) It is precisely because Apple doesn't support it that it becomes that more compelling --- I knew it was possible - I hated the 'knee-jerk' response of 'just use bootcamp' etc

Apple can be, and certainly has been a great (slight tongue-in-cheek) company -- but their tendency to obscure the truth about their products and the deep veil of restrictions they put on things again, makes it fun and compelling to 'stick it to them'

So glad to help !!!!! Was really happy -- I even am able to install Windows 7 UEFI mode by DISM'ing an image from windows 10 and disabling vesa during boot (basically it's a blind boot) ---

Cheers,

Derek Trueblood Riddle

Cheers,

I do actually have FreeBSD 12 on there :) , used to have OpenBSD ---Maybe if eCOMSTATION ever supports UEFI I could try it----Using only UEFI installs It's fun to use Mac's built in boot menu (was an early rEFIt and rEFInd user) by making small HFS+ partitions with a SYSTEM/LIBRARY/CORESERVICES structure to put efi bootloaders directly or a symlink to the ESP and make a .VolumeIcon.icns image of my choice----- Never intended to be so flippant in my responses I just am always trying to figure out how to do things that are not documented but perfectly safe using my background in IT -

You are probably right; most users should follow the well documented protocol--But there once was a time when Apple attracted the 'power user tinkerer' and I come from that legacy - so as much as I can appreciate the 'appliance-like, don't need to understand nature' of Apple computers.....it is after all (after the switch to intel) an x86 x64 computer--

-Derek Trueblood Riddle

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

You can do this without using Clover and use the registry hack detailed in the post ---I alluded to the potential dangers of using Clover in my original post but for me personally, I have never had a problem using Clover on a 'real Mac.' From my perspective it seems that is usually 'operator error' when people have 'bricked' their macs using Clover.

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