Mazafromavignon

Q: No audio : Windows 10 Bootcamp

Hi everybody. I begin to apologise because I'm french and my english is not perfect.

 

So, you are, the apple community, my last chance.

 

First of all : I give you my set up, that will be usefull.

Config : Macbook pro late 2011

Upgrade with SSD 850 evo

So I have 1 HD and 1 SSD.

 

I recently instaled Windows 10 with Bootcamp on the Hard Disk. Everything works well, but I don't have audio.

I had installed the latest Bootcamp (Drivers) on Windows 10. But at this point I had no audio.

 

I saw on "device manager" that the "Hight Definition audio codec" is installed, but badly. I can see a Yellow exclamation mark and an error in the property (Code 10).

 

Then, I tried to uninstall this Driver (directly in the device Manager), to install it better. But nothing looks work.

I had also tried to download directly the latest driver on the Realtek Website.

 

I have more information for you : If I plug a jack I have the same issue.

In the Mac partition : The latest OS Yosemite is installed

When I installed W10, it was on an empty partition, with a boutable USB drive.

I tried the latest Bootcamp and also 5.1.5626

 

I really hope that you'll can help me.

Thank You

MacBook Pro, Other OS, Windows 10

Posted on Aug 4, 2015 8:55 PM

Close

Q: No audio : Windows 10 Bootcamp

  • All replies
  • Helpful answers

first Previous Page 4 of 4
  • by Eric Landry,

    Eric Landry Eric Landry Aug 26, 2015 8:28 PM in response to Loner T
    Level 1 (10 points)
    Aug 26, 2015 8:28 PM in response to Loner T

    Loner T, nice explanation!

     

    For Diralban and Mazafromavigon, my post is in the 1st page of the thread and basically what is says is: I install Windows 7 which installs in "bios" mode, I install bootcamp  then I upgrade it to Windows 10 and repair the bootcamp install.

     

    You can't install Windows 10 from scratch in bios mode but you can upgrade a Windows 7 to Windows 10 and the sound will work, it works for me... you just need a Windows 7 license!

     

    Eric

  • by TGIK,

    TGIK TGIK Mar 9, 2016 10:58 PM in response to Loner T
    Level 1 (4 points)
    Mar 9, 2016 10:58 PM in response to Loner T

    It seems it is really a combination of Apple's EFI implementation coupled with how Windows "sees" system devices during EFI boot  since Linux and FreeBSD initialize the PCI audio bridge fine in EFI on older macs (e.g. 2011 MacBook Pro). That's why it is frustrating and also why it seems it is something that 'could' be fixed.



  • by Andrii_UA,

    Andrii_UA Andrii_UA Aug 16, 2016 1:58 AM in response to Mazafromavignon
    Level 1 (8 points)
    Aug 16, 2016 1:58 AM in response to Mazafromavignon

    Ok, I understand I may be a bit late to the party, but I had just solved the audio problem with Windows 10. Now I am writing this under my Windows 10 account, while listening to Aristocrats Radio =)

     

    I have a MacBook Pro 13" (mid-2012), 500 GB SSD and 16 GB RAM.

     

    This issue boils down to a poor EFI support on older MacBooks. Boot Camp assumes it can do just fine with this, when creating a USB installer and partitioning the hard drive. However, EFI boot mode exposes devices in a different way, which effectively leads to audio not working.

     

    Basically, the solution is to use a legacy MBR boot mode, when installing Windows. However, due to Boot Camp's tricky partitioning of a hard drive, legacy mode will not allow Windows installation to that partition (the infamous message "Windows cannot be installed. The selected disk is of GPT partition style" etc.).

     

    To install Windows 10 without any of these problems, I did the following:

    0. Saved the latest Windows drivers to a USB stick via Boot Camp.

    1. Burned a Win10 ISO image to a DVD.

    2. Merged a Boot Camp-created partition back to a single MacOS partition (did that via Boot Camp).

    3. Created a new partition for Windows 10 in a Disk Utility (I assigned 100 GB, formatted to FAT).

    4. Re-formatted this new partition to NTFS, using a third-party software. I used Tuxera NTFS for Mac (http://www.tuxera.com/products/tuxera-ntfs-for-mac/). It has a 15-day free trial.

    5. Put my fresh Win10 DVD to an optical drive and rebooted, while holding Option key (alt).

    6. In a boot options screen, I selected DVD "Windows" (Do not choose EFI boot.). Windows installation started.

    7. In a Windows Installer Disk selector screen, I chose to install Windows to that NTFS partition created earlier.

     

    It all went smoothly afterwards. Windows reboots a few times during installation process, as usual. In these cases please hold Option key during reboot, and then select to boot from hard drive "Windows".

     

    After Windows is installed, do not forget to install latest Windows drivers from your USB stick.

     

    NB: Before all that, I also played a bit with marking my MBR partition from hybrid to protected (see here: http://fgimian.github.io/blog/2016/03/12/installing-windows-10-on-a-mac-without- bootcamp/). However, I am not sure this actually was important in my case.

  • by Walking Teddy,

    Walking Teddy Walking Teddy Aug 21, 2016 2:56 AM in response to Andrii_UA
    Level 1 (12 points)
    Desktops
    Aug 21, 2016 2:56 AM in response to Andrii_UA

    Great job. I have the exact same model of your mac, and so I have the audio problem on windows 10. But this is the thing. I need another partition for my data, so I made another partition after installing windows. If I made a partition in the first place, windows wouldn't be installed at all(Like GPT disk error.) So you have only windows and mac os partition, or more?

    Thank you.

  • by Andrii_UA,

    Andrii_UA Andrii_UA Aug 21, 2016 5:46 AM in response to Walking Teddy
    Level 1 (8 points)
    Aug 21, 2016 5:46 AM in response to Walking Teddy

    I have two partitions, one for OSX and one for Win10. I am no expert here, but I guess you can keep your partition structure. I would just make sure Windows partition is NTFS-formatted before reinstalling Windows, to avoid that nasty GPT error. Good luck.

first Previous Page 4 of 4